section
stringclasses 4
values | filename
stringlengths 6
32
| text
stringlengths 104
10.3M
| lang
stringclasses 44
values |
|---|---|---|---|
converted_docs | 275389 | **AC21 Members at the time of approval of the two Consensus Reports**
- **Patricia Layton, Clemson University (Chair)**
```{=html}
<!-- -->
```
- **Daryl Buss, University of Wisconsin Veterinary School**
- **Leon Corzine, Farmer**
- **Carole Cramer, Virginia Tech**
- **Dick Crowder, American Seed Trade Association**
- **Michael Dykes, Monsanto**
- **Juan Enriquez-Cabot, Biotechonomy**
- **Randal Giroux, Cargill**
- **Duane Grant, Farmer**
```{=html}
<!-- -->
```
- **David Hoisington, CIMMYT**
- **Gregory Jaffe, Center for Science in the Public Interest**
- **Carol Tucker Foreman, Consumer Federation of America**
- **Terry Medley, DuPont**
```{=html}
<!-- -->
```
- **Margaret Mellon, Union of Concerned Scientists**
- **Ronald Olson, General Mills**
- **Jerome Slocum, Farmer and Grain Elevator Operator**
- **Keith Triebwasser, Procter and Gamble**
- **Lisa Zannoni, BASF**
| en |
converted_docs | 547550 | **Long Island Rail Road East Side Access**
**New York, New York**
(November 2006)
# Description
The Metropolitan Transportation Authority's (MTA) Long Island Rail Road
(LIRR) is constructing a new direct 3.5-mile commuter rail extension
from LIRR's Main and Port Washington Branch Lines in Long Island and
Queens, to Grand Central Terminal (GCT) on Manhattan's East Side. The
project includes the construction new tunnels beneath Sunnyside Yard
connecting to the currently unused lower level of the 63^rd^ Street
Tunnel beneath the East River. In Manhattan, the project will continue
west beneath 63^rd^ Street and toward Park Avenue under the Lexington
Avenue subway, turning south beneath the existing MTA-Metro North
Railroad tracks under Park Avenue to a new LIRR passenger concourse in
the lower level of GCT. At GCT, the project will provide new tracks,
platforms, entrances, waiting areas, ticket windows, and other services.
The current highway system and East River crossings (bridges and
tunnels) to Manhattan from Nassau/Suffolk (and parts of eastern Queens)
are at capacity and subject to severe congestion and long delays.
Expansion of the highway network is not feasible due to lack of
available rights-of-way, high costs, and potentially adverse
environmental impacts in a "severe" non-attainment area for ozone. The
LIRR operates at capacity in this area with peak service of 37 trains
per hour into its only Manhattan terminal at Penn Station. Nearly half
of LIRR's 106,000 existing daily riders have destinations on Manhattan's
East Side, and currently spend approximately 20 minutes "doubling back"
from Penn Station on the island's West Side. Without the project, future
LIRR trains to Penn Station will be severely congested, and are
projected to operate at 27 percent over their passenger-carrying
capacity. This level of crowding and discomfort would discourage or
prevent new riders from using the LIRR to reach Manhattan. By
redirecting trains to GCT, this congestion would be relieved and added
capacity for Amtrak and New Jersey Transit service would be created at
Penn Station.
The total project cost under the Full Funding Grant Agreement (FFGA) is
\$7,386.00 million. The Section 5309 New Starts funding share is
\$2,632.10 million.
# Status
# MTA completed a major investment study for the project corridor in April 1998. FTA approved MTA's request to advance the project into preliminary engineering in September 1998. A Draft Environmental Impact Statement (EIS) was completed in May 2000; a Final EIS was completed in March 2001; and an environmental Record of Decision was issued by FTA in May 2001. Under a Letter of No Prejudice (LONP) authority MTA began construction in late 2001. The LONP authority approved was \$1,080.04 million, which was liquidated upon FFGA execution. FTA approved the project into final design in February 2002. FTA issued a supplemental environmental Finding of No Significant Impact in July 2006, due to the redesign of a vent facility at 50^th^ Street. MTA and FTA entered into an FFGA in December 2006, with revenue operations scheduled for December 2013.
SAFETEA-LU Section 3043(b)(20) authorized the LIRR East Side Access
project for final design and construction. Through FY 2006, Congress
has appropriated \$587.77 million in Section 5309 New Starts funds for
the project.
+----------------------------+--------------+-------------------------+
| # **Reported | | |
| Reported in Year of Expend | | |
| iture Dollarsxpenditure** | | |
| {#reportedreported-in-yea | | |
| r-of-expenditure-dollarsxp | | |
| enditure .Table-Heading-1} | | |
+----------------------------+--------------+-------------------------+
| **[Source of | **Total | **[Appropriations to |
| Funds]{.underline}** | Funding | Date]{.underline}** |
| | [ | |
| | (million)]{. | |
| | underline}** | |
+----------------------------+--------------+-------------------------+
| **Federal:** | \$2,632.11 | \$587.77 million |
| | | appropriated through |
| Section 5309 New Starts | \$11.20 | FY 2006 |
| | | |
| FFGA Commitment | \$22.98 | |
| | | |
| Flexible Funds (CMAQ) | \$16.26 | |
| | | |
| Section 5309 Fixed | | |
| Guideway | | |
| | | |
| Modernization Funds | | |
| | | |
| Section 5307 Urbanized | | |
| Area | | |
| | | |
| Formula Funds | | |
+----------------------------+--------------+-------------------------+
| **State:** | \$450.00 | []{.mark} |
| | | |
| State Transportation Bond | []{.mark} | |
| | | |
| Act of 2005 | | |
+----------------------------+--------------+-------------------------+
| **Local:** | []{.mark} | []{.mark} |
| | | |
| MTA Dedicated Sources | \$3,217.35 | |
| (bonds, surplus toll | | |
| revenues, etc.) | \$1,036.10 | |
| | | |
| MTA Operating Budget | | |
+----------------------------+--------------+-------------------------+
| **TOTAL** | ** | []{.mark} |
| | \$7,386.00** | |
+----------------------------+--------------+-------------------------+
| **NOTE:** The sum of the | | |
| figures may differ from | | |
| the total as listed due to | | |
| rounding. | | |
+----------------------------+--------------+-------------------------+
MAP
| en |
all-txt-docs | 830424 |
000
ASUS65 KTWC 100038
RTPTWC
REGIONAL TEMPERATURE AND PRECIPITATION SUMMARY
NATIONAL WEATHER SERVICE TUCSON AZ
538 PM MST TUE SEP 9 2008
TODAYS HIGH AND OVERNIGHT LOW TEMPERATURES AS OF 5 PM TODAY.
24 HOUR PRECIPITATION AND SNOWFALL ENDING AT 5 PM TODAY.
* DENOTES 24 HOUR HIGH AND LOW TEMPERATURE ENDING AT 5 PM TODAY.
M DENOTES MISSING.
T DENOTES TRACE OF PRECIPITATION.
.B TUS 0909 MS DH17/TN/TX/PP/SF/SD
: NEW SNOW
:ID STATION ELEV LOW HIGH PRECIP SNOW DEPTH
: ARIZONA
: PIMA COUNTY
DMA :DAVIS-MONTHAN AFB 2675: 73 / 94 / 0.00 / / /
ORGA3 :ORGAN PIPE CACTUS * 1678: 72 / 96 / 0.00 / / /
SDMA3 :SONORA DESERT MUSEUM 2768: 69 / 96 / 0.00 / / /
TUS :TUCSON INTL APT 2550: 70 / 97 / 0.00 / / /
SKIA3 :MT LEMMON-SMRHAVEN * 8210: M / M / M / / /
: COCHISE COUNTY
BISA3 :BISBEE * 5560: 55 / 81 / 0.28 / / /
BOWA3 :BOWIE * 3810: M / M / M / / /
HRFA3 :CORONADO N. M. * 5242: 56 / 83 / 0.00 / / /
DUGA3 :DOUGLAS * 4040: 62 / 91 / 0.00 / / /
DUG :BISBEE-DOUGLAS APT 4100: 62 / 91 / 0.01 / / /
SEVA3 :SIERRA VISTA * 4600: 62 / 88 / 0.00 / / /
: PINAL COUNTY
ORAA3 :ORACLE * 4510: M / M / M / / /
PICA3 :PICACHO PEAK * 1830: 71 / 100 / 0.00 / / /
: SANTA CRUZ COUNTY
ADRA3 :ELGIN 4858: 57 / 86 / 0.00 / / /
OLS :NOGALES INTL APT 3930: 63 / 90 / 0.00 / / /
: GRAHAM COUNTY
SAFA3 :SAFFORD AG STATION * 2955: 67 / 89 / 0.09 / / /
SAD :SAFFORD AIRPORT 3170: 75 / 90 / 0.02 / / /
.END
| en |
markdown | 664577 | # Presentation: 664577
**BUCKLEY**
**SUNDANCE**
**FT. PECK**
**PEACE CANYON**
**MICA**
**VANCOUVER**
**SEATTLE**
**PRINCE RUPERT**
**AREA**
**AREA**
**COLSTRIP**
**BOISE**
**PORTLAND**
**AREA**
**MALIN**
**TABLE MTN**
**ROUND MTN**
**SALT LAKE**
**CITY AREA**
**MEXICO**
**EL PASO**
**AREA**
**DEVERS**
**LUGO**
**SAN FRANCISCO**
**MIDPOINT**
**AREA**
**LOS ANGELES**
**AREA**
**ALBUQUERQUE**
**AREA**
**NAVAJO**
**DENVER**
**AREA**
**MOJAVE**
**HOOVER**
**PHOENIX**
**AREA**
**LANGDON**
**HOT SPRINGS**
**HELLS**
**CANYON**
**CHIEF JOSEPH**
**BURNS**
**PINTO**
**FOUR**
**CORNERS**
**SHASTA**
**LANGDON**
**CANADA**
**UNITED STATES**
**66**
**65**
**14**
**8**
**30**
**27**
**15**
**49**
**31**
**6**
**19**
**22**
_**Predominate Dir**_
**3 Sp – S to N**
** ****Su – N to S**
**14 All Seasons - E to W**
**15 All Seasons – N to S**
**16 Su – SW to NE**
** ****Sp – NE to SW**
**18 Sp – S to N**
** ****W – balanced**
**20 W – **
** ****Sp – balanced**
**23 All – 345 to 500**
**24 All Seasons – W to E**
**26 W – balanced**
** ****Sp – S to N**
** ****Su – S to N**
**32 All Seasons – **
**34 Su – N to S**
** ****W – S to N**
**45 All – balanced**
**65 Su – balanced**
** ****Sp – N to S**
** ****W – S to N**
**34**
**47**
**16**
**3**
**35**
**18**
**5**
**4**
**6**
**17**
**20**
**23**
**24**
**26**
**32**
**36**
**45**
**46**
**50**
**51**
**48**
**48**
**Uni-directional Flow Paths**
**Bi-directional Flow Paths (see notes above right, for predominate seasonal flow directions)**
**BUCKLEY**
**SUNDANCE**
**FT. PECK**
**PEACE CANYON**
**MICA**
**VANCOUVER**
**SEATTLE**
**PRINCE RUPERT**
**AREA**
**AREA**
**COLSTRIP**
**BOISE**
**PORTLAND**
**AREA**
**MALIN**
**TABLE MTN**
**ROUND MTN**
**SALT LAKE**
**CITY AREA**
**MEXICO**
**EL PASO**
**AREA**
**DEVERS**
**LUGO**
**SAN FRANCISCO**
**MIDPOINT**
**AREA**
**LOS ANGELES**
**AREA**
**ALBUQUERQUE**
**AREA**
**NAVAJO**
**DENVER**
**AREA**
**MOJAVE**
**HOOVER**
**PHOENIX**
**AREA**
**LANGDON**
**HOT SPRINGS**
**HELLS**
**CANYON**
**CHIEF JOSEPH**
**BURNS**
**PINTO**
**FOUR**
**CORNERS**
**SHASTA**
**LANGDON**
**CANADA**
**UNITED STATES**
**66**
**65**
**14**
**8**
**30**
**27**
**15**
**49**
**31**
**6**
**19**
**22**
**34**
**47**
**16**
**3**
**35**
**18**
**5**
**4**
**6**
**17**
**20**
**23**
**24**
**26**
**32**
**36**
**45**
**46**
**50**
**51**
**48**
**48**
_**Winter 2001-02**_
**Actual Flow > 75% of OTC greater than 50% of time**
**Actual Flow > 75% of OTC between 25% and 50 % of time**
**Actual Flow > 75% of OTC between 0% and 25% of time**
**BUCKLEY**
**SUNDANCE**
**FT. PECK**
**PEACE CANYON**
**MICA**
**VANCOUVER**
**SEATTLE**
**PRINCE RUPERT**
**AREA**
**AREA**
**COLSTRIP**
**BOISE**
**PORTLAND**
**AREA**
**MALIN**
**TABLE MTN**
**ROUND MTN**
**SALT LAKE**
**CITY AREA**
**MEXICO**
**EL PASO**
**AREA**
**DEVERS**
**LUGO**
**SAN FRANCISCO**
**MIDPOINT**
**AREA**
**LOS ANGELES**
**AREA**
**ALBUQUERQUE**
**AREA**
**NAVAJO**
**DENVER**
**AREA**
**MOJAVE**
**HOOVER**
**PHOENIX**
**AREA**
**LANGDON**
**HOT SPRINGS**
**HELLS**
**CANYON**
**CHIEF JOSEPH**
**BURNS**
**PINTO**
**FOUR**
**CORNERS**
**SHASTA**
**LANGDON**
**CANADA**
**UNITED STATES**
**66**
**65**
**14**
**8**
**30**
**27**
**15**
**49**
**31**
**6**
**19**
**22**
**34**
**47**
**16**
**3**
**35**
**18**
**5**
**4**
**6**
**17**
**20**
**23**
**24**
**26**
**32**
**36**
**45**
**46**
**50**
**51**
**48**
**48**
_**Winter 98-99 thru 01-02 (Based on Heaviest Loading Year)**_
**Actual Flow > 75% of OTC greater than 50% of time**
**Actual Flow > 75% of OTC between 25% and 50 % of time**
**Actual Flow > 75% of OTC between 0% and 25% of time**
**BUCKLEY**
**SUNDANCE**
**FT. PECK**
**PEACE CANYON**
**MICA**
**VANCOUVER**
**SEATTLE**
**PRINCE RUPERT**
**AREA**
**AREA**
**COLSTRIP**
**BOISE**
**PORTLAND**
**AREA**
**MALIN**
**TABLE MTN**
**ROUND MTN**
**SALT LAKE**
**CITY AREA**
**MEXICO**
**EL PASO**
**AREA**
**DEVERS**
**LUGO**
**SAN FRANCISCO**
**MIDPOINT**
**AREA**
**LOS ANGELES**
**AREA**
**ALBUQUERQUE**
**AREA**
**NAVAJO**
**DENVER**
**AREA**
**MOJAVE**
**HOOVER**
**PHOENIX**
**AREA**
**LANGDON**
**HOT SPRINGS**
**HELLS**
**CANYON**
**CHIEF JOSEPH**
**BURNS**
**PINTO**
**FOUR**
**CORNERS**
**SHASTA**
**LANGDON**
**CANADA**
**UNITED STATES**
**66**
**65**
**14**
**8**
**30**
**27**
**15**
**49**
**31**
**6**
**19**
**22**
**34**
**47**
**16**
**3**
**35**
**18**
**5**
**4**
**6**
**17**
**20**
**23**
**24**
**26**
**32**
**36**
**45**
**46**
**50**
**51**
**48**
**48**
_**Spring 02**_
**Actual Flow > 75% of OTC greater than 50% of time**
**Actual Flow > 75% of OTC between 25% and 50 % of time**
**Actual Flow > 75% of OTC between 0% and 25% of time**
**BUCKLEY**
**SUNDANCE**
**FT. PECK**
**PEACE CANYON**
**MICA**
**VANCOUVER**
**SEATTLE**
**PRINCE RUPERT**
**AREA**
**AREA**
**COLSTRIP**
**BOISE**
**PORTLAND**
**AREA**
**MALIN**
**TABLE MTN**
**ROUND MTN**
**SALT LAKE**
**CITY AREA**
**MEXICO**
**EL PASO**
**AREA**
**DEVERS**
**LUGO**
**SAN FRANCISCO**
**MIDPOINT**
**AREA**
**LOS ANGELES**
**AREA**
**ALBUQUERQUE**
**AREA**
**NAVAJO**
**DENVER**
**AREA**
**MOJAVE**
**HOOVER**
**PHOENIX**
**AREA**
**LANGDON**
**HOT SPRINGS**
**HELLS**
**CANYON**
**CHIEF JOSEPH**
**BURNS**
**PINTO**
**FOUR**
**CORNERS**
**SHASTA**
**LANGDON**
**CANADA**
**UNITED STATES**
**66**
**65**
**14**
**8**
**30**
**27**
**15**
**49**
**31**
**6**
**19**
**22**
**34**
**47**
**16**
**3**
**35**
**18**
**5**
**4**
**6**
**17**
**20**
**23**
**24**
**26**
**32**
**36**
**45**
**46**
**50**
**51**
**48**
**48**
_**Spring 99 thru 02 (Based on Heaviest Loading Year)**_
**Actual Flow > 75% of OTC greater than 50% of time**
**Actual Flow > 75% of OTC between 25% and 50 % of time**
**Actual Flow > 75% of OTC between 0% and 25% of time**
**BUCKLEY**
**SUNDANCE**
**FT. PECK**
**PEACE CANYON**
**MICA**
**VANCOUVER**
**SEATTLE**
**PRINCE RUPERT**
**AREA**
**AREA**
**COLSTRIP**
**BOISE**
**PORTLAND**
**AREA**
**MALIN**
**TABLE MTN**
**ROUND MTN**
**SALT LAKE**
**CITY AREA**
**MEXICO**
**EL PASO**
**AREA**
**DEVERS**
**LUGO**
**SAN FRANCISCO**
**MIDPOINT**
**AREA**
**LOS ANGELES**
**AREA**
**ALBUQUERQUE**
**AREA**
**NAVAJO**
**DENVER**
**AREA**
**MOJAVE**
**HOOVER**
**PHOENIX**
**AREA**
**LANGDON**
**HOT SPRINGS**
**HELLS**
**CANYON**
**CHIEF JOSEPH**
**BURNS**
**PINTO**
**FOUR**
**CORNERS**
**SHASTA**
**LANGDON**
**CANADA**
**UNITED STATES**
**66**
**65**
**14**
**8**
**30**
**27**
**15**
**49**
**31**
**6**
**19**
**22**
**34**
**47**
**16**
**3**
**35**
**18**
**5**
**4**
**6**
**17**
**20**
**23**
**24**
**26**
**32**
**36**
**45**
**46**
**50**
**51**
**48**
**48**
_**Summer 01**_
**Actual Flow > 75% of OTC greater than 50% of time**
**Actual Flow > 75% of OTC between 25% and 50 % of time**
**Actual Flow > 75% of OTC between 0% and 25% of time**
**BUCKLEY**
**SUNDANCE**
**FT. PECK**
**PEACE CANYON**
**MICA**
**VANCOUVER**
**SEATTLE**
**PRINCE RUPERT**
**AREA**
**AREA**
**COLSTRIP**
**BOISE**
**PORTLAND**
**AREA**
**MALIN**
**TABLE MTN**
**ROUND MTN**
**SALT LAKE**
**CITY AREA**
**MEXICO**
**EL PASO**
**AREA**
**DEVERS**
**LUGO**
**SAN FRANCISCO**
**MIDPOINT**
**AREA**
**LOS ANGELES**
**AREA**
**ALBUQUERQUE**
**AREA**
**NAVAJO**
**DENVER**
**AREA**
**MOJAVE**
**HOOVER**
**PHOENIX**
**AREA**
**LANGDON**
**HOT SPRINGS**
**HELLS**
**CANYON**
**CHIEF JOSEPH**
**BURNS**
**PINTO**
**FOUR**
**CORNERS**
**SHASTA**
**LANGDON**
**CANADA**
**UNITED STATES**
**66**
**65**
**14**
**8**
**30**
**27**
**15**
**49**
**31**
**6**
**19**
**22**
**34**
**47**
**16**
**3**
**35**
**18**
**5**
**4**
**6**
**17**
**20**
**23**
**24**
**26**
**32**
**36**
**45**
**46**
**50**
**51**
**48**
**48**
_**Summer 99 thru 01 (Based on Heaviest Loading Year)**_
**Actual Flow > 75% of OTC greater than 50% of time**
**Actual Flow > 75% of OTC between 25% and 50 % of time**
**Actual Flow > 75% of OTC between 0% and 25% of time** | en |
markdown | 693629 | # Presentation: 693629
## OCFO Town Hall
**January 24, 2007**
## Agenda
**Safety**
**Tang Center - Kathleen Handron**
**Controller’s Reorganization**
**Director’s Retreat**
**Move Back to the Hill **
**Budget Outlook**
**Awards and Recognition**
## Ergo Challenges 2007
- Ergo injuries continue
- to be over 50% of
- all recordable injuries
- Total recordables in
- first quarter 2007 are
- already > half of DOE
- target for the year
- Based on walk-thrus and
- sweeps, we estimate 25%
- of employees are experiencing
- recurring discomfort at work
## People working in awkward postures!
- 1. Mouse arm
- 3. Bent wrist
- & palm planting
- 4. Bike riding
- posture
- 2. Raised
- shoulders
**Notes:**
These are typical postures we have observed at LBNL
## People working under stress and deadlines!
***Budget ***
***Crunch!***
*PRDs!*
***FY Deadlines!***
- Fewer Resources!
- Long Hours!
***Working at home!***
- 10-hour Days!
**Grant **
**Deadlines!**
*8 Days-a-week!*
*Year End Close!*
- NEED IT NOW!
## People are exhibiting their discomfort!
*My aching back!*
*My throbbing mouse** arm*
## What EH&S is doing...
- Pilot rollout of Remedy Interactive software
- for employee self-assess and training
- (3 Divisions- OCFO, IT and EH&S)
- Fulltime Ergo Desk for help at x 5818
- Increasing ergo staff for “discomfort evals”
- Rollout Ergo Advocate training program - *more resources!*
- Improving the Ergo Database - *clear, concise and user friendly*
**Ergo@lbl.gov**
## What you can do to control injuries...
- Set realistic expectations for staff workloads
- Plan ahead for spikes and crunch periods
- Adjust for shifts in people resources
- Create a supportive work atmosphere
- Require Supervisor Ergo training EH&S 22
- Prompt staff to report ergo problems and request evals early
- Implement Ergo Eval recommendations promptly...*or faster!*
- Encourage people to get up and move
- Call Ergo at extension 5818 or email _[Ergo@lbl.gov](mailto:Ergo@lbl.gov)__ for assistance_
## OCFO Interim Org Chart
**OCFO Interim Org Chart**
## DIRECTOR’S RETREAT
## What’s the Problem? ~$14m
- **Moving people and money between LBNL & UC is difficult & time consuming**
**Persistent unresolved issues hinder scientific collaborations**
- **Significant resources are expended on maintaining inefficient processes**
** ****Confusing processes and mechanisms (e.g. IUTs) are used to handle:**
**Multi Location Appointments (MLAs)-non Faculty**
**Joint Faculty Appointments**
**GSRAs**
**R&D Subcontracts**
**What’s the Problem? ****~$14m**
## Decrease the Cost of Doing Business
**Reduce total indirect costs**
**G&A**
**Recharges**
**Burdens**
**Efficiencies**
**Within Ops Divisions**
**Across Ops Divisions**
**Partnership with Science Divisions**
**With Internal Audit**
**Reduce services**
**Changed business model**
## Efficiencies to Date only current changes shown here
**Efficiencies to Date****only current changes shown here**
| | $K | | |
| --- | --- | --- | --- |
| Supply chain | 1,500 | For first year | |
| Redefinition/reduction MII | 2,400 | Ongoing | |
| Staffing | 5,400 | Ongoing (CFO& Facilities >50 FTEs) | |
| Metal Rack outsourced | 53 | Ongoing | |
| Warehouse relocated | 620 | Ongoing | |
| Stores shutdown | 145 | Ongoing | |
| Email | 700 | Recharge ongoing | |
| Telephone Services | 540 | Recharge ongoing | |
| IT infrastructure | 485 | GPE ongoing | |
| Personal Identification Verification | <9,000
1,000 | One time
Ongoing | Cost avoidance |
## Travel Re-engineering Recommendations
- Develop one consistent institutional process *
- Divisions are currently handling pre & post-travel processes in many different ways:
- Some don’t require pre-approval
- # of approvals vary
- Use of Gelco varies by division
- Domestic travel: require pre-approval within divisions; recommend using email
- Reimburse traveler only after all required receipts have been submitted *
- Highly encourage practice of reimbursing for actual cost of meals & incidental expenses (M&IE) up to maximum per diem rates, and clarify policy
- Default reimbursement (other than airfare) directly to employee’s bank account rather than disbursing checks*
- Move expense reimbursement of travel to Disbursements *
- If above recommendations are adopted, replace Gelco with an intuitive, user-friendly interface coupled with PeopleSoft travel module, and also mandate use of system
- The system should be used by all travelers
- *Represents best practice
## 937 Move Back to the Hill
**937 Lease Expires April, 2009 – We Will Move**
**Lease cost is $1.8M a year**
**Moving out over a phased period – TBD when**
**Current plan is for OCFO to be mostly co-located in and around building 90 and the 90 trailers**
**Some units may co-locate in building 46 as well**
## Budget Outlook
**OCFO FY 07 Budget reduced ~$600k**
**Accomplished thru 100% Voluntary Reduction In Force – Across all of OCFO**
**Continuing Resolution/Omnibus Bill**
**Under CR, no new project starts**
**Omnibus may provide some level of funding for large initiatives but not in detail (like a single appropriation)**
**IF Omnibus bill passes we will receive up-front funding rather than incremental, but even after it is signed it will take 1.5 months to receive...at best**
**Thanks for your significant contributions! **
## Awards and Recognition
**Annie Owens, ****EETD**
**New Employees**
**David McFann,**** Property**
**Mary Thach,**** Payroll**
**Nancy Roberts, ****Facilities**
**Rose Katsus, ****Financial Policy & Training**
**Stacy Wilson, ****Direct Budget**
**Alicia Middleton,**** Life Sciences**
**Sonia Dominguez,**** Life Sciences**
**Cynthia Ernesst, ****Life Sciences**
**David Kong, ****Indirect Budget**
**Kate Ahearn,**** Procurement**
**Hanh Le,**** Procurement**
**John Tennyson, ****Procurement**
**Theresa Hatch, ****Procurement**
**Linda Nowell,**** SPO**
**Brigitte Roberts,**** Property**
**Teresa Grossman, ****Budget Office**
**Doug Goodman, ****Field Operations**
**Jayde Van Ter Pool, ****Travel**
**Angela Ford**, **SPO**
**Samuel ****Johnson****,**** ****SPO**
## Awards and Recognition
**OPAs**
## Awards and Recognition
**SPOT Awards**
**Sally Areceneaux**
**Patty Atases**
**Chuck Axthelm**
**Melissa Baksic**
**Armando Bautista**
**Michelle Bennett**
**Ron Brown**
**Neda Busler**
**Sandra Cheeks**
**Helena Cheng**
**Kimmy Cheung**
**Sharon Chiou**
**Lisa Cordova**
**Lauretta Corsair**
**Denise Davis**
**Angela Dawn-White**
**Sarah Eary**
**Brian Fox**
**Sallie Frainier**
**David Garcia**
**Lorenza Gibson**
**Carol Gilbert**
**Susan Gisser**
**Susan Gisser**
**Gina Goodman**
**Linda Griffin**
**Heidi Hauett**
**David Hathaway**
**Bridget Haverty**
**Grace Huang**
**Tanya James**
**Vivian Kim**
**Joy Kono**
**Anne Ku**
**Su-Jane Lai**
**Rick Larson**
**Judy Lee**
**Victor Lorencz**
## Awards and Recognition (cont.)
**Chi-Kin Lou**
**Laura Lou**
**Gary Mack**
**Tony Marques**
**Eva McNeil**
**Sally Nasman**
**Suzanne Nolan**
**Sonia Ortiz**
**Lisa Oshiro**
**Denny Parra**
**David Pastor**
**Aurora Pecoraro**
**SPOT Awards**
**Kameswara Upadhyayula (UK)**
**Elijah Walker**
**Linda Williams**
**Ken Winters**
**Eleni Yatar**
**Susan Peterson**
**Linda Posey**
**Lee Purbaugh**
**Maxine Redfearn**
**Erin Reiche**
**Rosa Rodriguez-Flores**
**Glenna Rogers**
**Dolores Sanchez**
**Rosario Sayson**
**Anastasia Schiller**
**Jill Stark**
**Tony Tiritilli**
## Awards and Recognition
**10 YEARS**
**Melissa Baksic****Armando Bautista****Craig Hopkins****Laura Luo****Gary Mack****Emmy Randol**
**Service Pins**
**25 YEARS**
**Derrol Hammer****Theresa Lessard-Smith****Anil More****Sally Nasman****Linda Williams**
**30 YEARS**
**Alan Campbell****Patrice Atases**
**15 YEARS**
**Maureen Cowger****Glenda Fish****Grace Miller****Melissa Prince**
**20 YEARS**
**David Garcia** | en |
converted_docs | 569511 | > 
{width="0.625in" height="0.6201388888888889in"}
**Transportation Equity in Emergencies:**
**A Review of the Practices of State Departments of Transportation,
Metropolitan Planning Organizations, and Transit Agencies in 20
Metropolitan Areas**
**Final Report**
**May, 2007**
**FTA-PA-26-8001-2007**
+----------------+-----+----------+-----------+---+---+-----------------+
| # REPORT DOCU | | | | * | | |
| MENTATION PAGE | | | | F | | |
| | | | | o | | |
| | | | | r | | |
| | | | | m | | |
| | | | | A | | |
| | | | | p | | |
| | | | | p | | |
| | | | | r | | |
| | | | | o | | |
| | | | | v | | |
| | | | | e | | |
| | | | | d | | |
| | | | | * | | |
| | | | | | | |
| | | | | * | | |
| | | | | O | | |
| | | | | M | | |
| | | | | B | | |
| | | | | N | | |
| | | | | o | | |
| | | | | . | | |
| | | | | 0 | | |
| | | | | 7 | | |
| | | | | 0 | | |
| | | | | 4 | | |
| | | | | - | | |
| | | | | 0 | | |
| | | | | 1 | | |
| | | | | 8 | | |
| | | | | 8 | | |
| | | | | * | | |
+----------------+-----+----------+-----------+---+---+-----------------+
| Public | | | | | | |
| reporting | | | | | | |
| burden for | | | | | | |
| this | | | | | | |
| collection of | | | | | | |
| information is | | | | | | |
| estimated to | | | | | | |
| average 1 hour | | | | | | |
| per response, | | | | | | |
| including the | | | | | | |
| time for | | | | | | |
| reviewing | | | | | | |
| instructions, | | | | | | |
| searching | | | | | | |
| existing data | | | | | | |
| sources, | | | | | | |
| gathering and | | | | | | |
| maintaining | | | | | | |
| the data | | | | | | |
| needed, and | | | | | | |
| completing and | | | | | | |
| reviewing the | | | | | | |
| collection of | | | | | | |
| information. | | | | | | |
| Send comments | | | | | | |
| regarding this | | | | | | |
| burden | | | | | | |
| estimate or | | | | | | |
| any other | | | | | | |
| aspect of this | | | | | | |
| collection of | | | | | | |
| information, | | | | | | |
| including | | | | | | |
| suggestions | | | | | | |
| for reducing | | | | | | |
| this burden, | | | | | | |
| to Washington | | | | | | |
| Headquarters | | | | | | |
| Services, | | | | | | |
| Directorate | | | | | | |
| for | | | | | | |
| Information | | | | | | |
| Operations and | | | | | | |
| Reports, 1215 | | | | | | |
| Jefferson | | | | | | |
| Davis Highway, | | | | | | |
| Suite 1204, | | | | | | |
| Arlington, VA | | | | | | |
| 22202-4302, | | | | | | |
| and to the | | | | | | |
| Office of | | | | | | |
| Management and | | | | | | |
| Budget, | | | | | | |
| Paperwork | | | | | | |
| Reduction | | | | | | |
| Project | | | | | | |
| (0704-0188), | | | | | | |
| Washington, DC | | | | | | |
| 20503. | | | | | | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 1\. AGENCY USE | | 2\. | | 3 | | |
| ONLY (Leave | | REPORT | | \ | | |
| blank) | | DATE | | . | | |
| | | | | R | | |
| | | May 2007 | | E | | |
| | | | | P | | |
| | | | | O | | |
| | | | | R | | |
| | | | | T | | |
| | | | | T | | |
| | | | | Y | | |
| | | | | P | | |
| | | | | E | | |
| | | | | A | | |
| | | | | N | | |
| | | | | D | | |
| | | | | D | | |
| | | | | A | | |
| | | | | T | | |
| | | | | E | | |
| | | | | S | | |
| | | | | C | | |
| | | | | O | | |
| | | | | V | | |
| | | | | E | | |
| | | | | R | | |
| | | | | E | | |
| | | | | D | | |
| | | | | | | |
| | | | | F | | |
| | | | | i | | |
| | | | | n | | |
| | | | | a | | |
| | | | | l | | |
| | | | | R | | |
| | | | | e | | |
| | | | | p | | |
| | | | | o | | |
| | | | | r | | |
| | | | | t | | |
| | | | | - | | |
| | | | | - | | |
| | | | | - | | |
| | | | | M | | |
| | | | | a | | |
| | | | | y | | |
| | | | | 2 | | |
| | | | | 0 | | |
| | | | | 0 | | |
| | | | | 7 | | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 4\. TITLE AND | | | | | 5 | |
| SUBTITLE | | | | | \ | |
| | | | | | . | |
| Transportation | | | | | F | |
| Equity and | | | | | U | |
| Emergency | | | | | N | |
| Preparedness: | | | | | D | |
| A Review of | | | | | I | |
| the Practices | | | | | N | |
| of State | | | | | G | |
| Departments of | | | | | N | |
| T | | | | | U | |
| ransportation, | | | | | M | |
| Metropolitan | | | | | B | |
| Planning | | | | | E | |
| Organizations, | | | | | R | |
| and Transit | | | | | S | |
| Agencies in 20 | | | | | | |
| Metropolitan | | | | | F | |
| Areas | | | | | T | |
| | | | | | A | |
| | | | | | - | |
| | | | | | P | |
| | | | | | A | |
| | | | | | - | |
| | | | | | 2 | |
| | | | | | 6 | |
| | | | | | - | |
| | | | | | 8 | |
| | | | | | 0 | |
| | | | | | 0 | |
| | | | | | 1 | |
| | | | | | - | |
| | | | | | 2 | |
| | | | | | 0 | |
| | | | | | 0 | |
| | | | | | 7 | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 6\. AUTHOR(S) | | | | | | |
| | | | | | | |
| Denise Bailey, | | | | | | |
| Sandra | | | | | | |
| Swiacki, | | | | | | |
| Annemarie | | | | | | |
| Byrnes, James | | | | | | |
| Buckley, Diane | | | | | | |
| King, Valerie | | | | | | |
| Piper, Mara | | | | | | |
| Marino, | | | | | | |
| Subhash | | | | | | |
| Mundle, George | | | | | | |
| Pierlott, | | | | | | |
| Andrew Lynd | | | | | | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 7\. PERFORMING | | | | | 8 | |
| ORGANIZATION | | | | | \ | |
| NAME(S) AND | | | | | . | |
| ADDRESS(ES) | | | | | P | |
| | | | | | E | |
| Milligan & | | | | | R | |
| Company, LLC | | | | | F | |
| | | | | | O | |
| 105 N. 22^nd^ | | | | | R | |
| Street, 2^nd^ | | | | | M | |
| 'Floor | | | | | I | |
| | | | | | N | |
| Philadelphia, | | | | | G | |
| PA 19103 | | | | | O | |
| | | | | | R | |
| Mundle & | | | | | G | |
| Associates, | | | | | A | |
| Inc. | | | | | N | |
| | | | | | I | |
| 1520 Locust | | | | | Z | |
| Street, Suite | | | | | A | |
| 801 | | | | | T | |
| | | | | | I | |
| Philadelphia, | | | | | O | |
| PA 19102 | | | | | N | |
| | | | | | R | |
| | | | | | E | |
| | | | | | P | |
| | | | | | O | |
| | | | | | R | |
| | | | | | T | |
| | | | | | N | |
| | | | | | U | |
| | | | | | M | |
| | | | | | B | |
| | | | | | E | |
| | | | | | R | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 9\. | | | | | 1 | |
| SPONSOR | | | | | 0 | |
| ING/MONITORING | | | | | \ | |
| AGENCY NAME(S) | | | | | . | |
| AND | | | | | S | |
| ADDRESS(ES) | | | | | P | |
| | | | | | O | |
| ### Fe | | | | | N | |
| deral Transit | | | | | S | |
| Administration | | | | | O | |
| | | | | | R | |
| U.S. | | | | | I | |
| Department of | | | | | N | |
| Transportation | | | | | G | |
| | | | | | / | |
| Washington, DC | | | | | M | |
| 20590 Website | | | | | O | |
| URL | | | | | N | |
| \[www | | | | | I | |
| .fta.dot.gov\] | | | | | T | |
| | | | | | O | |
| | | | | | R | |
| | | | | | I | |
| | | | | | N | |
| | | | | | G | |
| | | | | | \ | |
| | | | | | A | |
| | | | | | G | |
| | | | | | E | |
| | | | | | N | |
| | | | | | C | |
| | | | | | Y | |
| | | | | | R | |
| | | | | | E | |
| | | | | | P | |
| | | | | | O | |
| | | | | | R | |
| | | | | | T | |
| | | | | | N | |
| | | | | | U | |
| | | | | | M | |
| | | | | | B | |
| | | | | | E | |
| | | | | | R | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 11. | | | | | | |
| Supplementary | | | | | | |
| Notes. | | | | | | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 12a. | | | | | 1 | |
| DISTRIBUTIO | | | | | 2 | |
| N/AVAILABILITY | | | | | b | |
| STATEMENT | | | | | . | |
| | | | | | D | |
| **Available | | | | | I | |
| From:** | | | | | S | |
| National | | | | | T | |
| Technical | | | | | R | |
| Information | | | | | I | |
| Service/NTIS, | | | | | B | |
| 5285 Port | | | | | U | |
| Royal Road, | | | | | T | |
| Springfield, | | | | | I | |
| Virginia | | | | | O | |
| 22161. Phone | | | | | N | |
| 703.605.6000, | | | | | C | |
| Fax | | | | | O | |
| 703.605.6900, | | | | | D | |
| | | | | | E | |
| Email | | | | | | |
| \[orders@ntis. | | | | | | |
| fedworld.gov\] | | | | | | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 13. ABSTRACT | | | | | | |
| | | | | | | |
| The Hurricane | | | | | | |
| Katrina | | | | | | |
| disaster has | | | | | | |
| raised concern | | | | | | |
| that | | | | | | |
| government at | | | | | | |
| all levels is | | | | | | |
| not adequately | | | | | | |
| prepared to | | | | | | |
| respond to | | | | | | |
| major | | | | | | |
| disasters or | | | | | | |
| catastrophic | | | | | | |
| incidents and, | | | | | | |
| in particular, | | | | | | |
| is not well | | | | | | |
| prepared to | | | | | | |
| assist members | | | | | | |
| of the public | | | | | | |
| who, by virtue | | | | | | |
| of their age, | | | | | | |
| ability, | | | | | | |
| income, | | | | | | |
| national | | | | | | |
| origin, or | | | | | | |
| medical | | | | | | |
| history, will | | | | | | |
| have specific | | | | | | |
| mobility, | | | | | | |
| sheltering, | | | | | | |
| c | | | | | | |
| ommunications, | | | | | | |
| or other | | | | | | |
| special needs | | | | | | |
| in emergency | | | | | | |
| events. This | | | | | | |
| report reviews | | | | | | |
| the extent to | | | | | | |
| which transit | | | | | | |
| providers, | | | | | | |
| metropolitan | | | | | | |
| planning | | | | | | |
| organizations, | | | | | | |
| and state | | | | | | |
| departments of | | | | | | |
| transportation | | | | | | |
| in selected | | | | | | |
| metropolitan | | | | | | |
| regions in the | | | | | | |
| United States | | | | | | |
| and Puerto | | | | | | |
| Rico are | | | | | | |
| identifying | | | | | | |
| and addressing | | | | | | |
| the needs of | | | | | | |
| populations | | | | | | |
| that may be | | | | | | |
| especially | | | | | | |
| vulnerable in | | | | | | |
| the event of a | | | | | | |
| natural or | | | | | | |
| man-made | | | | | | |
| disaster. The | | | | | | |
| report | | | | | | |
| suggests that | | | | | | |
| targeted | | | | | | |
| outreach and | | | | | | |
| assistance | | | | | | |
| measures as | | | | | | |
| well as | | | | | | |
| coordination | | | | | | |
| amongst local | | | | | | |
| transportation | | | | | | |
| and emergency | | | | | | |
| management | | | | | | |
| agencies would | | | | | | |
| help local | | | | | | |
| agencies be | | | | | | |
| better | | | | | | |
| prepared to | | | | | | |
| assist | | | | | | |
| populations | | | | | | |
| with specific | | | | | | |
| needs in | | | | | | |
| emergencies. | | | | | | |
+----------------+-----+----------+-----------+---+---+-----------------+
| 14\. SUBJECT | | | | | | 14. NUMBER OF |
| TERMS | | | | | | PAGES |
| | | | | | | |
| Emergency | | | | | | 60 |
| preparedness, | | | | | | |
| civil rights. | | | | | | |
+----------------+-----+----------+-----------+---+---+-----------------+
| | | | | | | 16\. PRICE CODE |
+----------------+-----+----------+-----------+---+---+-----------------+
| 17\. SECURITY | 1 | | 19\. | | | 20\. LIMITATION |
| C | 8\. | | SECURITY | | | OF ABSTRACT |
| LASSIFICATION\ | SE | | CLASSI | | | |
| OF REPORT | CUR | | FICATION\ | | | |
| | ITY | | OF | | | |
| Unclassified | CLA | | ABSTRACT | | | |
| | SSI | | | | | |
| | FIC | | Unc | | | |
| | ATI | | lassified | | | |
| | ON\ | | | | | |
| | OF | | | | | |
| | T | | | | | |
| | HIS | | | | | |
| | P | | | | | |
| | AGE | | | | | |
| | | | | | | |
| | Unc | | | | | |
| | las | | | | | |
| | sif | | | | | |
| | ied | | | | | |
+----------------+-----+----------+-----------+---+---+-----------------+
***NOTICE:***
This document is disseminated under the sponsorship of the United States
Department of Transportation in the interest of information exchange.
The United States Government assumes no liability for its contents or
use thereof.
The United States Government does not endorse manufacturers or
products. Trade or manufacturer's names appear herein solely because
they are essential to the objective of this report.
**Transportation Equity in Emergencies:**
**A Review of the Practices of State Departments of Transportation,
Metropolitan Planning Organizations, and Transit Agencies in 20
Metropolitan Areas**
May 2007** **
>
*Prepared by*
Milligan & Company, LLC
105 N. 22^nd^ Street, 2^nd^ 'Floor
Philadelphia, PA 19103
*Prepared for*
Federal Transit Administration
U.S. Department of Transportation
Washington, DC 20590
>
*Available Online \[http://www.fta.dot.gov\]*
Federal Transit Administration
Office of Research, Demonstration, and Innovation
400 7th Street, SW, Room 6427
Washington, DC 20590
*Report Number*
FTA-PA-26-8001-2007
**Table of Contents**
I. Executive Summary 1
II\. Introduction and Background 3
III\. Study Scope 11
IV\. Study Methodology 16
V. Overview of the Metropolitan Area Demographics 18
VI\. Results of the Agency Plan Assessment 34
VII\. Promising Practices 39
VIII\. Conclusions and Recommendations 42
IX\. Resources 44
[Appendix](#VConclusionsandRecommen) A: Summary of Demographic Profiles
47
Appendix B: List of Agencies Reviewed 58
[Demographic Profiles]{.underline}
A demographic profile of each metropolitan area featured in this report
is located at
<http://www.fta.dot.gov/civilrights/civil_rights_6343.html>.
[List of Tables]{.underline}
Table II-1: Summary of Relevant Reports 5
Table V-1: Summary of Demographic Information Based on Arithmetic
Mean of Census Tracts 19
Table V-2: Minority Proportion Summary 21
Table V-3: Below Poverty Proportion Summary 23
Table V-4: LEP Proportion Summary 25
Table V-5: Zero-Car Household Summary 27
Table V-6: Summary of Correlation Coefficients 29
Table V-7: Summary of Natural and Man-made Disasters 33
Table VI-1: Summary of Agency Survey
Results......................................34
[List of Maps]{.underline}
Map V-1: Honolulu, HI CBSA Minority Population 22
Map V-2: St. Louis, MO-IL CSA Below Poverty Population 24
# Map V-3: Los Angeles CSA LEP Population 26
Map V-4: Baltimore, MD Zero-Car Households 28
Map V-5: Pittsburgh, PA CSA Zero-Car Population 31
Map V-6: Flagstaff, Arizona CBSA Zero-Car Population 32
**Foreword**
This study was commissioned in order to promote nondiscrimination in the
emergency preparedness activities administered by recipients of FTA
financial assistance. It reviewed the extent to which transit providers,
metropolitan planning organizations, and state departments of
transportation in selected metropolitan regions in the United States and
Puerto Rico are identifying and addressing the needs of populations that
may be especially vulnerable in the event of a natural or man-made
disaster. This report also provides resources that should assist
officials in these and other metropolitan regions to better incorporate
attention to populations with specific mobility needs into their ongoing
emergency planning activities.
This study was conducted with funds from the Transportation Equity
Research Program (TERP) under Section 3046(a) of the Safe, Accountable,
Flexible, Efficient Transportation Equity Act: A Legacy for Users
(SAFETEA-LU). This program provides funding for research and
demonstration activities that focus on the impacts that transportation
planning, investment, and operations have on low-income and minority
populations that are transit dependent.
**I. Executive Summary**
The Hurricane Katrina disaster of 2005 has prompted stakeholders in
government and civil society to ensure that the civil rights of persons
in the United States are protected during emergencies. While Katrina
affected hundreds of thousands of people along the Gulf Coast, those
populations that were least able to escape harm's way and most acutely
affected by the disaster included racial and ethnic minorities, people
with disabilities, and older adults whose civil rights America's
landmark laws were established to uphold. As policy makers at all levels
of government work to improve their emergency preparedness, disaster
response, and disaster recovery activities in the wake of recent
catastrophic events, government has a responsibility to ensure that
persons will not be denied the benefits of, be excluded from
participation in, or be subject to discrimination under these vital
programs and activities on the grounds of race, color, national origin,
disability, age or other classes covered under our nation's civil rights
laws and policy directives.
The Federal Transit Administration's (FTA) Office of Civil Rights
commissioned this report in order to promote nondiscrimination in the
emergency preparedness activities administered by recipients of FTA
financial assistance. This report reviews the extent to
which transit providers, metropolitan planning organizations, and state
departments of transportation in selected metropolitan regions in the
United States and Puerto Rico are identifying and addressing the needs
of populations that may be especially vulnerable in the event of a
natural or man-made disaster. The report also provides resources that
should assist officials in these and other metropolitan regions to
better incorporate attention to populations with specific mobility needs
into their ongoing emergency planning activities. This report does not
constitute a civil rights compliance review of any FTA recipient nor was
this report prepared in response to a complaint of discrimination
against a recipient.
This study focuses on emergency preparedness activities being conducted
in 20 metropolitan regions that have recently experienced natural or
man-made disasters and also have populations with relatively high
overall numbers and proportions of racial and ethnic minorities, persons
with low incomes, persons with limited English proficiency, and persons
living in households without vehicles. Our assumption was that officials
in these regions would be especially attuned to the emergency evacuation
needs of these populations and would be a source of effective and
promising practices. However, with some exceptions, the agencies
reviewed in this study have taken very limited steps towards involving
populations with specific mobility needs in emergency preparedness
planning, identifying the locations of and communicating emergency
preparedness instructions to these populations, or coordinating with
other agencies to meet the specific needs of these populations in an
emergency. While many agencies have conducted important outreach,
analysis, and coordinating activities to address the needs of their
general population in emergencies, few have targeted these activities to
assist their region's most vulnerable people.
Part 2 of this report discusses emergency preparedness for populations
with specific needs and summarizes federal civil rights requirements,
specific guidance on emergency preparedness issued by FTA, and the
findings of recent reports by other governmental and non-governmental
agencies. Part 3 describes this report's scope and Part 4 explains the
study's methodology. Part 5 summarizes the demography, transit coverage,
and disaster risks of the selected regions. Part 6 discusses the
activities of FTA recipients in these regions, as they relate to
emergency preparedness, and Part 7 highlights promising practices
gleaned from reviews of emergency preparedness plans and interviews with
agency staff members. Part 8 consists of conclusions and
recommendations, and the appendices present detailed demographic
profiles of the 20 metropolitan regions selected for study which should
help planners in these regions better target their activities towards
specific-needs populations (and planners in other regions might consider
preparing similar profiles of their area).
State departments of transportation, metropolitan planning
organizations, and public transportation providers have the potential to
play important supporting roles before, during, and after emergencies
that require evacuation. This report and accompanying technical
resources should assist these and other emergency management agencies in
facilitating the safe and efficient evacuation of people---particularly
those for whom community and public transportation is their primary
means of mobility---and ensuring equitable and inclusive public action
in times of need.
**II. Introduction and Background**
Public emergency evacuations in response to natural and man-made
emergencies occur frequently in the United States. According to the
Nuclear Regulatory Commission, emergency evacuations of at least 100
people occur more than once a week, and major evacuations of more than
1,000 people occur more than three times per month. While most prior
evacuations have proceeded safely and effectively, this nation's
experience during the September 11, 2001, terrorist attacks and in the
aftermath of Hurricane Katrina's August 29, 2005, landfall on the Gulf
Coast have raised concern that government at all levels is not
adequately prepared to respond to major disasters or catastrophic
incidents and, in particular, is not well prepared to assist members of
the public who, by virtue of their age, ability, income, national
origin, or medical history, will have specific mobility, sheltering,
communications, or other special needs in emergency events.[^1]
The incomplete evacuation of New Orleans prior to Hurricane Katrina's
landfall, combined with the widespread flooding after the hurricane,
required a post-hurricane evacuation of 70,000 people in New Orleans for
which federal, state, and city officials had not been prepared. Hundreds
of people who remained behind died as floodwaters enveloped low lying
neighborhoods in waters above the roof lines. Those who escaped to high
ground suffered horrible conditions in the Superdome, the Convention
Center, and other spontaneous gathering spots. Meanwhile, hundreds of
city buses and school buses that could have been used for an evacuation
sat flooded or without drivers.[^2]
Studies that have been issued after Katrina indicate that low-income
residents, most of whom were African American, as well as persons with
disabilities, older adults persons with limited English proficiency, and
other persons (such as tourists without access to private
transportation) were most likely to have remained in vulnerable areas
prior to Katrina making landfall and were most adversely affected by the
hurricane and subsequent flooding. Many low-income residents either did
not have access to private transportation or had exhausted their
disposable income by the end of the month and had no money for gasoline.
In a survey of people from New Orleans who were evacuated to the
Astrodome and other large facilities in Houston, 23% of respondents
stated they were physically unable to leave and an additional 23% of
respondents indicated that they had to care for someone who was
physically unable to leave.[^3] Other residents who could have left
chose not to heed evacuation orders. Older adults and people with
disabilities were disproportionately affected by the disaster. According
to the AARP, 73% of Hurricane Katrina-related deaths in the New Orleans
area were among persons aged 60 or over, although they comprised only
15% of the population of New Orleans. People who could not speak or
understand English may have also had difficulty accessing emergency
evacuation instructions.[^4]
The demography of New Orleans made many of its residents especially
vulnerable to the effects of the hurricane. Prior to Katrina, nearly
50,000 poor New Orleanians lived in neighborhoods where the poverty rate
exceeded 40% and the city ranked second among the nation's 50 largest
cities in the degree to which poor families, mostly African American,
were clustered in extremely poor neighborhoods. In addition, 15% of
households in New Orleans did not own personal vehicles, compared with
10% of households in the United States. Under these circumstances, many
people in New Orleans' high-poverty neighborhoods could not rely on
friends or relatives for transportation, shelter, or financial
assistance when disaster struck. Although New Orleans' geographic
characteristics meant that its residents were especially vulnerable to
the effects of hurricanes, many additional American metropolitan regions
that may also
be at risk for natural and man-made disasters also have racially
segregated areas with concentrated poverty and high proportions of
households without vehicles.[^5]
**[Previous Studies]{.underline}**
In the wake of Hurricanes Katrina and Rita, reports published by the
Government Accountability Office (GAO), multiple federal agencies, and
not-for-profit organizations have evaluated the state of emergency
preparedness in areas around the country. The scope and methodology of
recent reports vary, with some reports focusing on emergency
preparedness for a specific segment of society, such as people with
disabilities or older adults, and others examining measures for a wider
population of persons with specific needs. Likewise, some reports have
focused on a small sample of state or local government agencies while
other reports have a national scope. Regardless of the scope or
methodology, recent reports have consistently concluded that gaps remain
in emergency preparedness for populations with specific mobility needs.
Emergency management personnel may benefit from reviewing the following
reports (web links to these reports can be found in the "Resources"
section of this report).
**Table II-1: Summary of Relevant Reports**
------------------------------ ---------------- --------------- -------------- ---------------------------- --------------------------
**Report Title** **Sponsoring **Publication **Geographic **Activities Reviewed** **Focus Populations**
Organization** Date** Area Studied**
Catastrophic Hurricane U.S. DOT June 2006 5 Gulf Coast Evacuation and sheltering People with disabilities,
Evacuation Plan Evaluation states and children, elderly, people
selected in institutions, people
counties in without vehicles
these states
In the Eye of the Storm National Council February 2006 Areas affected Communications, evacuation, Latinos
of La Raza by Katrina and sheltering, employment
Rita
Nationwide Plan Review U.S. DHS June 2006 State, Evacuation, sheltering, People with disabilities
territorial, medical care, police, fire,
urban area rescue
emergency
plans
We Can Do Better AARP May 2006 Nationwide Evacuation, sheltering, Older adults
medical care, communication
Strategies in Emergency National September 2006 Nationwide Coordination, identification Transportation-dependent
Preparedness for Consortium on of transportation-dependent populations
Transportation-Dependent Human Services groups evacuation
Populations Transportation
The Impact of Hurricanes National Council August 2006 Gulf Coast Evacuation, sheltering, People with disabilities
Katrina and Rita on People on Disability areas affected medical care, housing,
with Disabilities by Katrina and education, employment
Rita
Emergency Evacuation Report American Highway October 2006 37 largest Evacuation using highways Highway users
Card Users Alliance urban areas
Transportation-Disadvantaged U.S. GAO December 2006 California, State and local Low-income persons, people
Populations: Actions Needed to Florida, transportation/evacuation. with disabilities, older
Clarify Responsibilities and Louisiana, New adults, LEP persons
Increase Preparedness for York,
Evacuations Washington, DC
------------------------------ ---------------- --------------- -------------- ---------------------------- --------------------------
**"Catastrophic Hurricane Evacuation Plan Evaluation," prepared by the
U.S. Department of Transportation (issued 2006).** In response to
requirements of Section 10204 of SAFETEA-LU and the FY 2006 DOT
Appropriations Act, U.S. DOT developed a systematic, analytical process
to evaluate the readiness and adequacy of state and local jurisdictions'
evacuation plans. Evacuation plans for all five Gulf states---Alabama,
Florida, Louisiana, Mississippi, and Texas---and a sample of 58 counties
and parishes in each state were assessed on how well they addressed
seven key elements of evacuation planning and implementation. The seven
areas are decision-making and management; planning; public communication
and preparedness; evacuation of people with special needs; evacuation
operations; sheltering; and training and exercises. This report
determined that plans in the Gulf Coast region for evacuating persons
with various special needs generally are not well developed. The report
recommended that state and local agencies should work with the special
needs communities to develop systems whereby those requiring specialized
transportation or sheltering services during evacuations can make their
needs known to emergency managers and operators of transportation and
sheltering services before evacuations.
**"Nationwide Plan Review," prepared by the Department of Homeland
Security (DHS) (issued June 2006).** The purpose of this report was to
assess the status of catastrophic planning and draw initial conclusions
for strengthening plans and planning processes at the federal, state,
and local levels of government. The review defines special needs as
encompassing an extremely broad segment of the population, including
people with disabilities, minority groups, people who do not speak
English, children and the elderly, those who live in poverty or are on
public assistance, and those who rely on public transportation. Specific
weaknesses in planning areas noted include: (1) there is a widespread
inability to provide messages to the public in multiple languages, (2)
overall, planners have not thoroughly and/or realistically determined
how they will manage special needs populations that require evacuation,
and (3) traditional sheltering procedures do not adequately accommodate
special needs populations. The review outlines 15 initial conclusions
for states and 24 for the federal government. Most conclusions focus on
the need to make specific improvements in plans and to modernize
planning efforts.
"Transportation-Disadvantaged Populations: Actions Needed to Clarify
Responsibilities and Increase Preparedness for Evacuations," prepared by
the United States Government Accountability Office (issued December
2006). This report reviews the practices of emergency management, public
safety, and transit and transportation agency officials in five major
cities---Los Angeles, CA; Miami, FL; New Orleans, LA; Buffalo, NY; and
Washington, DC---as well as state emergency management and
transportation officials in Florida, Louisiana and New York, to
determine the extent to which officials in these states and localities
were addressing the needs of transportation-disadvantaged populations,
which included people with disabilities, older adults, and people with
low-income and limited English proficiency. The GAO report determined
that state and local governments are generally not well prepared to
evacuate transportation-disadvantaged populations, but some have begun
to address challenges and barriers. The report also concluded that the
federal government could do more to assist state and local governments
to address the needs of transportation-disadvantaged populations.
"We Can Do Better -- Lessons Learned for Protecting Older Persons in
Disasters," prepared by AARP (issued May 2006). This report highlights
lessons learned from a conference of national, state, and local leaders
on the needs of older adults in disasters as well as a literature review
and data from a survey of persons aged 50 or older conducted by Harris
Interactive on behalf of AARP in November 2005. The report notes that
government emergency planning documents or processes at any
level---federal, state, or local---rarely mention the needs of
vulnerable older persons. The report recommends establishment of clear
lines of authority among federal, local, and state governments as well
as with private sector entities, and that the federal Interagency
Coordinating Council on Emergency Preparedness and Individuals with
Disabilities also address the needs of vulnerable older persons who do
not have disabilities.
"The Impact of Hurricanes Katrina and Rita on People with Disabilities:
A Look Back and Remaining Challenges," prepared by the National Council
on Disability (NCD) (issued August 2006). This report focuses on the
effects of hurricanes on people with all types of disabilities and
highlights the need for plans to be more inclusive of disabled persons.
It highlights some of the challenges faced by the disabled community in
evacuation, shelter, and recovery operations. These include barriers to
accessible emergency information and accessible transportation. The
emergency preparedness and response to hurricanes Katrina and Rita are
presented. The NCD found that almost immediately after Katrina, there
were roughly 155,000 people with disabilities over the age of 5---or
about 25% of the cities' populations---living in the three cities
hardest hit by the hurricane: Biloxi, MS; Mobile, AL; and New Orleans,
LA. The report notes NCD's findings on communications actions during
Katrina, including those by the Federal Communications Commission and
FEMA and the failure to use the Emergency Alert System. The report notes
that local evacuation plans failed to adequately provide for the
transportation needs of people with disabilities for two reasons. First,
many local planners reported they were unaware that people with
disabilities have special evacuation needs. Second, when local planners
were aware of the need to plan for people with disabilities, the plans
failed because they did not involve people with disabilities in the
development of the plans.
**"In the Eye of the Storm," prepared by the National Council of La Raza
(issued February 2006).** This report examines how the needs of Latinos
and other communities were addressed by the federal government and the
American Red Cross. The report focuses on communications, evacuation,
sheltering and employment, and includes recommendations to improve
public and private response in future disasters. This report addressed
the importance of providing emergency information and instructions in
multiple languages.
"Strategies in Emergency Preparedness for Transportation-Dependent
Populations," prepared by the National Consortium on Human Services
Transportation (issued September 2006). According to this report,
identifying and tracking the locations and needs of
transportation-dependent people during emergencies are considerations
that require a preemptive communitywide effort. Before an emergency
occurs, this would mean establishing information that confirms the
locations of, and particularly concentrations of, individuals who
require transportation during an evacuation. This report discusses the
need for collaboration, especially among transportation interests, with
organizations and agencies involved in emergency response, and a variety
of community-based groups, in planning for the transportation needs of
residents requiring mobility assistance during an emergency.
**"Emergency Evacuation Report Card 2006," prepared by the American
Highway Users Alliance (issued 2006).** This report evaluates and rates
the evacuation capacity of America's 37 largest urban areas and
concludes that 25 urban areas could face greater challenges than New
Orleans experienced after Hurricane Katrina. The report notes that each
urban area examined needs to be prepared to evacuate its citizens in the
event of catastrophe, and that urban areas are preparing disaster
readiness plans that include detailed plans for evacuations. The report
recommends the establishment of a National Standards and Reporting
System in a cooperative effort of governments at every level, expansion
of roadway capacity, expansion of automobile access, and completion of
urban area evacuation operations planning.
**[Existing and Pending Federal Guidance on Emergency Preparedness for
Populations with Specific Needs]{.underline}**
The Federal Transit Administration (FTA) and Federal Highway
Administration (FHWA), together with their partners in the
transportation industry, have issued or are in the process of issuing
guidance on emergency preparedness, disaster response, and disaster
recovery based on lessons learned from recent disasters and on
information learned from the above reports.
FTA's Disaster Response and Recovery Resource for Transit Agencies was
developed in August of 2006 (see
[**http://www.fta.dot.gov**](http://www.fta.dot.gov/)). This resource
provides best practices and links to specific resources for transit
agencies concerning critical disaster elements such as emergency
preparedness, disaster response, and recovery. One section of this
resource includes guidance on identifying and addressing the specific
needs of predominately minority and low-income communities, persons with
limited English proficiency, persons with disabilities, and older adults
in the delivery of emergency services. The resource recommends several
tips for ensuring that transit agencies and MPOs adequately address the
needs of these populations in the emergency preparedness planning
process. These include:
- Encouraging and securing the participation of special needs
populations in the planning process when developing emergency
preparedness plans;
- Identifying areas with high concentrations of minority and
low-income persons, persons with limited English proficiency,
persons with disabilities, and older adults who may require
additional assistance in an emergency, including evacuation;
- Partnering with faith- or cultural-based, social service, and other
nonprofit organizations that are active in local communities to link
residents with emergency preparedness information and services;
- Ensuring adequate resources, including the appropriate numbers and
types of vehicles for evacuating special needs populations during an
emergency; and
- Providing information regarding emergency evacuation and
transportation with local partnering agencies and organizations.
Strategies in Emergency Preparedness for Transportation-Dependent
Populations, including the Transportation and Emergency Preparedness
Checklist, was prepared in September of 2006 by the National Consortium
on Human Services Transportation (see
[**http://www.emergencyprep.dot.gov**](http://www.emergencyprep.dot.gov/))
with input from the U.S. Department of Transportation. This report
highlights the essential strategies for providing safe and efficient
transportation for persons requiring mobility assistance in the event of
an emergency. These include:
- Planning and coordinating the transportation needs of vulnerable
populations in advance;
- Developing strong community partnerships;
- Identifying and locating transportation-dependent populations;
- Developing effective and innovative methods to communicate with
those in need of mobility prior to and during emergency situations;
and
- Ensuring appropriate access to necessary equipment and vehicles for
evacuation.
In addition, FHWA and FTA are collaborating in producing a series of
primers on evacuation for use by state and local agencies. This material
is expected to be completed in 2007 and will provide specific guidance
for conducting evacuations and include information addressing the needs
of transportation-disadvantaged populations.
**[Civil Rights Directives]{.underline}**
In addition to existing guidance on emergency preparedness, civil rights
statutes and policy directives may apply to the emergency preparedness
programs, policies, and activities administered by recipients of federal
financial assistance. These directives include:
**Title VI of the Civil Rights Act of 1964 and the U.S. DOT Title VI
Regulations under 49 CFR 21.** Title VI provides that no person in the
United States shall, on the grounds of race, color, or national origin,
be denied the benefits of, excluded from participation in, or subject to
discrimination under programs or activities receiving federal financial
assistance. The U.S. DOT Title VI regulations effectuate the provisions
of Title VI for recipients of DOT funding. They prohibit recipients, in
the course of determining the types of services, financial aid,
benefits, and facilities that they will provide, from using criteria or
methods of administration that have the effect of subjecting persons to
discrimination on the basis of their race, color, or national origin,
and require recipients to take affirmative action to ensure that no
person is excluded from participation in or denied the benefits of the
recipient's programs or activities on the grounds of race, color, or
national origin.
**U.S. DOT Order on Environmental Justice** (issued April 1997). This
order states that it is the policy of DOT to promote the principles of
environmental justice (as embodied in Executive Order 12898, "Federal
Actions To Address Environmental Justice in Minority Populations and
Low-Income Populations") through the incorporation of those principles
in all DOT programs, policies, and activities. The principles of
environmental justice are to avoid, minimize, or mitigate
disproportionately high and adverse human health and environmental
effects, including social and economic effects, on minority populations
and low-income populations, to ensure the full and fair participation by
all potentially affected communities in the transportation
decision-making process, and to prevent the denial of, reduction in, or
significant delay in the receipt of benefits by minority and low-income
populations.
**U.S. DOT Policy Guidance Concerning Recipients' Responsibilities to
Limited English Proficient (LEP) Persons** (issued December 2005). This
policy guidance clarifies the responsibilities of recipients of federal
financial assistance from the U.S. Department of Transportation and aids
them in fulfilling their responsibilities to limited English proficient
persons, pursuant to Title VI of the Civil Rights Act of 1964 and
Executive Order 13166, "Improving Access to Services for Persons With
Limited English Proficiency."
**The December 12, 2005, Memorandum from Assistant Attorney General for
Civil Rights Wan J. Kim to the Directors of Civil Rights at all Federal
Agencies.** This memorandum from the Department of Justice requested
that federal agencies provide assistance in responding to the urgent
needs of limited English proficient and other vulnerable communities
affected by hurricanes Katrina and Rita. The memorandum urged each
agency to consider civil rights issues in all aspects of its hurricane
response, both in the short term and the long term.
**Section 504 of the Rehabilitation Act of 1973.** This section of the
Act provides that no otherwise qualified individual with a disability in
the United States shall, solely by reason of her or his disability, be
excluded from the participation in, be denied the benefits of, or be
subjected to discrimination under any program or activity receiving
federal financial assistance or under any program or activity.
**Americans with Disabilities Act of 1990 (ADA) and the DOT ADA
Regulations at 49 CFR Parts 37 and 38.** The ADA prohibits
discrimination and ensures accessible transportation for persons with
disabilities. The DOT ADA regulations contain provisions on acquisition
of accessible vehicles by private and public entities, requirements for
complementary paratransit service by public entities operating a
fixed-route system, and other provisions of nondiscriminatory accessible
transportation service.
**Executive Order 13347, Individuals with Disabilities in Emergency
Preparedness** (issued July 2004). This order states that it is the
policy of the federal government to ensure the safety and security of
individuals with disabilities in situations involving disasters,
including earthquakes, tornadoes, fires, floods, hurricanes, and acts of
terrorism. According to the order, each federal agency is required to
consider, in its emergency preparedness planning, the unique needs of
agency employees with disabilities and individuals with disabilities
whom the agency serves. The order also encourages the consideration of
the unique needs of employees and individuals with disabilities served
by state, local, and tribal governments and private organizations in
emergency preparedness planning.
**Age Discrimination Act of 1975** prohibits discrimination on the basis
of age in programs and activities receiving federal financial
assistance.
III\. Study Scope
This study was designed to complement existing or pending assessments of
the state of emergency preparedness activities in jurisdictions across
the United States. Given limited resources, the study focused on
activities designed to address the needs of some but not all populations
that could be defined as having "special needs" in an emergency.
Likewise, the study surveyed activities in a limited number of
metropolitan regions across the United States and focused on the
activities of some but not all of the agencies that have a role to play
in emergencies.
**[Populations]{.underline}**
This study focused on emergency preparedness activities designed to
address the needs of the following populations:
**Racial and ethnic minorities.** These populations comprised a
disproportionate share of persons who remained in New Orleans during the
hurricane Katrina disaster and are more likely to have low incomes or
live in households without vehicles.[^6] Persons who are members of
racial and ethnic minority groups may not necessarily need additional
transportation assistance in an emergency because the inability to
provide personal transportation or access conventional public
transportation is usually a function of income or age or disability.
However, it is essential that government agencies secure the trust and
cooperation of the affected public in an emergency and, in this respect,
a recent study indicates that racial and ethnic minorities may be more
likely to discount information received from government agencies in
emergency situations.[^7] This report sought to determine the extent to
which the focus agencies were taking specific steps to communicate and
build relationships with the racial and ethnic minority populations
served by the agencies.
**Persons with low-incomes.** This population comprises a
disproportionate share of persons who do not have ready access to
personal transportation or could not afford to use personal
transportation in an emergency. Low-income populations may also have
difficulty obtaining shelter, medical assistance, and other services
during and after an emergency.[^8]
**Persons with limited English proficiency.** People who have a limited
ability to read, write, speak, or understand English represent a growing
population in the United States.[^9] According to the 2000 census, the
number of people with limited English proficiency increased by 65% from
1990 to 2000. Among limited English speakers, Spanish is the language
most frequently spoken, followed by Chinese (Cantonese or Mandarin),
Vietnamese, and Korean. Public transit is a key means of achieving
mobility for many LEP persons. According to the 2000 census, more than
11% of LEP persons aged 16 years and over reported use of public transit
as their primary means of transportation to work, compared with about 4%
of English speakers. In emergency situations, LEP persons may need to
receive information and instructions in languages other than English and
may need additional transportation assistance in an emergency that
requires an evacuation.
**Persons living in households without vehicles.** This population
includes households that cannot drive or cannot afford to own a vehicle
as well as persons who have chosen not to own vehicles.[^10] Households
with incomes under \$25,000 comprise a disproportionate share of
zero-vehicle households, as do recent immigrants and racial and ethnic
minorities. People with disabilities and older adults may also be
disproportionately represented in this category. The 2000 census
reported a total of 10.9 million zero-vehicle households and such
households are concentrated in the northeast United States. While some
zero-vehicle households may be able to rely on friends, neighbors, or
extended families to evacuate in emergencies, this population is likely
to depend on government assistance to evacuate.
**[Geographic Areas]{.underline}**
This study focused on metropolitan areas (as defined by the U.S. Census)
because many natural and man-made disasters affect entire regions. The
study examined data from the 2000 census to identify metropolitan areas
with both high total numbers and high proportions of the study's focus
populations. The regions selected for study ranked among the top 20
metropolitan statistical areas in at least five of the following
categories:
1. The total number of minority persons residing in the region
2. The proportion of total persons in the region who are members of
minority groups
3. The total number of low-income persons residing in the region
4. The proportion of total persons in the region who are low income
5. The total number of persons in the region with limited English
proficiency
6. The proportion of total persons in the region with limited English
proficiency
7. The total number of households in the region without vehicles
8. The proportion of total households in the region without vehicles
The region selection also reflected an intention to study areas in
geographically diverse parts of the country, with large, mid-sized, and
small populations and that are particularly vulnerable to natural
disasters, such as hurricanes, earthquakes, floods, forest fires, and
winter storms, and man-made disasters, such as industrial accidents and
terrorist attacks.
This screening resulted in the selection of the following metropolitan
regions (the regions are presented in this section and in the remainder
of the report and Appendix, geographically from the west to east):
1. Honolulu, HI Core-Based Statistical Area (CBSA)
2. San Jose-San Francisco-Oakland, CA Core Statistical Area (CSA)
3. Los Angeles-Long Beach-Riverside, CA CSA
4. Seattle-Bellevue-Tacoma, WA CSA
5. Flagstaff, AZ CBSA
6. Brownsville-Harlingen, TX CBSA
7. Houston-Baytown-Huntsville, TX CSA
8. Lafayette, LA CBSA
9. Pine Bluff, AR CBSA
10. St. Louis, MO-IL CBSA
11. Chicago-Naperville-Joliet, IL-IN-WI CSA
12. Atlanta-Sandy Springs-Marietta, GA CBSA
13. Albany, GA CBSA
14. Pittsburgh, PA CBSA
15. Miami-Ft. Lauderdale-Miami Beach, FL CBSA
16. Washington-Baltimore-Northern Virginia, DC-MD-VA-WV CSA
17. Philadelphia-Camden-Vineland, PA, NJ, DE-MD CSA
18. New York-Newark-Bridgeport, NY-NJ-CT-PA CSA
19. Boston-Worchester-Manchester, MA-NH CSA
20. San Juan-Caguas-Fajardo, PR CSA
Of the 20 metropolitan areas selected for study six regions have
populations of less than 1 million people, 12 have populations of
between 1 million and 10 million, and two regions (Los Angeles and New
York) have populations of over 10 million. The median population of the
metropolitan areas is 3,604,165. The region's total geographic area
ranges from 604 square miles in the case of Honolulu CBSA to over 18,000
miles for the Flagstaff CBSA. Additional data on these regions are
presented in this report's Appendix A and accompanying metropolitan area
profiles.
**[FTA Recipients]{.underline}**
[]{.mark}
FTA assessed the emergency preparedness programs and activities of its
three primary grant recipients: public transportation providers,
metropolitan planning organizations (MPO), and state departments of
transportation (State DOT). It is important to note that in emergency
situations it is not these agencies but the local government
authorities, usually the city or county emergency management agency,
that provide initial response capabilities. Local government emergency
management agencies are responsible for coordinating the other entities
that have responsibilities during a crisis and the local political
executive has the authority to issue an evacuation order. At the same
time, transit agencies, MPOs, and State DOTs have the potential to play
important roles in an emergency and some of these entities have provided
important support in past events. (A complete list of the agencies that
were examined for this report is included in Appendix B.)
>
**State departments of transportation** are usually the primary agency
for their state's emergency support function (ESF) #1 (Transportation).
State DOTs provide technical assistance and resources to local
governments prior to an emergency and provide transportation resources
in the event that local resources become overwhelmed in an emergency.
State DOTs may provide resources to local and state governments in
neighboring jurisdictions through mutual assistance agreements and the
Emergency Management Assistance Compact (EMAC). State DOTs typically
collect and analyze traffic information, provide evacuation route plans,
conduct traffic incident management with first responders and local law
enforcement, and order and provide traffic operations resources to
support evacuation and other movement coordination.
**Metropolitan planning organizations** generally have information that
could be useful for evacuation planning, including demographic data,
roadway capacity data, information on planned roadway and transit
improvements, and traffic count data, as well as transportation modeling
capabilities to predict traffic congestion. Some MPOs may also have the
responsibility to support the State DOT, local government, and/or
emergency management agency in evacuation modeling. In addition, some
MPOs are also operational organizations that may coordinate transit
services and have other resources to assist in evacuations. Because the
impacts of many man-made and natural disasters are experienced at the
regional level, MPOs could act as a forum where local agencies
coordinate with their regional counterparts.
**Transit agencies** are a potential source of vehicles and personnel
during emergencies.[^11] Agency staff and vehicles could be used to
transport people from an affected area to shelters or to designated
staging areas for intercity transportation, if necessary. Transit
agencies that provide fixed-route service are also required to provide
complementary paratransit service for eligible persons with
disabilities, and these providers have information on the locations and
mobility needs of their clients. The ability of transit agencies to
participate in evacuations will vary depending on the nature of the
emergency, whether local agencies have advance warning of the event,
whether the affected population is within the transit agency's service
area, and whether local planning and coordination has taken place within
the transit agency and between the agency and local stakeholders.
Researchers for this study sought to obtain information from 18 State
DOTs, 20 MPOs, and 34 transit agencies that serve the 20 metropolitan
regions selected for study. (A list of agencies where information
requests were made is included in Appendix B to this report.)[^12]
**IV. Study Methodology**
[]{.mark}
This study took place between June 2006 and January 2007 and consisted
of the following steps:
[]{.mark}
**[Metropolitan Area Profiles]{.underline}**
Researchers prepared demographic profiles for each of the 20 regions
selected for study. The profiles are designed to identify the
transportation resources in each region, the types of disasters that
have affected the regions in the past or may occur in the region in the
future, and any populations that might be particularly at risk during an
emergency and can be found at
<http://www.fta.dot.gov/civilrights/civil_rights_6343.html>.
Each profile contains the following information:
[]{.mark}
> 1\. The geographic boundaries of the region and the political
> jurisdictions that comprise the region
>
> 2\. The state department(s) of transportation, metropolitan planning
> organization(s), and transit agencies serving the region
>
> 3\. The number and proportion of minority, low-income, and limited
> English proficient persons residing in the region, including any areas
> within the region where the proportion of minority and low-income
> residents is greater than the regional average
>
> 4\. Geographic Information Systems (GIS) maps highlighting areas where
> the proportion of minority, low-income, and limited English proficient
> residents is greater than the regional average overlaid on a map of
> the transit routes serving these areas
>
> 5\. The number and proportion of households without vehicles available
> and areas within the region where the proportion of households without
> vehicles available is greater than the regional average
>
> 6\. GIS maps that highlight areas where the proportion of households
> without vehicles available is greater than the regional average
> overlaid on a map of the transit routes serving these areas
>
> 7\. Correlation tables of minority persons, low-income persons,
> limited English proficient persons, and households without vehicles
>
> 8\. A brief description of the natural and/or man-made disasters that
> have directly affected the region in the past 20 years
>
> 9\. A description of which types of natural and/or man-made disasters
> are most likely to affect the region in the future[^13]
**[Emergency Plan Reviews]{.underline}**
Based on the information collected in the metropolitan area profiles,
researchers attempted to identify and obtain any emergency preparedness
plans or information documents produced by the State DOTs, MPOs, and
transit agencies in the regions. Researchers searched agency websites
for emergency preparedness information and contacted agencies that did
not have such information on their website with an invitation to share
any emergency preparedness plans with FTA. The FTA Office of Civil
Rights informed these agencies that it was producing a technical
assistance report and was not conducting a compliance review or
investigating a complaint of discrimination.
The FTA Office of Civil Rights also communicated that it was not asking
the recipients to provide any sensitive security information in response
to this request.
Researchers reviewed agency emergency preparedness plans for information
on the following six topics:
> 1\. Any public involvement process that contributed to the agency's
> emergency preparedness plan and, in particular, any opportunities for
> minority, low-income, and LEP persons and households without vehicles
> to participate in this process.
>
> 2\. The extent to which unique emergency response needs for each of
> the above groups were identified and accounted for.
>
> 3\. Any provisions for communicating the emergency plan and emergency
> preparedness instructions to the public and, in particular, any
> provisions to communicate emergency information to minority,
> low-income, and LEP persons and households without vehicles.
>
> 4\. Any provisions for evacuating persons in emergency situations and,
> in particular, evacuation procedures that address the needs of
> minority, low-income, and LEP persons and households without vehicles.
>
> 5\. Any provisions to use the region's transit system or coordinated
> human services transportation to assist in an evacuation prior to or
> following an emergency, and use of transit and coordinated human
> services transportation to return people to their communities after
> the emergency has ended and it is safe to return.
>
> 6\. Any provisions for coordinating emergency preparedness with
> relevant local, state, and federal agencies and, in particular, any
> coordination plans that focus on emergency preparedness for minority,
> low-income, and LEP persons and households without vehicles.
**[Follow-Up Interviews with Selected Agencies]{.underline}**
After reviewing the emergency preparedness information that was either
published on-line or provided by the agencies, researchers invited
representatives from nine State DOTs, nine MPOs, and nine transit
agencies to discuss their emergency preparedness, disaster response, and
disaster recovery plans in greater detail. These interviews, which were
conducted via phone and e-mail, were designed to clarify existing agency
plans and identify effective or promising practices that could be shared
with other FTA grantees.
**V. Overview of the Metropolitan Area Demographics**
The 20 metropolitan areas in this study are home to thousands of
low-income racial and ethnic minorities without ready access to private
transportation and whose demographics mirror the thousands of New
Orleanians who remained in the city during and after the Hurricane
Katrina disaster. Many of these people live in high-poverty
neighborhoods similar to New Orleans' Lower Ninth Ward and may be
especially vulnerable in an emergency because of the social isolation,
degraded infrastructure, high crime rates, low population density, and
other social problems common to many high-poverty urban
neighborhoods.[^14]
This chapter provides an overview of the information contained in the
metropolitan area profiles prepared for this study and includes the
following findings:
- Most of the metropolitan areas contain neighborhoods with high
levels of racial segregation. Thirteen of the 20 areas contain
census tracts where the proportion of minority persons was at least
twice the average for the region and 12 out of 20 areas contained
census tracts where racial and ethnic minorities comprised 80% to
100% of the population of that tract.
- Most of the metropolitan areas also contain neighborhoods with
concentrated poverty. Fifteen of the 20 areas contain census tracts
where the proportion of persons below the poverty line was twice the
average for the metropolitan area. Fourteen of 20 metropolitan areas
include census tracts where the proportion of persons living below
the poverty line is at least 40%.
- Ten of the 20 metropolitan areas include census tracts where the
proportion of LEP persons is at least 40%.
- Fifteen of the 20 metropolitan areas contain census tracts where at
least 40% of the households are without vehicles. These areas
consist of the 14 metropolitan areas with populations of 1 million
or more as well as the Honolulu Hawaii metropolitan area.
- There appears to be a great deal of geographic overlap between the
neighborhoods with high levels of racial segregation, concentrated
poverty, and zero-vehicle households.
- The metropolitan regions with populations of 1 million or more have
extensive transit coverage and most of the census tracts with high
proportions of low-income persons and households without vehicles
reside within the public transit service area.
- The metropolitan areas with populations of under 1 million have less
extensive public transit coverage and a number of census tracts in
these regions with relatively high proportions of households without
vehicles may not have easy access to public transportation.
- All of the metropolitan areas have experienced a wide range of
natural or man-made disasters in recent years, including severe
storms, tornados, flooding, hurricanes, earthquakes, fires, severe
winter weather, heat waves, and terrorist attacks. No one type of
disaster predominates across the 20 metropolitan areas.
The remainder of this chapter details the results of the demographic
analysis of the metropolitan areas studied.
**[Summary of Demographic Information]{.underline}**
The table below summarizes the demographic information developed and
utilized during this study for the 20 regions. For the purpose of
comparison, statistics for the United States and for pre-Katrina New
Orleans are also provided in this and the following tables.
Table V-1: Summary of Demographic Information Based on Arithmetic Mean
of Census Tracts
+------+---+---------+---------+---------+----------+--------+----------+
| ** | | **R | **Popul | **M | * | **P | * |
| Regi | | egion** | ation** | inority | *Limited | ercent | *Percent |
| on** | | | | Pop | English | of | of |
| | | * | | ulation | Pro | Popu | Zero-Car |
| ** | | *Name** | | (%)** | ficiency | lation | Hous |
| Numb | | | | | Po | Below | eholds** |
| er** | | | | | pulation | Pov | |
| | | | | | (%)** | erty** | |
+======+===+=========+=========+=========+==========+========+==========+
| | | United | 281, | 25% | 8% | 12% | 10% |
| | | States | 421,906 | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| | | **New | 1, | 43% | 3% | 18% | 15% |
| | | Orl | 316,510 | | | | |
| | | eans-Me | | | | | |
| | | tairie- | | | | | |
| | | Kenner, | | | | | |
| | | LA | | | | | |
| | | ( | | | | | |
| | | 2000)** | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 1 | | Ho | 876,151 | 77% | 14% | 11% | 12% |
| | | nolulu, | | | | | |
| | | HI | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 2 | | San | 7, | 40% | 17% | 9% | 10% |
| | | Jose | 088,410 | | | | |
| | | -San | | | | | |
| | | Fran | | | | | |
| | | cisco-O | | | | | |
| | | akland, | | | | | |
| | | CA | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 3 | | Los | 16, | 44% | 24% | 15% | 11% |
| | | Angel | 365,553 | | | | |
| | | es-Long | | | | | |
| | | Be | | | | | |
| | | ach-Riv | | | | | |
| | | erside, | | | | | |
| | | CA | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 4 | | Sea | 3, | 20% | 6% | 9% | 7% |
| | | ttle-Be | 604,165 | | | | |
| | | llevue- | | | | | |
| | | Tacoma, | | | | | |
| | | WA | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 5 | | Fla | 116,320 | 34% | 11% | 17% | 7% |
| | | gstaff, | | | | | |
| | | AZ | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 6 | | B | 335,227 | 20% | 37% | 34% | 12% |
| | | rownsvi | | | | | |
| | | lle-Har | | | | | |
| | | lingen, | | | | | |
| | | TX | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 7 | | Housto | 4, | 30% | 15% | 14% | 9% |
| | | n-Bayto | 815,122 | | | | |
| | | wn-Hunt | | | | | |
| | | sville, | | | | | |
| | | TX | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 8 | | Laf | 239,086 | 30% | 5% | 17% | 10% |
| | | ayette, | | | | | |
| | | LA | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 9 | | Pine | 107,341 | 49% | 1.2% | 18% | 10% |
| | | Bluff, | | | | | |
| | | AR | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 10 | | St. | 2, | 26% | 2% | 12% | 11% |
| | | Louis, | 698,687 | | | | |
| | | MO-IL | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 11 | C | | 9, | 38% | 11% | 13% | 17% |
| | h | | 302,726 | | | | |
| | i | | | | | | |
| | c | | | | | | |
| | a | | | | | | |
| | g | | | | | | |
| | o | | | | | | |
| | - | | | | | | |
| | N | | | | | | |
| | a | | | | | | |
| | p | | | | | | |
| | e | | | | | | |
| | r | | | | | | |
| | v | | | | | | |
| | i | | | | | | |
| | l | | | | | | |
| | l | | | | | | |
| | e | | | | | | |
| | - | | | | | | |
| | J | | | | | | |
| | o | | | | | | |
| | l | | | | | | |
| | i | | | | | | |
| | e | | | | | | |
| | t | | | | | | |
| | , | | | | | | |
| | I | | | | | | |
| | L | | | | | | |
| | - | | | | | | |
| | I | | | | | | |
| | N | | | | | | |
| | - | | | | | | |
| | W | | | | | | |
| | I | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 12 | A | | 4, | 40% | 6% | 11% | 10% |
| | t | | 247,981 | | | | |
| | l | | | | | | |
| | a | | | | | | |
| | n | | | | | | |
| | t | | | | | | |
| | a | | | | | | |
| | - | | | | | | |
| | S | | | | | | |
| | a | | | | | | |
| | n | | | | | | |
| | d | | | | | | |
| | y | | | | | | |
| | S | | | | | | |
| | p | | | | | | |
| | r | | | | | | |
| | i | | | | | | |
| | n | | | | | | |
| | g | | | | | | |
| | s | | | | | | |
| | - | | | | | | |
| | M | | | | | | |
| | a | | | | | | |
| | r | | | | | | |
| | i | | | | | | |
| | e | | | | | | |
| | t | | | | | | |
| | t | | | | | | |
| | a | | | | | | |
| | , | | | | | | |
| | G | | | | | | |
| | A | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 13 | A | | 157,833 | 54% | 1.4% | 23% | 14% |
| | l | | | | | | |
| | b | | | | | | |
| | a | | | | | | |
| | n | | | | | | |
| | y | | | | | | |
| | , | | | | | | |
| | G | | | | | | |
| | A | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 14 | P | | 2, | 13% | 16% | 12% | 15% |
| | i | | 431,087 | | | | |
| | t | | | | | | |
| | t | | | | | | |
| | s | | | | | | |
| | b | | | | | | |
| | u | | | | | | |
| | r | | | | | | |
| | g | | | | | | |
| | h | | | | | | |
| | , | | | | | | |
| | P | | | | | | |
| | A | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 15 | M | | 5, | 28% | 19% | 14% | 11% |
| | i | | 007,564 | | | | |
| | a | | | | | | |
| | m | | | | | | |
| | i | | | | | | |
| | - | | | | | | |
| | F | | | | | | |
| | t | | | | | | |
| | . | | | | | | |
| | L | | | | | | |
| | a | | | | | | |
| | u | | | | | | |
| | d | | | | | | |
| | e | | | | | | |
| | r | | | | | | |
| | d | | | | | | |
| | a | | | | | | |
| | l | | | | | | |
| | e | | | | | | |
| | - | | | | | | |
| | M | | | | | | |
| | i | | | | | | |
| | a | | | | | | |
| | m | | | | | | |
| | i | | | | | | |
| | B | | | | | | |
| | e | | | | | | |
| | a | | | | | | |
| | c | | | | | | |
| | h | | | | | | |
| | , | | | | | | |
| | F | | | | | | |
| | L | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 16 | W | | 7, | 40% | 6% | 9% | 14% |
| | a | | 572,647 | | | | |
| | s | | | | | | |
| | h | | | | | | |
| | i | | | | | | |
| | n | | | | | | |
| | g | | | | | | |
| | t | | | | | | |
| | o | | | | | | |
| | n | | | | | | |
| | - | | | | | | |
| | B | | | | | | |
| | a | | | | | | |
| | l | | | | | | |
| | t | | | | | | |
| | i | | | | | | |
| | m | | | | | | |
| | o | | | | | | |
| | r | | | | | | |
| | e | | | | | | |
| | - | | | | | | |
| | N | | | | | | |
| | o | | | | | | |
| | . | | | | | | |
| | V | | | | | | |
| | A | | | | | | |
| | , | | | | | | |
| | D | | | | | | |
| | C | | | | | | |
| | - | | | | | | |
| | M | | | | | | |
| | D | | | | | | |
| | - | | | | | | |
| | V | | | | | | |
| | A | | | | | | |
| | - | | | | | | |
| | W | | | | | | |
| | V | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 17 | P | | 5, | 28% | 5% | 11% | 15% |
| | h | | 883,585 | | | | |
| | i | | | | | | |
| | l | | | | | | |
| | a | | | | | | |
| | d | | | | | | |
| | e | | | | | | |
| | l | | | | | | |
| | p | | | | | | |
| | h | | | | | | |
| | i | | | | | | |
| | a | | | | | | |
| | - | | | | | | |
| | C | | | | | | |
| | a | | | | | | |
| | m | | | | | | |
| | d | | | | | | |
| | e | | | | | | |
| | n | | | | | | |
| | - | | | | | | |
| | V | | | | | | |
| | i | | | | | | |
| | n | | | | | | |
| | e | | | | | | |
| | l | | | | | | |
| | a | | | | | | |
| | n | | | | | | |
| | d | | | | | | |
| | , | | | | | | |
| | P | | | | | | |
| | A | | | | | | |
| | , | | | | | | |
| | N | | | | | | |
| | J | | | | | | |
| | , | | | | | | |
| | D | | | | | | |
| | E | | | | | | |
| | - | | | | | | |
| | M | | | | | | |
| | D | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 18 | N | | 21, | 39% | 16% | 13% | 29% |
| | e | | 361,785 | | | | |
| | w | | | | | | |
| | Y | | | | | | |
| | o | | | | | | |
| | r | | | | | | |
| | k | | | | | | |
| | - | | | | | | |
| | N | | | | | | |
| | e | | | | | | |
| | w | | | | | | |
| | a | | | | | | |
| | r | | | | | | |
| | k | | | | | | |
| | - | | | | | | |
| | B | | | | | | |
| | r | | | | | | |
| | i | | | | | | |
| | d | | | | | | |
| | g | | | | | | |
| | e | | | | | | |
| | p | | | | | | |
| | o | | | | | | |
| | r | | | | | | |
| | t | | | | | | |
| | , | | | | | | |
| | N | | | | | | |
| | Y | | | | | | |
| | - | | | | | | |
| | N | | | | | | |
| | J | | | | | | |
| | - | | | | | | |
| | C | | | | | | |
| | T | | | | | | |
| | - | | | | | | |
| | P | | | | | | |
| | A | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 19 | B | | 5, | 16% | 8% | 9% | 13% |
| | o | | 715,698 | | | | |
| | s | | | | | | |
| | t | | | | | | |
| | o | | | | | | |
| | n | | | | | | |
| | - | | | | | | |
| | W | | | | | | |
| | o | | | | | | |
| | r | | | | | | |
| | c | | | | | | |
| | h | | | | | | |
| | e | | | | | | |
| | s | | | | | | |
| | t | | | | | | |
| | e | | | | | | |
| | r | | | | | | |
| | - | | | | | | |
| | M | | | | | | |
| | a | | | | | | |
| | n | | | | | | |
| | c | | | | | | |
| | h | | | | | | |
| | e | | | | | | |
| | s | | | | | | |
| | t | | | | | | |
| | e | | | | | | |
| | r | | | | | | |
| | , | | | | | | |
| | M | | | | | | |
| | A | | | | | | |
| | - | | | | | | |
| | N | | | | | | |
| | H | | | | | | |
| | C | | | | | | |
| | S | | | | | | |
| | A | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| 20 | S | | 2, | 21% | 71% | 44% | 29% |
| | a | | 518,893 | | | | |
| | n | | | | | | |
| | J | | | | | | |
| | u | | | | | | |
| | a | | | | | | |
| | n | | | | | | |
| | - | | | | | | |
| | C | | | | | | |
| | a | | | | | | |
| | g | | | | | | |
| | u | | | | | | |
| | a | | | | | | |
| | s | | | | | | |
| | - | | | | | | |
| | F | | | | | | |
| | a | | | | | | |
| | j | | | | | | |
| | a | | | | | | |
| | r | | | | | | |
| | d | | | | | | |
| | o | | | | | | |
| | , | | | | | | |
| | P | | | | | | |
| | R | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
| | T | | **100, | **34,03 | **14,2 | ** | **5 |
| | o | | 445,861 | 4,895** | 39,582** | 11,842 | ,874,874 |
| | t | | 35%** | | | ,121** | 5%** |
| | a | | | **33%** | **14%** | | |
| | l | | | | | * | |
| | & | | | | | *11%** | |
| | A | | | | | | |
| | v | | | | | | |
| | e | | | | | | |
| | r | | | | | | |
| | a | | | | | | |
| | g | | | | | | |
| | e | | | | | | |
| | f | | | | | | |
| | o | | | | | | |
| | r | | | | | | |
| | 2 | | | | | | |
| | 0 | | | | | | |
| | r | | | | | | |
| | e | | | | | | |
| | g | | | | | | |
| | i | | | | | | |
| | o | | | | | | |
| | n | | | | | | |
| | s | | | | | | |
| | r | | | | | | |
| | e | | | | | | |
| | v | | | | | | |
| | i | | | | | | |
| | e | | | | | | |
| | w | | | | | | |
| | e | | | | | | |
| | d | | | | | | |
+------+---+---------+---------+---------+----------+--------+----------+
#
# For each of the areas summarized above, details of the demographics for each region and correlations among the populations examined are presented on the following pages.
**[Racial and Ethnic Minorities]{.underline}**
- The average minority population proportion across all 20 regions is
33%.
# The minority proportions range from 13% in Pittsburgh, PA, to 77% in Honolulu, HI.
# Ten out of 20 regions had census tracts where the proportion of minority persons was greater than the 33% 20-region average. Only one region has a proportion of minority persons that is more than double the 20-region average.
The following table ranks the 20 regions based on minority population
proportion.
**Table V-2: Minority Proportion Summary**
{width="6.0in" height="4.613194444444445in"}
**Map V-1: Honolulu, HI CBSA Minority Population**
# This map of the Honolulu, HI CBSA illustrates a region where 63% of the census tracts located in the CBSA have an above average percentage of minority population.
**[Persons with Low-Incomes]{.underline}**
#
# The average below poverty population proportion across all 20 regions is 11%.
# The low-income proportions range from 9% in the Boston, San Francisco, Seattle, and Washington, DC metropolitan areas to 44% in the San Juan metropolitan area.
# Twelve out of 20 regions had census tracts where the proportion of below poverty persons was greater than the 11% 20-region average.
The table on page 27 ranks the 20 regions based on below poverty
population proportion.
**Table V-3: Low-Income Population Summary**
-------------------------------------------- --------------------------
**Region** **Proportion Below
Poverty**
United States 12%
**New Orleans-Metairie-Kenner, LA (2000)** 18%
San Juan-Caguas-Fajardo, PR 44%
Brownsville-Harlingen, TX 34%
Albany, GA 23%
Pine Bluff, AR 18%
Flagstaff 17%
Lafayette, LA 17%
Los Angeles-Long Beach-Riverside, CA 15%
Miami-Ft. Lauderdale-Miami Beach, FL 14%
Houston-Baytown-Huntsville, TX 14%
New York-Newark-Bridgeport, NY-NJ-CT-PA 13%
Pittsburgh, PA 12%
St. Louis, MO-IL 12%
Philadelphia-Camden-Vineland, PA, NJ, DE-MD 11%
Honolulu, HI 11%
Atlanta-Sandy Springs-Marietta, GA 11%
Chicago-Naperville-Joliet, IL-IN-WI 10%
San Jose -San Francisco-Oakland, CA 9%
Seattle-Bellevue-Tacoma, WA 9%
Boston, MA 9%
Washington-Baltimore-No. VA, DC-MD-VA-WV 9%
-------------------------------------------- --------------------------
{width="3.375in" height="3.05625in"}
**Map V-2: St. Louis, MO-IL CSA Below Poverty Population**
The map of the St. Louis metropolitan area illustrates a region with
relatively low proportions of persons living below poverty in the
outlying areas but with neighborhoods in the urban core where up to 66%
of the persons are below the poverty line.
**[Persons with Limited English Proficiency]{.underline}**
# The average limited English proficient population proportion across all 20 regions is 14%.
# The limited English proportions range from 1.2% in Pine Bluff, AR to 71% in San Juan-Caguas, PR.
# Eight out of 20 regions had census tracts where the proportion of limited English proficient persons was greater than the 14% 20-region average. Only the San Juan-Caguas, PR region, which is a native-Spanish-speaking territory, has a proportion of limited English proficient persons that far exceeds the 20-region average. Brownsville- Harlingen, TX, located near the U.S.-Mexico border had an LEP proportion that was more than double the 20-region average.
The following table ranks the 20 regions based on limited English
proficient population proportion.
**Table V-4, LEP Proportion Summary**
#
#
#
#
# {width="6.25in" height="3.902083333333333in"}
# Map V-3: Los Angeles CSA LEP Population
# The map of the Los Angeles CSA illustrates a metropolitan area with some neighborhoods with high proportions of persons who may be LEP. The census tracts shaded in yellow have between 46% and 67% of persons who speak English less than "very well" and the tracts shaded in red have between 67% and 100% of the population who speak English less than "very well."
**[Zero-Car Households]{.underline}**
# The average zero-car household proportion across all 20 regions is 5%.
# The zero-car household proportions range from 7% in Seattle-Bellevue-Tacoma, WA and Flagstaff, AZ to 29% in the New York-Newark-Bridgeport, NY-NJ-CT-PA and San Juan-Caguas-Fajardo, PR CSAs.
# All 20 regions had census tracts where the proportion of zero-car households was greater than the 5% 20-region average. Thirteen of the regions had a proportion of zero-car households that was more than double the 20-region average.
The following table ranks the 20 regions based on zero-car household
proportion.
**Table V-5: Zero-Car Household Summary**
---------------------------------------- ------------------------------
**Region** **Proportion Zero-Car
Households**
United States 10%
**New Orleans-Metairie-Kenner, LA 15%
(2000)**
New York-Newark-Bridgeport, NY-NJ-CT-PA 29%
San Juan-Caguas-Fajardo, PR 29%
Chicago-Naperville-Joliet, IL-IN-WI 17%
Pittsburgh, PA 15%
Philadelphia-Camden-Vineland, PA, NJ, 15%
DE-MD
Washington-Baltimore-No. VA, DC-MD-VA-WV 14%
Albany, GA 14%
Boston-Worchester-Manchester, MA-NH CSA 13%
Honolulu, HI 12%
Brownsville-Harlingen, TX 12%
Los Angeles-Long Beach-Riverside, CA 11%
Miami-Ft. Lauderdale-Miami Beach, FL 11%
St. Louis, MO--IL 11%
Atlanta-Sandy Springs-Marietta, GA 10%
San Jose -San Francisco-Oakland, CA 10%
Pine Bluff, AR 10%
Lafayette, LA 10%
Houston-Baytown-Huntsville, TX 9%
Seattle-Bellevue-Tacoma, WA 7%
Flagstaff, AZ 7%
---------------------------------------- ------------------------------
**Map V-4: Baltimore, MD Zero-Car Households**
# 
#
#
# The above map from the Washington, DC-Baltimore metropolitan area is an example of a region where zero-vehicle households are concentrated in urban neighborhoods. Some Baltimore neighborhoods have between 44% and 100% of households without vehicles.
**[Correlations]{.underline}**
As discussed in the Methodology section, four demographic populations
taken from the census data (minority persons, low-income persons,
limited English proficient persons (LEP), and households without
vehicles available) were examined to determine if there were any
correlations among the data. The following charts compare each
individual demographic with the other three demographics used in the
study. The closer the correlation coefficient is to 1.0, the stronger
the correlation between the data. Using correlations, emergency
preparedness coordinators may be able to determine where and how they
may need to adjust or improve their preparedness plans to meet the needs
of the transit-dependent populations in their area.
The table below presents a summary of the correlation coefficients for
the demographic data examined as part of this study. The table columns
are arranged in descending order of the number of areas with
correlations over 0.50. These data are further discussed below.
**Table V-6: Summary of Correlation Coefficients -- Minority Population\
** (Correlations over 0.50 shown in **bold**)
-------------- ---------- ------------ ------------ ---------- ------------ ------------
**Region** **Below **Minority **Minority **Below **Minority **Zero-Car
Poverty -- -- Below -- Zero-Car Poverty -- -- LEP** HH -- LEP**
Zero-Car Poverty** HH** LEP**
HH**
Honolulu **0.57** 0.50 0.18 **0.58** **0.76** 0.50
San Jose **0.63** **0.51** 0.37 0.40 **0.73** 0.36
Los Angeles **0.68** **0.75** 0.45 **0.77** **0.79** 0.50
Seattle **0.62** **0.64** 0.34 **0.57** **0.89** 0.34
Flagstaff **0.76** **0.91** **0.65** 0.26 0.32 0.14
Brownsville **0.58** **0.65** 0.40 **0.83** **0.83** 0.47
Houston **0.82** **0.71** **0.57** **0.77** **0.65** **0.54**
Lafayette **0.79** **0.87** **0.78** **0.62** 0.31 0.27
Pine Bluff **0.83** **0.68** **0.65** 0.12 0.02 -0.01
St. Louis **0.79** **0.71** **0.60** 0.18 0.10 0.30
Chicago **0.82** **0.74** **0.70** 0.08 0.05 0.06
Atlanta **0.90** **0.63** **0.63** 0.13 0.15 0.05
Albany **0.68** **0.81** **0.64** -0.27 -0.06 0.16
Pittsburgh **0.71** **0.52** **0.60** 0.23 0.21 0.35
Miami **0.63** **0.66** 0.22 0.50 0.16 0.29
Washington, DC **0.76** **0.56** 0.42 0.19 0.41 0.09
Philadelphia **0.82** **0.79** **0.70** **0.61** 0.44 0.44
New York **0.65** **0.77** **0.57** **0.70** **0.63** **0.51**
Boston **0.73** **0.72** **0.57** **0.76** **0.76** **0.62**
San Juan **0.70** 0.42 0.41 **0.68** 0.49 0.44
Number of 20 18 12 10 8 3
Areas with
Correlations
\> 0.50
New Orleans **0.88** **0.75** **0.72** -0.13 -0.11 -0.13
-------------- ---------- ------------ ------------ ---------- ------------ ------------
- [Below Poverty Population and Zero-Car Households]{.underline} --
The table shows that below poverty population is most strongly
associated with zero-car households. All 20 areas show correlations
of over 0.50 between these two statistics. The correlation
coefficients range from a low of 0.57 (Honolulu, HI) to a high of
0.90 (Atlanta, GA).
- [Below Poverty and Minority Populations]{.underline} -- Below
poverty and minority populations also show correlations of over 0.50
among the areas examined. All but two of the areas in the study had
correlations above this range between these two statistics. The
lowest correlation among these 18 areas was observed in San Jose, CA
with a coefficient of 0.51 and the highest was observed in
Flagstaff, AZ with a coefficient of 0.91.
- [Minority Population and Zero-Car Households]{.underline} -- These
two statistics exhibit a correlation of over 0.50 in more than half
(12 of 20) of the areas. The correlation coefficients in these 12
areas appear to be clustered between 0.57 and 0.78. Furthermore, the
areas in which this stronger positive relationship is observed are
mostly in the Eastern and Midwest regions of the country.
- [Below Poverty and LEP Populations]{.underline} -- Half of the areas
examined in this study exhibit a correlation of over 0.50 between
below poverty and LEP populations. Correlation coefficients in these
10 areas range from a low of 0.58 (Honolulu, HI) to a high of 0.83
(Brownsville, TX).
- [Minority and LEP Populations]{.underline} -- Eight of the areas
showed a correlation of over 0.50 between minority and LEP
populations. The highest correlation coefficient (0.89) was observed
for Seattle, WA. Brownsville, TX also shows a particularly strong
positive correlation with a coefficient of 0.83.
- [Zero-Car Households and LEP]{.underline} -- Only three of the 20
areas showed a correlation of over 0.50 between zero-car households
and LEP population. These areas are: Boston, MA (0.62); Houston, TX
(0.54); and New York, NY (0.51).
By using correlations such as those discussed above, emergency
preparedness coordinators can identify how they can better serve the
needs of transportation-disadvantaged populations in their areas. For
example, they could ensure that emergency notices and broadcasts are
made in languages other than English in order to reach those populations
with limited English proficiency. Also, emergency planners can identify
areas in which not only transportation, but other resources might be
needed (e.g., temporary housing, emergency living expenses, and
relocation expenses).
**[Public Transportation Coverage]{.underline}**
Overall, most areas examined in this study have extensive public transit
coverage, particularly among the larger urban areas (e.g., New York,
Boston, Washington, Miami, Philadelphia, Pittsburgh, Los Angeles,
Seattle, and San Francisco-San Jose). These areas also tend to operate a
diverse mix of services---motorbus, paratransit, heavy rail, light rail,
and commuter rail. While there are pockets of census tracts with higher
than average minority, below poverty, and LEP populations and zero-car
households that are not served by public transit, most of the census
tracts fall within the transit service areas. An example of some of
these areas are described below:
- [Houston CSA]{.underline} -- Nearly all of Harris County is served
by transit. There are, however, small pockets of
transit-disadvantaged populations in the surrounding areas that are
not served by transit.
- [San Juan CSA]{.underline} -- There is a considerable concentration
of census tracts with higher than average minority and below poverty
populations and above average zero-car households in the transit
service area. Although many similar census tracts exist outside the
transit service area, these tend to be in the less densely populated
suburban and rural areas.
- [Atlanta CBSA]{.underline} -- The disadvantaged areas of DeKalb,
Fulton, and Clayton counties appear to be well served by transit
service from the different transit agencies that operate in the
region. The areas not served by transit tend to be distant from the
urban core and have relatively few census tracts with higher than
average transit-disadvantaged populations.
- [Pittsburgh CBSA]{.underline} -- The urban areas of Allegheny
County, including Pittsburgh, are served well by transit services.
As such, nearly all of the census tracts with minority and LEP
populations, and zero-car households are within the transit service
boundary. However, a relatively small number of below poverty census
tracts are located in the rural areas of Butler, Armstrong, and
Fayette counties outside the transit service boundary.
- [Honolulu CBSA]{.underline} -- Nearly all of the Island of Oahu is
served by the transit system. Only a sparsely populated area at the
island's interior lacks access to transit.
{width="1.5291666666666666in"
height="2.1458333333333335in"}
Map IV-5: Pittsburgh, PA CSA Zero-Car Population
The map of the Pittsburgh, PA CBSA illustrates a region where nearly all
of the census tracts with an above average percentage of zero-car
households are within the transit service boundary. As shown, the census
tracts with higher than average proportions of zero-car households are
predominately in the urban core, which is very well served by transit.
Transit service coverage is less extensive in the smaller urban areas,
particularly in the outlying communities. The smaller urban areas tend
to have fewer agencies providing transit service as well as a less
diverse mix of operations. The transit systems tend to provide only bus
and paratransit services. Examples of some of these areas are described
below:
- [Lafayette CBSA]{.underline} -- The areas to the south and east of
the city are not within the transit service boundary. These areas
also have a number of census tracts with higher than average
minority, below poverty, and LEP populations and to a lesser extent
zero-car households.
- [Brownsville-Harlingen CBSA]{.underline} -- There are a large
proportion of census tracts that are not within the transit service
area---24 of the 39 census tracts with above average minority
populations are outside the transit service boundary.
- [Pine Bluff CBSA]{.underline} -- This area also has a fair number of
census tracts that are not served by transit and also have above
average concentrations of minority, below poverty, and LEP
populations and zero-car households.
- [Flagstaff CBSA]{.underline} -- The transit service area is confined
to the urban core of the city. Large areas outside the urban center,
including areas with some of the highest concentrations of minority,
below poverty, and LEP populations and zero-car households, are not
served by the transit system.
{width="4.473611111111111in"
height="5.059722222222222in"}
**Map IV-6:** **Flagstaff, Arizona CBSA Zero-Car Population**
The map of the Flagstaff, AZ CBSA illustrates an area where many of the
census tracts with an above average percentage of zero-car households
are outside the transit service area.
While the transit service area is not necessarily a direct indicator of
a region's ability to adequately respond to an emergency incident, the
availability of transit assets and facilities may factor into a region's
response. As such, it is important for emergency planners to know which
communities within their region are potentially vulnerable and how the
regional assets and resources can be used to mitigate the negative
impacts of emergency incidents when they occur.
**[Vulnerabilities to Natural and Man-made Disasters]{.underline}**
The table below summarizes some of the identified occurrences of natural
and man-made disasters that have occurred in the regions of this study
over the past 10 years as well as the types of disasters for which the
metropolitan areas are most at risk.
**Table IV-7: Summary of Natural and Man-made Disasters**[^15]
--------------- ---------------------------- --------------------------
**Region** **Past Event** **Risk of Future Event**
Honolulu Wild fire, flood Earthquake
San Francisco Earthquake, wild fire, Earthquake
mudslide
Los Angeles Earthquake, wild fire, Earthquake
mudslide
Seattle Severe storm, flood, tornado Earthquake
Flagstaff Wild fire, flood, tornado Wild fire
Brownsville Hurricane, flood Hurricane
Houston Hurricane, flood, tornado Hurricane
Lafayette Hurricane Hurricane
Pine Bluff Severe storm, flood, tornado Severe storm
St. Louis Severe winter weather Winter weather, heat wave
Chicago Heat wave, severe winter Winter weather, heat wave
weather
Atlanta Severe storm Severe storm
Albany Severe storm, tornado Severe storm
Pittsburgh Severe storm, severe winter Severe storm, winter
weather weather
Miami Hurricane Hurricane
Washington DC Terrorist attack, hurricane Terrorist attack,
hurricane
Philadelphia Hurricane, severe winter Hurricane, severe winter
weather weather
New York Terrorist attack, blackout Terrorist attack,
hurricane
Boston Severe winter weather Hurricane, severe winter
weather
San Juan Hurricane Hurricane
--------------- ---------------------------- --------------------------
**VI. Results of the Agency Plan Assessment**
As noted in the Methodology section of this report, emergency response
plans
were obtained either through agency websites or by written request from
FTA's Office of Civil Rights. While researchers did not request any
sensitive security information, many agencies were nonetheless reluctant
to share information not currently available in the public domain, as it
was incorporated into their security plans. For this study, FTA
requested information on emergency response plans of 72 entities;
consisting of 18 State DOTs, 34 transit agencies, and 20 MPOs and
received information from 53 entities; consisting of 15 State DOTs, 25
transit agencies, and 13 MPOs was reviewed.
The table below presents the results of the analysis of emergency
preparedness activities on the six topics listed in the methodology
section.
**Table VI-1, Summary of Agency Survey Results**
------------------------------------------- --------- ------------ ----------
**Topic** **State **Transit **MPOs**
DOTs** Agencies**
1\. General Public Involvement 1 of 15 2 of 25 1 of 13
1a. Involvement on focus populations 0 of 15 0 of 25 0 of 13
2\. Accounting for the needs of focus 3 of 15 3 of 25 0 of 13
populations
3\. Communicating emergency Information to 11 of 15 14 of 25 3 of 13
the public
3a. Communicating to focus populations 0 of 15 3 of 25 2 of 13
4\. General Evacuation Planning 9 of 15 14 of 25 6 of 13
4a. Evacuation planning for focus 2 of 15 1 of 25 0 of 13
populations
5\. Use of the transit system in an 9 of 15 14 of 25 12 of 13
evacuation
6\. General Coordination Procedures 12 of 15 25 of 25 13 of 13
6a. Coordination activities targeted at 0 of 15 0 of 25 0 of 13
focus populations
------------------------------------------- --------- ------------ ----------
**[Topic #1: Public Involvement in Emergency Preparedness
Planning]{.underline}**
Researchers sought information on any public involvement process that
contributed to the agency's emergency preparedness plan and, in
particular, any opportunities for minority, low-income, and LEP persons
and households without vehicles to participate in this process.
Very few of the State DOTs, MPOs, or transit agencies surveyed sought to
involve the public in general or members of the focus populations of
this study in the course of assembling an emergency preparedness plan.
One State DOT does encourage general public involvement in the
development of local and regional plans, but does not specifically focus
on the populations that were a part of this study.
In some instances, plans produced by MPOs are made available to the
public through various means, including through publications, at public
meetings, and on their websites. The Metropolitan Washington Council of
Governments has as a goal in its National Capital Region Homeland
Security Strategic Plan to provide opportunities for individuals to
become involved in emergency preparedness.
Two transit agencies, Chicago Transit Authority and New York's
Metropolitan Transportation Authority (MTA), did note that they had
provided for comment and feedback from the public on the plan once it
was developed. (Because transit agencies were not generally the lead
agency in the local or regional emergency response plan, there typically
was no public input sought or utilized by transit agencies in developing
these emergency preparedness plans.)
**[Topic #2: Identifying the Needs of Focus Populations]{.underline}**
[]{.mark}
Researchers reviewed plans to determine the extent to which the plans
identified and responded to the unique needs of the focus populations.
None of the plans prepared by State DOTs, MPOs, or transit agencies
identified any specific mobility needs associated with racial and ethnic
minorities, persons with low-incomes, persons with disabilities, and
households without vehicles.
State DOT staff communicated to researchers that, in general, the county
or local government is responsible for managing logistics for special
needs groups and requesting additional transportation support from the
state if needed. The Arizona and Louisiana DOT included portions of
these groups in their plans, but did not provide information on the
numbers or locations of these populations. Arizona includes LEP persons
in its category of special needs and Louisiana includes
institutionalized and non-institutionalized persons. Additionally,
Louisiana includes persons without their own transportation in their
state planning.
California's Office of Emergency Services encourages the use of
community-based organizations to address the disabled, homeless,
elderly, children, non-English speakers, people living in poverty, and
people who are culturally or geographically isolated. However, it was
noted the focus was not on transportation, but primarily the
post-disaster needs of these vulnerable populations.
> []{.mark}
None of the MPOs had incorporated information on the focus populations
into
the emergency response plans in which they had a coordinating role. One
MPO did note that the area covered was culturally diverse, and one MPO
has as an action item to review Geographic Information System data in
support of its plan.
Among the transit providers, the City and County of Honolulu includes in
the group of primary evacuees, persons at home without cars and
non-drivers. The Chicago Transit Authority noted that it has identified
the rail lines that primarily serve minority communities, but that it
had limited additional information integrated into its plan. One transit
agency, New York's MTA, which has a major role in its city's evacuation
plan, noted that estimates on the number of people that would need
evacuation took into account income and access to a private vehicle.
Additionally, this agency noted that the public information on the
city's plan is available in 11 languages.
[]{.mark}
**[Topic #3: Communicating to the General Public and to Focus
Populations]{.underline}**
[]{.mark}
Researchers sought information on any provisions for communicating
emergency plan information and emergency preparedness instructions to
the public and, in particular, any provisions to communicate emergency
information to minority, low-income, and LEP persons and households
without vehicles.
[]{.mark}
Most State DOTs, MPOs, and transit agencies assessed had plans to
communicate emergency preparedness information to the general public,
but only a few of these agencies had plans for targeting emergency
communications to the focus populations of this study.
Eleven State DOTs indicated that they have plans to communicate with the
public prior to and during an emergency, but none of the State DOT
communications plans specifically addressed this report's focus
populations. It was noted during plan review and interviews that during
emergency events, DOTs may set up their own Emergency Operations Centers
(EOC), if appropriate, and coordinate with the state EOC through
appointed liaisons. In general, it was described that emergency
information generated by the DOT and meant for the public is typically
sent to the public information officer in the state EOC for
dissemination. The types of communications to the public included
information on the locations of the disaster and evacuation route
information. Five of the states described information on a process
similar to that described above.
[]{.mark}
Among the MPOs, San Francisco's Metropolitan Transportation Commission
has a role in testing the communications systems of the local area
transit systems and conducts an annual exercise to test information
dissemination from them to the public. The Metropolitan Washington
Council of Governments has as a goal in the National Capital Region
Homeland Security Strategic Plan to establish public emergency message
templates for disseminating information to special needs populations,
which include people with disabilities and non-English speakers.
[]{.mark}
Fourteen transit agencies provided information on providing emergency
information to the general public. Three agencies, Los Angeles County
Metropolitan Transportation Authority, New York's Metropolitan
Transportation Authority, and Chicago Transit Authority, noted their
ability to communicate in multiple languages in the event of an
emergency. While these agencies all noted that they were not the lead
coordinating agency, they did note their ability to communicate with the
public in multiple languages. New York's MTA and the Chicago Transit
Authority also cited their localities' use of a "311" phone number to
disseminate emergency information to the public and the staffing of
these call centers with bilingual personnel. New York's MTA also noted
its locality also has a website that makes emergency preparedness
materials available on the Internet in multiple languages.
[]{.mark}
**[Topic #4: Evacuation Planning for the General Public and Focus
Populations]{.underline}**
[]{.mark}
Researchers sought information on any provisions for evacuating persons
in emergency situations and, in particular, evacuation procedures that
address the needs of minority, low-income, and LEP persons and
households without vehicles.
Most agencies assessed had plans for evacuating the general public in
emergencies, but only a few agencies had plans targeted at evacuating
the focus populations. Nine of the State DOTs provided information on
coordinating either evacuation or sheltering aspects during an emergency
with transportation, and Arizona and Louisiana discussed those with
"special needs." Arizona includes LEP persons in its category of special
needs and Louisiana includes institutionalized and non-institutionalized
persons. Arizona included in its Evacuation ESF, for which the DOT is a
support agency, the need to ensure that at the county or local level,
consideration be given to ensuring that persons with special needs,
including LEP persons, are identified, located, and evacuated.
None of the MPO plans reviewed focused on the evacuation or sheltering
of the focus populations, however, information from six of the agencies
reviewed included evacuation and sheltering in general for emergencies.
[]{.mark}
Transit agencies expressed that they have a key role in the
transportation services for evacuation and safe return, but coordination
is generally managed by the local or regional lead agency. One agency,
New York's MTA, did utilize the local area's projected numbers of
evacuees, which took into account income and access to a private
vehicle, along with its own demographic and system information to
develop detailed information on where service may need to be enhanced to
facilitate an evacuation. Its plan also included providing increased
personnel at key locations to control crowds and provide customer
information.
> []{.mark}
**[Topic #5: Use of Public Transportation in Emergencies]{.underline}**
Researchers sought information on any provisions to use the region's
transit system or coordinated human services transportation to assist in
an evacuation prior to or following an emergency, and use of transit and
coordinated human services transportation to return people to their
communities after the emergency has ended and it is safe to return.
The majority of agencies assessed indicated that the transit system
would play a role in an emergency evacuation.
Nine State DOTs provided information on using transit in evacuations.
Most DOTs examined divide their states into DOT districts, each having
its own administrative headquarters. The districts are typically
responsible for coordinating availability, procurement, and use of
transit assets with local entities such as transit agencies and school
districts, and evacuation routes with local jurisdictions. Memoranda of
understanding and other agreements, usually managed by the DOTs or the
states, are in place with local jurisdictions, transit agencies, and
private/public transportation entities for agreement on transit assets
availability to the partnering agencies as needed.
Twelve MPOs included information on how public transit and other
transportation functions would be coordinated in an emergency. Most of
the plans, even those in draft form, provide an inventory of
transportation assets or have made provisions to include them in future
drafts of their plans. In addition, 14 of the transit agencies provided
specific information on their roles in an emergency.
**[Topic #6: Interagency Coordination]{.underline}**
[]{.mark}
Researchers sought information on any provisions for coordinating
emergency preparedness with relevant local, state, and federal agencies
and, in particular, any coordination plans that focus on emergency
preparedness for minority, low-income, and LEP persons and households
without vehicles. The majority of agencies that were assessed, including
all the MPOs and all the transit agencies that provided information to
the researchers, indicated that they had procedures in place for
coordinating with other agencies prior to and during an emergency, but
none of the agencies had coordination measures in place that focused on
emergency preparedness for the focus populations.
[]{.mark}
[]{.mark}
> []{.mark}
**[VII.]{.smallcaps} Promising Practices**
Although most State DOTs, MPOs, and transit agencies had few specific
policies and procedures in place for responding to the specific needs of
racial and ethnic minorities, low-income or LEP populations, and
households without vehicles, researchers identified a number of
promising practices developed by the agencies that were assessed and
have the potential to be implemented in other metropolitan areas. This
section summarizes such practices being developed or implemented by
State DOTs, MPOs, and transit agencies.
**[State Departments of Transportation]{.underline}**
In general, the decentralization of DOT emergency management functions
among territorial districts enables DOTs to better coordinate transit
asset utilization among county and local governments, transit agencies,
school districts, and public/private transportation companies. This also
can promote emergency management response with the establishment of an
Emergency Operations Center in close proximity to the impact area and
could be adopted by other agencies.
Memorandums of understanding or similar agreements among parties ensure
full knowledge of assets available to potential impact areas, and assure
the parties of full cooperation should their area be affected by an
emergency event. Arizona's ESF-15 (Evacuation), for which Arizona DOT is
a support agency, includes a concept of operations that is the
responsibility of county and local governments (another set of ESF-15
support agencies). The concept states, "Consideration will be given to
ensuring that special needs persons, i.e., non-English speaking,
elderly, physically or mentally disabled, latchkey children, etc., are
identified, located and evacuated from the danger area."
[]{.mark}
While there was not wide evidence of specific considerations of
emergency services for households without vehicles addressed in State
DOT plans, the State of Louisiana's Emergency Operations plan designates
Louisiana DOTD as responsible for ESF-1 (Transportation). Attachment 8
to ESF-1 provides a general framework for Bus Staging
Operations/Movement Control Center for ESF-1. The goal of Attachment 8
is to provide bus transportation for persons needing assistance
evacuating from risk parishes, including special needs individuals.
[]{.mark}
**[Metropolitan Planning Organizations]{.underline}**
While MPOs are not typically the lead agency in emergency response plan
development, several of them appear to be developing or assisting in the
coordination of these plans. For example, the Metropolitan
Transportation Commission in the San Francisco region is involved in
coordinating the region's plan and the East West Gateway Coordinating
Council in the St. Louis region is developing a plan for which it
expects to have an outline completed in early 2007.
The Metropolitan Washington Council of Governments provided information
on extensive emergency plan coordination that it has performed in its
region which includes a Community Engagement objective and initiatives
on participation, education, and communication to be completed through
2009.
**[Transit Agencies]{.underline}**
Some transit agencies are coordinating with state, county, and/or local
emergency agencies and other emergency management partners to prepare to
respond to populations with specific needs in an emergency. Miami-Dade
Transit has representatives from bus and rail operations to act as
liaisons to the appropriate city or county emergency operations center.
AC Transit coordinates with county-level emergency response providers,
and MTC has an emergency preparedness committee that works with local
transit operators to help test emergency response plans. Sound Transit
cited integration into regional and cross-jurisdictional planning
activity as an effective practice for its agency.
Additionally, ongoing unified command training and operations among
emergency management partners can serve to strengthen the effectiveness
of emergency response plans. Chicago Transit Authority participates in
unified command training and operations with governmental agencies, and
coordinates with the City of Chicago, Cook County, Chicago Fire and
Police departments, and the 40 suburban municipalities served by the
authority.
[]{.mark}
One of the most far-reaching plans was prepared by the New York City
Office of Emergency Management (OEM) and was provided by the
Metropolitan Transportation Authority. OEM contracted with U.S. Army
Corps of Engineers to conduct analyses detailing the number of persons
and the demographics of the people who would have to be evacuated for
three scales of emergency, and developed an evacuation and sheltering
plan that is scalable according to the severity of the event. Public
transportation is a key component of the New York City plan. The
Metropolitan Transportation Authority has developed operating plans in
support of the New York City Coastal Storm Plan that incorporate the
analysis provided by OEM. []{.mark}
[]{.mark}
New Yorkers can learn their assigned evacuation center by calling 311,
the Citizen Service Center, which can provide assistance in 170
languages. Additionally, maps of the city's evacuation centers are
available in 11 languages on OEM's website at
[NYC.gov/oem](http://nyc.gov/html/oem/html/home/home.shtml). MTA NYC
Transit provided travel directions from evacuation zones to evacuation
centers for use by 311 and for the City's online Hurricane Evacuation
Zone Finder tool hosted on OEM's website (available in English only).
Printed materials are also provided by OEM in multiple languages; for
example, the Ready New York household preparedness guide is available in
ten languages.
[]{.mark}
The Los Angeles County Metropolitan Transportation Authority addresses
emergency concerns of LEP persons using announcements in other than
English. The agency also has a staff of translators available through
telephone. New York City has addressed emergency needs of LEP persons as
well.
For the regions reviewed, the lead agencies for emergency management
response are typically responsible for communications plans. Transit
agencies generally provide a supporting role to these agencies regarding
the transportation components of plans developed on the regional/local
level. An increased use of the Internet as a communication tool was
noted in many regions. Additionally, emergency response campaigns, such
as the "Ready New York" efforts are becoming more prevalent to prepare
communities for differing types of communities.
### VIII. Conclusions and Recommendations
The twenty metropolitan areas surveyed in this report have neighborhoods
where large
numbers of people may have difficulty evacuating in advance of or in the
aftermath of a natural or man-made emergency. Each of the metropolitan
areas surveyed includes racially segregated high-poverty areas with
relatively high proportions of people with limited English proficiency
and zero-vehicle households. In the event of an emergency, many of the
residents of these neighborhoods may be more likely to discount
emergency instructions or may not have the money or the mobility to
evacuate independently.
Most of those neighborhoods with higher than average proportions of
minority, low-income, and LEP persons and zero-vehicle households were
well served by existing public transportation agencies, which, in theory
and depending on the circumstances of the emergency, could play a role
in evacuating people without other means of transportation. However most
of the transit agencies as well as the metropolitan planning
organizations and state departments of transportation surveyed in this
report had taken limited steps to address the needs of these populations
in an emergency.
In general, emergency response procedures of the focus agencies of this
study do not routinely or systematically address the needs of the focus
populations of this review.
Many states, regions, and transit agencies have not thoroughly
identified these transportation-disadvantaged populations within their
areas. The inclusion of evacuation, sheltering, and return
considerations for these populations in emergency response plans could
be greatly enhanced.
**[Recommendations]{.underline}**
- **Demographic profiles should be developed and incorporated into
emergency response plans.** No matter who is the lead agency for
developing the plans, an understanding of the populations that
comprise the subject area of the plan would greatly improve the
plans' applicability and effectiveness. Knowledge of the number and
location of transportation-disadvantaged populations during an
emergency is essential in evaluating if current assets or deployable
assets will be available and adequate.
> The demographic profiles prepared in conjunction with this report (and
> which are located at
> <http://www.fta.dot.gov/civilrights/civil_rights_6343.html>) can
> assist agencies in estimating the number of people who may not be able
> to self-evacuate, in planning evacuation routes and staging areas, and
> in conducting targeted community outreach on emergency preparedness.
- **Strategies should be developed for more public input into the
establishment of the plans.** There are sources of knowledge within
communities on the particular needs of the
transportation-disadvantaged. In addition to those noted in other
reports, such as faith-based organizations, there are networks of
community-based organizations that serve disadvantaged populations
and could provide valuable input into the emergency response,
evacuation, sheltering, and return plans of local areas. Developing
ways for these organizations to be involved in plan development
would add to the sufficiency of these plans and the ability to carry
them out.
- **Strategies should be developed for effective communication of the
plans.** Knowing the concentrations of limited English proficiency
populations and what their communications needs are will aid in the
ability to communicate effectively with these populations during an
emergency. Using demographic data and outreach to community-based
organizations will aid in the plans' overall effectiveness.
- **Transit agencies should improve emergency management and response
communication and coordination with county and state emergency
management agencies.** In several instances during the study,
transit agencies could not clearly define their role in the event of
an emergency, beyond internal procedures. Because there is a wide
range of types of agencies that lead the development and enactment
of emergency response plans, transit agencies should be certain of
their role in the event of emergencies, understand the command and
control procedures for their assets, and provide input using the
knowledge they have on moving the public.
> These recommendations are similar to the guidance developed in the
> special needs section of FTA's Disaster Response and Recovery Manual,
> which was published in August of 2006, and the Transportation and
> Emergency Preparedness Checklist issued in September of 2006 by the
> National Consortium on Human Services Transportation. FTA's manual can
> be found at [http://www.fta.dot.gov](http://www.fta.dot.gov/) and the
> National Consortium's checklist and accompanying strategy paper can be
> found at
> [http://www.disabilityinfo.gov](http://www.disabilityinfo.gov/).
### IX. Resources
The links below connect the reader to source documents and other
resources summarized or referenced in this report. Additional
information on emergency preparedness, disaster response, and disaster
recovery activities can be found at the following links:
- The FTA Safety and Security web page at
<http://transit-safety.volpe.dot.gov/>
- The FTA Civil Rights web page at
<http://www.fta.dot.gov/civil_rights.html>
- The U.S. DOT web page on emergency transportation for people with
disabilities at
[http://www.emergencyprep.dot.gov](http://www.emergencyprep.dot.gov/)
- The FHWA emergency transportation web page at
<http://www.ops.fhwa.dot.gov/publications/publications.htm#eto>
**Links to Guidance**
- [DOT Title VI
Regulations](http://www.fta.dot.gov/documents/49_CFR_21.doc)\
<http://www.fta.dot.gov/documents/49_CFR_21.doc>.
- DOT [**Limited English Proficient Persons
Guidance**](http://a257.g.akamaitech.net/7/257/2422/01jan20051800/edocket.access.gpo.gov/2005/05-23972.htm)
[**http://a257.g.akamaitech.net/7/257/2422/01jan20051800/edocket.access.gpo.gov/2005/05-23972.htm**](http://a257.g.akamaitech.net/7/257/2422/01jan20051800/edocket.access.gpo.gov/2005/05-23972.htm).
- [**SAFETEA-LU**](http://www.fta.dot.gov/index_4696.html)
> [**http://www.fta.dot.gov/index_4696.html**](http://www.fta.dot.gov/index_4696.html).
- [**Section 504 of the Rehabilitation Act of
1973**](http://www.usdoj.gov/crt/ada/adahom1.htm)
> [**http://www.usdoj.gov/crt/ada/adahom1.htm**](http://www.usdoj.gov/crt/ada/adahom1.htm).
- [**Executive Order 13347, Individuals with Disabilities in Emergency
Preparedness**](http://www.whitehouse.gov/news/releases/2004/07/20040722-10.html)
> [**http://www.whitehouse.gov/news/releases/2004/07/20040722-10.html**](http://www.whitehouse.gov/news/releases/2004/07/20040722-10.html).
- [**Age Discrimination Act of
1975**](http://www.dol.gov/dol/topic/discrimination/agedisc.htm)
> <http://www.dol.gov/dol/topic/discrimination/agedisc.htm>.
- [**Americans with Disabilities Act of
1990**](http://www.usdoj.gov/crt/ada/adahom1.htm)
> [**http://www.usdoj.gov/crt/ada/adahom1.htm**](http://www.usdoj.gov/crt/ada/adahom1.htm).
Links to Related Reports
- [The Federal Response to Hurricane Katrina: Lessons
Learned](http://www.whitehouse.gov/reports/katrina-lessons-learned.pdf)
<http://www.whitehouse.gov/reports/katrina-lessons-learned.pdf>.
- [We Can Do Better -- Lessons Learned for Protecting Older Persons in
Disasters](http://assets.aarp.org/rgcenter/il/better.pdf)
> <http://assets.aarp.org/rgcenter/il/better.pdf>.
- [Strategies in Emergency Preparedness for Transportation-Dependent
Populations](http://www.dotcr.ost.dot.gov/Documents/Emergency/Emergency Preparedness Strategy Paper.doc)
[http://www.dotcr.ost.dot.gov/Documents/Emergency/Emergency
Preparedness Strategy
Paper.doc](http://www.dotcr.ost.dot.gov/Documents/Emergency/Emergency Preparedness Strategy Paper.doc).
- [National Workshop on Transportation
Equity](http://www.fta.dot.gov/documents/Masterdocument.doc)
<http://www.fta.dot.gov/documents/Masterdocument.doc>.
- [The Impact of Hurricanes Katrina and Rita on People with
Disabilities](http://www.ncd.gov/newsroom/publications/2006/pdf/hurricanes_impact.pdf)
<http://www.ncd.gov/newsroom/publications/2006/pdf/hurricanes_impact.pdf>.
- [Government Accountability Office--Disaster
Preparedness](http://www.gao.gov/new.items/d06790t.pdf)
<http://www.gao.gov/new.items/d06790t.pdf>.
- [Emergency Evacuation Report Card
2006](http://www.highways.org/pdfs/evacuation_report_card2006.pdf)
<http://www.highways.org/pdfs/evacuation_report_card2006.pdf>.
**Summaries of Other Related Materials**
- [Transit Agency Security and Emergency Management Protective
Measures](http://transit-safety.volpe.dot.gov/publications/security/ProtectiveMeasures/PDF/ProtectiveMeasures.pdf),
November 2006. This guidance, prepared by the Federal Transit
Administration in consultation with the Department of Homeland
Security Transportation Security Administration and the Office of
Grants and Training and the American Public Transportation
Association, provides a comprehensive approach for transit agencies
to integrate their entire security and emergency management programs
with the Department of Homeland Security Advisory System threat
conditions.
<http://transit-safety.volpe.dot.gov/publications/security/ProtectiveMeasures/PDF/ProtectiveMeasures.pdf>.
- [Disaster Response and Recovery Resource for Transit
Agencies](http://transit-safety.volpe.dot.gov/publications/safety/DisasterResponse/HTML/DisasterResponse.htm),
August 2006. Prepared for the Federal Transit Administration, this
report provides best practices and links to specific resources for
transit agencies concerning critical disaster elements such as
emergency preparedness, disaster response, and recovery.
> [http://transit-safety.volpe.dot.gov/publications/safety/DisasterResponse
> /HTML/DisasterResponse.htm](http://transit-safety.volpe.dot.gov/publications/safety/DisasterResponse /HTML/DisasterResponse.htm).
- [Memorandum from Norman T. Mineta, Emergency Preparedness for People
with Disabilities]{.underline}, August 2003. This memorandum
provides answers to basic questions about emergency preparedness and
the needs of people with disabilities in the Department of
Transportation.
<http://www.dotcr.ost.dot.gov/documents/dotpart/pwd_guidelines.htm>.
- [The Public Transportation System Security and Emergency
Preparedness Planning
Guide,](http://transit-safety.volpe.dot.gov/Publications/security/PlanningGuide.pdf)
January 2003. This guidance, prepared for the Federal Transit
Administration provides information to support the activities of
public transportation systems to plan for and respond to major
security threats and emergencies.
<http://transit-safety.volpe.dot.gov/Publications/security/PlanningGuide.pdf>.
- [U.S. Department of Transportation (DOT) Order
1900.9](http://www.dot.gov/ost/oet/1900-9.pdf), April 2000. This DOT
order describes the department's roles, responsibilities and actions
that apply to emergency transportation management during domestic
and national security emergencies.
<http://www.dot.gov/ost/oet/1900-9.pdf>.
- [Critical Incident Management
Guidelines](http://onlinepubs.trb.org/onlinepubs/security/FinalCrisisManagementGuidelines.pdf), 1998.
Prepared for the Federal Transit Administration, this document
provides comprehensive discussion of community activities necessary
to support emergency preparedness, mitigation, response, and
recovery.
<http://onlinepubs.trb.org/onlinepubs/security/FinalCrisisManagementGuidelines.pdf>.
- [Recommended Emergency Preparedness Guidelines for Urban Rural and
Specialized Transit
Systems](http://www.ctav.org/Downloads/Rec_Emer_Prep_For_Urban_Rural_Spec_Tran_Sys.pdf), 1991.
These guidelines, prepared for the Federal Transit Administration,
provide recommendations designed to assist transit system and
emergency response organization personnel to evaluate and modify
their emergency response plans to address the needs of urban, rural,
and specialized transit passengers.
<http://www.ctav.org/Downloads/Rec_Emer_Prep_For_Urban_Rural_Spec_Tran_Sys.pdf>.
[]{.mark}
### Appendix A
# Summary of Demographic Profiles
#
**Region 1: Honolulu, HI Core-Based Statistical Area (CBSA)**
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 604
Census Tracts 216
Total Population 876,151
Minority Population 689,668
Below Poverty Population 83,937
Population (5 years and older) 814,820
LEP Population (5 years and older) 113,550
Total Households 286,450
Zero-Car Households 36,614
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Honolulu, HI CBSA**
regional populations:
- correlation of 0.76 between minority and LEP populations
- correlation of 0.58 between below poverty and LEP populations
- correlation of 0.57 between below poverty populations and zero-car
households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.50 between minority and below poverty populations
```{=html}
<!-- -->
```
- correlation of 0.50 between LEP populations and zero-car households
- correlation of 0.18 between minority populations and zero-car
households
**Region 2: San Jose-San Francisco-Oakland, CA Core Statistical Area
(CSA)**
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 8,818.6
Census Tracts 1,465
Total CSA Population 7,088,410
Minority Population 2,923,892
Below Poverty Population 607,698
Population (5 years and older) 7,783,306
LEP Population (5 years and older) 1,147,090
Total Households 2,571,456
Zero-Car Households 254,141
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **San Jose -San
Francisco-Oakland, CA CSA** regional populations:
- correlation of 0.73 between minority and LEP populations
- correlation of 0.63 between below poverty populations and zero-car
households
- correlation of 0.51 between minority and below poverty populations
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.40 between below poverty and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.37 between minority populations and zero-car
households
```{=html}
<!-- -->
```
- correlation of 0.36 between LEP populations and zero-car households
#
# Region 3: Los Angeles-Long Beach-Riverside, CA CSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 34,000
Census Tracts 3,373
Total Population 16,365,553
Minority Population 7,344,772
Below Poverty Population 2,510,110
Population (5 years and older) 15,124,980
LEP Population (5 years and older) 3,707,686
Total Households 5,347,107
Zero-Car Households 537,885
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Los Angeles-Long
Beach-Riverside, CA CSA** regional populations:
- correlation of 0.79 between minority and LEP populations
- correlation of 0.77 between below poverty and LEP populations
- correlation of 0.75 between minority and below poverty populations
- correlation of 0.68 between below poverty populations and zero-car
households
Correlations between other populations that were below .50 are as
follows:
- correlation of 0.50 between LEP populations and zero-car households
```{=html}
<!-- -->
```
- correlation of 0.45 between minority populations and zero-car
households
#
# Region 4: Seattle-Bellevue-Tacoma, WA CSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 8,247
Census Tracts 784
Total Population 3,604,165
Minority Population 741,164
Below Poverty Population 303,090
Population (5 years and older) 3,368,005
LEP Population (5 years and older) 213,575
Total Households 1,410,381
Zero-Car Households 108,408
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the
**Seattle-Bellevue-Tacoma, WA CSA** regional populations:
- correlation of 0.89 between minority and LEP populations
- correlation of 0.64 between minority and below poverty populations
- correlation of 0.62 between below poverty populations and zero-car
households
- correlation of 0.57 between below poverty and LEP populations
Correlations between other populations that were below .50 are as
follows:
- correlation of 0.34 between minority populations and zero-car
households
```{=html}
<!-- -->
```
- correlation of 0.34 between LEP populations and zero-car households
# Region 5: Flagstaff, AZ CBSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 18,658
Census Tracts 27
Total Population 116,320
Minority Population 42,939
Below Poverty Population 20,609
Population (5 years and older) 107,876
LEP Population (5 years and older) 10,836
Total Households 40,448
Zero-Car Households 2,790
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Flagstaff CBSA**
regional populations:
- correlation of 0.91 between minority and below poverty populations
- correlation of 0.76 between below poverty populations and zero-car
households
- correlation of 0.65 between minority populations and zero-car
households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.32 between minority and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.26 between below poverty and LEP populations
- correlation of 0.14 between LEP populations and zero-car households
# Region 6: Brownsville-Harlingen, TX CBSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 953
Census Tracts 86
Total CBSA Population 335,227
Minority Population 66,088
Below Poverty Population 107,970
Population (5 years and older) 303,483
LEP Population (5 years and older) 106,588
Total Households 119,654
Zero-Car Households 11,305
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the
**Brownsville-Harlingen, TX CBSA** regional populations:
- correlation of 0.85 between below poverty and LEP populations
- correlation of 0.83 between minority populations and LEP populations
- correlation of 0.65 between minority and below poverty populations
- correlation of 0.58 between below poverty and zero-car households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.47 between LEP populations and zero-car households
```{=html}
<!-- -->
```
- correlation of 0.40 between minority populations and zero-car
households
## Region 7: Houston-Baytown-Huntsville, TX CSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 1,134
Census Tracts 908
Total Population 4,815,122
Minority Population 1,785,856
Below Poverty Population 649,801
Population (5 years and older) 4,429,761
LEP Population (5 years and older) 674,321
Total Households 1,689,003
Zero-Car Households 130,092
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the
**Houston-Baytown-Huntsville, TX CSA** regional populations:
- correlation of 0.82 between below poverty population and zero-car
households
- correlation of 0.77 between below poverty and LEP populations
- correlation of 0.71 between minority and below poverty populations
- correlation of 0.65 between minority and LEP populations
- a correlation of 0.57 between minority populations and zero-car
households
- a correlation of 0.54 between LEP and zero-car households
# Region 8: Lafayette, LA CBSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 1,087
Census Tracts 50
Total Population 239,086
Minority Population 67,288
Below Poverty Population 39,477
Population (5 years and older) 221,495
LEP Population (5 years and older) 11,337
Total Households 89,536
Zero-Car Households 7,883
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Lafayette, LA CBSA**
regional populations:
- correlation of 0.87 between minority and below poverty populations
- correlation of 0.79 between below poverty and zero-car households
- correlation of 0.78 between minority populations and zero-car
households
- correlation of 0.62 between below poverty and LEP populations
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.31 between minority and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.27 between LEP populations and zero-car households
***Region 9: Pine Bluff, AR CBSA***
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 2,085.3
Census Tracts 33
Total Population 107,341
Minority Population 49,832
Below Poverty Population 19,689
Population (5 years and older) 101,333
LEP Population (5 years and older) 1,178
Total Households 38,093
Zero-Car Households 4,124
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Pine Bluff, AR
CBSA** regional populations:
- correlation of 0.83 between below poverty populations and zero-car
households
- correlation of 0.68 between minority and below poverty populations
- correlation of 0.65 between minority populations and zero-car
households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.12 between below poverty and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.02 between minority and LEP populations
```{=html}
<!-- -->
```
- correlation of -0.01 between LEP populations and zero-car households
# Region 10: St. Louis, MO-IL CBSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 8,831
Census Tracts 551
Total Population 2,698,687
Minority Population 569,975
Below Poverty Population 264,721
Population (5 years and older) 2,519,595
LEP Population (5 years and older) 49,291
Total Households 1,048,279
Zero-Car Households 93,475
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **St. Louis, MO-IL
CBSA** regional populations:
- correlation of 0.79 between below poverty populations and zero-car
households
- correlation of 0.71 between minority and below poverty populations
- correlation of 0.60 between minority populations and zero-car
households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.30 between LEP populations and zero-car households
- correlation of 0.18 between below poverty and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.10 between minority and LEP populations
**Region 11: Chicago-Naperville-Joliet, IL-IN-WI CSA**
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 8,573
Census Tracts 2,105
Total Population 9,302,726
Minority Population 3,051,134
Below Poverty Population 954,168
Population (5 years and older) 8,617,563
LEP Population (5 years and older) 1,017,833
Total Households 3,355,583
Zero-Car Households 453,809
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the
**Chicago-Naperville-Joliet, IL-IN-WI CSA** regional populations:
- correlation of 0.82 between below poverty populations and zero-car
households
- correlation of 0.74 between minority and below poverty populations
- correlation of 0.70 between minority populations and zero-car
households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.08 between below poverty and LEP populations
- correlation of 0.06 between LEP populations and zero-car households
```{=html}
<!-- -->
```
- correlation of 0.05 between minority and LEP populations
**Region 12:** Atlanta-Sandy Springs-Marietta, GA CBSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 8,483.9
Census Tracts 690
Total CBSA Population 4,247,981
Minority Population 1,552,523
Below Poverty Population 397,037
Population (5 years and older) 4,190,991
LEP Population (5 years and older) 259,256
Total Households 1,554,154
Zero-Car Households 492,166
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Atlanta-Sandy
Springs-Marietta, GA CBSA** regional populations:
- correlation of 0.90 between below poverty populations and zero-car
households
- correlation of 0.63 between minority and below poverty populations
- correlation of 0.63 between minority populations and zero-car
households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.15 between minority and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.13 between below poverty and LEP populations
- correlation of 0.05 between LEP populations and zero-car households
**Region 13:** Albany, GA CBSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 1,960
Census Tracts 46
Total Population 157,833
Minority Population 79,972
Below Poverty Population 33,002
Population (5 years and older) 145,995
LEP Population (5 years and older) 2,037
Total Households 57,403
Zero-Car Households 6,556
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Albany, GA CBSA**
regional populations:
- correlation of 0.81 between minority and below poverty populations
- correlation of 0.68 between below poverty populations and zero-car
households
- correlation of 0.64 between minority populations and zero-car
households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.16 between LEP populations and zero-car households
- correlation of -0.06 between minority and LEP populations
```{=html}
<!-- -->
```
- correlation of -0.27 between below poverty and LEP populations
Region 14: Pittsburgh, PA CBSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 5,336
Census Tracts 721
Total Population 2,431,087
Minority Population 248,643
Below Poverty Population 256,990
Population (5 years and older) 2,296,228
LEP Population (5 years and older) 35,276
Total Households 995,505
Zero-Car Households 127,554
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Pittsburgh, PA
CBSA** regional populations:
- correlation of 0.71 between below poverty populations and zero-car
households
- correlation of 0.60 between minority populations and zero-car
households
- correlation of 0.52 between minority and below poverty populations
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.35 between LEP populations and zero-car households
- correlation of 0.23 between below poverty and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.21 between minority and LEP populations
## Region 15: Miami-Ft. Lauderdale-Miami Beach, FL CBSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 5,441
Census Tracts 891
Total Population 5,007,564
Minority Population 1,397,512
Below Poverty Population 692,014
Population (5 years and older) 4,695,898
LEP Population (5 years and older) 1,008,963
Total Households 1,905,394
Zero-Car Households 210,173
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **Miami-Ft.
Lauderdale-Miami Beach, FL CBSA** regional populations:
- correlation of 0.66 between minority and below poverty populations
- correlation of 0.63 between below poverty populations and zero-car
households
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.50 between below poverty and LEP populations
- correlation of 0.29 between LEP populations and zero-car households
- correlation of 0.22 between minority and zero-car households
```{=html}
<!-- -->
```
- correlation of 0.16 between minority and LEP populations
**Region 16: Washington-Baltimore-Northern Virginia, DC-MD-VA-WV** CSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 10,120
Census Tracts 1,682
Total Population 7,572,647
Minority Population 2,813,359
Below Poverty Population 608,605
Population (5 years and older) 7,055,969
LEP Population (5 years and older) 484,644
Total Households 2,857,170
Zero-Car Households 341,145
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the
**Washington-Baltimore-Northern Virginia, DC-MD-VA-WV CSA** regional
populations:
- correlation of 0.76 between below poverty populations and zero-car
households
- correlation of 0.56 between minority and below poverty populations
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.42 between minority and zero-car households
- correlation of 0.41 between minority and LEP populations
- correlation of 0.19 between below poverty and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.09 between LEP populations and zero-car households
#
# Region 17: Philadelphia-Camden-Vineland, PA, NJ, DE-MD CSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 12,164
Census Tracts 1,504
Total Population 5,883,585
Minority Population 1,610,875
Below Poverty Population 619,316
Population (5 years and older) 5,455,406
LEP Population (5 years and older) 269,492
Total House Holds 2,183,587
Zero-Car Households 336,339
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the
**Philadelphia-Camden-Vineland, PA, NJ, DE-MD CSA** regional
populations:
- correlation of 0.82 between below poverty populations and zero-car
households
- correlation of 0.79 between minority and below poverty populations
- correlation of 0.70 between minority populations and zero-car
households
- correlation of 0.61 between below poverty and LEP populations
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.44 between minority and LEP populations
```{=html}
<!-- -->
```
- correlation of 0.44 between LEP populations and zero-car households
**Region 18: New York-Newark-Bridgeport, NY-NJ-CT-PA** CSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 12,164
Census Tracts 5,194
Total Population 21,361,785
Minority Population 7,628,665
Below Poverty Population 2,697,696
Population (5 years and older) 19,913,957
LEP Population (5 years and older) 3,080,373
Total Households 7,799,409
Zero-Car Households 2,221,628
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **New
York-Newark-Bridgeport, NY-NJ-CT-PA CSA** regional populations:
- correlation of 0.77 between minority and below poverty populations
- correlation of 0.70 between below poverty and LEP populations
- correlation of 0.65 between below poverty and zero-car households
- correlation of 0.63 between minority and LEP populations
- correlation of 0.57 between minority populations and zero-car
households
```{=html}
<!-- -->
```
- correlation of 0.51 between LEP populations and zero-car households
> **Region 19: Boston-Worchester-Manchester, MA-NH CSA**
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 7,497
Census Tracts 1,210
Total Population 5,715,698
Minority Population 840,864
Below Poverty Population 464,431
Population (5 years and older) 5,350,416
LEP Population (5 years and older) 387,430
Total Housing Households 2,182,343
Zero-Car Housing Units 264,431
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the
**Boston-Worchester-Manchester, MA-NH CSA** regional populations:
- correlation of 0.76 between minority and LEP populations
- correlation of 0.76 between below poverty and LEP populations
- correlation of 0.73 between below poverty and zero-car households
- correlation of 0.72 between minority and below poverty populations
- correlation of 0.62 between LEP populations and zero-car households
```{=html}
<!-- -->
```
- correlation of 0.57 between minority populations and zero-car
households
**Region 20:** San Juan-Caguas-Fajardo, PR CSA
----------------------------------------------- -----------------------
**Statistic** **Value**
Area (sq. mi.) 1,700
Census Tracts 540
Total CBSA Population 2,518,893
Minority Population 529,874
Below Poverty Population 1,120,365
Population (5 years and older) 2,323,928
LEP Population (5 years and older) 1,658,826
Total Households 838,664
Zero-Car Households 234,356
----------------------------------------------- -----------------------
Positive correlations greater than 0.50 among the **San
Juan-Caguas-Fajardo, PR CSA** regional populations:
- correlation of 0.70 between below poverty populations and zero-car
households
- correlation of 0.68 between below poverty and LEP populations
Correlations between other populations that were below 0.50 are as
follows:
- correlation of 0.49 between minority and LEP populations
- correlation of 0.42 between minority and below poverty populations
```{=html}
<!-- -->
```
- correlation of 0.44 between LEP populations and zero-car households
- correlation of 0.41 between minority and LEP populations
**Appendix B\
List of Agencies Reviewed**
----------------------- ----------------------------- -----------------
**Region** **Agency** **Type**
**Honolulu** Hawaii DOT State DOT
Oahu Metropolitan Planning MPO
Organization
Oahu Transit Service Transit provider
**San Francisco** California DOT State DOT
Metropolitan Transportation MPO
Commission
AC Transit Transit provider
Bay Area Rapid Transit Transit provider
San Francisco Municipal Transit provider
Railway
San Mateo County (Sam Trans) Transit provider
Santa Clara Valley Transit Transit provider
Golden Gate Transit Transit provider
**Los Angeles** California DOT State DOT
Southern California MPO
Association of Governments
Southern California Regional Transit provider
Rail Authority (METROLINK)
Los Angeles County Transit provider
Metropolitan Transportation
Authority (METRO)
**Seattle** Washington State DOT State DOT
Puget Sound Regional Council MPO
King County Department of Transit provider
Transportation
Sound Transit Transit provider
**Flagstaff** Arizona DOT State DOT
Flagstaff MPO MPO
Mountain Line Transit/ VanGO Transit provider
Paratransit
**Brownsville** TXDOT State DOT
Brownsville MPO MPO
Brownsville Urban System Transit provider
**Houston** TXDOT State DOT
Galveston Area Council MPO
Metro Transit provider
**Lafayette** Louisiana DOT State DOT
Lafayette Transit System Transit provider
**Pine Bluff** Arkansas DOT State DOT
** ** Southeast Arkansas Regional MPO
Planning Commission
Pine Bluff Transit Transit provider
----------------------- ----------------------------- -----------------
**List of Agencies Reviewed (Continued)**
----------------------- ----------------------------- -----------------
**Region** **Agency** **Type**
**St. Louis** Missouri DOT State DOT
** ** Illinois DOT State DOT
** ** East West Gateway Council of MPO
Governments
Metro (Bi-State) Transit provider
**Chicago** Illinois DOT State DOT
Indiana DOT State DOT
Wisconsin DOT State DOT
Southeastern Wisconsin MPO
Regional Planning Commission
Chicago Area Transportation MPO
Study
Chicago Transit Authority Transit provider
Metra Transit provider
City of Kenosha DOT Transit provider
Lake County Transit provider
**Atlanta** Georgia DOT State DOT
** ** Atlanta Regional Commission MPO
Metropolitan Atlanta Rapid Transit provider
Transit Authority
Georgia Regional Transit Transit provider
Authority
Cobb Community Transit Transit provider
Gwinnett County Department of Transit provider
Transportation
**Albany** Georgia DOT State DOT
** ** City of Albany Planning and MPO
Development Services
Department
Albany Transit System Transit provider
**Pittsburgh** Pennsylvania DOT State DOT
** ** Southwestern Pennsylvania MPO
Commission
Port Authority of Allegheny Transit provider
County
**Miami** Florida DOT State DOT
Miami Urbanized Area MPO MPO
Miami-Dade Transit Agency Transit provider
----------------------- ----------------------------- -----------------
**List of Agencies Reviewed (Continued)**
----------------------- ----------------------------- -----------------
**Philadelphia** Pennsylvania DOT State DOT
** ** Delaware Valley Regional MPO
Planning Commission
South Jersey Metropolitan MPO
Planning Commission
Southeastern Pennsylvania Transit provider
Public Transit Authority
(SEPTA)
New Jersey Transit Transit provider
Delaware Transit Corporation Transit provider
**New York** New York State DOT State DOT
** ** Connecticut DOT State DOT
** ** New Jersey DOT State DOT
** ** North Jersey Transportation MPO
Planning Authority
** ** New York Metropolitan MPO
Transportation Council
MTA (Includes LIRR, MNR, and Transit provider
NYCT)
New Jersey Transit Transit provider
**Boston** Massachusetts DOT State DOT
Boston MPO MPO
MBTA Transit provider
**San Juan** Departamento de DOT/MPP
transportacion y obras
publicas
METRO -- San Juan Transit provider
----------------------- ----------------------------- -----------------
> []{#VConclusionsandRecommen .anchor}
[^1]: As noted in the Department of Homeland Security's Nationwide Plan
Review, published in June 2006, no singular definition of the term
"special needs" exists although the term is widely used within the
emergency management world. The term "special needs" generally
includes people with disabilities, minority groups, people who do
not speak English, children, and the elderly as well as people who
live in poverty, people without private transportation, people who
rely on caregivers for assistance, and people who live in facilities
such as nursing homes and supervised group homes as well as people
living independently. This report focuses on a subset of this larger
population of persons who may have specific needs in an emergency.
[^2]: Detailed accounts of the impacts of and government action before,
during, and after Hurricane Katrina can be found in reports
published by the White House, the U.S. Senate Committee on Homeland
Security and Government Affairs, and the U.S. House of
Representatives Select Bipartisan Committee to Investigate the
Preparation for and Response to Hurricane Katrina.
[^3]: *Survey of Hurricane Katrina Evacuees*, the Washington Post/Kaiser
Family Foundation/Harvard University, September 2005.
[^4]: The U.S. DOT Catastrophic Hurricane Evacuation Plan Assessment
describes minimal disaster response efforts to help evacuate the
Spanish-speaking community of the Gulf Coast.
[^5]: *Katrina's Window: Confronting Concentrated Poverty Across
America*, by Alan Berube and Bruce Katz, the Brookings Institution,
October 2005.
[^6]: For the purposes of this study, "minority" means a person who is:
(1) Black (a person having origins in any of the black racial groups
of Africa); (2) Hispanic (a person of Mexican, Puerto Rican, Cuban,
Central or South American, or other Spanish culture or origin,
regardless of race); (3) Asian American (a person having origins in
any of the original peoples of the Far East, Southeast Asia, the
Indian subcontinent, or the Pacific Islands); or (4) American Indian
and Alaskan Native (a person having origins in any of the original
people of North America and who maintains cultural identification
through tribal affiliation or community recognition).
[^7]: The New York Academy of Medicine's *Redefining Readiness* included
a nationwide survey in which participants were given scenarios of a
smallpox outbreak and a dirty bomb explosion in their communities
and asked how they would respond. In response to the smallpox
outbreak scenario, 41% of survey respondents said they were worried
that government officials would tell them to do something that is
not in their best interests and/or that government officials would
decide to do something that the government knew would harm them in
some way. These concerns were more prevalent among people who are
Hispanic (61%), African American (57%), foreign born (55%), have low
incomes (51%), or did not attend college (51%) and these concerns
would make 26% of the population afraid to go to a vaccination site
in the scenario.
[^8]: Low income is defined in the U.S. DOT Order on Environmental
Justice, and for the purposes of this study, as a person whose
median household income is at or below the Department of Health and
Human Services poverty guidelines.
[^9]: The U.S. DOT Policy Guidance Concerning Recipients'
Responsibilities to Limited English Proficient (LEP) Persons states
that individuals who do not speak English as their native language
and who have a limited ability to read, write, speak, or understand
English can be limited English proficient. This report categorized
as LEP persons who reported to the 2000 census that English was not
their native language and that they spoke English less than "very
well."
[^10]: The data on zero-vehicle households featured in this report are
derived from the "vehicles available" question on the 2000 census
long form.
[^11]: This study did not examine the programs, policies, or activities
of providers of school bus, charter bus, or intercity bus
transportation or intercity rail transportation, although these
entities have been and continue to be involved in emergency
preparedness and disaster response activities.
[^12]: FTA did not seek to obtain information for every transit agency
serving each of the 20 metropolitan areas. In large metropolitan
areas, such as the San Francisco, Los Angeles, and New York regions,
this study sought information from agencies that served the areas
within the region with high proportions of the study's focus
populations.
[^13]: An inventory of natural and man-made disasters in each
metropolitan area was compiled by accessing information on the
National Climatic Data Center "Billion Dollar Weather Disasters"
website at <http://lwf.ncdc.noaa.gov/oa/reports/billionz.html>.
These data were cross-referenced with the disasters listed on FEMA's
disaster website at <http://www.fema.gov/news/disasters.fema>.
Information on past and potential man-made disasters was complied
through web and Wikipedia searches and by the NRC's list of nuclear
facilities in each state.
[^14]: The relationship between urban environmental depravation and
mortality during a natural disaster is discussed in *Heat Wave: A
Social Autopsy of Disaster in Chicago*, by Eric Klinenberg. *Heat
Wave* describes the characteristics of Chicago neighborhoods whose
residents experienced a disproportionately high number of
heat-related deaths in the 1994 heat wave. The Chicago community
areas with the highest heat-related mortality rates also included
high rates of elderly individuals living alone, high crime rates,
and high proportions of people living in poverty.
[^15]: Sources: National Climatic Data Center "Billion Dollar Weather
Disasters" website at
<http://lwf.ncdc.noaa.gov/oa/reports/billionz.html> and FEMA's
disaster website at <http://www.fema.gov/news/disasters.fema>.
| en |
markdown | 675060 | # Presentation: 675060
## Two Consolidation Projects:
**Towards an International MME: CFS+EUROSIP(UKMO,ECMWF,METF) ****11 slides**
**Towards a National MME: CFS and GFDL**** 18 slides**
## Does the NCEP CFS add to the skill of the European DEMETER-3 to produce a viable International Multi Model Ensemble (IMME) ?
**Huug van den Dool**
- Climate Prediction Center, NCEP/NWS/NOAA
**Suranjana Saha and Åke Johansson**
- Environmental Modeling Center, NCEP/NWS/NOAA
**August 2007**
## DATA and DEFINITIONS USED
DEMETER-3 (DEM3) = ECMWF + METFR + UKMO
CFS
IMME = DEM3 + CFS
1981 – 2001
4 Initial condition months : Feb, May, Aug and Nov
Leads 1-5
Monthly means
**DEMETER-3 (DEM3) = ECMWF + METFR + UKMO**
**CFS **
**IMME = DEM3 + CFS**
**1981 – 2001**
**4 Initial condition months : Feb, May, Aug and Nov**
**Leads 1-5 **
**Monthly means**
## DATA/Definitions USED (cont)
Deterministic : Anomaly Correlation
Probabilistic : Brier Score (BS) and Rank Probability Score (RPS)
Ensemble Mean and PDF
T2m and Prate
Europe and United States
“ NO (fancy) consolidation, equal weights, NO Cross-validation”
**Deterministic : Anomaly Correlation**
**Probabilistic : Brier Score (BS) and Rank Probability Score (RPS)**
**Ensemble Mean and PDF**
**T2m and Prate**
**Europe and United States**
**“ ****NO (fancy) consolidation, equal weights, NO Cross-validation”**
## DATA/Definitions USED (cont)
Verification Data :
T2m : CPC Monthly Analysis of the CAMS + Global Historical Climate Network (Fan and Van den Dool 2007)
Prate : CMAP (Xie-Arkin 1997)
**Verification Data**** :**
**T2m : CPC Monthly Analysis of the CAMS + Global Historical Climate Network (Fan and Van den Dool 2007) **
**Prate : CMAP (Xie-Arkin 1997)**
## Number of times IMME improves upon DEM-3 : out of 20 cases (4 IC’s x 5 leads):
| Region | EUROPE | EUROPE | USA | USA |
| --- | --- | --- | --- | --- |
| Variable | T2m | Prate | T2m | Prate |
| Anomaly
Correlation | 9 | 14 | 14 | 14 |
| Brier Score | 16 | 18.5 | 19 | 20 |
| RPS | 14 | 15 | 19.5 | 20 |
- “The bottom line”
## Frequency of being the best model in 20 cases in terms of Anomaly Correlation of the Ensemble Mean
- “**Another bottom line”**
| | | CFS | ECMWF | METFR | UKMO |
| --- | --- | --- | --- | --- | --- |
| T2m | USA | 4 | 5 | 5 | 6 |
| T2m | EUROPE | 3 | 5 | 6 | 5 |
| Prate
| USA | 7 | 3 | 3 | 6 |
| Prate | EUROPE | 11 | 0 | 0 | 5 |
## Frequency of being the best model in 20 cases in terms of Brier Score of the PDF
- “**Another bottom line”**
| | | CFS | ECMWF | METFR | UKMO |
| --- | --- | --- | --- | --- | --- |
| T2m | USA | 11 | 2 | 1 | 5 |
| T2m | EUROPE | 10 | 3 | 1 | 3 |
| Prate
| USA | 17 | 2 | 0 | 1 |
| Prate | EUROPE | 18 | 0 | 1 | 1 |
## Frequency of being the best model in 20 cases in terms of Ranked Probability Score (RPS) of the PDF
- “**Another bottom line”**
| | | CFS | ECMWF | METFR | UKMO |
| --- | --- | --- | --- | --- | --- |
| T2m | USA | 9 | 4 | 1 | 6 |
| T2m | EUROPE | 9 | 3 | 4 | 3 |
| Prate
| USA | 19 | 0 | 0 | 1 |
| Prate | EUROPE | 18 | 0 | 0 | 1 |
## CONCLUSIONS
Overall, NCEP CFS contributes to the skill of IMME (relative to DEM3) for equal weights.
This is especially so in terms of the probabilistic Brier Score
and for Precipitation
- Overall, NCEP CFS contributes to the skill of IMME (relative to DEM3) for equal weights.
- This is especially so in terms of the probabilistic Brier Score
- and for Precipitation
## CONCLUSIONS (Cont)
In comparison to ECMWF, METFR and UKMO,
the CFS as an individual model does:
well in deterministic scoring (AC) for Prate and
very well in probability scoring (BS) for Prate and T2m
over both USA and EUROPEAN domains
- In comparison to ECMWF, METFR and UKMO,
- the CFS as an individual model does:
- well in deterministic scoring (AC) for Prate and
- very well in probability scoring (BS) for Prate and T2m
- over both USA and EUROPEAN domains
## CONCLUSIONS (Cont)
The relative weakness of the CFS is in the deterministic scoring (AC) for T2m (which is near average of the other models) over both EUROPE and USA
Skill (if any) over EUROPE or USA is very modest for any model, or any combination of models
The Brier Score shows rare improvements over climatological probabilities in this study
The AC for the ensemble mean gives a more “positive” impression about skill than the Brier Score
- The relative weakness of the CFS is in the deterministic scoring (AC) for T2m (which is near average of the other models) over both EUROPE and USA
- Skill (if any) over EUROPE or USA is very modest for any model, or any combination of models
**The Brier Score shows rare improvements over climatological probabilities in this study**
**The AC for the ensemble mean gives a more “positive” impression about skill than the Brier Score**
## Study of the performance of GFDL seasonal forecasts in a Multi Model Ensemble at NCEP
**Huug van den Dool**
- Climate Prediction Center/NCEP/NWS/NOAA
**Suranjana Saha**
- Environmental Modeling Center/NCEP/NWS/NOAA
## Data Used
4 initial conditions: April 1, May 1, Oct 1 and Nov 1
10 member one-year forecasts (leads 0 thru 11)
Period 1981-2005 (25 years)
GFDL has a fully coupled model CM2.1 (IPCC version)
- 4 initial conditions: April 1, May 1, Oct 1 and Nov 1
- 10 member one-year forecasts (leads 0 thru 11)
- Period 1981-2005 (25 years)
- GFDL has a fully coupled model CM2.1 (IPCC version)
## Verification Data Used
Focus on monthly mean 2m-temperature and precipitation over the continental US
Verification of 2m-temperature against GHCN+CAMS (land only)
Verification of precipitation against CMAP ( land and ocean)
Area: valid grid points (2.5x2.5) within 25N-50N, 125W-65W box over the US
- Focus on monthly mean 2m-temperature and precipitation over the continental US
- Verification of 2m-temperature against GHCN+CAMS (land only)
- Verification of precipitation against CMAP ( land and ocean)
- Area: valid grid points (2.5x2.5) within 25N-50N, 125W-65W box over the US
## Comparison to the NCEP Climate Forecast System (CFS)
GFDL members start a few days before and on the first of the month.
CFS members are clustered around the 11th and 21st of the previous month and the 1st of the initial month.
In an NCEP operational setting, the GFDL model would be run everyday (similar to the CFS).
Therefore, the calibration of the operational forecast would be obtained from an interpolation of two sets of forecasts, a month apart (one of which would be a month old), thus resulting in a possible degradation of skill.
- GFDL members start a few days before and on the first of the month.
- CFS members are clustered around the 11th and 21st of the previous month and the 1st of the initial month.
- In an NCEP operational setting, the GFDL model would be run everyday (similar to the CFS).
- Therefore, the calibration of the operational forecast would be obtained from an interpolation of two sets of forecasts, a month apart (one of which would be a month old), thus resulting in a possible degradation of skill.
## VERIFICATION OF US PRATE ANOMALY CORRELATION
## CFS US PRATE ANOMALY CORRELATION
**CFS**** US PRATE ANOMALY CORRELATION**
**There are 32 ENTRIES: 8 leads for 4 initial months**
- **initial month apr may oct nov**
** ****lead**
** ****8** **.126 **** **** .143 .059 .083**
** ****7**** .135 .174 .101 .034**
** ****6**** -.001 .071 .081 .112 **
** ****5**** .098 .035 .123 .041**
** ****4**** **** ****.027 .087 ****.227**** .168**
** ****3 **** .049 .025 .166 ****.231**
** ****2 **** .058 .061 .119 ****.220**
** ****1 **** .142 .030 .149 .161 **
** ****0**** .191 .244 .189 .277**
**Worst mean-sd mean mean+sd best**
** ****-.001 .043 ****.104**** .166 .231**
**NO CROSS VALIDATION**
**Some skill **
**in ENSO months**
## CFS US PRATE ANOMALY CORRELATION
**CFS**** US PRATE ANOMALY CORRELATION**
**There are 32 ENTRIES: 8 leads for 4 initial months**
- **initial month apr may oct nov**
** ****lead**
** ****8 ****.062 .093 .007 .024**
** ****7**** .125 .107 .062 -.017**
** ****6**** -.090 -.039 .039 .058**
** ****5**** .038 -.056 .056 -.016**
** ****4**** -.033 .033 .192 .086 **
** ****3**** -.023 -.073 .120 .191**
** ****2**** -.028 -.016 .065 .182**
** ****1 **** .113 -.059 .122 .101**
** ****0**** .139 .241 .116 .248**
**Worst mean-sd mean mean+sd best**
** ****-.090 -.032 ****.045**** .121 .192**
**CROSS VALIDATION CV3RE**
**CV brings **
**all numbers down**
## GFDL US PRATE ANOMALY CORRELATION
**GFDL**** US PRATE ANOMALY CORRELATION**
**There are 32 ENTRIES: 8 leads for 4 initial months**
- **initial month apr may oct nov**
** ****lead**
** ****8 ****.027 .044 .045 .048**
** ****7**** .122 -.002 .032 .091**
** ****6 **** -.040 .138 .057 .066**
** ****5**** .003 .047 .113 .016**
** ****4**** .061 -.019 .153 .081**
** ****3**** .093 .024 .071 .154**
** ****2**** .059 .099 .166 .109**
** ****1**** .120 .074 .085 ****.217**
** ****0**** .184 .219 .087 .250**
**Worst mean-sd mean mean+sd best**
**-.040 .018 ****.074**** .130 .217 **
**NO CROSS VALIDATION**
**Weak skill **
**in ENSO months**
## MME2 US PRATE ANOMALY CORRELATION
**MME2**** US PRATE ANOMALY CORRELATION**
**There are 32 ENTRIES: 8 leads for 4 initial months**
- **initial month apr may oct nov**
** ****lead**
** ****8 ****.104 .135 .065 .082**
** ****7 **** .168 .112 .091 .075**
** ****6**** -.032 .140 .092 .115**
** ****5**** .062 .056 .149 .039 **
** ****4**** .060 .043 ****.241**** .159**
** ****3 **** .093 .032 .147 ****.234**
** ****2 **** .076 .105 .183 .199**
** ****1**** .165 .067 .145 ****.227**
** ****0**** .223 .277 .170 .311**
**Worst mean-sd mean mean+sd best**
** ****-.032 .051 ****.113**** .176 .241**
**NO CROSS VALIDATION**
## US PRATE (AC) BEST out of 32 cases (4 IC’s x 8 leads):
| CFS | GFDL | MME2 |
| --- | --- | --- |
| 22 | 10 | |
| 13 | | 19 |
| | 3 | 28 |
| .045 | .009 | .035 |
| CFS | GFDL | MME2 |
| --- | --- | --- |
| 21 | 11 | |
| 20 | | 12 |
| | 12 | 20 |
| .104 | .074 | .113 |
**NO CV**
**CV3RE**
**US PRATE (AC)****BEST ****out of 32 cases (4 IC’s x 8 leads):**
**MEAN AC**
**MEAN AC**
## US PRATE (summary)
- MME2 is slightly better than CFS alone
- MME2 is better than GFDL alone
- Numerically, differences are minuscule,
- and the existence of **any skill** is debatable
**US PRATE (summary)**
## PRATE OVER NINO 3.4 AREA (summary)
** ****GFDL has ENSOs, maybe even too strong in 1983 and 1998, but**
**the precipitation anomalies are weak at the equator and are pushed **
**away from the equator, mainly into the southern hemisphere.**
**PRATE OVER NINO 3.4 AREA ****(summary)**
**CFS MME2 GFDL **
**.532 .520 .313**** (NO CV)**
**.511 .481 .252 ****(CV3RE)**
## VERIFICATION OF
**US SURFACE TEMPERATURE ****ANOMALY CORRELATION**
## US 2m TEMPERATURE (AC) BEST out of 32 cases (4 IC’s x 8 leads):
| CFS | GFDL | MME2 |
| --- | --- | --- |
| 13 | 19 | |
| 13 | | 19 |
| | 19 | 13 |
| .026 | .029 | .009 |
| CFS | GFDL | MME2 |
| --- | --- | --- |
| 15 | 17 | |
| 13 | | 18 |
| | 13 | 18 |
| .080 | .099 | .113 |
**NO CV**
**CV3RE**
**US 2m TEMPERATURE (AC)****BEST** **out of 32 cases (4 IC’s x 8 leads):**
**MEAN AC**
**MEAN AC**
## US 2m TEMPERATURE (summary)
- MME2 is slightly better than CFS alone
- MME2 is not better than GFDL alone
- Numerically, differences are minuscule,
- and the existence of **any skill** is debatable
**US 2m TEMPERATURE (summary)**
## TREND ANALYSIS OF US 2m TEMP
- **Effect of OCN (Optimal Climate Normals)**
**filtering on AC scores for all 32 cases **
**(NO-CV)**
**9 year running mean is removed**
** **** ****RAW OCN-filtered**
** ****GFDL**** ****0.099**** 0.068**
** ****CFS**** 0.080 ****0.073**
** ****GFDL loses its advantage over the CFS **
**when the trend is removed**
**TREND ANALYSIS OF US 2m TEMP**
## CONCLUSIONS (1)
**CONCLUSIONS (1)**
- **Skill of both, CFS and GFDL, is extremely low for both 2m temperature (T2M) and precipitation (PRATE) over the US, and this skill wilts further upon cross validation (CV3RE)**
** ****GFDL makes no contribution to the skill of MME2 for PRATE over the US **
** ****GFDL makes no contribution to the skill of MME2 for PRATE over the tropical Pacific (Nino 3.4 area)**
** ****GFDL has a small edge over the CFS and contributes to MME2 for T2M over the US **
## CONCLUSIONS (2)
**CONCLUSIONS (2)**
- **The inconsistency between performance in PRATE and T2M is explained by inclusion of historical CO2 etc, i.e. GFDL does a better job on the decadal temperature trends. This is explained by the drop in the skill when the trend is removed. **
** ****The empirical tool, OCN (Optimal Climate Normals), is routinely used by CPC to incorporate decadal trends in the consolidation of the official seasonal forecasts for US T2M. Its performance is better than any of their dynamical tools.**
## From Delsole(2007)
- Surprisingly, none of the regression models proposed here can consistently beat the skill of a simple multi-model mean
- “Under suitable assumptions, both the Bayesian estimate and the constrained least squares solution reduce to standard ridge regression”.
## Kharin and Zwiers(2002):
- Several methods of combining individual forecasts from a group of climate models to produce an ensemble forecast are considered
- In the extratropics, the regression-improved ensemble mean performs best.
- The “superensemble” forecast that is obtained by optimally weighting the individual ensemble members does not perform as well as either the simple ensemble mean or the regression-improved ensemble mean.
- The sample size evidently is too small to estimate reliably the relatively large number of optimal weights required for the superensemble approach.
## Finally Huug van den Dool, 2007
- There is essentially not enough hindcast data for these fancy consolidation methods to work (21-25 years is nothing !!). ((There may be exceptions))
- There is no (or not enough) independent information in model A versus Model B
**We have to be rigorous in CV procedures!**
## The rest is EXTRA
## Classic
- +Delsole limit
- +CPC limit
## Appendix: Consolidation Techniques
- A technique to linearly combine any set of models
- Example: Con3 = a***A** + b***B** + c***C, **
- where A, B and C are forecasts and a, b, and c coefficients.
- The coefficients ideally depend on skill and co-linearity among the models, as determined from many hindcasts
- Because of near instability of the matrix problem, NCEP applies ‘ridging’ to the covariance matrix, and tries to pool as much data as possible (areas, leads..).
- To arrive at a skill estimate, we perform a 3 year-out cross validation (CV3), namely the year in consideration and two more years chosen at random (to reduce CV pathological problems)
## BRIER SCORE FOR 3-CLASS SYSTEM
**1**. **Calculate tercile boundaries from observations 1981-2001 (1982-2002 for longer leads) at each gridpoint.**
**2. Assign departures from model’s own climatology (based on 21 years, all members) to one of the three classes: Below (B), Normal (N) and Above (A), and find the fraction of forecasts (F) among all participating ensemble members for these classes denoted by FB, FN and FA respectively, such that FB+ FN+FA=1 . **
**3. Denoting Observations as O, we calculate a Brier Score (BS) as :**
** ****BS={(FB-OB)**2 +(FN-ON)**2 + (FA-OA)**2}/3, **
** ****aggregated over all years and all grid points. **
** ****{{For example, when the observation is in the B class, we have (1,0,0) for (OB, ON, OA) etc.}}**
**4. BS for random deterministic prediction: 0.444**
** ****BS for ‘always climatology’ (1/3****rd****,1/3****rd****,1/3****rd****) : 0.222**
**5. RPS: The same as Brier Score, but for cumulative distribution (no-skill=0.148**)
## Anomaly correlation does not asymptote to 100 at fcst time=0
**Anomaly correlation does not asymptote to 100 at fcst time=0**
**Interpolation of initial conditions from Reanalysis 2 may not be correct or accurate**
## CROSS-VALIDATION
- Anomaly Pattern correlation over the tropical Pacific. Average for all leads and initial months. Empty bar: Full (dependent), filled bar: 3-yr out cross-validated.
## Peña and Van den Dool (2008) Consolidation of Multi Method Forecasts by Ridge Regression: Application to Pacific Sea Surface Temperature
- Strategies to increase the ratio of the effective sample size of the training data to the number of coefficients to be fitted are proposed and tested. These strategies include:
- i) objective selection of a smaller subset of models, ii) pooling of information from neighboring gridpoints, and iii) consolidating all ensemble members rather than each model’s ensemble average.
- In all variations of the ridge regression consolidation methods tested, increased effective sample size produces more stable weights and more skillful predictions on independent data.
- In the western tropical Pacific, most consolidation methods outperform the simple equal weight ensemble average; in other regions they have similar skill as measured by both the anomaly correlation and the relative operating curve.
- The main obstacle to progress is a short period of data and a lack of independent information among models.
- CV3RE | en |
converted_docs | 699372 | +-------------------------+-------------+--------+--------------------+
| # LT Project | **Contact** | ## | **email** |
| | | Phone | |
+-------------------------+-------------+--------+--------------------+
| COTF | Dr. James | 304-24 | coffield@cet.edu |
| | Coffield | 3-2388 | |
+-------------------------+-------------+--------+--------------------+
| COTF | Ron Eddy | 304-24 | reddy2@cet.edu |
| | | 3-2388 | |
+-------------------------+-------------+--------+--------------------+
| COTF | Dr. Stanley | 202-48 | sjones@cet.edu |
| | Jones | 8-5155 | |
+-------------------------+-------------+--------+--------------------+
| -------------------- | Horace | 301-28 | Horace.G |
| Digital Earth PC | Mitchell | 6-1634 | .Mitchell@nasa.gov |
| | | | |
| -------------------- | | | |
+-------------------------+-------------+--------+--------------------+
| Digital Earth PC | Eric | 301-28 | esok@co |
| | Sokolowsky | 6-3751 | simo.gsfc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Earth Portal | Karl | 412-26 | k@cmu.edu |
| | Fischer | 8-8862 | |
+-------------------------+-------------+--------+--------------------+
| -------------------- | Peter | 412-26 | coppin@cmu.edu |
| Eventscope Portal to | Coppin | 8-1565 | |
| Mars | | | |
| | | | |
| -------------------- | | | |
+-------------------------+-------------+--------+--------------------+
| Eventscope Portal to | Karl | 412-26 | k@cmu.edu |
| Mars | Fischer | 8-1565 | |
+-------------------------+-------------+--------+--------------------+
| Haptics Augmented NASA | Jeff Seaton | 757-86 | j.m.se |
| Data Sets Online | | 4-6687 | aton@larc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Headquarters | Shelley | 202-35 | sca |
| | Canright | 8-1021 | nright@hq.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Headquarters | Phil West | 202-35 | Philip.r. |
| | | 8-1584 | west1@jsc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Headquarters/COTF | Nitin Naik | 202-35 | nnitin@hq.nasa.gov |
| | | 8-1100 | |
+-------------------------+-------------+--------+--------------------+
| Information | Dr. Robert | 281-48 | Robert. |
| Accessibility Lab | Shelton | 3-5901 | o.Shelton@nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Information | Stephanie | 281-48 | Stephanie.l.s |
| Accessibility Lab | Smith | 3-9626 | mith1@jsc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Information | Terry | 281-24 | terry.r.hod |
| Accessibility Lab | Hodgson | 4-5765 | gson1@jsc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Joined Digital Library | Blanche | 301-28 | bmeeson |
| | Meeson | 6-7831 | @see.gsfc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Joined Digital Library | Shelley E. | 301-28 | solds |
| | Olds | 6-1799 | @see.gsfc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| Joined Digital Library | Rob | 301-86 | Rob_a |
| | Antonucci | 7-2131 | ntonucci@sesda.com |
+-------------------------+-------------+--------+--------------------+
| Quest Innovative | Geoffrey | 650-60 | gbruce |
| Streaming | Bruce | 4-2587 | @mail.arc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| -------------------- | Tom Gaskins | 650-64 | tom@tomgaskins.com |
| Telescopes In | | 1-1786 | |
| Education | | | |
| | | | |
| -------------------- | | | |
+-------------------------+-------------+--------+--------------------+
| -------------------- | Gregg | 321-86 | Gregg.Bucking |
| Virtual Laboratory | Buckingham | 7-8777 | ham-1@ksc.nasa.gov |
| | | | |
| -------------------- | | | |
+-------------------------+-------------+--------+--------------------+
| Virtual Laboratory | Brandt | 321-86 | Brandt.Sec |
| | Secosh | 7-2107 | osh-1@ksc.nasa.gov |
+-------------------------+-------------+--------+--------------------+
| -------------------- | Ruth | 206-43 | Ruth.A.Pete |
| Virtual Wind Tunnel | Petersen | 3-9714 | rsen@lerc.nasa.gov |
| | | | |
| -------------------- | | | |
+-------------------------+-------------+--------+--------------------+
| en |
converted_docs | 206485 | Federal Communications Commission FCC 07-103
**STATEMENT OF**
**COMMISSIONER MICHAEL J. COPPS**
RE: Sunset of the Cellular Radiotelephone Service Analog Service
Requirement and Related Matters, RM No. 11355
In our initial decision to sunset over time the cellular
radiotelephone service analog requirement, I expressed concern about
whether industry would be able to develop digital devices in sufficient
time to enable digital service for individuals with hearing and speech
disabilities (who, at that time, relied exclusively on analog devices).
As it turned out, carriers, equipment manufacturers, members of the
disability community and the FCC were able to work together to develop
digital equipment solutions, even with some time to spare. Likewise,
other affected groups, such as the telematics industry, went to great
effort to prepare for the transition, and they now inform the Commission
that they, too, are ready for the transition. A lot of good work has
been done. I commend all the parties who came together to work on this.
We ***are*** transitioning to a new digital America. The
changes and wonders it will usher in are mind-boggling. But getting
there, and getting there together, takes some special commitment and
some very hard work. In this instance, we can now work to move the ball
forward. This action permits the wireless industry to redeploy spectrum
from analog to digital use, much to the enhancement of carriers' ability
to provide wireless broadband services. This change is of particular
importance to rural carriers, for whom the analog requirement is
disproportionately burdensome.
I do wish to comment briefly on the alarm industry's
assertion that---despite more than five years warning---it now requires
additional time to prepare for the transition. I am aware of the
challenges this industry, like others, confronted. But I think it is
neither equitable nor necessary to hold up the transition on this
account. As today's item explains, some of this industry's own data
indicates that there has been sufficient time to replace those alarms
that rely on cellular analog service as a primary means of
communication. It is an objective that can ***still be accomplished on
time*** if the industry determines that its single-minded focus going
forward should be on replacing radios rather than prolonging a search
for regulatory relief.
My thanks to all who worked so hard, both in the affected
industries and here at the Commission, to get this job done.
| en |
log-files | 956218 | Log_1 2001-12-20T13:16:56 blc_sa 1.6: Task blc_sa running in SINGLE mode
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Beginning parameters
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter obs_group = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter startLevel = COR
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter endLevel = IMA
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter only_clean = no
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter run_spiskymax = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter run_spiros = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter clobber = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spi_gain_corr_prpOG = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spi_gain_corr_inSWG =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spi_gain_corr_outfile =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spi_gain_corr_coeffDOL = /isdc/integration/spi_int/sw_rep/analysis-sw/spi/spi_gain_corr/spi_gain_coeff.fits[SPI.-COEF-CAL]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spi_gain_corr_clobber = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter blc_spipoint_rwgroup = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter blc_spipoint_swgroup = swg_spi.fits
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter blc_spipoint_pointing-file = spi/pointings.fits
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter blc_spipoint_time-correlation-dol = ../../aux/adp/0001.000/time_correlation.fits
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spigti_rogroup =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spigti_rwgroup = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spigti_ropointing =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spigti_rwgti = spi/gti.fits(SPI.-OBS.-GTI.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spigti_numdet = 85
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spigti_det_id = 0-84
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spigti_clobber = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spidead_in-og-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spidead_dead-time-dol = spi/dead_time.fits(SPI.-OBS.-DTI.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spidead_out-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spidead_swg-index-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spidead_gti-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spidead_clobber = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spidead_chatter = 20
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spidead_deadtimecorrection = 0.97
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_outfile =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_in-og-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_energy-boundaries-dol = spi/energy_boundaries.fits(SPI.-EBDS-SET.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_out-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_swg-index-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_gti-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_deadtime-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_ebounds-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_clobber = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_binfile = none
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_nregions = 5
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_regions = 25,40,654,669,2069,4069
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_nbins = 15,6,15,14,2
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_telescope = INTEGRAL
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_instrume = SPI
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_filter =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_bintype = PI
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_chatter = 20
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_clobber = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spibounds_mode = h
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_outfile = hist
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_in-og-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_det-spec-dol = spi/evts_det_spec.fits(SPI.-OBS.-DSP.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_out-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_swg-index-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_gti-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_deadtime-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_ebounds-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_clobber = yes
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_dtype = 1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_psdtype = raw
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_detnums = 0-84
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_multipointing = d
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_tstart = indef
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_tstop = indef
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_instrume = SPI
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_chatter = 20
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spihist_outputformat = ISDC
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_in-og-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_pointing-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_ebounds-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_evts-det-spec-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_gti-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_deadtime-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-mod-idx = spi/back_model_index.fits(SPI.-BMOD-DSP-IDX.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-mod-dol = back_model.fits(SPI.-BMOD-DSP.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_out-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-const = YES
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-const-value = 2.0e-5
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-linear = NO
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-linear-mjd0 = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-linear-slope = 0.1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-sincos = NO
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-sincos-mjd0 = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-sincos-period = 0.15
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-sin-amp = 1.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-cos-amp = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-model-gen = NO
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiback_back-model-comp-1 =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_mode = SPECTRA
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_in-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_pointing-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_gti-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_deadtime-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_ebounds-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_evts-det-spec-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_back-model-idx =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_source-cat-dol = source_res_in.fits[1]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_source-res = source_res.fits(SPI.-SRCL-RES.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_inst-resp-idx = /isdc/integration/ic/spi/rsp/spi_irf_grp_0007.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_out-og-dol = og_spiros.fits(GNRL-OBSG-GRP.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-idx = spi/spiros_image_index.fits(SPI.-SKY.-IMA-IDX.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-int = spi/spiros_image_int
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-err = spi/spiros_image_err
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-res = spi/spiros_image_res
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-sig = spi/spiros_image_sig
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_source-det-spec-idx = src_det_spec_index.fits(SPI.-SDET-SPE-IDX.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_source-det-spec = NO
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_back-det-spec-idx = spi/back_det_spec_index.fits(SPI.-BACK-DSP-IDX.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_back-det-spec = NO
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_reference-coord = RADEC
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-proj = CAR
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-fov = USER
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_center-long = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_center-lat = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-dim-long = 51
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-dim-lat = 51
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-pixel-long = 0.1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-pixel-lat = 0.1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_image-orient = STANDARD
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_pole-long = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_pole-lat = 90.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_optistat = CHI2
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_solution-constr = NONE
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_location-max-error = 0.1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_iteration-output = YES
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_pixel-func =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_pixel-size = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_constrtype =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_constrmult = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_constrincr = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_constriter = 0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_nagoptions =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_nofsources = 1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_kofsources = POINT
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_sigmathres = 3.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_srclocprec = 0.05
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_srcwidprec = 0.2
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_chilocstep = 0.05
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_chiwidstep = 0.2
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_energy-response = N
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_source-relocation = NO
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_background_method = 3
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_spectrum-binning = SINGLE
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_source-spec-idx = spi/source_spectra_index.fits(SPI.-SRC.-SPE-IDX.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_source-spec = source_spectra.fits
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_blur-size = 1.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_srclocbins = COUNT
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_source-spec-qdp = YES
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_ebinfunc = XSPEC
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_nofebins = 0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_ebinscal =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_ebinsamp = 5.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiros_response-file = N
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_debug = 0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_display = 0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_title = spiskymax v20 137-Cs processing
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_rogroup = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_rwgroup =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_counts_input_file =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_pointing_input_file =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_ebounds_input_file =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_deadtime-dol =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_background_input_file =
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_irf_input_file = /isdc/integration/ic/spi/rsp/spi_irf_grp_0007.fits[GROUPING]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_source-cat-dol = source_res_in.fits[1]
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_image-idx = spi/skymax_index.fits(SPI.-SKY.-IMA-IDX.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_image-int = skymax_image.fits
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_source-res-dol = spi/spiskymax_sources.fits(SPI.-SRCL-RES.tpl)
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_skymap_system = C
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_image-fov = SURVEY
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_center-long = 1.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_center-lat = 2.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_image-pixel-long = 0.5
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_image-pixel-lat = 0.5
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_image-dim-long = 40
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_image-dim-lat = 41
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_chi_0 = -10.
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_chi_1 = +10.
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_d_chi = 0.50
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_psi_0 = -10.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_psi_1 = +10.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_d_psi = 0.50
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_energy_range_min = 1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_energy_range_max = 52
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_max_iter = 100
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_image_default = 1.0e-3
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_background_scaling_default = 1.0e-0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_background_entropy_factor = 1.0e-0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_background_method = 2
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_memsys_iBayes = 1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_memsys_iEntropy = 1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_memsys_fAim = 1.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_n_source_fluxes = 1
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_source_chi_1 = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_source_psi_1 = 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_source_ON_radius_1 = 2.00
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_source_OFF_radius_1 = 4.00
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_n_profiles = 0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_profile_chi_0 = 180.0 180.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_profile_chi_1 = 200.0 200.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_profile_d_chi = 1.0 2.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_profile_psi_0 = +2.0 +2.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_profile_psi_1 = +2.0 +2.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_profile_d_psi = 2.0 2.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_xn_profiles = 6
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_xprofile_chi_0 = -20.0 -20.0 -20.0 +1.0 +1.0 0.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_xprofile_chi_1 = +20.0 +20.0 +20.0 +1.0 +1.0 6.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_xprofile_d_chi = 1.0 2.0 5.0 4.0 2.0 2.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_xprofile_psi_0 = -0.0 0.0 -0.0 -20.0 -20.0 -20.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_xprofile_psi_1 = +0.0 +0.0 +0.0 +20.0 +20.0 +20.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Parameter spiskymax_xprofile_d_psi = 2.0 2.0 3.0 1.0 2.0 1.0
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Ending parameters
Log_1 2001-12-20T13:16:56 blc_sa 1.6: Running in normal mode, default parameter prompting
Log_0 2001-12-20T13:16:56 blc_sa 1.6: Attempting to launch GUI for task blc_sa
Log_1 2001-12-20T13:17:09 blc_sa 1.6: Current ISDCLEVL is PRP
Log_0 2001-12-20T13:17:09 blc_sa 1.6: We will step forward in the standard analysis.
Log_0 2001-12-20T13:17:09 blc_sa 1.6: The only_cleaning is set to 0
Log_0 2001-12-20T13:17:09 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/spi_gain_corr prpOG="og_spi.fits[GROUPING]" inSWG="" outfile="" coeffDOL="/isdc/integration/spi_int/sw_rep/analysis-sw/spi/spi_gain_corr/spi_gain_coeff.fits[SPI.-COEF-CAL]" clobber="yes" | tee /tmp/isdcroot.32741.6709.out
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Task spi_gain_corr running in SINGLE mode
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Beginning parameters
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Parameter prpOG = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Parameter inSWG =
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Parameter outfile =
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Parameter coeffDOL = /isdc/integration/spi_int/sw_rep/analysis-sw/spi/spi_gain_corr/spi_gain_coeff.fits[SPI.-COEF-CAL]
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Parameter clobber = yes
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Ending parameters
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: Running in normal mode, default parameter prompting
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: ************************************************************
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: * spi_gain_corr *
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: * -------------------------------------------------------- *
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: * Version : 0.8.0 *
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: * Date : 17-December-2001 *
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: * Authors : Jurgen Knodlseder (CESR) / P.D. & V.B. (ISDC) *
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: * Low energy gain coefficients provided by MPE *
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: * High energy gain coefficients provided by CEA-CE Saclay *
Log_0 2001-12-20T13:17:09 spi_gain_corr 0.8.0: ************************************************************
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: corrected data --STAMP-- og_spi.fits[GROUPING,1,BINTABLE]
Log_1 2001-12-20T13:17:09 spi_gain_corr 0.8.0: 1 SWG found in og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2001-12-20T13:17:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000108900010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_0 2001-12-20T13:17:11 spi_gain_corr 0.8.0: Task terminated.
Log_1 2001-12-20T13:17:11 spi_gain_corr 0.8.0: Task spi_gain_corr terminating with status 0
Log_0 2001-12-20T13:17:11 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/blc_spipoint rwgroup="og_spi.fits[GROUPING]" swgroup="swg_spi.fits" pointing-file="spi/pointings.fits" time-correlation-dol="../../aux/adp/0001.000/time_correlation.fits" | tee /tmp/isdcroot.882.8058.out
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Task blc_spipoint running in SINGLE mode
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Beginning parameters
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Parameter rwgroup = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Parameter swgroup = swg_spi.fits
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Parameter pointing-file = spi/pointings.fits
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Parameter time-correlation-dol = ../../aux/adp/0001.000/time_correlation.fits
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Ending parameters
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Running in normal mode, default parameter prompting
Log_0 2001-12-20T13:17:12 blc_spipoint 1.8:
Log_0 2001-12-20T13:17:12 blc_spipoint 1.8: TSTART[1]: 467.154018
Log_0 2001-12-20T13:17:12 blc_spipoint 1.8: TSTOP [1]: 467.165893
Log_0 2001-12-20T13:17:12 blc_spipoint 1.8: 1 SW paths found in directory scw
Log_0 2001-12-20T13:17:12 blc_spipoint 1.8: 1 SWG files found.
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: creation of pointing structure --STAMP-- spi/pointings.fits[SPI.-OBS.-PNT,1,BINTABLE]
Log_0 2001-12-20T13:17:12 blc_spipoint 1.8: Created successfully spi/pointings.fits(SPI.-OBS.-PNT.tpl)
Log_0 2001-12-20T13:17:12 blc_spipoint 1.8: Running dal_attach Parent="/unsaved_data/spi_int/single_scws/obs/obs089/og_spi.fits[GROUPING]" Child1="spi/pointings.fits[1]" Child2="" Child3="" Child4="" Child5="" | tee /tmp/isdcroot.17720.25116.out
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Task dal_attach running in SINGLE mode
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Beginning parameters
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Parameter Parent = /unsaved_data/spi_int/single_scws/obs/obs089/og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Parameter Child1 = spi/pointings.fits[1]
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Parameter Child2 =
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Parameter Child3 =
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Parameter Child4 =
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Parameter Child5 =
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Ending parameters
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Running in normal mode, default parameter prompting
Log_1 2001-12-20T13:17:12 dal_attach 1.2.1: Task dal_attach terminating with status 0
Log_0 2001-12-20T13:17:12 blc_spipoint 1.8: Attached spi/pointings.fits[1] to the OG /unsaved_data/spi_int/single_scws/obs/obs089/og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Reached the end of blc_spipoint, status 0
Log_1 2001-12-20T13:17:12 blc_spipoint 1.8: Task blc_spipoint terminating with status 0
Log_0 2001-12-20T13:17:13 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/spigti rogroup="" rwgroup="og_spi.fits[GROUPING]" ropointing="" rwgti="spi/gti.fits(SPI.-OBS.-GTI.tpl)" numdet="85" det_id="0-84" clobber="yes" | tee /tmp/isdcroot.1790.9407.out
Log_1 2001-12-20T13:17:13 spigti 1.8: Task spigti running in SINGLE mode
Log_1 2001-12-20T13:17:13 spigti 1.8: Beginning parameters
Log_1 2001-12-20T13:17:13 spigti 1.8: Parameter rogroup =
Log_1 2001-12-20T13:17:13 spigti 1.8: Parameter rwgroup = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:13 spigti 1.8: Parameter ropointing =
Log_1 2001-12-20T13:17:13 spigti 1.8: Parameter rwgti = spi/gti.fits(SPI.-OBS.-GTI.tpl)
Log_1 2001-12-20T13:17:13 spigti 1.8: Parameter numdet = 85
Log_1 2001-12-20T13:17:13 spigti 1.8: Parameter det_id = 0-84
Log_1 2001-12-20T13:17:13 spigti 1.8: Parameter clobber = yes
Log_1 2001-12-20T13:17:13 spigti 1.8: Ending parameters
Log_1 2001-12-20T13:17:13 spigti 1.8: Running in normal mode, default parameter prompting
Log_0 2001-12-20T13:17:13 spigti 1.8: Start calculation of the SPI gti
Log_0 2001-12-20T13:17:13 spigti 1.8: List of 85 detectors:
Log_0 2001-12-20T13:17:13 spigti 1.8: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Log_0 2001-12-20T13:17:13 spigti 1.8: 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
Log_0 2001-12-20T13:17:13 spigti 1.8: 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
Log_0 2001-12-20T13:17:13 spigti 1.8: 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59
Log_0 2001-12-20T13:17:13 spigti 1.8: 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
Log_0 2001-12-20T13:17:13 spigti 1.8: 75 76 77 78 79 80 81 82 83 84
Log_0 2001-12-20T13:17:13 spigti 1.8: Accessing some GTI data from housekeeping. They are not used, so do not worry about eventually occuring errors!
Log_0 2001-12-20T13:17:13 spigti 1.8: number of DATA_GAPS entries: 8
Log_1 2001-12-20T13:17:13 spigti 1.8: OBTStart0 = 467.154435, numValues = 1
Log_1 2001-12-20T13:17:13 spigti 1.8: OBTStop0 = 467.166310, numValues = 1
Log_1 2001-12-20T13:17:13 spigti 1.8: numValues from DAL3HKgetNumGTI = 8
Log_1 2001-12-20T13:17:13 spigti 1.8: GTI access test finished. Status set back to 0
Log_0 2001-12-20T13:17:13 spigti 1.8: Mean ontime for all detectors: 1026.000000
Log_1 2001-12-20T13:17:13 spigti 1.8: creation of GTI structure --STAMP-- spi/gti.fits[SPI.-OBS.-GTI,1,BINTABLE]
Log_0 2001-12-20T13:17:13 spigti 1.8: End of calculation of the SPI gti
Log_1 2001-12-20T13:17:13 spigti 1.8: Task spigti terminating with status 0
Log_0 2001-12-20T13:17:13 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/spidead in-og-dol="" dead-time-dol="spi/dead_time.fits(SPI.-OBS.-DTI.tpl)" out-og-dol="og_spi.fits[GROUPING]" swg-index-dol="" gti-dol="" clobber="yes" chatter="20" deadtimecorrection="0.97" | tee /tmp/isdcroot.1790.9407.out
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Task /isdc/integration/spi_int/sw_rep/bin/spidead running in SINGLE mode
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Beginning parameters
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Parameter in-og-dol =
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Parameter dead-time-dol = spi/dead_time.fits(SPI.-OBS.-DTI.tpl)
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Parameter out-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Parameter swg-index-dol =
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Parameter gti-dol =
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Parameter clobber = yes
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Parameter chatter = 20
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Parameter deadtimecorrection = 0.97
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Ending parameters
Log_1 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Running in normal mode, default parameter prompting
Log_0 2001-12-20T13:17:13 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Start calculation of the SPI dead times
Log_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Assumed live time fraction for pseudo detectors: 0.970000
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[19] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[20] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[21] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[22] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[23] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[24] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[25] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[26] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[27] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[28] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[29] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[30] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[31] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[32] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[33] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[34] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[35] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[36] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[37] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[38] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[39] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[40] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[41] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[42] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[43] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[44] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[45] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[46] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[47] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[48] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[49] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[50] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[51] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[52] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[53] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[54] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[55] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[56] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[57] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[58] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[59] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[60] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[61] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[62] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[63] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[64] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[65] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[66] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[67] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[68] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[69] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[70] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[71] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[72] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[73] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[74] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[75] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[76] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[77] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[78] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[79] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[80] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[81] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[82] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[83] = 0.97
Warn_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: deadtimec[84] = 0.97
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: creation of DTI structure --STAMP-- spi/dead_time.fits[SPI.-OBS.-DTI,1,BINTABLE]
Log_0 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: End of calculation of the SPI dead times
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spidead 1.4: Task /isdc/integration/spi_int/sw_rep/bin/spidead terminating with status 0
Log_0 2001-12-20T13:17:14 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/spibounds outfile="" in-og-dol="" energy-boundaries-dol="spi/energy_boundaries.fits(SPI.-EBDS-SET.tpl)" out-og-dol="og_spi.fits[GROUPING]" swg-index-dol="" gti-dol="" deadtime-dol="" ebounds-dol="" clobber="yes" binfile="none" nregions="5" regions="25,40,654,669,2069,4069" nbins="15,6,15,14,2" telescope="INTEGRAL" instrume="SPI" filter="" bintype="PI" chatter="20" clobber="yes" mode="h" | tee /tmp/isdcroot.18629.26466.out
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Task /isdc/integration/spi_int/sw_rep/bin/spibounds running in SINGLE mode
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Beginning parameters
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter outfile =
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter in-og-dol =
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter energy-boundaries-dol = spi/energy_boundaries.fits(SPI.-EBDS-SET.tpl)
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter out-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter swg-index-dol =
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter gti-dol =
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter deadtime-dol =
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter ebounds-dol =
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter clobber = yes
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter binfile = none
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter nregions = 5
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter regions = 25,40,654,669,2069,4069
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter nbins = 15,6,15,14,2
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter telescope = INTEGRAL
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter instrume = SPI
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter filter =
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter bintype = PI
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter chatter = 20
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter clobber = yes
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Parameter mode = h
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Ending parameters
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Running in normal mode, default parameter prompting
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7:
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: SPIBOUNDS Version 1.0.7
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7:
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7:
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Group: /unsaved_data/spi_int/single_scws/obs/obs089/og_spi.fits[GROUPING,1,BINTABLE]
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: binfile: NONE
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: nregions: 5
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: region: 25.000000 - 40.000000 number of bins: 15
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: region: 40.000000 - 654.000000 number of bins: 6
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: region: 654.000000 - 669.000000 number of bins: 15
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: region: 669.000000 - 2069.000000 number of bins: 14
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: region: 2069.000000 - 4069.000000 number of bins: 2
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: telescope: INTEGRAL
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: instrume: SPI
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: filter:
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: chantype: PI
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: chatter: 20
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: clobber: 1
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7:
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Creating Binning File...
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7:
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: ... Using CreateEboundsExt 1.0.0
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: ... Written the extension header keywords
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: ... Successfully written the EBOUNDS extension
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Cleaning up...
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Program executed successfully.
Log_1 2001-12-20T13:17:14 /isdc/integration/spi_int/sw_rep/bin/spibounds 1.0.7: Task /isdc/integration/spi_int/sw_rep/bin/spibounds terminating with status 0
Log_0 2001-12-20T13:17:15 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/spihist outfile="hist" in-og-dol="" det-spec-dol="spi/evts_det_spec.fits(SPI.-OBS.-DSP.tpl)" out-og-dol="og_spi.fits[GROUPING]" swg-index-dol="" gti-dol="" deadtime-dol="" ebounds-dol="" clobber="yes" dtype="1" psdtype="raw" detnums="0-84" multipointing="d" tstart="indef" tstop="indef" instrume="SPI" chatter="20" outputformat="ISDC" | tee /tmp/isdcroot.2699.10756.out
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Task /isdc/integration/spi_int/sw_rep/bin/spihist running in SINGLE mode
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Beginning parameters
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter outfile = hist
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter in-og-dol =
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter det-spec-dol = spi/evts_det_spec.fits(SPI.-OBS.-DSP.tpl)
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter out-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter swg-index-dol =
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter gti-dol =
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter deadtime-dol =
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter ebounds-dol =
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter clobber = yes
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter dtype = 1
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter psdtype = raw
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter detnums = 0-84
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter multipointing = d
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter tstart = indef
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter tstop = indef
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter instrume = SPI
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter chatter = 20
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Parameter outputformat = ISDC
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Ending parameters
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Running in normal mode, default parameter prompting
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: SPIHIST Version 2.1.5
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: tstart: INDEF
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: tstop: INDEF
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: format: ISDC
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: instrumet: SPI
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: clobber: 1
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: chatter: 20
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Verifying input parameters...
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Reading Binning File...
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Reading Pointing Extension...
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Reading Good Time Extension...
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Pointing(s) (1-1):
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: 467.154435 - 467.166310
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Processing detectors of multiplicity 0...
Log_1 2001-12-20T13:17:15 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Reading events...
Log_1 2001-12-20T13:17:17 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: OBTStart = 467.154435
Log_1 2001-12-20T13:17:17 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: OBTStop = 467.166310
Log_1 2001-12-20T13:17:17 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: spihist found 68534 events
Log_1 2001-12-20T13:17:17 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: time selected: 467.154530 467.166216
Log_1 2001-12-20T13:17:17 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: nEvents: 68534 numGoodEvents: 68527
Log_1 2001-12-20T13:17:17 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Processing Data...
Log_1 2001-12-20T13:17:18 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:18 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Processing detectors of multiplicity 1...
Log_1 2001-12-20T13:17:18 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Reading events...
Log_1 2001-12-20T13:17:19 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: OBTStart = 467.154435
Log_1 2001-12-20T13:17:19 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: OBTStop = 467.166310
Log_1 2001-12-20T13:17:19 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: spihist found 111775 events
Log_1 2001-12-20T13:17:19 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: time selected: 467.154530 467.166216
Log_1 2001-12-20T13:17:19 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: nEvents: 111775 numGoodEvents: 110983
Log_1 2001-12-20T13:17:19 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Processing Data...
Log_1 2001-12-20T13:17:20 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:20 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Processing detectors of multiplicity 2...
Log_1 2001-12-20T13:17:20 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Reading events...
Log_1 2001-12-20T13:17:22 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: OBTStart = 467.154435
Log_1 2001-12-20T13:17:22 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: OBTStop = 467.166310
Log_1 2001-12-20T13:17:22 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: spihist found 60129 events
Log_1 2001-12-20T13:17:22 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: time selected: 467.154530 467.166216
Log_1 2001-12-20T13:17:22 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: nEvents: 60129 numGoodEvents: 59941
Log_1 2001-12-20T13:17:22 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Processing Data...
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Processing detectors of multiplicity 3...
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Reading events...
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: OBTStart = 467.154435
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: OBTStop = 467.166310
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: spihist found 7920 events
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: time selected: 467.154532 467.166215
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: nEvents: 7920 numGoodEvents: 7917
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Processing Data...
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5:
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: ... Using DataExtension 1.0.0
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: ... Written the extension header keywords
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Cleaning up...
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Program executed successfully.
Log_1 2001-12-20T13:17:23 /isdc/integration/spi_int/sw_rep/bin/spihist 2.1.5: Task /isdc/integration/spi_int/sw_rep/bin/spihist terminating with status 0
Log_0 2001-12-20T13:17:23 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/spiback in-og-dol="" pointing-dol="" ebounds-dol="" evts-det-spec-dol="" gti-dol="" deadtime-dol="" back-mod-idx="spi/back_model_index.fits(SPI.-BMOD-DSP-IDX.tpl)" back-mod-dol="back_model.fits(SPI.-BMOD-DSP.tpl)" out-og-dol="og_spi.fits[GROUPING]" back-const="YES" back-const-value="2e-05" back-linear="NO" back-linear-mjd0="0" back-linear-slope="0.1" back-sincos="NO" back-sincos-mjd0="0" back-sincos-period="0.15" back-sin-amp="1" back-cos-amp="0" back-model-gen="NO" back-model-comp-1="" | tee /tmp/isdcroot.6333.16153.out
Log_1 2001-12-20T13:17:24 spiback 2.2: Task spiback running in SINGLE mode
Log_1 2001-12-20T13:17:24 spiback 2.2: Beginning parameters
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter in-og-dol =
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter pointing-dol =
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter ebounds-dol =
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter evts-det-spec-dol =
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter gti-dol =
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter deadtime-dol =
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-mod-idx = spi/back_model_index.fits(SPI.-BMOD-DSP-IDX.tpl)
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-mod-dol = back_model.fits(SPI.-BMOD-DSP.tpl)
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter out-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-const = YES
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-const-value = 2e-05
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-linear = NO
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-linear-mjd0 = 0
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-linear-slope = 0.1
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-sincos = NO
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-sincos-mjd0 = 0
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-sincos-period = 0.15
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-sin-amp = 1
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-cos-amp = 0
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-model-gen = NO
Log_1 2001-12-20T13:17:24 spiback 2.2: Parameter back-model-comp-1 =
Log_1 2001-12-20T13:17:24 spiback 2.2: Ending parameters
Log_1 2001-12-20T13:17:24 spiback 2.2: Running in normal mode, default parameter prompting
Log_0 2001-12-20T13:17:24 spiback 2.2: Reading input parameters for executable program spiback_main
Log_0 2001-12-20T13:17:24 spiback 2.2: Background has a CONSTANT component with amplitude 0.000020000 cnts/sec/kev/det.
Alert_1 2001-12-20T13:17:24 spiback 2.2: Source catalogue not specified in the OGDI so will assume there are no known sources
Log_0 2001-12-20T13:17:24 spiback 2.2: Count data is for 85 detectors, 1 pointings and 52 energy bins
Log_0 2001-12-20T13:17:24 spiback 2.2: Allocating data arrays for <spiback> in memory.
Log_0 2001-12-20T13:17:24 spiback 2.2: Creating output background response data and its index file
Log_1 2001-12-20T13:17:24 spiback 2.2: Created by subroutine "spiback_output_index" --STAMP-- spi/back_model_index.fits[GROUPING,1,BINTABLE]
Log_1 2001-12-20T13:17:24 spiback 2.2: Created by subroutine "spiback_output_component" --STAMP-- spi/back_model.fits[SPI.-BMOD-DSP,1,BINTABLE]
Log_0 2001-12-20T13:17:24 spiback 2.2: CONSTANT component 1 has been created and attached to background model index.
Log_0 2001-12-20T13:17:24 spiback 2.2:
Log_0 2001-12-20T13:17:24 spiback 2.2: Exiting SPIBACK
Log_0 2001-12-20T13:17:24 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/spiros mode="SPECTRA" in-og-dol="og_spi.fits[GROUPING]" pointing-dol="" gti-dol="" deadtime-dol="" ebounds-dol="" evts-det-spec-dol="" back-model-idx="" source-cat-dol="source_res_in.fits[1]" source-res="source_res.fits(SPI.-SRCL-RES.tpl)" inst-resp-idx="/isdc/integration/ic/spi/rsp/spi_irf_grp_0007.fits[GROUPING]" out-og-dol="og_spiros.fits(GNRL-OBSG-GRP.tpl)" image-idx="spi/spiros_image_index.fits(SPI.-SKY.-IMA-IDX.tpl)" image-int="spi/spiros_image_int" image-err="spi/spiros_image_err" image-res="spi/spiros_image_res" image-sig="spi/spiros_image_sig" source-det-spec-idx="src_det_spec_index.fits(SPI.-SDET-SPE-IDX.tpl)" source-det-spec="NO" back-det-spec-idx="spi/back_det_spec_index.fits(SPI.-BACK-DSP-IDX.tpl)" back-det-spec="NO" reference-coord="RADEC" image-proj="CAR" image-fov="USER" center-long="0" center-lat="0" image-dim-long="51" image-dim-lat="51" image-pixel-long="0.1" image-pixel-lat="0.1" image-orient="STANDARD" pole-long="0" pole-lat="90" optistat="CHI2" solution-constr="NONE" location-max-error="0.1" iteration-output="YES" pixel-func="" pixel-size="0" constrtype="" constrmult="0" constrincr="0" constriter="0" nagoptions="" nofsources="1" kofsources="POINT" sigmathres="3" srclocprec="0.05" srcwidprec="0.2" chilocstep="0.05" chiwidstep="0.2" energy-response="N" source-relocation="NO" background_method="3" spectrum-binning="SINGLE" source-spec-idx="spi/source_spectra_index.fits(SPI.-SRC.-SPE-IDX.tpl)" source-spec="source_spectra.fits" blur-size="1" srclocbins="COUNT" source-spec-qdp="YES" ebinfunc="XSPEC" nofebins="0" ebinscal="" ebinsamp="5" response-file="N" | tee /tmp/isdcroot.23172.444.out
Log_1 2001-12-20T13:17:25 spiros 2.3: Task spiros running in SINGLE mode
Log_1 2001-12-20T13:17:25 spiros 2.3: Beginning parameters
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter mode = SPECTRA
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter in-og-dol = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter pointing-dol =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter gti-dol =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter deadtime-dol =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter ebounds-dol =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter evts-det-spec-dol =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter back-model-idx =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter source-cat-dol = source_res_in.fits[1]
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter source-res = source_res.fits(SPI.-SRCL-RES.tpl)
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter inst-resp-idx = /isdc/integration/ic/spi/rsp/spi_irf_grp_0007.fits[GROUPING]
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter out-og-dol = og_spiros.fits(GNRL-OBSG-GRP.tpl)
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-idx = spi/spiros_image_index.fits(SPI.-SKY.-IMA-IDX.tpl)
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-int = spi/spiros_image_int
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-err = spi/spiros_image_err
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-res = spi/spiros_image_res
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-sig = spi/spiros_image_sig
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter source-det-spec-idx = src_det_spec_index.fits(SPI.-SDET-SPE-IDX.tpl)
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter source-det-spec = NO
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter back-det-spec-idx = spi/back_det_spec_index.fits(SPI.-BACK-DSP-IDX.tpl)
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter back-det-spec = NO
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter reference-coord = RADEC
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-proj = CAR
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-fov = USER
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter center-long = 0
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter center-lat = 0
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-dim-long = 51
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-dim-lat = 51
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-pixel-long = 0.1
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-pixel-lat = 0.1
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter image-orient = STANDARD
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter pole-long = 0
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter pole-lat = 90
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter optistat = CHI2
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter solution-constr = NONE
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter location-max-error = 0.1
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter iteration-output = YES
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter pixel-func =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter pixel-size = 0
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter constrtype =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter constrmult = 0
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter constrincr = 0
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter constriter = 0
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter nagoptions =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter nofsources = 1
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter kofsources = POINT
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter sigmathres = 3
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter srclocprec = 0.05
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter srcwidprec = 0.2
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter chilocstep = 0.05
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter chiwidstep = 0.2
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter energy-response = N
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter source-relocation = NO
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter background_method = 3
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter spectrum-binning = SINGLE
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter source-spec-idx = spi/source_spectra_index.fits(SPI.-SRC.-SPE-IDX.tpl)
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter source-spec = source_spectra.fits
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter blur-size = 1
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter srclocbins = COUNT
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter source-spec-qdp = YES
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter ebinfunc = XSPEC
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter nofebins = 0
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter ebinscal =
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter ebinsamp = 5
Log_1 2001-12-20T13:17:25 spiros 2.3: Parameter response-file = N
Log_1 2001-12-20T13:17:25 spiros 2.3: Ending parameters
Log_1 2001-12-20T13:17:25 spiros 2.3: Running in normal mode, default parameter prompting
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: ==================================================================================================
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_main> will now execute all data preprocessing steps required prior to image reconstruction
Log_0 2001-12-20T13:17:25 spiros 2.3: ==================================================================================================
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_main> retrieving program input parameters with <spiros_parameters>.
Log_0 2001-12-20T13:17:25 spiros 2.3: Reading input parameters for executable program spiros
Log_0 2001-12-20T13:17:25 spiros 2.3: There are no special options for NAG subroutines.
Log_0 2001-12-20T13:17:25 spiros 2.3: Will solve for image/source intensities as a set of simultaneous equations.
Log_0 2001-12-20T13:17:25 spiros 2.3: Background model values will be handled as relative function values.
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_main> retrieving observation parameters with <spibham_input_observ_parm>!
Log_0 2001-12-20T13:17:25 spiros 2.3: Count data is for 85 detectors, 1 pointings, 52 energy bins and 1 background model components
Alert_0 2001-12-20T13:17:25 spiros 2.3: There is only one pointing exposure!
Alert_0 2001-12-20T13:17:25 spiros 2.3: A single background rate multiplier only will be returned.
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_main> reading in observation group data with <spiros_imaging_count_data>.
Log_0 2001-12-20T13:17:25 spiros 2.3: Image and pointing coordinate system will be RADEC
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_imaging_count_data> reading in background model component response with <spibham_input_observ_data>.
Log_0 2001-12-20T13:17:25 spiros 2.3: Count variance values will be modified with a mean value for low counts using CHI2 optimization
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_imaging_count_data> reading in background model component response with <spibham_input_backgr_data>.
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_main> configuring IRF control blocks in <DAL3SPIgetDetectorIRF_config>!
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: Image FOV is a 51 by 51 grid of 0.10 by 0.10 degree pixels centred at 0.000, 0.000
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: There will be no reconstruction of an image pixel array for diffuse emission.
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_main> allocating space for 4 sources, 88 pixels and 208 energy bins
Log_0 2001-12-20T13:17:25 spiros 2.3: Allocating image arrays for a maximum length of 1048576
Log_0 2001-12-20T13:17:25 spiros 2.3: Constructing pixel and energy bin parameters for detector background components.
Log_0 2001-12-20T13:17:25 spiros 2.3: Constructing pixel and energy bin parameters of sources from input catalogue.
Log_0 2001-12-20T13:17:25 spiros 2.3: There will be no imaging of sources - spectral extraction of known sources only.
Log_0 2001-12-20T13:17:25 spiros 2.3:
Log_0 2001-12-20T13:17:25 spiros 2.3: ===============================================================================
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_source_spectra> now extracting the spectra of all known and new sources
Log_0 2001-12-20T13:17:25 spiros 2.3: ===============================================================================
Log_0 2001-12-20T13:17:25 spiros 2.3: <spiros_source_spectra> will now extract spectra in single energy bins with <spiros_source_spectra_binwise>
Log_0 2001-12-20T13:17:30 spiros 2.3:
Log_0 2001-12-20T13:17:30 spiros 2.3: ---------------------------------------------------------------------------------------------------
Log_0 2001-12-20T13:17:30 spiros 2.3: Source Pixels Source-flux Flux-error Sigma Source-location Type Indentifier/variability
Log_0 2001-12-20T13:17:30 spiros 2.3: ---------------------------------------------------------------------------------------------------
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 85 0.2656E+06 695.3 382.0 0.000 0.000 D BACKGROUND / CONSTANT
Log_0 2001-12-20T13:17:31 spiros 2.3: 1 1 2.745 0.6587E-02 416.8 0.000 0.000 S SOURCE-1 / CONSTANT
Log_0 2001-12-20T13:17:31 spiros 2.3:
Log_0 2001-12-20T13:17:31 spiros 2.3: ------------------------------------------------------------------------------------------------
Log_0 2001-12-20T13:17:31 spiros 2.3: Source Pixel-no Pixel-flux Flux-error Sigma Pixel-location Pixel-shape Width Index
Log_0 2001-12-20T13:17:31 spiros 2.3: ------------------------------------------------------------------------------------------------
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 1 3124. 75.41 41.4 0.000 0.000 POINT 0.000 1
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 2 3124. 75.41 41.4 0.000 0.000 POINT 0.000 2
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 3 3124. 75.41 41.4 0.000 0.000 POINT 0.000 3
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 4 3124. 75.41 41.4 0.000 0.000 POINT 0.000 4
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 5 3124. 75.41 41.4 0.000 0.000 POINT 0.000 5
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 6 3124. 75.41 41.4 0.000 0.000 POINT 0.000 6
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 7 3124. 75.41 41.4 0.000 0.000 POINT 0.000 7
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 8 3124. 75.41 41.4 0.000 0.000 POINT 0.000 8
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 9 3124. 75.41 41.4 0.000 0.000 POINT 0.000 9
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 10 3124. 75.41 41.4 0.000 0.000 POINT 0.000 10
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 11 3124. 75.41 41.4 0.000 0.000 POINT 0.000 11
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 12 3124. 75.41 41.4 0.000 0.000 POINT 0.000 12
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 13 3124. 75.41 41.4 0.000 0.000 POINT 0.000 13
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 14 3124. 75.41 41.4 0.000 0.000 POINT 0.000 14
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 15 3124. 75.41 41.4 0.000 0.000 POINT 0.000 15
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 16 3124. 75.41 41.4 0.000 0.000 POINT 0.000 16
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 17 3124. 75.41 41.4 0.000 0.000 POINT 0.000 17
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 18 3124. 75.41 41.4 0.000 0.000 POINT 0.000 18
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 19 3124. 75.41 41.4 0.000 0.000 POINT 0.000 19
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 20 3124. 75.41 41.4 0.000 0.000 POINT 0.000 20
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 21 3124. 75.41 41.4 0.000 0.000 POINT 0.000 21
Log_0 2001-12-20T13:17:31 spiros 2.3: 0 22 3124. 75.41 41.4 0.000 0.000 POINT 0.000 22
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 23 3124. 75.41 41.4 0.000 0.000 POINT 0.000 23
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 24 3124. 75.41 41.4 0.000 0.000 POINT 0.000 24
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 25 3124. 75.41 41.4 0.000 0.000 POINT 0.000 25
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 26 3124. 75.41 41.4 0.000 0.000 POINT 0.000 26
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 27 3124. 75.41 41.4 0.000 0.000 POINT 0.000 27
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 28 3124. 75.41 41.4 0.000 0.000 POINT 0.000 28
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 29 3124. 75.41 41.4 0.000 0.000 POINT 0.000 29
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 30 3124. 75.41 41.4 0.000 0.000 POINT 0.000 30
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 31 3124. 75.41 41.4 0.000 0.000 POINT 0.000 31
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 32 3124. 75.41 41.4 0.000 0.000 POINT 0.000 32
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 33 3124. 75.41 41.4 0.000 0.000 POINT 0.000 33
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 34 3124. 75.41 41.4 0.000 0.000 POINT 0.000 34
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 35 3124. 75.41 41.4 0.000 0.000 POINT 0.000 35
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 36 3124. 75.41 41.4 0.000 0.000 POINT 0.000 36
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 37 3124. 75.41 41.4 0.000 0.000 POINT 0.000 37
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 38 3124. 75.41 41.4 0.000 0.000 POINT 0.000 38
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 39 3124. 75.41 41.4 0.000 0.000 POINT 0.000 39
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 40 3124. 75.41 41.4 0.000 0.000 POINT 0.000 40
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 41 3124. 75.41 41.4 0.000 0.000 POINT 0.000 41
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 42 3124. 75.41 41.4 0.000 0.000 POINT 0.000 42
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 43 3124. 75.41 41.4 0.000 0.000 POINT 0.000 43
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 44 3124. 75.41 41.4 0.000 0.000 POINT 0.000 44
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 45 3124. 75.41 41.4 0.000 0.000 POINT 0.000 45
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 46 3124. 75.41 41.4 0.000 0.000 POINT 0.000 46
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 47 3124. 75.41 41.4 0.000 0.000 POINT 0.000 47
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 48 3124. 75.41 41.4 0.000 0.000 POINT 0.000 48
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 49 3124. 75.41 41.4 0.000 0.000 POINT 0.000 49
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 50 3124. 75.41 41.4 0.000 0.000 POINT 0.000 50
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 51 3124. 75.41 41.4 0.000 0.000 POINT 0.000 51
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 52 3124. 75.41 41.4 0.000 0.000 POINT 0.000 52
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 53 3124. 75.41 41.4 0.000 0.000 POINT 0.000 53
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 54 3124. 75.41 41.4 0.000 0.000 POINT 0.000 54
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 55 3124. 75.41 41.4 0.000 0.000 POINT 0.000 55
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 56 3124. 75.41 41.4 0.000 0.000 POINT 0.000 56
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 57 3124. 75.41 41.4 0.000 0.000 POINT 0.000 57
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 58 3124. 75.41 41.4 0.000 0.000 POINT 0.000 58
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 59 3124. 75.41 41.4 0.000 0.000 POINT 0.000 59
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 60 3124. 75.41 41.4 0.000 0.000 POINT 0.000 60
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 61 3124. 75.41 41.4 0.000 0.000 POINT 0.000 61
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 62 3124. 75.41 41.4 0.000 0.000 POINT 0.000 62
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 63 3124. 75.41 41.4 0.000 0.000 POINT 0.000 63
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 64 3124. 75.41 41.4 0.000 0.000 POINT 0.000 64
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 65 3124. 75.41 41.4 0.000 0.000 POINT 0.000 65
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 66 3124. 75.41 41.4 0.000 0.000 POINT 0.000 66
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 67 3124. 75.41 41.4 0.000 0.000 POINT 0.000 67
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 68 3124. 75.41 41.4 0.000 0.000 POINT 0.000 68
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 69 3124. 75.41 41.4 0.000 0.000 POINT 0.000 69
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 70 3124. 75.41 41.4 0.000 0.000 POINT 0.000 70
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 71 3124. 75.41 41.4 0.000 0.000 POINT 0.000 71
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 72 3124. 75.41 41.4 0.000 0.000 POINT 0.000 72
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 73 3124. 75.41 41.4 0.000 0.000 POINT 0.000 73
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 74 3124. 75.41 41.4 0.000 0.000 POINT 0.000 74
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 75 3124. 75.41 41.4 0.000 0.000 POINT 0.000 75
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 76 3124. 75.41 41.4 0.000 0.000 POINT 0.000 76
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 77 3124. 75.41 41.4 0.000 0.000 POINT 0.000 77
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 78 3124. 75.41 41.4 0.000 0.000 POINT 0.000 78
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 79 3124. 75.41 41.4 0.000 0.000 POINT 0.000 79
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 80 3124. 75.41 41.4 0.000 0.000 POINT 0.000 80
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 81 3124. 75.41 41.4 0.000 0.000 POINT 0.000 81
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 82 3124. 75.41 41.4 0.000 0.000 POINT 0.000 82
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 83 3124. 75.41 41.4 0.000 0.000 POINT 0.000 83
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 84 3124. 75.41 41.4 0.000 0.000 POINT 0.000 84
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 85 3124. 75.41 41.4 0.000 0.000 POINT 0.000 85
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 1 2.745 0.6587E-02 416.8 0.000 0.000 POINT 0.000 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0.000 0.000 0.000
Log_0 2001-12-20T13:17:32 spiros 2.3:
Log_0 2001-12-20T13:17:32 spiros 2.3: --------------------------------------------------------------------------------------------------------
Log_0 2001-12-20T13:17:32 spiros 2.3: Source Bin-no Bin-flux Flux-error Sigma Bin energy Bin-shape Width Error Pixel
Log_0 2001-12-20T13:17:32 spiros 2.3: --------------------------------------------------------------------------------------------------------
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 1 0.8911 2.821 0.3 25.000 26.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 2 0.7664 2.822 0.3 26.000 27.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 3 1.265 2.799 0.5 27.000 28.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 4 2.398 2.759 0.9 28.000 29.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 5 1.991 2.781 0.7 29.000 30.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 6 1.326 2.798 0.5 30.000 31.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 7 1.600 2.779 0.6 31.000 32.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 8 2.350 2.774 0.8 32.000 33.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 9 1.507 2.782 0.5 33.000 34.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 10 0.9155 2.821 0.3 34.000 35.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 11 2.424 2.761 0.9 35.000 36.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 12 0.6329 2.823 0.2 36.000 37.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 13 2.106 2.773 0.8 37.000 38.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 14 0.5986 2.821 0.2 38.000 39.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 15 0.8092 2.822 0.3 39.000 40.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 16 -0.2218 0.4479E-01 -5.0 40.000 142.333 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 17 -0.3129 0.6504E-01 -4.8 142.333 244.667 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 18 1.296 0.1285 10.1 244.667 347.000 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 19 6.403 0.2595 24.7 347.000 449.333 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 20 8.122 0.3108 26.1 449.333 551.667 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 21 13.17 0.3976 33.1 551.667 654.000 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 22 13.43 3.944 3.4 654.000 655.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 23 21.15 3.861 5.5 655.000 656.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 24 16.25 4.078 4.0 656.000 657.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 25 18.29 4.582 4.0 657.000 658.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 26 35.10 5.864 6.0 658.000 659.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 27 20.03 7.350 2.7 659.000 660.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 28 -72.69 10.45 -7.0 660.000 661.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 29 -253.3 23.06 -11.0 661.000 662.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 30 -133.7 11.57 -11.6 662.000 663.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 31 -51.11 7.669 -6.7 663.000 664.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 32 15.41 4.894 3.1 664.000 665.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 33 23.34 3.683 6.3 665.000 666.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 34 13.51 2.967 4.6 666.000 667.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 35 3.868 2.900 1.3 667.000 668.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 36 1.299 2.886 0.5 668.000 669.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 37 0.2161 0.6048E-01 3.6 669.000 769.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 38 0.3581 0.6473E-01 5.5 769.000 869.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 39 0.3907 0.8379E-01 4.7 869.000 969.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 40 0.2229 0.6715E-01 3.3 969.000 1069.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 41 0.9097E-01 0.6527E-01 1.4 1069.000 1169.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 42 0.3509 0.5762E-01 6.1 1169.000 1269.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 43 0.3206 0.6538E-01 4.9 1269.000 1369.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 44 0.8687 0.1759 4.9 1369.000 1469.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 45 0.1728 0.4634E-01 3.7 1469.000 1569.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 46 0.3059 0.5225E-01 5.9 1569.000 1669.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 47 0.6574E-01 0.5084E-01 1.3 1669.000 1769.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 48 0.1784 0.4177E-01 4.3 1769.000 1869.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 49 0.1896 0.3839E-01 4.9 1869.000 1969.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 50 0.1190 0.3648E-01 3.3 1969.000 2069.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 51 0.1158 0.1250E-01 9.3 2069.000 3069.000 HAT 1000.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 0 52 0.1904E-01 0.3353E-02 5.7 3069.000 4069.000 HAT 1000.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 1 0.6667E-03 0.8756E-04 7.6 25.000 26.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 2 0.7561E-03 0.9321E-04 8.1 26.000 27.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 3 0.3812E-03 0.5703E-04 6.7 27.000 28.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 4 0.5032E-03 0.7008E-04 7.2 28.000 29.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 5 0.6945E-03 0.8958E-04 7.8 29.000 30.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 6 0.4758E-03 0.6811E-04 7.0 30.000 31.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 7 0.5434E-03 0.7381E-04 7.4 31.000 32.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 8 0.3504E-03 0.5944E-04 5.9 32.000 33.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 9 0.6821E-03 0.8856E-04 7.7 33.000 34.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 10 0.8590E-03 0.9923E-04 8.7 34.000 35.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 11 0.2099E-03 0.4183E-04 5.0 35.000 36.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 12 0.4899E-03 0.6834E-04 7.2 36.000 37.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 13 0.6251E-03 0.8192E-04 7.6 37.000 38.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 14 0.5250E-03 0.7125E-04 7.4 38.000 39.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 15 0.9058E-03 0.1019E-03 8.9 39.000 40.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 16 0.1997E-02 0.1502E-04 133.0 40.000 142.333 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 17 0.2522E-02 0.1736E-04 145.3 142.333 244.667 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 18 0.1621E-02 0.1437E-04 112.8 244.667 347.000 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 19 0.1615E-02 0.1512E-04 106.8 347.000 449.333 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 20 0.2103E-02 0.1797E-04 117.0 449.333 551.667 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 21 0.2487E-02 0.2061E-04 120.7 551.667 654.000 HAT 102.333 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 22 0.2248E-02 0.2034E-03 11.1 654.000 655.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 23 0.1735E-02 0.1884E-03 9.2 655.000 656.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 24 0.3056E-02 0.2401E-03 12.7 656.000 657.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 25 0.3880E-02 0.2649E-03 14.6 657.000 658.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 26 0.1189E-01 0.4512E-03 26.3 658.000 659.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 27 0.7571E-01 0.1113E-02 68.0 659.000 660.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 28 0.2871 0.2161E-02 132.9 660.000 661.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 29 0.4955 0.2884E-02 171.8 661.000 662.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 30 0.3668 0.2442E-02 150.2 662.000 663.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 31 0.1063 0.1322E-02 80.4 663.000 664.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 32 0.1201E-01 0.4537E-03 26.5 664.000 665.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 33 0.2463E-03 0.6727E-04 3.7 665.000 666.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 34 0.3063E-04 0.3948E-04 0.8 666.000 667.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 35 0.6557E-04 0.3919E-04 1.7 667.000 668.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 36 0.8546E-04 0.4075E-04 2.1 668.000 669.000 HAT 1.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 37 0.1120E-03 0.4597E-05 24.4 669.000 769.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 38 0.9114E-04 0.4268E-05 21.4 769.000 869.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 39 0.1250E-03 0.5223E-05 23.9 869.000 969.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 40 0.9453E-04 0.4538E-05 20.8 969.000 1069.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 41 0.8473E-04 0.4395E-05 19.3 1069.000 1169.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 42 0.6258E-04 0.3942E-05 15.9 1169.000 1269.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 43 0.3299E-04 0.3074E-05 10.7 1269.000 1369.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 44 0.2449E-03 0.8797E-05 27.8 1369.000 1469.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 45 0.1365E-04 0.2081E-05 6.6 1469.000 1569.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 46 0.2560E-04 0.2902E-05 8.8 1569.000 1669.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 47 0.5044E-04 0.3799E-05 13.3 1669.000 1769.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 48 0.9552E-05 0.1991E-05 4.8 1769.000 1869.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 49 0.5771E-05 0.1499E-05 3.9 1869.000 1969.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 50 0.4143E-05 0.1304E-05 3.2 1969.000 2069.000 HAT 100.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 51 0.1254E-04 0.6658E-06 18.8 2069.000 3069.000 HAT 1000.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 52 0.1873E-06 0.7006E-07 2.7 3069.000 4069.000 HAT 1000.000 0.000 1 0 1
Log_0 2001-12-20T13:17:32 spiros 2.3:
Log_0 2001-12-20T13:17:32 spiros 2.3: 1 detector background sources and 1 sky sources returned.
Log_0 2001-12-20T13:17:32 spiros 2.3: CHI-square parameter is 45179.99 for 4316 DOF and difference of 439.83 standard deviations
Log_0 2001-12-20T13:17:32 spiros 2.3:
Log_0 2001-12-20T13:17:32 spiros 2.3: ============================================================================================
Log_0 2001-12-20T13:17:32 spiros 2.3: <spiros_main> will now output background and source count spectra and a new source catalogue
Log_0 2001-12-20T13:17:32 spiros 2.3: ============================================================================================
Log_0 2001-12-20T13:17:32 spiros 2.3: Creating and indexing source spectra output to source_spectra.fits
Log_1 2001-12-20T13:17:32 spiros 2.3: Created by subroutine "spibham_output_source_spectrum" --STAMP-- spi/source_spectra.fits[SPI.-SRC.-SPE,1,BINTABLE]
Log_0 2001-12-20T13:17:32 spiros 2.3: Source SOURCE-1 has been attached to source spectrum index.
Log_1 2001-12-20T13:17:32 spiros 2.3: Created by subroutine "spibham_output_source_spectra" --STAMP-- spi/source_spectra_index.fits[GROUPING,1,BINTABLE]
Log_0 2001-12-20T13:17:32 spiros 2.3:
Log_1 2001-12-20T13:17:32 spiros 2.3: Created by subroutine "spibham_output_source_catalogue" --STAMP-- source_res.fits[SPI.-SRCL-RES,1,BINTABLE]
Log_0 2001-12-20T13:17:32 spiros 2.3: Creating output to source catalogue /unsaved_data/spi_int/single_scws/obs/obs089/source_res.fits
Log_1 2001-12-20T13:17:32 spiros 2.3: Created by subroutine "spibham_output_source_catadata" --STAMP-- source_res.fits[SPI.-SRCL-RES,1,BINTABLE]
Log_0 2001-12-20T13:17:32 spiros 2.3:
Log_0 2001-12-20T13:17:32 spiros 2.3: Output of background count spectra not requested
Log_0 2001-12-20T13:17:32 spiros 2.3: Output of source detector spectra not requested
Log_0 2001-12-20T13:17:32 spiros 2.3: Any instrument response file on disk called spiros.rsp will be deleted.
Log_0 2001-12-20T13:17:32 spiros 2.3:
Log_0 2001-12-20T13:17:32 spiros 2.3: <spiros_main> updating output Observation Group with essential keywords and closing it.
Log_0 2001-12-20T13:17:32 spiros 2.3: <spiros_main> exiting after successful execution.
Log_1 2001-12-20T13:17:32 spiros 2.3: Task spiros terminating with status 0
Log_0 2001-12-20T13:17:33 blc_sa 1.6: Running /isdc/integration/spi_int/sw_rep/bin/spiskymax debug="0" display="0" title="spiskymax v20 137-Cs processing" rogroup="og_spi.fits[GROUPING]" rwgroup="" counts_input_file="" pointing_input_file="" ebounds_input_file="" deadtime-dol="" background_input_file="" irf_input_file="/isdc/integration/ic/spi/rsp/spi_irf_grp_0007.fits[GROUPING]" source-cat-dol="source_res_in.fits[1]" image-idx="spi/skymax_index.fits(SPI.-SKY.-IMA-IDX.tpl)" image-int="skymax_image.fits" source-res-dol="spi/spiskymax_sources.fits(SPI.-SRCL-RES.tpl)" skymap_system="C" image-fov="SURVEY" center-long="1" center-lat="2" image-pixel-long="0.5" image-pixel-lat="0.5" image-dim-long="40" image-dim-lat="41" chi_0="-10" chi_1="10" d_chi="0.5" psi_0="-10" psi_1="10" d_psi="0.5" energy_range_min="1" energy_range_max="52" max_iter="100" image_default="0.001" background_scaling_default="1" background_entropy_factor="1" background_method="2" memsys_iBayes="1" memsys_iEntropy="1" memsys_fAim="1" n_source_fluxes="1" source_chi_1="0" source_psi_1="0" source_ON_radius_1="2" source_OFF_radius_1="4" n_profiles="0" profile_chi_0="180.0 180.0" profile_chi_1="200.0 200.0" profile_d_chi=" 1.0 2.0" profile_psi_0=" +2.0 +2.0" profile_psi_1=" +2.0 +2.0" profile_d_psi=" 2.0 2.0" xn_profiles="6" xprofile_chi_0="-20.0 -20.0 -20.0 +1.0 +1.0 0.0" xprofile_chi_1="+20.0 +20.0 +20.0 +1.0 +1.0 6.0" xprofile_d_chi=" 1.0 2.0 5.0 4.0 2.0 2.0" xprofile_psi_0=" -0.0 0.0 -0.0 -20.0 -20.0 -20.0" xprofile_psi_1=" +0.0 +0.0 +0.0 +20.0 +20.0 +20.0" xprofile_d_psi=" 2.0 2.0 3.0 1.0 2.0 1.0" | tee /tmp/isdcroot.10876.22899.out
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Task spiskymax running in SINGLE mode
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Beginning parameters
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter debug = 0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter display = 0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter title = spiskymax v20 137-Cs processing
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter rogroup = og_spi.fits[GROUPING]
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter rwgroup =
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter counts_input_file =
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter pointing_input_file =
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter ebounds_input_file =
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter deadtime-dol =
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter background_input_file =
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter irf_input_file = /isdc/integration/ic/spi/rsp/spi_irf_grp_0007.fits[GROUPING]
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter source-cat-dol = source_res_in.fits[1]
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter image-idx = spi/skymax_index.fits(SPI.-SKY.-IMA-IDX.tpl)
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter image-int = skymax_image.fits
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter source-res-dol = spi/spiskymax_sources.fits(SPI.-SRCL-RES.tpl)
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter skymap_system = C
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter image-fov = SURVEY
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter center-long = 1
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter center-lat = 2
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter image-pixel-long = 0.5
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter image-pixel-lat = 0.5
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter image-dim-long = 40
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter image-dim-lat = 41
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter chi_0 = -10
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter chi_1 = 10
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter d_chi = 0.5
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter psi_0 = -10
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter psi_1 = 10
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter d_psi = 0.5
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter energy_range_min = 1
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter energy_range_max = 52
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter max_iter = 100
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter image_default = 0.001
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter background_scaling_default = 1
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter background_entropy_factor = 1
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter background_method = 2
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter memsys_iBayes = 1
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter memsys_iEntropy = 1
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter memsys_fAim = 1
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter n_source_fluxes = 1
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter source_chi_1 = 0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter source_psi_1 = 0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter source_ON_radius_1 = 2
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter source_OFF_radius_1 = 4
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter n_profiles = 0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter profile_chi_0 = 180.0 180.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter profile_chi_1 = 200.0 200.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter profile_d_chi = 1.0 2.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter profile_psi_0 = +2.0 +2.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter profile_psi_1 = +2.0 +2.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter profile_d_psi = 2.0 2.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter xn_profiles = 6
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter xprofile_chi_0 = -20.0 -20.0 -20.0 +1.0 +1.0 0.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter xprofile_chi_1 = +20.0 +20.0 +20.0 +1.0 +1.0 6.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter xprofile_d_chi = 1.0 2.0 5.0 4.0 2.0 2.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter xprofile_psi_0 = -0.0 0.0 -0.0 -20.0 -20.0 -20.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter xprofile_psi_1 = +0.0 +0.0 +0.0 +20.0 +20.0 +20.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Parameter xprofile_d_psi = 2.0 2.0 3.0 1.0 2.0 1.0
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Ending parameters
Log_1 2001-12-20T13:17:33 spiskymax 20.0: Running in normal mode, default parameter prompting
Log_1 2001-12-20T13:17:37 spiskymax 20.0: CommonPreparePARsStrings status=0
Log_1 2001-12-20T13:17:37 spiskymax 20.0: spiskymax_get_par ends
Log_1 2001-12-20T13:17:37 spiskymax 20.0: >> spiskymax_processing begins
Log_1 2001-12-20T13:17:37 spiskymax 20.0: read_SPI_OBS_DSP begins
Log_1 2001-12-20T13:17:37 spiskymax 20.0: read_SPI_OBS_DSP ends
Log_1 2001-12-20T13:17:37 spiskymax 20.0: DALobjectFindElement status=0
Log_1 2001-12-20T13:17:37 spiskymax 20.0: DAL3GENindexGetNumMembers status=0
Log_1 2001-12-20T13:17:37 spiskymax 20.0: DAL3GENindexGetNumMembers NumMembers=1
Log_1 2001-12-20T13:17:37 spiskymax 20.0: DAL3GENindexGetMember status=0
Log_1 2001-12-20T13:17:37 spiskymax 20.0: image_definition begins
Log_1 2001-12-20T13:17:37 spiskymax 20.0: image_definition ends
Log_1 2001-12-20T13:17:40 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #1 +++++++++++++++
Log_1 2001-12-20T13:17:40 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:17:40 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:17:40 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:17:40 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:17:41 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:17:41 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:17:41 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:17:42 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:17:42 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:17:42 spiskymax 20.0: Good = 10.4 = [ 10.0 , 10.9 ]
Log_1 2001-12-20T13:17:42 spiskymax 20.0: Evidence = -49.4 = [ -49.5 , -49.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:17:42 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:17:42 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:17:42 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-8.288e-06 +-1.295e-04 sigma= -0.06
Log_1 2001-12-20T13:17:42 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:17:42 spiskymax 20.0:
------------- Analysing source catalogue for energy range 25.00-26.00 keV
Log_1 2001-12-20T13:17:43 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:17:43 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:17:43 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-8.288e-06 +-1.295e-04 sigma= -0.06
Log_1 2001-12-20T13:17:43 spiskymax 20.0:
----------End analysing source catalogue for energy range 25.00-26.00 keV
Log_1 2001-12-20T13:17:43 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #1 +++++++++++++++
Log_1 2001-12-20T13:17:46 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #2 +++++++++++++++
Log_1 2001-12-20T13:17:46 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:17:46 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:17:46 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:17:46 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:17:47 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:17:47 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:17:47 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:17:48 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:17:48 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:17:48 spiskymax 20.0: Good = 10.7 = [ 10.3 , 11.1 ]
Log_1 2001-12-20T13:17:48 spiskymax 20.0: Evidence = -52.1 = [ -52.2 , -52.0 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:17:48 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:17:48 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:17:49 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=8.944e-05 +-1.526e-04 sigma= 0.59
Log_1 2001-12-20T13:17:49 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:17:49 spiskymax 20.0:
------------- Analysing source catalogue for energy range 26.00-27.00 keV
Log_1 2001-12-20T13:17:49 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:17:49 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:17:49 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=8.944e-05 +-1.526e-04 sigma= 0.59
Log_1 2001-12-20T13:17:49 spiskymax 20.0:
----------End analysing source catalogue for energy range 26.00-27.00 keV
Log_1 2001-12-20T13:17:49 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #2 +++++++++++++++
Log_1 2001-12-20T13:17:52 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #3 +++++++++++++++
Log_1 2001-12-20T13:17:52 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:17:52 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:17:53 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:17:53 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:17:53 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:17:53 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:17:54 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:17:54 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:17:54 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:17:55 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:17:55 spiskymax 20.0: Good = 11.4 = [ 11.0 , 11.7 ]
Log_1 2001-12-20T13:17:55 spiskymax 20.0: Evidence = -53.5 = [ -53.6 , -53.4 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:17:55 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:17:55 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:17:55 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.159e-04 +-1.627e-04 sigma= 0.71
Log_1 2001-12-20T13:17:55 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:17:55 spiskymax 20.0:
------------- Analysing source catalogue for energy range 27.00-28.00 keV
Log_1 2001-12-20T13:17:56 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:17:56 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:17:56 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.159e-04 +-1.627e-04 sigma= 0.71
Log_1 2001-12-20T13:17:56 spiskymax 20.0:
----------End analysing source catalogue for energy range 27.00-28.00 keV
Log_1 2001-12-20T13:17:56 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #3 +++++++++++++++
Log_1 2001-12-20T13:17:59 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #4 +++++++++++++++
Log_1 2001-12-20T13:17:59 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:17:59 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:17:59 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:17:59 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:00 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:00 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:00 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:01 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:01 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:01 spiskymax 20.0: Good = 13.1 = [ 12.5 , 13.8 ]
Log_1 2001-12-20T13:18:01 spiskymax 20.0: Evidence = -53.9 = [ -54.1 , -53.8 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:01 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:01 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:01 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.462e-04 +-1.922e-04 sigma= 0.76
Log_1 2001-12-20T13:18:01 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:01 spiskymax 20.0:
------------- Analysing source catalogue for energy range 28.00-29.00 keV
Log_1 2001-12-20T13:18:01 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:01 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:02 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.462e-04 +-1.922e-04 sigma= 0.76
Log_1 2001-12-20T13:18:02 spiskymax 20.0:
----------End analysing source catalogue for energy range 28.00-29.00 keV
Log_1 2001-12-20T13:18:02 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #4 +++++++++++++++
Log_1 2001-12-20T13:18:05 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #5 +++++++++++++++
Log_1 2001-12-20T13:18:05 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:05 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:05 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:05 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:05 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:06 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:06 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:06 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:07 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:18:07 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:07 spiskymax 20.0: Good = 10.3 = [ 9.8 , 10.7 ]
Log_1 2001-12-20T13:18:07 spiskymax 20.0: Evidence = -47.0 = [ -47.1 , -46.9 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:07 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:07 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:07 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.220e-04 +-1.616e-04 sigma= 0.75
Log_1 2001-12-20T13:18:07 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:07 spiskymax 20.0:
------------- Analysing source catalogue for energy range 29.00-30.00 keV
Log_1 2001-12-20T13:18:07 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:07 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:08 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.220e-04 +-1.616e-04 sigma= 0.75
Log_1 2001-12-20T13:18:08 spiskymax 20.0:
----------End analysing source catalogue for energy range 29.00-30.00 keV
Log_1 2001-12-20T13:18:08 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #5 +++++++++++++++
Log_1 2001-12-20T13:18:11 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #6 +++++++++++++++
Log_1 2001-12-20T13:18:11 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:11 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:11 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:11 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:12 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:12 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:12 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:12 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:13 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:18:13 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:13 spiskymax 20.0: Good = 10.4 = [ 10.1 , 10.7 ]
Log_1 2001-12-20T13:18:13 spiskymax 20.0: Evidence = -51.3 = [ -51.3 , -51.2 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:13 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:13 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:14 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.281e-04 +-1.897e-04 sigma= 0.68
Log_1 2001-12-20T13:18:14 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:14 spiskymax 20.0:
------------- Analysing source catalogue for energy range 30.00-31.00 keV
Log_1 2001-12-20T13:18:14 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:14 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:14 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.281e-04 +-1.897e-04 sigma= 0.68
Log_1 2001-12-20T13:18:14 spiskymax 20.0:
----------End analysing source catalogue for energy range 30.00-31.00 keV
Log_1 2001-12-20T13:18:14 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #6 +++++++++++++++
Log_1 2001-12-20T13:18:17 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #7 +++++++++++++++
Log_1 2001-12-20T13:18:17 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:17 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:17 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:17 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:18 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:18 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:18 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:19 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:19 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:18:20 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:18:20 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:18:21 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:18:21 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:22 spiskymax 20.0: Good = 11.9 = [ 11.7 , 12.2 ]
Log_1 2001-12-20T13:18:22 spiskymax 20.0: Evidence = -51.9 = [ -52.0 , -51.9 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:22 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:22 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:22 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.041e-04 +-1.579e-04 sigma= 0.66
Log_1 2001-12-20T13:18:22 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:22 spiskymax 20.0:
------------- Analysing source catalogue for energy range 31.00-32.00 keV
Log_1 2001-12-20T13:18:22 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:22 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:22 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.041e-04 +-1.579e-04 sigma= 0.66
Log_1 2001-12-20T13:18:22 spiskymax 20.0:
----------End analysing source catalogue for energy range 31.00-32.00 keV
Log_1 2001-12-20T13:18:22 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #7 +++++++++++++++
Log_1 2001-12-20T13:18:27 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #8 +++++++++++++++
Log_1 2001-12-20T13:18:27 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:27 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:27 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:27 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:27 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:28 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:28 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:28 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:29 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:18:29 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:29 spiskymax 20.0: Good = 9.9 = [ 9.5 , 10.2 ]
Log_1 2001-12-20T13:18:29 spiskymax 20.0: Evidence = -48.3 = [ -48.4 , -48.2 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:29 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:29 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:29 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=4.496e-05 +-1.447e-04 sigma= 0.31
Log_1 2001-12-20T13:18:29 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:29 spiskymax 20.0:
------------- Analysing source catalogue for energy range 32.00-33.00 keV
Log_1 2001-12-20T13:18:29 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:29 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:30 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=4.496e-05 +-1.447e-04 sigma= 0.31
Log_1 2001-12-20T13:18:30 spiskymax 20.0:
----------End analysing source catalogue for energy range 32.00-33.00 keV
Log_1 2001-12-20T13:18:30 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #8 +++++++++++++++
Log_1 2001-12-20T13:18:33 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #9 +++++++++++++++
Log_1 2001-12-20T13:18:33 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:33 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:33 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:33 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:33 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:34 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:34 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:34 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:35 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:35 spiskymax 20.0: Good = 12.0 = [ 11.9 , 12.2 ]
Log_1 2001-12-20T13:18:35 spiskymax 20.0: Evidence = -50.1 = [ -50.1 , -50.0 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:35 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:35 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:35 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=6.654e-05 +-1.499e-04 sigma= 0.44
Log_1 2001-12-20T13:18:35 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:35 spiskymax 20.0:
------------- Analysing source catalogue for energy range 33.00-34.00 keV
Log_1 2001-12-20T13:18:35 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:35 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:35 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=6.654e-05 +-1.499e-04 sigma= 0.44
Log_1 2001-12-20T13:18:35 spiskymax 20.0:
----------End analysing source catalogue for energy range 33.00-34.00 keV
Log_1 2001-12-20T13:18:35 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #9 +++++++++++++++
Log_1 2001-12-20T13:18:38 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #10 +++++++++++++++
Log_1 2001-12-20T13:18:38 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:38 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:39 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:39 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:39 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:39 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:40 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:40 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:40 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:18:41 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:18:41 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:41 spiskymax 20.0: Good = 10.9 = [ 10.6 , 11.2 ]
Log_1 2001-12-20T13:18:41 spiskymax 20.0: Evidence = -52.8 = [ -52.8 , -52.7 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:41 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:41 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:42 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-2.028e-05 +-1.944e-04 sigma= -0.10
Log_1 2001-12-20T13:18:42 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:42 spiskymax 20.0:
------------- Analysing source catalogue for energy range 34.00-35.00 keV
Log_1 2001-12-20T13:18:42 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:42 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:42 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-2.028e-05 +-1.944e-04 sigma= -0.10
Log_1 2001-12-20T13:18:42 spiskymax 20.0:
----------End analysing source catalogue for energy range 34.00-35.00 keV
Log_1 2001-12-20T13:18:42 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #10 +++++++++++++++
Log_1 2001-12-20T13:18:45 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #11 +++++++++++++++
Log_1 2001-12-20T13:18:45 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:45 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:45 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:46 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:46 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:46 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:46 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:47 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:47 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:18:47 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:48 spiskymax 20.0: Good = 11.4 = [ 10.9 , 11.8 ]
Log_1 2001-12-20T13:18:48 spiskymax 20.0: Evidence = -49.4 = [ -49.5 , -49.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:48 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:48 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:48 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=6.966e-05 +-1.475e-04 sigma= 0.47
Log_1 2001-12-20T13:18:48 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:48 spiskymax 20.0:
------------- Analysing source catalogue for energy range 35.00-36.00 keV
Log_1 2001-12-20T13:18:48 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:48 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:48 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=6.966e-05 +-1.475e-04 sigma= 0.47
Log_1 2001-12-20T13:18:48 spiskymax 20.0:
----------End analysing source catalogue for energy range 35.00-36.00 keV
Log_1 2001-12-20T13:18:48 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #11 +++++++++++++++
Log_1 2001-12-20T13:18:51 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #12 +++++++++++++++
Log_1 2001-12-20T13:18:51 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:51 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:52 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:52 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:52 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:52 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:53 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:18:53 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:18:53 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:18:54 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:18:54 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:18:54 spiskymax 20.0: Good = 12.6 = [ 12.4 , 12.8 ]
Log_1 2001-12-20T13:18:54 spiskymax 20.0: Evidence = -57.3 = [ -57.3 , -57.2 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:18:54 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:54 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:18:55 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=9.246e-05 +-2.062e-04 sigma= 0.45
Log_1 2001-12-20T13:18:55 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:18:55 spiskymax 20.0:
------------- Analysing source catalogue for energy range 36.00-37.00 keV
Log_1 2001-12-20T13:18:55 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:18:55 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:18:55 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=9.246e-05 +-2.062e-04 sigma= 0.45
Log_1 2001-12-20T13:18:55 spiskymax 20.0:
----------End analysing source catalogue for energy range 36.00-37.00 keV
Log_1 2001-12-20T13:18:55 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #12 +++++++++++++++
Log_1 2001-12-20T13:18:58 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #13 +++++++++++++++
Log_1 2001-12-20T13:18:58 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:18:58 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:18:58 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:18:59 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:18:59 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:18:59 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:18:59 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:19:00 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:19:00 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:19:00 spiskymax 20.0: Good = 12.9 = [ 12.4 , 13.5 ]
Log_1 2001-12-20T13:19:00 spiskymax 20.0: Evidence = -55.7 = [ -55.8 , -55.6 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:19:00 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:19:00 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:19:00 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=8.136e-05 +-2.044e-04 sigma= 0.40
Log_1 2001-12-20T13:19:00 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:19:00 spiskymax 20.0:
------------- Analysing source catalogue for energy range 37.00-38.00 keV
Log_1 2001-12-20T13:19:01 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:19:01 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:19:01 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=8.136e-05 +-2.044e-04 sigma= 0.40
Log_1 2001-12-20T13:19:01 spiskymax 20.0:
----------End analysing source catalogue for energy range 37.00-38.00 keV
Log_1 2001-12-20T13:19:01 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #13 +++++++++++++++
Log_1 2001-12-20T13:19:04 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #14 +++++++++++++++
Log_1 2001-12-20T13:19:04 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:19:04 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:19:04 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:19:04 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:19:05 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:19:05 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:19:05 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:19:06 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:19:06 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:19:06 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:19:07 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:19:07 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:19:07 spiskymax 20.0: Good = 12.3 = [ 11.8 , 12.7 ]
Log_1 2001-12-20T13:19:07 spiskymax 20.0: Evidence = -54.9 = [ -55.0 , -54.8 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:19:08 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:19:08 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:19:08 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=6.270e-05 +-1.817e-04 sigma= 0.35
Log_1 2001-12-20T13:19:08 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:19:08 spiskymax 20.0:
------------- Analysing source catalogue for energy range 38.00-39.00 keV
Log_1 2001-12-20T13:19:08 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:19:08 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:19:08 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=6.270e-05 +-1.817e-04 sigma= 0.35
Log_1 2001-12-20T13:19:08 spiskymax 20.0:
----------End analysing source catalogue for energy range 38.00-39.00 keV
Log_1 2001-12-20T13:19:08 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #14 +++++++++++++++
Log_1 2001-12-20T13:19:11 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #15 +++++++++++++++
Log_1 2001-12-20T13:19:11 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:19:12 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:19:12 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:19:12 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:19:12 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:19:13 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:19:13 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:19:13 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:19:14 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:19:14 spiskymax 20.0: Good = 12.7 = [ 12.2 , 13.1 ]
Log_1 2001-12-20T13:19:14 spiskymax 20.0: Evidence = -54.1 = [ -54.2 , -54.1 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:19:14 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:19:14 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:19:14 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.526e-04 +-1.925e-04 sigma= 0.79
Log_1 2001-12-20T13:19:14 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:19:14 spiskymax 20.0:
------------- Analysing source catalogue for energy range 39.00-40.00 keV
Log_1 2001-12-20T13:19:14 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:19:14 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:19:14 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.526e-04 +-1.925e-04 sigma= 0.79
Log_1 2001-12-20T13:19:14 spiskymax 20.0:
----------End analysing source catalogue for energy range 39.00-40.00 keV
Log_1 2001-12-20T13:19:14 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #15 +++++++++++++++
Log_1 2001-12-20T13:19:18 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #16 +++++++++++++++
Log_1 2001-12-20T13:19:18 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:19:18 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:19:18 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:19:18 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:19:18 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:19:18 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:19:19 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:19:19 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:19:19 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:19:19 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:19:19 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:19:20 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:19:20 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:19:20 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:19:20 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:19:21 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:19:21 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:19:21 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:19:21 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:19:22 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:19:22 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:19:22 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:19:22 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:19:23 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:19:23 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:19:23 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:19:23 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:19:24 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:19:24 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:19:24 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:19:25 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:19:25 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:19:25 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:19:25 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:19:26 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:19:26 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:19:26 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:19:27 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:19:27 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:19:27 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:19:28 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:19:28 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:19:28 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:19:28 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:19:29 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:19:29 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:19:29 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:19:30 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:19:30 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:19:31 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:19:31 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:19:31 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:19:32 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:19:32 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:19:33 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:19:33 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:19:34 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:19:34 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:19:35 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:19:35 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:19:36 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:19:36 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:19:37 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:19:38 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:19:38 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:19:39 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:19:40 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:19:40 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:19:41 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:19:42 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:19:43 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:19:44 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:19:44 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:19:45 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:19:46 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:19:47 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:19:48 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:19:49 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:19:50 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:19:51 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:19:52 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:19:53 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:19:54 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:19:55 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:19:56 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:19:57 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:19:59 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:20:00 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:20:01 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:20:02 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:20:03 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:20:04 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:20:06 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:20:06 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:20:08 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:20:09 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:20:11 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:20:12 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:20:13 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:20:15 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:20:15 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:20:16 spiskymax 20.0: Good = 21.9 = [ 20.9 , 23.0 ]
Log_1 2001-12-20T13:20:16 spiskymax 20.0: Evidence = -501.4 = [ -501.7 , -501.1 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:20:17 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:20:17 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:20:18 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=3.203e-02 +-3.570e-02 sigma= 0.90
Log_1 2001-12-20T13:20:18 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:20:18 spiskymax 20.0:
------------- Analysing source catalogue for energy range 40.00-142.33 keV
Log_1 2001-12-20T13:20:18 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:20:18 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:20:19 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=3.203e-02 +-3.570e-02 sigma= 0.90
Log_1 2001-12-20T13:20:19 spiskymax 20.0:
----------End analysing source catalogue for energy range 40.00-142.33 keV
Log_1 2001-12-20T13:20:19 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #16 +++++++++++++++
Log_1 2001-12-20T13:20:21 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #17 +++++++++++++++
Log_1 2001-12-20T13:20:21 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:20:21 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:20:21 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:20:21 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:20:22 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:20:22 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:20:22 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:20:22 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:20:22 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:20:23 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:20:23 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:20:23 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:20:23 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:20:23 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:20:23 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:20:24 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:20:24 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:20:24 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:20:24 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:20:24 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:20:25 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:20:25 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:20:25 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:20:25 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:20:25 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:20:26 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:20:26 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:20:26 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:20:26 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:20:26 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:20:27 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:20:27 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:20:27 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:20:27 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:20:27 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:20:28 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:20:28 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:20:28 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:20:28 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:20:28 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:20:29 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:20:29 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:20:29 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:20:29 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:20:30 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:20:30 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:20:30 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:20:31 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:20:31 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:20:31 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:20:32 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:20:32 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:20:32 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:20:33 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:20:33 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:20:33 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:20:34 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:20:34 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:20:35 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:20:35 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:20:36 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:20:36 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:20:37 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:20:37 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:20:38 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:20:38 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:20:39 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:20:40 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:20:40 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:20:41 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:20:41 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:20:42 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:20:43 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:20:43 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:20:44 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:20:45 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:20:45 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:20:46 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:20:47 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:20:47 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:20:48 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:20:49 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:20:50 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:20:51 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:20:51 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:20:52 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:20:53 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:20:54 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:20:55 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:20:56 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:20:57 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:20:58 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:20:59 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:21:00 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:21:01 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:21:02 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:21:03 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:21:04 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:21:05 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:21:07 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:21:08 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:21:09 spiskymax 20.0: Good = 30.4 = [ 29.0 , 31.8 ]
Log_1 2001-12-20T13:21:09 spiskymax 20.0: Evidence = -1162.1 = [ -1162.5 , -1161.8 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:21:11 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:21:11 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:21:12 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=9.009e-02 +-6.977e-03 sigma= 12.91
Log_1 2001-12-20T13:21:12 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:21:12 spiskymax 20.0:
------------- Analysing source catalogue for energy range 142.33-244.67 keV
Log_1 2001-12-20T13:21:12 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:21:12 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:21:13 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=9.009e-02 +-6.977e-03 sigma= 12.91
Log_1 2001-12-20T13:21:13 spiskymax 20.0:
----------End analysing source catalogue for energy range 142.33-244.67 keV
Log_1 2001-12-20T13:21:13 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #17 +++++++++++++++
Log_1 2001-12-20T13:21:13 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #18 +++++++++++++++
Log_1 2001-12-20T13:21:13 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:21:13 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:21:14 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:21:14 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:21:14 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:21:14 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:21:14 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:21:15 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:21:15 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:21:15 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:21:15 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:21:15 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:21:15 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:21:16 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:21:16 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:21:16 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:21:16 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:21:17 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:21:17 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:21:17 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:21:17 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:21:17 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:21:18 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:21:18 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:21:18 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:21:18 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:21:18 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:21:19 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:21:19 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:21:19 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:21:19 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:21:19 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:21:20 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:21:20 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:21:20 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:21:20 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:21:21 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:21:21 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:21:21 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:21:21 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:21:22 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:21:22 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:21:22 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:21:23 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:21:23 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:21:23 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:21:24 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:21:24 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:21:24 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:21:25 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:21:25 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:21:26 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:21:26 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:21:26 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:21:27 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:21:27 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:21:28 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:21:28 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:21:28 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:21:29 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:21:29 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:21:30 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:21:30 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:21:30 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:21:31 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:21:32 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:21:32 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:21:33 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:21:33 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:21:34 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:21:34 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:21:35 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:21:36 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:21:36 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:21:37 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:21:38 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:21:39 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:21:40 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:21:40 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:21:41 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:21:42 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:21:43 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:21:44 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:21:45 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:21:47 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:21:51 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:21:56 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:22:02 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:22:10 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:22:17 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:22:25 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:22:33 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:22:39 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:22:46 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:22:52 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:22:59 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:23:05 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:23:12 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:23:19 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:23:26 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:23:35 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:23:40 spiskymax 20.0: Good = 30.9 = [ 29.7 , 32.0 ]
Log_1 2001-12-20T13:23:40 spiskymax 20.0: Evidence = -1501.6 = [ -1501.9 , -1501.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:23:44 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:23:44 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:23:48 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=9.322e-02 +-3.924e-03 sigma= 23.76
Log_1 2001-12-20T13:23:48 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:23:48 spiskymax 20.0:
------------- Analysing source catalogue for energy range 244.67-347.00 keV
Log_1 2001-12-20T13:23:48 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:23:48 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:23:53 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=9.322e-02 +-3.924e-03 sigma= 23.76
Log_1 2001-12-20T13:23:53 spiskymax 20.0:
----------End analysing source catalogue for energy range 244.67-347.00 keV
Log_1 2001-12-20T13:23:53 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #18 +++++++++++++++
Log_1 2001-12-20T13:23:53 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #19 +++++++++++++++
Log_1 2001-12-20T13:23:53 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:23:53 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:23:53 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:23:53 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:23:53 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:23:54 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:23:54 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:23:54 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:23:54 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:23:54 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:23:54 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:23:55 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:23:55 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:23:55 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:23:55 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:23:55 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:23:56 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:23:56 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:23:56 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:23:56 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:23:56 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:23:57 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:23:57 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:23:57 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:23:57 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:23:57 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:23:58 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:23:58 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:23:58 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:23:58 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:23:58 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:23:59 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:23:59 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:23:59 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:23:59 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:24:00 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:24:00 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:24:00 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:24:00 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:24:01 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:24:01 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:24:01 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:24:02 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:24:02 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:24:02 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:24:02 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:24:03 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:24:03 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:24:03 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:24:04 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:24:04 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:24:05 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:24:05 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:24:05 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:24:06 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:24:06 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:24:07 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:24:07 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:24:07 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:24:08 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:24:08 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:24:09 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:24:09 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:24:10 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:24:10 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:24:11 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:24:11 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:24:12 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:24:13 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:24:13 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:24:14 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:24:15 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:24:15 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:24:16 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:24:17 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:24:18 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:24:19 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:24:19 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:24:20 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:24:21 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:24:22 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:24:23 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:24:25 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:24:28 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:24:34 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:24:39 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:24:46 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:24:51 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:24:57 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:25:03 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:25:09 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:25:15 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:25:22 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:25:28 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:25:33 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:25:39 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:25:45 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:25:51 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:25:58 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:26:08 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:26:20 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:26:24 spiskymax 20.0: Good = 30.4 = [ 29.0 , 31.7 ]
Log_1 2001-12-20T13:26:24 spiskymax 20.0: Evidence = -1587.3 = [ -1587.7 , -1587.0 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:26:28 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:26:28 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:26:33 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.016e-01 +-3.836e-03 sigma= 26.49
Log_1 2001-12-20T13:26:33 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:26:33 spiskymax 20.0:
------------- Analysing source catalogue for energy range 347.00-449.33 keV
Log_1 2001-12-20T13:26:33 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:26:33 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:26:38 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.016e-01 +-3.836e-03 sigma= 26.49
Log_1 2001-12-20T13:26:38 spiskymax 20.0:
----------End analysing source catalogue for energy range 347.00-449.33 keV
Log_1 2001-12-20T13:26:38 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #19 +++++++++++++++
Log_1 2001-12-20T13:26:39 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #20 +++++++++++++++
Log_1 2001-12-20T13:26:39 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:26:39 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:26:39 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:26:39 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:26:39 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:26:39 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:26:40 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:26:40 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:26:40 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:26:40 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:26:40 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:26:41 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:26:41 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:26:41 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:26:41 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:26:41 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:26:42 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:26:42 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:26:42 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:26:42 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:26:43 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:26:43 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:26:43 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:26:43 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:26:43 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:26:44 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:26:44 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:26:44 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:26:44 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:26:45 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:26:45 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:26:45 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:26:45 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:26:45 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:26:46 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:26:46 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:26:46 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:26:46 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:26:47 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:26:47 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:26:47 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:26:47 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:26:48 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:26:48 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:26:48 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:26:49 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:26:49 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:26:49 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:26:49 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:26:50 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:26:50 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:26:50 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:26:51 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:26:51 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:26:51 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:26:52 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:26:52 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:26:52 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:26:53 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:26:53 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:26:54 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:26:54 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:26:54 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:26:55 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:26:55 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:26:56 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:26:56 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:26:57 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:26:57 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:26:58 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:26:58 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:26:59 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:26:59 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:27:00 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:27:00 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:27:01 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:27:02 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:27:02 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:27:03 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:27:03 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:27:04 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:27:05 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:27:05 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:27:06 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:27:07 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:27:08 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:27:08 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:27:09 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:27:10 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:27:11 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:27:12 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:27:14 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:27:18 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:27:23 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:27:29 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:27:35 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:27:43 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:27:51 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:27:58 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:28:05 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:28:13 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:28:17 spiskymax 20.0: Good = 28.2 = [ 27.2 , 29.2 ]
Log_1 2001-12-20T13:28:17 spiskymax 20.0: Evidence = -1475.4 = [ -1475.6 , -1475.1 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:28:21 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:28:21 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:28:25 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.706e-01 +-4.976e-03 sigma= 34.28
Log_1 2001-12-20T13:28:25 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:28:25 spiskymax 20.0:
------------- Analysing source catalogue for energy range 449.33-551.67 keV
Log_1 2001-12-20T13:28:25 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:28:25 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:28:29 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.706e-01 +-4.976e-03 sigma= 34.28
Log_1 2001-12-20T13:28:29 spiskymax 20.0:
----------End analysing source catalogue for energy range 449.33-551.67 keV
Log_1 2001-12-20T13:28:29 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #20 +++++++++++++++
Log_1 2001-12-20T13:28:29 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #21 +++++++++++++++
Log_1 2001-12-20T13:28:29 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:28:29 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:28:29 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:28:29 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:28:30 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:28:30 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:28:30 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:28:30 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:28:30 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:28:31 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:28:31 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:28:31 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:28:31 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:28:31 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:28:31 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:28:32 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:28:32 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:28:32 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:28:32 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:28:32 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:28:32 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:28:33 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:28:33 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:28:33 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:28:33 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:28:33 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:28:33 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:28:34 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:28:34 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:28:34 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:28:34 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:28:34 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:28:34 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:28:35 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:28:35 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:28:35 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:28:35 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:28:36 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:28:36 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:28:36 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:28:36 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:28:37 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:28:37 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:28:37 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:28:37 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:28:38 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:28:38 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:28:38 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:28:38 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:28:39 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:28:39 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:28:39 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:28:40 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:28:40 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:28:40 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:28:41 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:28:41 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:28:41 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:28:42 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:28:42 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:28:42 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:28:43 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:28:43 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:28:44 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:28:44 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:28:44 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:28:45 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:28:45 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:28:46 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:28:46 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:28:47 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:28:47 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:28:48 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:28:48 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:28:49 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:28:49 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:28:50 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:28:51 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:28:51 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:28:52 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:28:52 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:28:53 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:28:54 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:28:54 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:28:55 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:28:56 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:28:56 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:28:57 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:28:58 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:28:58 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:28:59 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:29:00 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:29:01 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:29:02 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:29:02 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:29:03 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:29:05 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:29:06 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:29:09 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:29:12 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:29:17 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:29:20 spiskymax 20.0: Good = 27.1 = [ 26.2 , 28.0 ]
Log_1 2001-12-20T13:29:20 spiskymax 20.0: Evidence = -1677.8 = [ -1678.0 , -1677.6 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:29:23 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:23 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:29:26 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.862e-01 +-6.318e-03 sigma= 29.47
Log_1 2001-12-20T13:29:26 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:26 spiskymax 20.0:
------------- Analysing source catalogue for energy range 551.67-654.00 keV
Log_1 2001-12-20T13:29:26 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:29:26 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:29:31 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.862e-01 +-6.318e-03 sigma= 29.47
Log_1 2001-12-20T13:29:31 spiskymax 20.0:
----------End analysing source catalogue for energy range 551.67-654.00 keV
Log_1 2001-12-20T13:29:31 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #21 +++++++++++++++
Log_1 2001-12-20T13:29:31 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #22 +++++++++++++++
Log_1 2001-12-20T13:29:31 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:29:31 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:29:31 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:29:31 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:29:31 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:29:32 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:29:32 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:29:32 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:29:33 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:29:33 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:29:33 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:29:34 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:29:34 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:29:34 spiskymax 20.0: Good = 23.0 = [ 22.5 , 23.5 ]
Log_1 2001-12-20T13:29:34 spiskymax 20.0: Evidence = -170.1 = [ -170.2 , -170.0 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:29:34 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:34 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:29:35 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.388e-03 +-5.367e-04 sigma= 2.59
Log_1 2001-12-20T13:29:35 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:35 spiskymax 20.0:
------------- Analysing source catalogue for energy range 654.00-655.00 keV
Log_1 2001-12-20T13:29:35 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:29:35 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:29:35 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.388e-03 +-5.367e-04 sigma= 2.59
Log_1 2001-12-20T13:29:35 spiskymax 20.0:
----------End analysing source catalogue for energy range 654.00-655.00 keV
Log_1 2001-12-20T13:29:35 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #22 +++++++++++++++
Log_1 2001-12-20T13:29:35 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #23 +++++++++++++++
Log_1 2001-12-20T13:29:35 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:29:35 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:29:35 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:29:36 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:29:36 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:29:36 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:29:36 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:29:37 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:29:37 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:29:37 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:29:38 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:29:38 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:29:39 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:29:39 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:29:39 spiskymax 20.0: Good = 21.9 = [ 20.9 , 22.9 ]
Log_1 2001-12-20T13:29:39 spiskymax 20.0: Evidence = -179.0 = [ -179.2 , -178.8 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:29:39 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:39 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:29:40 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.505e-03 +-6.019e-04 sigma= 2.50
Log_1 2001-12-20T13:29:40 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:40 spiskymax 20.0:
------------- Analysing source catalogue for energy range 655.00-656.00 keV
Log_1 2001-12-20T13:29:40 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:29:40 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:29:40 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.505e-03 +-6.019e-04 sigma= 2.50
Log_1 2001-12-20T13:29:40 spiskymax 20.0:
----------End analysing source catalogue for energy range 655.00-656.00 keV
Log_1 2001-12-20T13:29:40 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #23 +++++++++++++++
Log_1 2001-12-20T13:29:40 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #24 +++++++++++++++
Log_1 2001-12-20T13:29:40 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:29:40 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:29:40 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:29:41 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:29:41 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:29:41 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:29:42 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:29:42 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:29:42 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:29:43 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:29:43 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:29:43 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:29:44 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:29:44 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:29:45 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:29:45 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:29:46 spiskymax 20.0: Good = 20.9 = [ 20.0 , 21.8 ]
Log_1 2001-12-20T13:29:46 spiskymax 20.0: Evidence = -189.3 = [ -189.4 , -189.1 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:29:46 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:46 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:29:46 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.105e-03 +-5.596e-04 sigma= 3.76
Log_1 2001-12-20T13:29:46 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:46 spiskymax 20.0:
------------- Analysing source catalogue for energy range 656.00-657.00 keV
Log_1 2001-12-20T13:29:46 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:29:46 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:29:46 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.105e-03 +-5.596e-04 sigma= 3.76
Log_1 2001-12-20T13:29:46 spiskymax 20.0:
----------End analysing source catalogue for energy range 656.00-657.00 keV
Log_1 2001-12-20T13:29:46 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #24 +++++++++++++++
Log_1 2001-12-20T13:29:47 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #25 +++++++++++++++
Log_1 2001-12-20T13:29:47 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:29:47 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:29:47 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:29:47 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:29:47 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:29:48 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:29:48 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:29:48 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:29:48 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:29:49 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:29:49 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:29:49 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:29:50 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:29:50 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:29:50 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:29:51 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:29:51 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:29:51 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:29:52 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:29:52 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:29:53 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:29:53 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:29:54 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:29:54 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:29:55 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:29:56 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:29:56 spiskymax 20.0: Good = 19.5 = [ 18.6 , 20.4 ]
Log_1 2001-12-20T13:29:56 spiskymax 20.0: Evidence = -257.4 = [ -257.6 , -257.2 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:29:56 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:56 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:29:56 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=4.328e-03 +-7.699e-04 sigma= 5.62
Log_1 2001-12-20T13:29:56 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:29:56 spiskymax 20.0:
------------- Analysing source catalogue for energy range 657.00-658.00 keV
Log_1 2001-12-20T13:29:56 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:29:56 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:29:57 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=4.328e-03 +-7.699e-04 sigma= 5.62
Log_1 2001-12-20T13:29:57 spiskymax 20.0:
----------End analysing source catalogue for energy range 657.00-658.00 keV
Log_1 2001-12-20T13:29:57 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #25 +++++++++++++++
Log_1 2001-12-20T13:29:57 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #26 +++++++++++++++
Log_1 2001-12-20T13:29:57 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:29:57 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:29:57 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:29:57 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:29:58 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:29:58 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:29:58 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:29:58 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:29:59 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:29:59 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:29:59 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:29:59 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:29:59 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:30:00 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:30:00 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:30:00 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:30:00 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:30:01 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:30:01 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:30:02 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:30:02 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:30:02 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:30:03 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:30:03 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:30:03 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:30:04 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:30:04 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:30:05 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:30:06 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:30:06 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:30:07 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:30:07 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:30:07 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:30:08 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:30:08 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:30:09 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:30:09 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:30:09 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:30:10 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:30:10 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:30:11 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:30:12 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:30:14 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:30:16 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:30:20 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:30:24 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:30:30 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:30:37 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:30:46 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:30:54 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:31:01 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:31:07 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:31:13 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:31:19 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:31:23 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:31:27 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:31:30 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:31:32 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:31:34 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:31:37 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:31:39 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:31:42 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:31:43 spiskymax 20.0: Good = 13.4 = [ 12.8 , 14.0 ]
Log_1 2001-12-20T13:31:43 spiskymax 20.0: Evidence = -560.4 = [ -560.5 , -560.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:31:44 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:31:44 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:31:45 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.726e-02 +-8.179e-04 sigma= 21.11
Log_1 2001-12-20T13:31:45 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:31:45 spiskymax 20.0:
------------- Analysing source catalogue for energy range 658.00-659.00 keV
Log_1 2001-12-20T13:31:45 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:31:45 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:31:46 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.726e-02 +-8.179e-04 sigma= 21.11
Log_1 2001-12-20T13:31:46 spiskymax 20.0:
----------End analysing source catalogue for energy range 658.00-659.00 keV
Log_1 2001-12-20T13:31:46 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #26 +++++++++++++++
Log_1 2001-12-20T13:31:46 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #27 +++++++++++++++
Log_1 2001-12-20T13:31:46 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:31:46 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:31:47 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:31:47 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:31:47 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:31:47 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:31:47 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:31:48 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:31:48 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:31:48 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:31:48 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:31:48 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:31:48 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:31:49 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:31:49 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:31:49 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:31:49 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:31:49 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:31:50 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:31:50 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:31:50 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:31:50 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:31:51 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:31:51 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:31:51 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:31:51 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:31:52 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:31:52 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:31:52 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:31:53 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:31:53 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:31:53 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:31:53 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:31:54 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:31:54 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:31:54 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:31:54 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:31:55 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:31:55 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:31:55 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:31:56 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:31:56 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:31:56 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:31:56 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:31:57 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:31:57 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:31:57 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:31:58 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:31:58 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:31:59 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:31:59 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:31:59 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:32:00 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:32:00 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:32:01 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:32:01 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:32:01 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:32:02 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:32:03 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:32:04 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:32:06 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:32:08 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:32:12 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:32:16 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:32:21 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:32:27 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:32:33 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:32:40 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:32:47 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:32:54 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:33:01 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:33:06 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:33:11 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:33:14 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:33:18 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:33:21 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:33:23 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:33:25 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:33:27 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:33:28 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:33:30 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:33:32 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:33:33 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:33:35 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:33:36 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:33:38 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:33:40 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:33:41 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:33:42 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:33:43 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:33:44 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:33:45 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:33:45 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:33:46 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:33:47 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:33:49 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:33:52 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:33:55 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:34:00 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:34:02 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:34:04 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:34:05 spiskymax 20.0: Good = 6.3 = [ 6.0 , 6.6 ]
Log_1 2001-12-20T13:34:05 spiskymax 20.0: Evidence = -883.4 = [ -883.5 , -883.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:34:05 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:34:05 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:34:05 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=8.542e-02 +-1.582e-03 sigma= 54.01
Log_1 2001-12-20T13:34:05 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:34:05 spiskymax 20.0:
------------- Analysing source catalogue for energy range 659.00-660.00 keV
Log_1 2001-12-20T13:34:05 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:34:05 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:34:06 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=8.542e-02 +-1.582e-03 sigma= 54.01
Log_1 2001-12-20T13:34:06 spiskymax 20.0:
----------End analysing source catalogue for energy range 659.00-660.00 keV
Log_1 2001-12-20T13:34:06 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #27 +++++++++++++++
Log_1 2001-12-20T13:34:06 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #28 +++++++++++++++
Log_1 2001-12-20T13:34:06 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:34:06 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:34:06 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:34:06 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:34:06 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:34:07 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:34:07 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:34:07 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:34:07 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:34:07 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:34:07 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:34:08 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:34:08 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:34:08 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:34:08 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:34:08 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:34:09 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:34:09 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:34:09 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:34:09 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:34:09 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:34:10 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:34:10 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:34:10 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:34:10 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:34:10 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:34:11 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:34:11 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:34:11 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:34:11 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:34:11 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:34:12 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:34:12 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:34:12 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:34:12 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:34:13 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:34:13 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:34:13 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:34:13 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:34:14 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:34:14 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:34:14 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:34:14 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:34:15 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:34:15 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:34:15 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:34:15 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:34:16 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:34:16 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:34:16 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:34:17 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:34:17 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:34:17 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:34:18 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:34:18 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:34:18 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:34:19 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:34:19 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:34:19 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:34:20 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:34:20 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:34:20 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:34:21 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:34:21 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:34:21 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:34:22 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:34:22 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:34:23 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:34:23 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:34:23 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:34:24 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:34:24 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:34:24 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:34:25 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:34:25 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:34:26 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:34:26 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:34:26 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:34:27 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:34:27 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:34:28 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:34:28 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:34:29 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:34:30 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:34:32 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:34:34 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:34:37 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:34:40 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:34:44 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:34:48 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:34:53 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:34:58 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:35:03 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:35:09 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:35:16 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:35:23 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:35:30 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:35:37 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:35:43 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:35:48 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:35:53 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:35:55 spiskymax 20.0: Good = 11.1 = [ 10.7 , 11.6 ]
Log_1 2001-12-20T13:35:55 spiskymax 20.0: Evidence = -870.6 = [ -870.7 , -870.4 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:35:56 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:35:56 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:35:57 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.884e-01 +-2.482e-03 sigma= 116.18
Log_1 2001-12-20T13:35:57 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:35:57 spiskymax 20.0:
------------- Analysing source catalogue for energy range 660.00-661.00 keV
Log_1 2001-12-20T13:35:57 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:35:57 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:35:58 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.884e-01 +-2.482e-03 sigma= 116.18
Log_1 2001-12-20T13:35:58 spiskymax 20.0:
----------End analysing source catalogue for energy range 660.00-661.00 keV
Log_1 2001-12-20T13:35:58 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #28 +++++++++++++++
Log_1 2001-12-20T13:35:58 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #29 +++++++++++++++
Log_1 2001-12-20T13:35:58 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:35:58 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:35:58 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:35:59 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:35:59 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:35:59 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:35:59 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:35:59 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:36:00 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:36:00 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:36:00 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:36:00 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:36:00 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:36:00 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:36:01 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:36:01 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:36:01 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:36:01 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:36:01 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:36:02 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:36:02 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:36:02 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:36:02 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:36:02 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:36:03 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:36:03 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:36:03 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:36:03 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:36:03 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:36:04 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:36:04 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:36:04 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:36:04 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:36:04 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:36:05 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:36:05 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:36:05 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:36:05 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:36:06 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:36:06 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:36:06 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:36:06 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:36:06 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:36:07 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:36:07 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:36:07 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:36:07 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:36:08 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:36:08 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:36:08 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:36:09 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:36:09 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:36:09 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:36:09 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:36:10 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:36:10 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:36:10 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:36:11 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:36:11 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:36:11 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:36:12 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:36:12 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:36:12 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:36:12 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:36:13 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:36:13 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:36:13 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:36:14 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:36:14 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:36:14 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:36:15 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:36:15 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:36:15 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:36:16 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:36:16 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:36:17 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:36:17 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:36:17 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:36:18 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:36:18 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:36:18 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:36:19 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:36:19 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:36:19 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:36:20 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:36:20 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:36:21 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:36:21 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:36:22 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:36:22 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:36:23 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:36:24 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:36:25 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:36:26 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:36:28 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:36:30 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:36:33 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:36:35 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:36:38 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:36:41 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:36:45 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:36:47 spiskymax 20.0: Good = 14.0 = [ 13.6 , 14.5 ]
Log_1 2001-12-20T13:36:47 spiskymax 20.0: Evidence = -1237.7 = [ -1237.8 , -1237.5 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:36:48 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:36:48 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:36:48 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=4.945e-01 +-2.927e-03 sigma= 168.96
Log_1 2001-12-20T13:36:48 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:36:48 spiskymax 20.0:
------------- Analysing source catalogue for energy range 661.00-662.00 keV
Log_1 2001-12-20T13:36:48 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:36:48 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:36:49 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=4.945e-01 +-2.927e-03 sigma= 168.96
Log_1 2001-12-20T13:36:49 spiskymax 20.0:
----------End analysing source catalogue for energy range 661.00-662.00 keV
Log_1 2001-12-20T13:36:49 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #29 +++++++++++++++
Log_1 2001-12-20T13:36:50 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #30 +++++++++++++++
Log_1 2001-12-20T13:36:50 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:36:50 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:36:50 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:36:51 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:36:51 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:36:51 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:36:51 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:36:51 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:36:52 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:36:52 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:36:52 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:36:52 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:36:52 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:36:53 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:36:53 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:36:53 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:36:53 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:36:53 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:36:54 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:36:54 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:36:54 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:36:54 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:36:54 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:36:55 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:36:55 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:36:55 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:36:55 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:36:55 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:36:56 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:36:56 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:36:56 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:36:56 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:36:56 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:36:57 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:36:57 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:36:57 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:36:57 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:36:58 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:36:58 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:36:58 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:36:58 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:36:59 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:36:59 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:36:59 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:37:00 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:37:00 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:37:00 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:37:00 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:37:01 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:37:01 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:37:01 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:37:02 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:37:02 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:37:02 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:37:03 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:37:03 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:37:03 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:37:04 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:37:04 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:37:04 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:37:05 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:37:05 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:37:05 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:37:06 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:37:06 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:37:06 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:37:07 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:37:07 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:37:07 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:37:08 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:37:08 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:37:08 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:37:09 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:37:09 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:37:10 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:37:10 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:37:10 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:37:11 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:37:12 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:37:13 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:37:15 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:37:17 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:37:20 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:37:22 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:37:25 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:37:28 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:37:32 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:37:35 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:37:38 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:37:42 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:37:45 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:37:49 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:37:53 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:37:58 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:38:03 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:38:09 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:38:14 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:38:19 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:38:24 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:38:27 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:38:30 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:38:32 spiskymax 20.0: Good = 15.3 = [ 15.0 , 15.6 ]
Log_1 2001-12-20T13:38:32 spiskymax 20.0: Evidence = -1044.0 = [ -1044.0 , -1043.9 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:38:33 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:38:33 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:38:34 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=3.653e-01 +-3.550e-03 sigma= 102.92
Log_1 2001-12-20T13:38:34 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:38:34 spiskymax 20.0:
------------- Analysing source catalogue for energy range 662.00-663.00 keV
Log_1 2001-12-20T13:38:34 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:38:34 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:38:35 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=3.653e-01 +-3.550e-03 sigma= 102.92
Log_1 2001-12-20T13:38:35 spiskymax 20.0:
----------End analysing source catalogue for energy range 662.00-663.00 keV
Log_1 2001-12-20T13:38:35 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #30 +++++++++++++++
Log_1 2001-12-20T13:38:39 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #31 +++++++++++++++
Log_1 2001-12-20T13:38:39 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:38:39 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:38:39 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:38:39 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:38:39 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:38:39 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:38:40 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:38:40 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:38:40 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:38:40 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:38:40 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:38:40 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:38:41 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:38:41 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:38:41 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:38:41 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:38:41 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:38:42 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:38:42 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:38:42 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:38:42 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:38:42 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:38:43 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:38:43 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:38:43 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:38:43 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:38:43 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:38:44 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:38:44 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:38:44 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:38:44 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:38:45 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:38:45 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:38:45 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:38:45 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:38:46 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:38:46 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:38:46 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:38:47 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:38:47 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:38:47 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:38:48 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:38:48 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:38:48 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:38:49 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:38:49 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:38:49 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:38:50 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:38:50 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:38:50 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:38:51 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:38:51 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:38:51 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:38:52 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:38:52 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:38:52 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:38:53 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:38:53 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:38:54 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:38:54 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:38:54 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:38:55 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:38:56 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:38:58 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:39:00 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:39:02 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:39:05 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:39:07 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:39:10 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:39:13 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:39:16 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:39:19 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:39:22 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:39:25 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:39:28 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:39:32 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:39:36 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:39:39 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:39:42 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:39:45 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:39:49 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:39:52 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:39:55 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:39:59 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:40:01 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:40:03 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:40:05 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:40:07 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:40:09 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:40:11 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:40:13 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:40:14 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:40:16 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:40:17 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:40:19 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:40:20 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:40:22 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:40:23 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:40:25 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:40:26 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:40:27 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:40:28 spiskymax 20.0: Good = 14.4 = [ 14.0 , 14.7 ]
Log_1 2001-12-20T13:40:28 spiskymax 20.0: Evidence = -821.0 = [ -821.2 , -820.9 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:40:28 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:40:28 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:40:29 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.227e-01 +-3.694e-03 sigma= 33.21
Log_1 2001-12-20T13:40:29 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:40:29 spiskymax 20.0:
------------- Analysing source catalogue for energy range 663.00-664.00 keV
Log_1 2001-12-20T13:40:29 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:40:29 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:40:29 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=1.227e-01 +-3.694e-03 sigma= 33.21
Log_1 2001-12-20T13:40:29 spiskymax 20.0:
----------End analysing source catalogue for energy range 663.00-664.00 keV
Log_1 2001-12-20T13:40:29 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #31 +++++++++++++++
Log_1 2001-12-20T13:40:32 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #32 +++++++++++++++
Log_1 2001-12-20T13:40:32 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:40:32 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:40:33 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:40:33 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:40:33 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:40:33 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:40:33 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:40:34 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:40:34 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:40:34 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:40:34 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:40:34 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:40:35 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:40:35 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:40:35 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:40:35 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:40:36 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:40:36 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:40:36 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:40:36 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:40:37 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:40:37 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:40:37 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:40:37 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:40:38 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:40:38 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:40:38 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:40:39 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:40:39 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:40:39 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:40:40 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:40:40 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:40:40 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:40:41 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:40:41 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:40:41 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:40:42 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:40:42 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:40:43 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:40:43 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:40:44 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:40:47 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:40:49 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:40:52 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:40:55 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:40:58 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:41:02 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:41:05 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:41:08 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:41:12 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:41:16 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:41:20 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:41:24 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:41:27 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:41:31 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:41:34 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:41:38 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:41:41 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:41:44 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:41:46 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:41:49 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:41:51 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:41:53 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:41:54 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:41:56 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:41:57 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:41:59 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:42:00 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:42:01 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:42:03 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:42:04 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:42:05 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:42:06 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:42:07 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:42:08 spiskymax 20.0: Good = 11.8 = [ 11.8 , 11.9 ]
Log_1 2001-12-20T13:42:08 spiskymax 20.0: Evidence = -561.2 = [ -561.2 , -561.2 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:42:08 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:42:08 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:42:08 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.343e-02 +-8.836e-04 sigma= 26.51
Log_1 2001-12-20T13:42:08 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:42:08 spiskymax 20.0:
------------- Analysing source catalogue for energy range 664.00-665.00 keV
Log_1 2001-12-20T13:42:08 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:42:08 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:42:09 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.343e-02 +-8.836e-04 sigma= 26.51
Log_1 2001-12-20T13:42:09 spiskymax 20.0:
----------End analysing source catalogue for energy range 664.00-665.00 keV
Log_1 2001-12-20T13:42:09 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #32 +++++++++++++++
Log_1 2001-12-20T13:42:12 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #33 +++++++++++++++
Log_1 2001-12-20T13:42:12 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:42:12 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:42:12 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:42:13 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:42:13 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:42:13 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:42:13 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:42:14 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:42:14 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:42:14 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:42:15 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:42:15 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:42:15 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:42:16 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:42:16 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:42:16 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:42:17 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:42:18 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:42:18 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:42:18 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:42:21 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:42:24 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:42:29 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:42:33 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:42:38 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:42:42 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:42:44 spiskymax 20.0: Good = 16.2 = [ 15.6 , 16.9 ]
Log_1 2001-12-20T13:42:44 spiskymax 20.0: Evidence = -356.5 = [ -356.7 , -356.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:42:45 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:42:45 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:42:47 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.726e-03 +-3.124e-04 sigma= 8.73
Log_1 2001-12-20T13:42:47 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:42:47 spiskymax 20.0:
------------- Analysing source catalogue for energy range 665.00-666.00 keV
Log_1 2001-12-20T13:42:47 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:42:47 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:42:48 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.726e-03 +-3.124e-04 sigma= 8.73
Log_1 2001-12-20T13:42:48 spiskymax 20.0:
----------End analysing source catalogue for energy range 665.00-666.00 keV
Log_1 2001-12-20T13:42:48 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #33 +++++++++++++++
Log_1 2001-12-20T13:42:51 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #34 +++++++++++++++
Log_1 2001-12-20T13:42:51 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:42:51 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:42:52 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:42:52 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:42:52 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:42:52 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:42:53 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:42:53 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:42:53 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:42:54 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:42:54 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:42:54 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:42:54 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:42:55 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:42:55 spiskymax 20.0: Good = 10.5 = [ 10.2 , 10.9 ]
Log_1 2001-12-20T13:42:55 spiskymax 20.0: Evidence = -99.4 = [ -99.4 , -99.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:42:55 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:42:55 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:42:55 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=8.681e-06 +-5.352e-05 sigma= 0.16
Log_1 2001-12-20T13:42:55 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:42:55 spiskymax 20.0:
------------- Analysing source catalogue for energy range 666.00-667.00 keV
Log_1 2001-12-20T13:42:55 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:42:55 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:42:56 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=8.681e-06 +-5.352e-05 sigma= 0.16
Log_1 2001-12-20T13:42:56 spiskymax 20.0:
----------End analysing source catalogue for energy range 666.00-667.00 keV
Log_1 2001-12-20T13:42:56 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #34 +++++++++++++++
Log_1 2001-12-20T13:42:59 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #35 +++++++++++++++
Log_1 2001-12-20T13:42:59 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:42:59 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:43:00 spiskymax 20.0: Good = NaN = [ 49.6 , NaN ]
Log_1 2001-12-20T13:43:00 spiskymax 20.0: Evidence = NaN = [ -Inf , NaN ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:43:01 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:01 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:43:02 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.227e-09 +-1.285e+14 sigma= 0.00
Log_1 2001-12-20T13:43:02 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:02 spiskymax 20.0:
------------- Analysing source catalogue for energy range 667.00-668.00 keV
Log_1 2001-12-20T13:43:03 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:43:03 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:43:04 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.227e-09 +-1.285e+14 sigma= 0.00
Log_1 2001-12-20T13:43:04 spiskymax 20.0:
----------End analysing source catalogue for energy range 667.00-668.00 keV
Log_1 2001-12-20T13:43:04 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #35 +++++++++++++++
Log_1 2001-12-20T13:43:07 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #36 +++++++++++++++
Log_1 2001-12-20T13:43:07 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:43:08 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:43:09 spiskymax 20.0: Good = NaN = [ 51.8 , NaN ]
Log_1 2001-12-20T13:43:09 spiskymax 20.0: Evidence = NaN = [ -Inf , NaN ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:43:10 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:10 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:43:11 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.227e-09 +-1.287e+14 sigma= 0.00
Log_1 2001-12-20T13:43:11 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:11 spiskymax 20.0:
------------- Analysing source catalogue for energy range 668.00-669.00 keV
Log_1 2001-12-20T13:43:11 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:43:11 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:43:12 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.227e-09 +-1.287e+14 sigma= 0.00
Log_1 2001-12-20T13:43:13 spiskymax 20.0:
----------End analysing source catalogue for energy range 668.00-669.00 keV
Log_1 2001-12-20T13:43:13 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #36 +++++++++++++++
Log_1 2001-12-20T13:43:16 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #37 +++++++++++++++
Log_1 2001-12-20T13:43:16 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:43:16 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:43:16 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:43:16 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:43:17 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:43:17 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:43:17 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:43:17 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:43:17 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:43:17 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:43:18 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:43:18 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:43:18 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:43:18 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:43:19 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:43:19 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:43:19 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:43:19 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:43:20 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:43:20 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:43:20 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:43:20 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:43:21 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:43:21 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:43:22 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:43:22 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:43:22 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:43:23 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:43:23 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:43:24 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:43:25 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:43:25 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:43:26 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:43:26 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:43:27 spiskymax 20.0: Good = 27.2 = [ 26.3 , 28.2 ]
Log_1 2001-12-20T13:43:27 spiskymax 20.0: Evidence = -267.8 = [ -268.0 , -267.6 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:43:27 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:27 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:43:27 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.577e-04 +-1.504e-03 sigma= 0.17
Log_1 2001-12-20T13:43:27 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:27 spiskymax 20.0:
------------- Analysing source catalogue for energy range 669.00-769.00 keV
Log_1 2001-12-20T13:43:27 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:43:27 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:43:27 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.577e-04 +-1.504e-03 sigma= 0.17
Log_1 2001-12-20T13:43:27 spiskymax 20.0:
----------End analysing source catalogue for energy range 669.00-769.00 keV
Log_1 2001-12-20T13:43:27 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #37 +++++++++++++++
Log_1 2001-12-20T13:43:30 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #38 +++++++++++++++
Log_1 2001-12-20T13:43:30 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:43:31 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:43:31 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:43:31 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:43:31 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:43:31 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:43:31 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:43:32 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:43:32 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:43:32 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:43:32 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:43:33 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:43:33 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:43:33 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:43:33 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:43:34 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:43:34 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:43:34 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:43:34 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:43:35 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:43:35 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:43:35 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:43:36 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:43:36 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:43:37 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:43:37 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:43:38 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:43:38 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:43:39 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:43:39 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:43:39 spiskymax 20.0: Good = 26.6 = [ 25.3 , 27.8 ]
Log_1 2001-12-20T13:43:39 spiskymax 20.0: Evidence = -241.9 = [ -242.2 , -241.6 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:43:39 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:39 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:43:40 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-4.255e-04 +-1.409e-03 sigma= -0.30
Log_1 2001-12-20T13:43:40 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:40 spiskymax 20.0:
------------- Analysing source catalogue for energy range 769.00-869.00 keV
Log_1 2001-12-20T13:43:40 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:43:40 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:43:40 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-4.255e-04 +-1.409e-03 sigma= -0.30
Log_1 2001-12-20T13:43:40 spiskymax 20.0:
----------End analysing source catalogue for energy range 769.00-869.00 keV
Log_1 2001-12-20T13:43:40 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #38 +++++++++++++++
Log_1 2001-12-20T13:43:44 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #39 +++++++++++++++
Log_1 2001-12-20T13:43:44 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:43:44 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:43:44 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:43:44 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:43:44 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:43:45 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:43:45 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:43:45 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:43:45 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:43:45 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:43:46 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:43:46 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:43:46 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:43:46 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:43:47 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:43:47 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:43:47 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:43:47 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:43:47 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:43:48 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:43:48 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:43:48 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:43:49 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:43:49 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:43:50 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:43:50 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:43:50 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:43:51 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:43:51 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:43:52 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:43:52 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:43:53 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:43:54 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:43:54 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:43:55 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:43:55 spiskymax 20.0: Good = 27.2 = [ 26.3 , 28.1 ]
Log_1 2001-12-20T13:43:55 spiskymax 20.0: Evidence = -259.0 = [ -259.2 , -258.8 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:43:56 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:56 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:43:56 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-9.413e-04 +-1.323e-03 sigma= -0.71
Log_1 2001-12-20T13:43:56 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:43:56 spiskymax 20.0:
------------- Analysing source catalogue for energy range 869.00-969.00 keV
Log_1 2001-12-20T13:43:56 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:43:56 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:43:56 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-9.413e-04 +-1.323e-03 sigma= -0.71
Log_1 2001-12-20T13:43:56 spiskymax 20.0:
----------End analysing source catalogue for energy range 869.00-969.00 keV
Log_1 2001-12-20T13:43:56 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #39 +++++++++++++++
Log_1 2001-12-20T13:44:00 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #40 +++++++++++++++
Log_1 2001-12-20T13:44:00 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:44:00 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:44:01 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:44:01 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:44:01 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:44:01 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:44:01 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:44:02 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:44:02 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:44:02 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:44:02 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:44:02 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:44:03 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:44:03 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:44:03 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:44:03 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:44:03 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:44:04 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:44:04 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:44:04 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:44:05 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:44:05 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:44:05 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:44:06 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:44:06 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:44:07 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:44:07 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:44:08 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:44:08 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:44:09 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:44:09 spiskymax 20.0: Good = 24.8 = [ 23.8 , 25.8 ]
Log_1 2001-12-20T13:44:09 spiskymax 20.0: Evidence = -249.5 = [ -249.8 , -249.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:44:09 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:44:09 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:44:09 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-2.134e-04 +-1.095e-03 sigma= -0.19
Log_1 2001-12-20T13:44:09 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:44:09 spiskymax 20.0:
------------- Analysing source catalogue for energy range 969.00-1069.00 keV
Log_1 2001-12-20T13:44:10 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:44:10 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:44:10 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-2.134e-04 +-1.095e-03 sigma= -0.19
Log_1 2001-12-20T13:44:10 spiskymax 20.0:
----------End analysing source catalogue for energy range 969.00-1069.00 keV
Log_1 2001-12-20T13:44:10 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #40 +++++++++++++++
Log_1 2001-12-20T13:44:14 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #41 +++++++++++++++
Log_1 2001-12-20T13:44:14 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:44:14 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:44:14 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:44:15 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:44:15 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:44:15 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:44:15 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:44:15 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:44:16 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:44:16 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:44:16 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:44:16 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:44:17 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:44:17 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:44:17 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:44:17 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:44:18 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:44:18 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:44:19 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:44:19 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:44:19 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:44:20 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:44:20 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:44:21 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:44:21 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:44:22 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:44:22 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:44:22 spiskymax 20.0: Good = 24.4 = [ 23.5 , 25.3 ]
Log_1 2001-12-20T13:44:22 spiskymax 20.0: Evidence = -233.4 = [ -233.6 , -233.2 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:44:22 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:44:22 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:44:23 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-1.160e-04 +-9.451e-04 sigma= -0.12
Log_1 2001-12-20T13:44:23 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:44:23 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1069.00-1169.00 keV
Log_1 2001-12-20T13:44:23 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:44:23 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:44:23 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-1.160e-04 +-9.451e-04 sigma= -0.12
Log_1 2001-12-20T13:44:23 spiskymax 20.0:
----------End analysing source catalogue for energy range 1069.00-1169.00 keV
Log_1 2001-12-20T13:44:23 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #41 +++++++++++++++
Log_1 2001-12-20T13:44:26 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #42 +++++++++++++++
Log_1 2001-12-20T13:44:26 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:44:27 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:44:27 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:44:27 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:44:27 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:44:27 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:44:27 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:44:28 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:44:28 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:44:28 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:44:28 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:44:28 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:44:29 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:44:29 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:44:29 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:44:29 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:44:30 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:44:30 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:44:30 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:44:31 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:44:31 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:44:31 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:44:32 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:44:32 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:44:33 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:44:33 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:44:34 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:44:34 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:44:35 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:44:35 spiskymax 20.0: Good = 19.8 = [ 19.2 , 20.4 ]
Log_1 2001-12-20T13:44:35 spiskymax 20.0: Evidence = -220.2 = [ -220.3 , -220.1 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:44:35 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:44:35 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:44:36 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-7.364e-04 +-6.605e-04 sigma= -1.11
Log_1 2001-12-20T13:44:36 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:44:36 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1169.00-1269.00 keV
Log_1 2001-12-20T13:44:36 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:44:36 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:44:36 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-7.364e-04 +-6.605e-04 sigma= -1.11
Log_1 2001-12-20T13:44:36 spiskymax 20.0:
----------End analysing source catalogue for energy range 1169.00-1269.00 keV
Log_1 2001-12-20T13:44:36 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #42 +++++++++++++++
Log_1 2001-12-20T13:44:39 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #43 +++++++++++++++
Log_1 2001-12-20T13:44:39 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:44:39 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:44:39 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:44:39 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:44:40 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:44:40 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:44:40 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:44:40 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:44:40 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:44:41 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:44:41 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:44:41 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:44:41 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:44:42 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:44:42 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:44:42 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:44:43 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:44:43 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:44:43 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:44:44 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:44:44 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:44:45 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:44:45 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:44:46 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:44:46 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:44:47 spiskymax 20.0: Good = 23.0 = [ 21.9 , 24.1 ]
Log_1 2001-12-20T13:44:47 spiskymax 20.0: Evidence = -225.5 = [ -225.8 , -225.3 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:44:47 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:44:47 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:44:47 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-9.696e-05 +-1.281e-03 sigma= -0.08
Log_1 2001-12-20T13:44:47 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:44:47 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1269.00-1369.00 keV
Log_1 2001-12-20T13:44:47 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:44:47 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:44:47 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-9.696e-05 +-1.281e-03 sigma= -0.08
Log_1 2001-12-20T13:44:47 spiskymax 20.0:
----------End analysing source catalogue for energy range 1269.00-1369.00 keV
Log_1 2001-12-20T13:44:47 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #43 +++++++++++++++
Log_1 2001-12-20T13:44:50 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #44 +++++++++++++++
Log_1 2001-12-20T13:44:50 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:44:51 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:44:51 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:44:51 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:44:51 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:44:51 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:44:52 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:44:52 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:44:52 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:44:52 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:44:52 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:44:53 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:44:53 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:44:53 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:44:53 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:44:53 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:44:53 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:44:54 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:44:54 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:44:54 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:44:54 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:44:55 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:44:55 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:44:55 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:44:55 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:44:55 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:44:56 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:44:56 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:44:56 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:44:57 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:44:57 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:44:57 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:44:58 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:44:58 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:44:58 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:44:59 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:44:59 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:44:59 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:45:00 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:45:00 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:45:01 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:45:02 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:45:02 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:45:03 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:45:03 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:45:04 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:45:05 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:45:05 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:45:06 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:45:06 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:45:07 spiskymax 20.0: Good = 29.0 = [ 27.7 , 30.3 ]
Log_1 2001-12-20T13:45:07 spiskymax 20.0: Evidence = -286.8 = [ -287.1 , -286.5 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:45:07 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:07 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:45:07 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-1.474e-03 +-2.257e-03 sigma= -0.65
Log_1 2001-12-20T13:45:07 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:07 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1369.00-1469.00 keV
Log_1 2001-12-20T13:45:07 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:45:07 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:45:08 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-1.474e-03 +-2.257e-03 sigma= -0.65
Log_1 2001-12-20T13:45:08 spiskymax 20.0:
----------End analysing source catalogue for energy range 1369.00-1469.00 keV
Log_1 2001-12-20T13:45:08 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #44 +++++++++++++++
Log_1 2001-12-20T13:45:11 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #45 +++++++++++++++
Log_1 2001-12-20T13:45:11 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:45:11 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:45:11 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:45:11 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:45:11 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:45:12 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:45:12 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:45:12 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:45:12 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:45:13 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:45:13 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:45:13 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:45:14 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:45:14 spiskymax 20.0: Good = 12.4 = [ 11.9 , 12.8 ]
Log_1 2001-12-20T13:45:14 spiskymax 20.0: Evidence = -188.5 = [ -188.6 , -188.4 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:45:14 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:14 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:45:14 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-2.565e-04 +-4.032e-04 sigma= -0.64
Log_1 2001-12-20T13:45:14 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:14 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1469.00-1569.00 keV
Log_1 2001-12-20T13:45:14 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:45:14 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:45:14 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-2.565e-04 +-4.032e-04 sigma= -0.64
Log_1 2001-12-20T13:45:14 spiskymax 20.0:
----------End analysing source catalogue for energy range 1469.00-1569.00 keV
Log_1 2001-12-20T13:45:14 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #45 +++++++++++++++
Log_1 2001-12-20T13:45:17 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #46 +++++++++++++++
Log_1 2001-12-20T13:45:17 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:45:18 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:45:18 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:45:18 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:45:18 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:45:18 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:45:18 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:45:19 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:45:19 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:45:19 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:45:20 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:45:20 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:45:20 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:45:21 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:45:21 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:45:21 spiskymax 20.0: Good = 13.6 = [ 13.2 , 14.1 ]
Log_1 2001-12-20T13:45:21 spiskymax 20.0: Evidence = -184.1 = [ -184.2 , -184.0 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:45:21 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:21 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:45:21 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-1.213e-04 +-3.142e-04 sigma= -0.39
Log_1 2001-12-20T13:45:21 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:21 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1569.00-1669.00 keV
Log_1 2001-12-20T13:45:21 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:45:21 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:45:22 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-1.213e-04 +-3.142e-04 sigma= -0.39
Log_1 2001-12-20T13:45:22 spiskymax 20.0:
----------End analysing source catalogue for energy range 1569.00-1669.00 keV
Log_1 2001-12-20T13:45:22 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #46 +++++++++++++++
Log_1 2001-12-20T13:45:25 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #47 +++++++++++++++
Log_1 2001-12-20T13:45:25 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:45:25 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:45:25 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:45:25 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:45:25 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:45:25 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:45:26 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:45:26 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:45:26 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:45:26 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:45:26 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:45:27 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:45:27 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:45:27 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:45:28 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:45:28 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:45:28 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:45:29 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:45:29 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:45:29 spiskymax 20.0: Good = 17.3 = [ 16.8 , 17.9 ]
Log_1 2001-12-20T13:45:29 spiskymax 20.0: Evidence = -213.6 = [ -213.7 , -213.5 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:45:29 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:29 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:45:29 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-8.623e-05 +-5.075e-04 sigma= -0.17
Log_1 2001-12-20T13:45:29 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:29 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1669.00-1769.00 keV
Log_1 2001-12-20T13:45:29 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:45:29 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:45:30 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-8.623e-05 +-5.075e-04 sigma= -0.17
Log_1 2001-12-20T13:45:30 spiskymax 20.0:
----------End analysing source catalogue for energy range 1669.00-1769.00 keV
Log_1 2001-12-20T13:45:30 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #47 +++++++++++++++
Log_1 2001-12-20T13:45:33 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #48 +++++++++++++++
Log_1 2001-12-20T13:45:33 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:45:33 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:45:33 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:45:33 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:45:34 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:45:34 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:45:34 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:45:34 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:45:35 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:45:35 spiskymax 20.0: Good = 5.9 = [ 5.8 , 6.1 ]
Log_1 2001-12-20T13:45:35 spiskymax 20.0: Evidence = -162.2 = [ -162.2 , -162.1 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:45:35 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:35 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:45:35 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.160e-05 +-1.910e-04 sigma= 0.11
Log_1 2001-12-20T13:45:35 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:35 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1769.00-1869.00 keV
Log_1 2001-12-20T13:45:35 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:45:35 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:45:36 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.160e-05 +-1.910e-04 sigma= 0.11
Log_1 2001-12-20T13:45:36 spiskymax 20.0:
----------End analysing source catalogue for energy range 1769.00-1869.00 keV
Log_1 2001-12-20T13:45:36 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #48 +++++++++++++++
Log_1 2001-12-20T13:45:39 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #49 +++++++++++++++
Log_1 2001-12-20T13:45:39 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:45:39 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:45:40 spiskymax 20.0: Good = 66.9 = [ 48.9 , 85.0 ]
Log_1 2001-12-20T13:45:40 spiskymax 20.0: Evidence = -Inf = [ -3478.6 , -Inf ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:45:41 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:41 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:45:42 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.227e-09 +-1.303e+14 sigma= 0.00
Log_1 2001-12-20T13:45:42 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:42 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1869.00-1969.00 keV
Log_1 2001-12-20T13:45:42 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:45:42 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:45:43 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=2.227e-09 +-1.303e+14 sigma= 0.00
Log_1 2001-12-20T13:45:43 spiskymax 20.0:
----------End analysing source catalogue for energy range 1869.00-1969.00 keV
Log_1 2001-12-20T13:45:43 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #49 +++++++++++++++
Log_1 2001-12-20T13:45:47 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #50 +++++++++++++++
Log_1 2001-12-20T13:45:47 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:45:47 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:45:47 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:45:47 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:45:47 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:45:47 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:45:48 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:45:48 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:45:48 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:45:48 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:45:49 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:45:49 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:45:49 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:45:49 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:45:50 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:45:50 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:45:50 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:45:50 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:45:51 spiskymax 20.0: Good = 0.8 = [ 0.8 , 0.9 ]
Log_1 2001-12-20T13:45:51 spiskymax 20.0: Evidence = -153.8 = [ -153.8 , -153.8 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:45:51 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:51 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:45:51 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-2.487e-05 +-4.602e-05 sigma= -0.54
Log_1 2001-12-20T13:45:51 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:51 spiskymax 20.0:
------------- Analysing source catalogue for energy range 1969.00-2069.00 keV
Log_1 2001-12-20T13:45:51 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:45:51 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:45:51 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-2.487e-05 +-4.602e-05 sigma= -0.54
Log_1 2001-12-20T13:45:51 spiskymax 20.0:
----------End analysing source catalogue for energy range 1969.00-2069.00 keV
Log_1 2001-12-20T13:45:51 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #50 +++++++++++++++
Log_1 2001-12-20T13:45:54 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #51 +++++++++++++++
Log_1 2001-12-20T13:45:54 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:45:54 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:45:55 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:45:55 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:45:55 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:45:55 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:45:55 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:45:55 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:45:56 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:45:56 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:45:56 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:45:56 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:45:57 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:45:57 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:45:57 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:45:58 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:45:58 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:45:58 spiskymax 20.0: Good = 8.5 = [ 8.2 , 8.7 ]
Log_1 2001-12-20T13:45:58 spiskymax 20.0: Evidence = -622.5 = [ -622.5 , -622.4 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:45:58 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:58 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:45:58 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-8.344e-04 +-6.845e-04 sigma= -1.22
Log_1 2001-12-20T13:45:58 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:45:58 spiskymax 20.0:
------------- Analysing source catalogue for energy range 2069.00-3069.00 keV
Log_1 2001-12-20T13:45:58 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:45:58 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:45:58 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=-8.344e-04 +-6.845e-04 sigma= -1.22
Log_1 2001-12-20T13:45:58 spiskymax 20.0:
----------End analysing source catalogue for energy range 2069.00-3069.00 keV
Log_1 2001-12-20T13:45:58 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #51 +++++++++++++++
Log_1 2001-12-20T13:46:02 spiskymax 20.0: +++++++++ memsys5 analysis for energy range #52 +++++++++++++++
Log_1 2001-12-20T13:46:02 spiskymax 20.0: Iteration 1
Log_1 2001-12-20T13:46:02 spiskymax 20.0: Iteration 2
Log_1 2001-12-20T13:46:02 spiskymax 20.0: Iteration 3
Log_1 2001-12-20T13:46:03 spiskymax 20.0: Iteration 4
Log_1 2001-12-20T13:46:03 spiskymax 20.0: Iteration 5
Log_1 2001-12-20T13:46:04 spiskymax 20.0: Iteration 6
Log_1 2001-12-20T13:46:05 spiskymax 20.0: Iteration 7
Log_1 2001-12-20T13:46:05 spiskymax 20.0: Iteration 8
Log_1 2001-12-20T13:46:06 spiskymax 20.0: Iteration 9
Log_1 2001-12-20T13:46:07 spiskymax 20.0: Iteration 10
Log_1 2001-12-20T13:46:07 spiskymax 20.0: Iteration 11
Log_1 2001-12-20T13:46:08 spiskymax 20.0: Iteration 12
Log_1 2001-12-20T13:46:09 spiskymax 20.0: Iteration 13
Log_1 2001-12-20T13:46:09 spiskymax 20.0: Iteration 14
Log_1 2001-12-20T13:46:10 spiskymax 20.0: Iteration 15
Log_1 2001-12-20T13:46:11 spiskymax 20.0: Iteration 16
Log_1 2001-12-20T13:46:11 spiskymax 20.0: Iteration 17
Log_1 2001-12-20T13:46:12 spiskymax 20.0: Iteration 18
Log_1 2001-12-20T13:46:13 spiskymax 20.0: Iteration 19
Log_1 2001-12-20T13:46:13 spiskymax 20.0: Iteration 20
Log_1 2001-12-20T13:46:14 spiskymax 20.0: Iteration 21
Log_1 2001-12-20T13:46:15 spiskymax 20.0: Iteration 22
Log_1 2001-12-20T13:46:15 spiskymax 20.0: Iteration 23
Log_1 2001-12-20T13:46:16 spiskymax 20.0: Iteration 24
Log_1 2001-12-20T13:46:17 spiskymax 20.0: Iteration 25
Log_1 2001-12-20T13:46:17 spiskymax 20.0: Iteration 26
Log_1 2001-12-20T13:46:18 spiskymax 20.0: Iteration 27
Log_1 2001-12-20T13:46:19 spiskymax 20.0: Iteration 28
Log_1 2001-12-20T13:46:20 spiskymax 20.0: Iteration 29
Log_1 2001-12-20T13:46:20 spiskymax 20.0: Iteration 30
Log_1 2001-12-20T13:46:21 spiskymax 20.0: Iteration 31
Log_1 2001-12-20T13:46:22 spiskymax 20.0: Iteration 32
Log_1 2001-12-20T13:46:23 spiskymax 20.0: Iteration 33
Log_1 2001-12-20T13:46:23 spiskymax 20.0: Iteration 34
Log_1 2001-12-20T13:46:24 spiskymax 20.0: Iteration 35
Log_1 2001-12-20T13:46:25 spiskymax 20.0: Iteration 36
Log_1 2001-12-20T13:46:25 spiskymax 20.0: Iteration 37
Log_1 2001-12-20T13:46:26 spiskymax 20.0: Iteration 38
Log_1 2001-12-20T13:46:27 spiskymax 20.0: Iteration 39
Log_1 2001-12-20T13:46:27 spiskymax 20.0: Iteration 40
Log_1 2001-12-20T13:46:28 spiskymax 20.0: Iteration 41
Log_1 2001-12-20T13:46:29 spiskymax 20.0: Iteration 42
Log_1 2001-12-20T13:46:30 spiskymax 20.0: Iteration 43
Log_1 2001-12-20T13:46:31 spiskymax 20.0: Iteration 44
Log_1 2001-12-20T13:46:31 spiskymax 20.0: Iteration 45
Log_1 2001-12-20T13:46:32 spiskymax 20.0: Iteration 46
Log_1 2001-12-20T13:46:33 spiskymax 20.0: Iteration 47
Log_1 2001-12-20T13:46:33 spiskymax 20.0: Iteration 48
Log_1 2001-12-20T13:46:34 spiskymax 20.0: Iteration 49
Log_1 2001-12-20T13:46:35 spiskymax 20.0: Iteration 50
Log_1 2001-12-20T13:46:35 spiskymax 20.0: Iteration 51
Log_1 2001-12-20T13:46:36 spiskymax 20.0: Iteration 52
Log_1 2001-12-20T13:46:37 spiskymax 20.0: Iteration 53
Log_1 2001-12-20T13:46:38 spiskymax 20.0: Iteration 54
Log_1 2001-12-20T13:46:38 spiskymax 20.0: Iteration 55
Log_1 2001-12-20T13:46:39 spiskymax 20.0: Iteration 56
Log_1 2001-12-20T13:46:40 spiskymax 20.0: Iteration 57
Log_1 2001-12-20T13:46:40 spiskymax 20.0: Iteration 58
Log_1 2001-12-20T13:46:41 spiskymax 20.0: Iteration 59
Log_1 2001-12-20T13:46:42 spiskymax 20.0: Iteration 60
Log_1 2001-12-20T13:46:43 spiskymax 20.0: Iteration 61
Log_1 2001-12-20T13:46:43 spiskymax 20.0: Iteration 62
Log_1 2001-12-20T13:46:44 spiskymax 20.0: Iteration 63
Log_1 2001-12-20T13:46:45 spiskymax 20.0: Iteration 64
Log_1 2001-12-20T13:46:45 spiskymax 20.0: Iteration 65
Log_1 2001-12-20T13:46:46 spiskymax 20.0: Iteration 66
Log_1 2001-12-20T13:46:47 spiskymax 20.0: Iteration 67
Log_1 2001-12-20T13:46:47 spiskymax 20.0: Iteration 68
Log_1 2001-12-20T13:46:48 spiskymax 20.0: Iteration 69
Log_1 2001-12-20T13:46:49 spiskymax 20.0: Iteration 70
Log_1 2001-12-20T13:46:49 spiskymax 20.0: Iteration 71
Log_1 2001-12-20T13:46:50 spiskymax 20.0: Iteration 72
Log_1 2001-12-20T13:46:51 spiskymax 20.0: Iteration 73
Log_1 2001-12-20T13:46:52 spiskymax 20.0: Iteration 74
Log_1 2001-12-20T13:46:52 spiskymax 20.0: Iteration 75
Log_1 2001-12-20T13:46:53 spiskymax 20.0: Iteration 76
Log_1 2001-12-20T13:46:54 spiskymax 20.0: Iteration 77
Log_1 2001-12-20T13:46:55 spiskymax 20.0: Iteration 78
Log_1 2001-12-20T13:46:55 spiskymax 20.0: Iteration 79
Log_1 2001-12-20T13:46:56 spiskymax 20.0: Iteration 80
Log_1 2001-12-20T13:46:57 spiskymax 20.0: Iteration 81
Log_1 2001-12-20T13:46:57 spiskymax 20.0: Iteration 82
Log_1 2001-12-20T13:46:58 spiskymax 20.0: Iteration 83
Log_1 2001-12-20T13:46:59 spiskymax 20.0: Iteration 84
Log_1 2001-12-20T13:46:59 spiskymax 20.0: Iteration 85
Log_1 2001-12-20T13:47:00 spiskymax 20.0: Iteration 86
Log_1 2001-12-20T13:47:01 spiskymax 20.0: Iteration 87
Log_1 2001-12-20T13:47:01 spiskymax 20.0: Iteration 88
Log_1 2001-12-20T13:47:02 spiskymax 20.0: Iteration 89
Log_1 2001-12-20T13:47:03 spiskymax 20.0: Iteration 90
Log_1 2001-12-20T13:47:03 spiskymax 20.0: Iteration 91
Log_1 2001-12-20T13:47:04 spiskymax 20.0: Iteration 92
Log_1 2001-12-20T13:47:05 spiskymax 20.0: Iteration 93
Log_1 2001-12-20T13:47:05 spiskymax 20.0: Iteration 94
Log_1 2001-12-20T13:47:06 spiskymax 20.0: Iteration 95
Log_1 2001-12-20T13:47:07 spiskymax 20.0: Iteration 96
Log_1 2001-12-20T13:47:07 spiskymax 20.0: Iteration 97
Log_1 2001-12-20T13:47:08 spiskymax 20.0: Iteration 98
Log_1 2001-12-20T13:47:09 spiskymax 20.0: Iteration 99
Log_1 2001-12-20T13:47:09 spiskymax 20.0: Iteration 100
Log_1 2001-12-20T13:47:10 spiskymax 20.0: +++++++++Statistics+++++++++
Log_1 2001-12-20T13:47:11 spiskymax 20.0: Good = 0.0 = [ 0.0 , 0.0 ]
Log_1 2001-12-20T13:47:11 spiskymax 20.0: Evidence = -1470.0 = [ -1470.0 , -1470.0 ] = Log[e]Prob(Data)
Log_1 2001-12-20T13:47:11 spiskymax 20.0: ------------------- source fluxes and error analysis -----------------
Log_1 2001-12-20T13:47:11 spiskymax 20.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2001-12-20T13:47:11 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=0.000e+00 +-0.000e+00 sigma= NaN
Log_1 2001-12-20T13:47:11 spiskymax 20.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2001-12-20T13:47:11 spiskymax 20.0:
------------- Analysing source catalogue for energy range 3069.00-4069.00 keV
Log_1 2001-12-20T13:47:11 spiskymax 20.0: total number of sources in input catalogue=1
Log_1 2001-12-20T13:47:11 spiskymax 20.0: total number of sources in output catalogue=1
Log_1 2001-12-20T13:47:11 spiskymax 20.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=0.000e+00 +-0.000e+00 sigma= NaN
Log_1 2001-12-20T13:47:11 spiskymax 20.0:
----------End analysing source catalogue for energy range 3069.00-4069.00 keV
Log_1 2001-12-20T13:47:11 spiskymax 20.0: +++++++++ end of memsys5 analysis for energy range #52 +++++++++++++++
Log_1 2001-12-20T13:47:11 spiskymax 20.0: write_SKY_IMA begins
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALobjectFindElement status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALGetBaseType status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALGetBaseType baseType=6
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:11 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_1 2001-12-20T13:47:11 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:11 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,2,IMAGE]
Log_1 2001-12-20T13:47:11 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:11 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,3,IMAGE]
Log_1 2001-12-20T13:47:11 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:11 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,4,IMAGE]
Log_1 2001-12-20T13:47:11 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:11 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,5,IMAGE]
Log_1 2001-12-20T13:47:11 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:11 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,6,IMAGE]
Log_1 2001-12-20T13:47:11 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:11 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:11 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,7,IMAGE]
Log_1 2001-12-20T13:47:11 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:12 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,8,IMAGE]
Log_1 2001-12-20T13:47:12 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:12 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,9,IMAGE]
Log_1 2001-12-20T13:47:12 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:12 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,10,IMAGE]
Log_1 2001-12-20T13:47:12 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:12 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,11,IMAGE]
Log_1 2001-12-20T13:47:12 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:12 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,12,IMAGE]
Log_1 2001-12-20T13:47:12 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:12 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,13,IMAGE]
Log_1 2001-12-20T13:47:12 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:12 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,14,IMAGE]
Log_1 2001-12-20T13:47:12 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:12 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:12 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,15,IMAGE]
Log_1 2001-12-20T13:47:12 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:13 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,16,IMAGE]
Log_1 2001-12-20T13:47:13 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:13 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,17,IMAGE]
Log_1 2001-12-20T13:47:13 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:13 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,18,IMAGE]
Log_1 2001-12-20T13:47:13 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:13 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,19,IMAGE]
Log_1 2001-12-20T13:47:13 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:13 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:14 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,20,IMAGE]
Log_1 2001-12-20T13:47:14 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:14 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,21,IMAGE]
Log_1 2001-12-20T13:47:14 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:14 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,22,IMAGE]
Log_1 2001-12-20T13:47:14 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:14 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:14 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,23,IMAGE]
Log_1 2001-12-20T13:47:14 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:15 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,24,IMAGE]
Log_1 2001-12-20T13:47:15 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:15 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,25,IMAGE]
Log_1 2001-12-20T13:47:15 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:15 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:15 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,26,IMAGE]
Log_1 2001-12-20T13:47:15 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:16 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:16 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:16 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:16 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:16 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,27,IMAGE]
Log_1 2001-12-20T13:47:16 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:16 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:16 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:16 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:16 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:16 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,28,IMAGE]
Log_1 2001-12-20T13:47:16 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:17 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:17 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:17 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:17 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:17 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,29,IMAGE]
Log_1 2001-12-20T13:47:17 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:17 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:17 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:17 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:17 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:17 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,30,IMAGE]
Log_1 2001-12-20T13:47:17 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:18 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:18 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:18 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:18 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:18 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,31,IMAGE]
Log_1 2001-12-20T13:47:18 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:18 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:18 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:18 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:18 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:18 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,32,IMAGE]
Log_1 2001-12-20T13:47:18 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:19 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:19 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:19 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:19 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:19 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,33,IMAGE]
Log_1 2001-12-20T13:47:19 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:19 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:19 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:19 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:19 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:19 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,34,IMAGE]
Log_1 2001-12-20T13:47:19 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:20 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:20 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:20 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:20 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:20 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,35,IMAGE]
Log_1 2001-12-20T13:47:20 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:20 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:20 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:20 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:20 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:20 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,36,IMAGE]
Log_1 2001-12-20T13:47:20 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:21 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:21 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:21 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:21 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:21 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,37,IMAGE]
Log_1 2001-12-20T13:47:21 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:22 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:22 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:22 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:22 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:22 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,38,IMAGE]
Log_1 2001-12-20T13:47:22 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:22 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:22 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:22 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:22 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:22 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,39,IMAGE]
Log_1 2001-12-20T13:47:22 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:23 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:23 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:23 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:23 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:23 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,40,IMAGE]
Log_1 2001-12-20T13:47:23 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:24 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:24 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:24 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:24 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:24 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,41,IMAGE]
Log_1 2001-12-20T13:47:24 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:25 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:25 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:25 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:25 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:25 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,42,IMAGE]
Log_1 2001-12-20T13:47:25 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:25 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:25 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:25 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:25 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:25 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,43,IMAGE]
Log_1 2001-12-20T13:47:25 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:26 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:26 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:26 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:26 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:26 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,44,IMAGE]
Log_1 2001-12-20T13:47:26 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:27 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:27 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:27 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:27 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:27 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,45,IMAGE]
Log_1 2001-12-20T13:47:27 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:28 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:28 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:28 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:28 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:28 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,46,IMAGE]
Log_1 2001-12-20T13:47:28 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:29 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:29 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:29 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:29 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:29 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,47,IMAGE]
Log_1 2001-12-20T13:47:29 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:31 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:31 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:31 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:31 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:31 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,48,IMAGE]
Log_1 2001-12-20T13:47:31 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:32 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:32 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:32 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:32 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:32 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,49,IMAGE]
Log_1 2001-12-20T13:47:32 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:33 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:33 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:33 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:33 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:33 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,50,IMAGE]
Log_1 2001-12-20T13:47:33 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:34 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:34 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:34 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:34 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:34 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,51,IMAGE]
Log_1 2001-12-20T13:47:34 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:35 spiskymax 20.0: DAL3GENindexCreateMember status=0
Log_1 2001-12-20T13:47:35 spiskymax 20.0: DALarrayModStruct status=0
Log_1 2001-12-20T13:47:35 spiskymax 20.0: DALarrayPutSection status=0
Log_1 2001-12-20T13:47:35 spiskymax 20.0: DALindexUpdate status=-25109
Log_1 2001-12-20T13:47:35 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_image.fits[SPI.-SKY.-IMA,52,IMAGE]
Log_1 2001-12-20T13:47:35 spiskymax 20.0: CommonStampObject status=0
Log_1 2001-12-20T13:47:35 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_index.fits[GROUPING,1,BINTABLE]
Log_1 2001-12-20T13:47:35 spiskymax 20.0: write_SKY_IMA ends
Log_1 2001-12-20T13:47:35 spiskymax 20.0: write_profiles begins
Log_1 2001-12-20T13:47:35 spiskymax 20.0: DALobjectFindElement status=0
Log_1 2001-12-20T13:47:35 spiskymax 20.0: DALGetBaseType status=0
Log_1 2001-12-20T13:47:35 spiskymax 20.0: DALGetBaseType baseType=6
Log_1 2001-12-20T13:47:35 spiskymax 20.0: spiskymax v20 137-Cs processing --STAMP-- spi/skymax_index.fits[GROUPING,1,BINTABLE]
Log_1 2001-12-20T13:47:35 spiskymax 20.0: write_profiles ends
Log_1 2001-12-20T13:47:36 spiskymax 20.0: CommonCloseSWG=0
Log_1 2001-12-20T13:47:36 spiskymax 20.0: << spiskymax_processing ends
Log_1 2001-12-20T13:47:36 spiskymax 20.0: Task spiskymax terminating with status 0
Log_0 2001-12-20T13:47:37 blc_sa 1.6: SPI data analysis finished. Status 0
Log_1 2001-12-20T13:47:37 blc_sa 1.6: Task blc_sa terminating with status 0
| en |
converted_docs | 549292 | PUBLIC NOTICE{width="0.6541666666666667in"
height="0.6604166666666667in"}
FEDERAL COMMUNICATIONS COMMISSION
445 12th STREET, S.W.
WASHINGTON, D.C. 20554 **DA 04-442**
News media information 202/418-0500 Fax-On-Demand 202/418-2830 Internet:
http://www.fcc.gov ftp.fcc.gov
**MEDIA BUREAU ACTION February 24, 2004**
REQUEST FOR EXEMPTION FROM COMMISSION'S CLOSED CAPTIONING RULES
CSR 6287
Awakening Ministries has filed a petition for exemption from the closed
captioning requirements, pursuant to Section 79.1 of the Commission's
rules, 47 C.F.R. § 79.1. Petitioner claims that compliance would impose
an undue burden, as defined in Section 79.1(f) of the Commission's
rules, 47 C.F.R. § 79.1(f).
Comments and oppositions are due within 30 days from the date of this
public notice. Please place the case identifier, CSR 6287, on all
filings. Comments and oppositions sent via e-mail to the Commission will
be considered informal and are not part of the official record. In
addition, comments and oppositions filed must indicate that they have
been served on the petitioner. All comments and oppositions must be
served on petitioner at:
Awakening Ministries
Attn: Randy Phillips
P.O. Box 15086
Austin, TX 78761
In addition, an original and two copies of all comments and oppositions
must be filed with the Commission:
Secretary
Federal Communications Commission
445 12^th^ Street, S.W.
Washington, D.C. 20554
Petitioner's reply is due 20 days thereafter. Electronic filing is not
available at this time.
The petition and comments are available for public inspection in the
Commission's Reference Information Center:
445 12^th^ Street, S.W.
Washington, D.C. 20554
202-418-7092
**Accessible Formats**
To request materials in **accessible formats for people with
disabilities** (Braille, large print, electronic files, audio format),
send an e-mail to <fcc504@fcc.gov> or call the Consumer & Governmental
Affairs Bureau at 202-418-0531 (voice), 202-418-7365 (tty).
Media Contact: Michelle Russo at (202) 418-7200.
Media Bureau Contact: Sonia Greenaway-Mickle or Steve Garner at (202)
418-7200.
TTY: (202) 418-7172.
\--FCC\--
| en |
converted_docs | 071017 | # Execution
## Background
This chapter addresses program execution. Execution is that part of the
program where NOAA managers, employees and safety staff carry out the
day-to-day safety activities identified in the NOAA Safety Strategy and
funded through resource procedures.
Our discussion will cover four major aspects of safety program
execution: Injury Reporting; Operational Risk Management; Training; and
Outreach.
## Injury Reporting
### Current State
The U.S. Department of Commerce (DOC) *Occupational Safety and Health
Manual* (March 2000), provides policies, procedures, and
responsibilities for incident reporting, investigation and record
keeping. Each employee is responsible for reporting accidents to their
supervisor. Each supervisor is responsible for submitting Commerce
Department form number 137 (CD-137), *Report of Accident/Incident*, to
the appropriate Administrative Support Center (ASC) safety
representative. The ASC representative completes the Occupational Safety
and Health Association (OSHA) form number 200, *Log of Federal
Occupational Injuries and Illnesses*.
The DOC *Occupational Safety and Health Manual* also provides reporting
procedures and responsibilities for completion and submission of
Department of Labor forms CA-1, *Federal Employee's Notice of Traumatic
Injury and Claim for Continuation of Pay/Compensation*, and CA-2,
*Federal Employee's Notice of Occupational Disease and Claim for
Compensation*. The employee completes their request for compensation,
and forwards the form to their supervisor. The supervisor completes
their section of the form within 10 working days, and then forwards the
form directly to the DOC contractor managing the Federal Employees
Compensation Act (FECA) program for DOC.
Approximately 500 NOAA operating locations report injuries, as follows:
- Injuries with medical bills. Injured employees and their supervisors
send CA-1 and CA-2 compensation claims to Contract Claims Services,
Incorporated, a DOC contractor in Irving, TX, for claims processing:
```{=html}
<!-- -->
```
- Approximately half of claims forms are currently being copied and
sent to the Regional Safety Manager (RSM) to notify the RSM of the
injury. RSM's use the claim forms to count injuries and calculate
injury rates by line office.
- DOC sends monthly copies of CA-1 and CA-2 claims forms to the ECHSSO
Safety Division Chief, who faxes copies to the RSM's. The Safety
Division Chief also faxes copies of claims forms for National Marine
Fisheries Service (NMFS) employee injuries to the NMFS safety
manager to honor a request from the NMFS safety manager.
```{=html}
<!-- -->
```
- Supervisors of injured employees send CD Form 137 to RSM's to report
accidents. CD 137s are required for injuries and for accidents and
near-misses.
- The Lost Time Injury (LTI) rate from the Safety Information
Reporting System (SIRS) is used:
```{=html}
<!-- -->
```
- RSM's enter OSHA 200 log type data into a SIRS spreadsheet, and
e-mail an electronic copy monthly to the ECHSSO Safety Division
Chief for collation into a master SIRS report for NOAA.
- The ECHSSO Safety Division Chief sends the reports to the line
office safety managers.
Line offices have identified injury and accident reporting
inconsistencies (e.g., what is reported and to whom it is reported, and
the manner and timeliness of reporting). The forms currently used to
report accidents and injuries serve different purposes for different
offices. DOC and NOAA safety offices report that this, as well as recent
changes in reporting submission guidance, may be the sources of the
inconsistency.
Some line offices have recognized and developed procedures to resolve
the reporting inconsistencies within their line office, including the
following:
- The Marine Operations Center has drafted an internal instruction for
routing shipboard and marine center accident reports. The Marine
Operations Center is evaluating the possibility of using vendor
software to automate the injury reporting process.
- NOAA Fisheries has implemented a reporting process that augments the
DOC reporting requirement. At Fisheries, each injured employee's
supervisor sends a detailed e-mail regarding every mishap within 24
hours of occurrence. The email notifies the Deputy Assistant
Administrator for Operations and leadership throughout NOAA
Fisheries. Upon notification of the mishap, all leadership levels
within NOAA Fisheries take appropriate corrective action.
### Desired State
Supervisors report accidents rapidly throughout the supervisory chain of
command, with information available for review by the supporting line
office safety staff. This timely reporting provides responsible managers
information they need to take timely corrective action, and line office
safety staff to provide advice to their managers in accident
investigations and hazard abatement options. Accident information is
available to all supervisory levels faster than the compensation claim
information, and meets time requirements of 29 CFR 1960 for notifying
OSHA of fatalities and hospitalizations within 8 hours. Regional Safety
Managers have access to accident information for them to fulfill their
roles in providing technical support to NOAA locations in their
geographic region.
#### Defense Logistics Agency
Defense Logistics Agency has developed and implemented their Safety and
Health Information Reporting System (SHIRS), which has been in operation
for several years. SHIRS is a robust database designed to report and
monitor mishaps and their associated costs throughout DLA. Safety staff
record in SHIRS those accidents reported to them by supervisors. As a
check on supervisor accident reports, SHIRS automatically receives
injury compensation claim data from the DoD Civilian Personnel
Management System (CPMS)/Department of Labor Workers Compensation
Office, and matches injury claims against the accident reports. Injury
claims without an accident report are referred to the safety manager and
workplace supervisor for investigation and reporting in SHIRS. SHIRS
currently operates using a client-server software system. A fully
web-enabled version is being considered.
#### National Aeronautics and Space Administration
NASA has a mature injury reporting process that has been in place for
many years. Currently, this automated process is being modified to a
web-based platform. Safety and health professionals crosscheck the
mishaps reported in this in-house Incident Reporting Information System
(IRIS) with activity reported in the workers compensation claims
process.
#### National Institute of Science and Technology
The National Institute for Standards and Technology (NIST), as an agency
in the Department of Commerce (DOC) with NOAA, uses DOC procedures for
injury compensation claims. DOC has hired a contractor to manage all
workers compensation claims from all DOC organizations, including those
originating at NIST and NOAA. DOC receives the claims directly from the
contractor claims processor, and relies on these claims to monitor DOC
accident rates. Unfortunately, this claims process has not generated
accurate information for NIST or for NOAA. The NIST Occupational Health
and Safety Directorate (OHSD) Director has discovered problems ranging
from underreporting of accidents to claims assigned to the wrong
organization. The NIST OHSD Director is instituting a major initiative
to increase reporting and improve understanding of the sources of
accidents.
NIST is asking injured employees to report first to the NIST Health Unit
before seeking medical care from their personal health care provider.
The Health Unit has an on-site emergency medical technician and
ambulance for transporting employees to a local hospital for more
extensive care when needed. When employees report to the Health Unit,
they fill out a workers compensation claim form and a CD-137. The Health
Unit sends a copy of the CD-137 to the injured employee's supervisor and
to the Safety Office to collect additional information on the accident.
For employees not using the Health Unit, NIST also provides a copy of
the workers compensation claim forms and CD-137 on the NIST intranet web
site. As a quality control check, the Safety Office reviews all workers
compensation claims provided by DOC to make sure the Safety Office has
accident reports for all injuries. OHSD summarizes the accident data and
sends the Operating Unit Directors monthly reports of injuries.
The OHSD Director feels that the new process with employees reporting to
the Health Unit first is improving injury reporting. Since instituting
the new procedures, the NIST accident rate increased in Fiscal Year (FY)
2003. The OHSD Director is expecting the accident rates to decrease in
FY 2004 as the improved accident reporting provides information to
prevent accidents.
In addition to this traditional accident tracking and analysis by OHSD,
the supervisory chain performs direct verbal notification of accidents
from the supervisor to the line manager to the Operating Unit Director
and to the NIST Director and Public Relations Office.
### Recommendations
- Issue policy requiring employees and supervisors report accidents
within eight working hours to the management level responsible for
performing accident investigations.
- Issue accident investigation policy identifying levels and oversight
for accident review.
- Establish trained mishap investigation teams.
- Conduct NEC reviews of serious mishaps (i.e., a mishap resulting in
a fatality, three or more hospitalizations, permanent disability,
five or more lost work days, or high potential for multiple
injuries).
- NOAA develop or purchase a web-based accident reporting system to
support accident reporting to line managers and supporting safety
staff.
## Operational Risk Management
### Current State
Operational risk management (ORM) is the process whereby line managers
manage safety risks for their operations using the following steps:
- Identify safety hazards in work operations and locations.
- Assess risk of accidents from these hazards.
- Identify potential corrective actions, including cost of
implementing expected effectiveness and controlling risk and the
risk remaining after implementation.
- Select corrective actions to be implemented, and the accompanying
residual risk, at the appropriate level of authority.
- Implement corrective actions.
- Evaluate corrective actions for their effectiveness.
There is evidence of ORM principles being applied at multiple locations
within NOAA. However, application of ORM is inconsistent. NOAA Marine
and Aviation Operations (NMAO), National Weather Service (NWS) and
National Marine Fisheries Service (NMFS) have an existing approach
toward implementing ORM principles within their operations and tasks.
Other line offices rely on job hazard analyses (JHAs) as a method to
identify hazards. JHAs are also applied inconsistently throughout NOAA.
### Desired State
NOAA institutionalizes the principles of Operational Risk Management
(ORM) throughout the organization. ORM will be a decision making tool
used by people at all levels to increase operational effectiveness by
anticipating hazards and reducing the potential for loss, thereby
increasing the probability of a successful operation or task. The
benefits of applying the ORM process will reduce mishaps, lower injury
and property damage costs, provide for effective use of resources, and
improve training realism and effectiveness.
#### Navy and Marine Corps Operational Risk Management
Military commanders have a fundamental responsibility to safeguard
highly valued personnel and material resources, and to accept only the
minimal level of risk necessary to accomplish an assigned mission.
Historically, a greater percentage of losses during combat operations
was caused by mishaps than by enemy fire.
Since 1991, ORM, applied both in day-to-day operations and during crisis
periods, has produced dramatic results in reducing these losses. All
naval missions, as well as daily routines, involve risk. Every
operation, both on- and off-duty, requires some degree of decision
making that includes risk assessment and risk management. The naval
vision is to develop an environment where every leader, sailor, marine
and civilian is trained and motivated to personally manage risk in
everything they do, thereby completing all operations with minimum risk.
ORM is a decision making process that enhances operational capability.
ORM is a method for identifying hazards, assessing risks and
implementing controls to reduce the risk associated with any operation.
Implementation of ORM in the Department of the Navy will be accomplished
as follows:
- ORM will be included in the orientation and training of all military
personnel. The level of training will be commensurate with rank,
experience, and leadership position.
- ORM lessons learned will be submitted to the Chief of Naval
Operations and/or Commandant of the Marine Corps for inclusion in
ORM databases.
- The ORM process will be integrated into all levels of a command.
The Navy and Marine Corps make it clear that the leader directly
responsible for the mission makes ORM decisions. Prudence, experience,
judgment, intuition and situational awareness are critical elements in
making effective risk management decisions. When the leader responsible
for executing the mission determines that the risk associated with that
mission cannot be controlled at their level, or goes beyond the
commander's stated intent, they shall elevate the decision through their
chain of command.
The ORM concept
- is a decision making tool used by people at all levels to increase
operational effectiveness by anticipating hazards and reducing the
potential for loss, thereby increasing the probability of a
successful mission;
- increases the ability to make informed decisions by providing the
best baseline of knowledge and experience available; and
- minimizes risks to acceptable levels, commensurate with mission
accomplishment. The amount of risk taken varies, depending on the
mission, but the process is the same. Applying the ORM process
reduces mishaps, lowers costs, and results in a more efficient use
of resources.
ORM incorporates the following four principles:
- Accept risk when benefits outweigh the cost.
- Accept no unnecessary risk.
- Anticipate and manage risk by planning.
- Make risk decisions at the right level.
### Recommendations
Establish an ORM Process Improvement Team
Develop an ORM chapter as part of the NOAA Safety Manual, which includes
roles and responsibilities and an overall implementation plan.
Develop curricula and incorporate ORM policy and instruction in each
level of leadership training (senior-management, mid-level management,
first-line supervisors and employee levels).
Perform an ORM policy gap analysis of all written NOAA and line office
policies and procedures.
## Training
### Current State
#### Department of Commerce Requirements
Department of Commerce Safety Manual, Chapter 6, contains NOAA safety
training policy. Table 6-1 of that Manual provides the recommended
minimum safety training for job categories (top management, supervisory,
non-supervisory, employee representatives, collateral duty
representatives, and safety professionals).
DOC has a strong, comprehensive training policy. It specifically states
"top management personnel shall receive OSH \[occupational safety and
health\] training to enable them to actively and effectively support OSH
programs in their specific areas of responsibility." In addition to the
coverage of appropriate statutes, regulations, and applicable DOC OSH
standards, management level training shall include the following:
1. An in-depth examination of management's responsibilities that
includes training topics covering analysis of compliance procedures,
the study of current accident and injury reporting procedures, and a
thorough understanding of investigation/inspection procedures;
2. A review of DOC policy on all relevant aspects of the DOC OSH
program at all levels throughout the Department; and
3. A comprehensive examination and analysis of the operating unit
program objectives and goals.
The training goal for managers and supervisors is to enable them to
recognize unsafe/unhealthful working conditions and practices in the
workplace. Training goals also includes developing skills necessary to
manage the OSH program at the work unit level, developing management
skills training to motivate subordinates, and training that results in
integration of occupational safety with job training. Finally, the
supervisor training policy covers training for newly appointed
supervisors.
Specific safety training for non-supervisory personnel includes a
requirement for specialized job safety and health training directed to
the individual's work site with input and direction from the workplace
supervisor. For new employees, the manual lists required training, as
follows:
1. Individual responsibility for safety and health;
2. Employee reporting procedures for hazardous operations/conditions;
3. Awareness of hazards common to the individual's work site, trade,
occupation or tasks; and
4. Departmental and local policy on occupational safety and health.
The DOC Safety Manual also provides detailed training requirements for
Safety and Health Specialists and Collateral Duty Personnel.
#### NOAA-Wide Training
Currently, NOAA does not have a formal training program that follows the
DOC training policy and training requirements. NOAA does not appear to
have a standard way of certifying, recording, and tracking training that
has been conducted and completed. While the NOAA ECS Training Team
establishes budget priorities for training, the Training Team did not
meet in FY2003 because there was no ECS budget for training. NOAA NFA is
currently providing comprehensive safety training to supervisors on
their roles and responsibilities through either DuPont training (funded
by the line offices) or NOAA Stop Taking Avoidable Risks (STAR) (funded
by NFA). These programs include safety behavior, injury reporting, and
all other supervisor functions. NOAA NFA has initiated electronic safety
training for all employees. These programs have been accepted and well
supported.
#### Line Office Training
Each line office has implemented a safety training program, but the
degree of implementation varies between line offices. The line office
training efforts are described in detail in the line office reports
provided as appendices to this report.
NMAO provides its employees with additional job-related safety training.
For example, all NOAA Corps Officers receive pre-assignment training
that prepares them for NOAA ship and aircraft positions, NOAA shipboard
personnel receive training based on established International Convention
on Standards of Training, Certification, and Watchkeeping for Seafarers
(STCW) requirements, and NOAA divers receive extensive training. Fleet
inspectors attend U.S. Coast Guard training in ship inspection and
shipboard safety standards. Aircraft maintenance personnel are trained
to meet FAA and related requirements. Dive program and small boat
program managers are fully trained and conversant in their areas of
expertise.
NWS and NMAO each have electronic training tracking systems. NMAO is
investigating and implementing improvements in certification, record
keeping, and tracking of personnel being trained. A manual record
keeping system is currently in place at the Marine Operations Center
(MOC) until an automated system can be implemented to meet Integrated
Safety Management (ISM) requirements.
#### Professional Staff Training
NOAA has not established standard training requirements for its safety
professionals. Some, but not all, of the collateral duty safety
representatives have the 40-hour OSHA 600 Collateral Duty Safety
training course.
### Desired State
Every job has been evaluated using a job hazard analysis to identify
changes in the process and employee training requirements for unabated
hazards. Employees have received the training per the requirements. The
safety professionals assist managers, supervisors and employees in
completing the Job Hazard Analyses. Managers and supervisors know and
understand the hazards of each task. Managers, supervisors, and
employees receive web-based safety training (i.e., e-learning).
There is a training tracking system in place. Training information is
electronically recorded into a database. The database reminds managers,
supervisors, and employees about periodic training requirements.
Managers/supervisors/employees evaluate the adequacy of their training.
A training team uses these evaluations to improve each training course.
All new employees receive safety orientation training. All new
collateral duty safety representatives have received the OSHA 600
collateral duty safety class.
Safety professionals obtain training and maintain their professional
accreditation (i.e. CSP, CIH, PE). Safety professionals receive at least
one 40 hour advanced course and attend one safety conference per year.
#### National Institute of Science and Technology
Training---All employees and associates receive training in the skills
required to understand and comply with all safety policies and
requirements applicable to their daily activities.
- NIST employees and associates (including students) receive training
in NIST safety policies, practices, and procedures (routine and
emergency), with additional training for new employees and
associates.
- NIST Safety Council recommends a suite of suitable training
materials appropriate for different work environments.
- NIST ensures that all students and associates receive appropriate
supervision in safety procedures.
- NIST developed incident investigation procedures and trains
supervisors in their use.
The NIST Safety Office recognizes the difficulty of providing new
employees training in safe work procedures. They currently provide a
5-minute introduction to safety during new employee training and provide
supervisors with a standard form to train new employees.
Additionally, NIST provides task-specific safety training to employees,
and maintain a matrix of training completed for each employee. The
Safety Office is considering using Training and Education in the 21st
Century, Inc., to provide employees task specific safety training.
OHSD has plans to complete accident investigation training for managers
in the supervisory chain from Operating Unit Directors to Division
Chiefs. After 2004, the Safety Office plans to train supervisors
subordinate to Division Chiefs. The Chair of the Safety Council
introduces each accident investigation training class to demonstrate
accident investigations are a management responsibility, not a safety
staff task.
NIST senior management attended the 2-day DuPont Management Leadership
Course. The DuPont Safety Director provided the introductory
presentation. Attendees included the NIST Director, Operating Unit
directors and deputy directors, and Division chiefs (typically GS-15
level). NIST managers took three field trips to the DuPont Research
Facility and met with DuPont Senior Management. These trips gave NIST
managers insight into how safety is integrated into the daily operations
for a major research operation similar to NIST. After the field trips,
NIST managers identified best practices NIST needed to follow to instill
a safety culture into NIST operations. DuPont benchmarked the Chemical
Science & Technology Laboratory and the Electronics and Electrical
Engineering Laboratory and found the need to increase the safety culture
in these operations.
#### National Aeronautics and Space Administration
NASA provides an exhaustive array of safety training. It includes
instructor-based training at central locations, instructor visits to
Centers, and on-line courses at its "Site for Online Learning And
Resources"(SOLAR) at
https://solar.msfc.nasa.gov:443/solar/delivery/public/html/newindex.htm.
#### U.S. Postal Service
USPS established a Safety Training Working Group in FY00 to evaluate the
current state of safety training and to recommend a course of action to
solve USPS training issues. One result was to focus the workgroup's
efforts on the most critical OSHA programs, which they achieved by
developing a training matrix.
The training matrix identified critical OSHA programs and corresponding
OSHA/USPS training requirements. The matrix breaks training requirements
into three groups: Customer Services; Vehicle Maintenance Facilities;
and Plants, Bulk Mail Centers and Air Mail Centers. Designated
assignments, job classifications and employee potential for exposure
then serve to filter specific training needs.
If the safety training is not available from USPS, the matrix contains
guidelines to develop local training or to evaluate vendor training that
meets the OSHA required elements. USPS distributed the matrices and
advised the USPS Area Directors to develop a plan for identifying and
addressing gaps in OSHA and postal required training.
USPS identified the benefits of this approach to include: management
commitment to safety training; completing required training; reducing
injuries and illnesses; reducing training costs; and increasing the use
of existing training resources.
As the next step, the USPS Safety Training Working Group developed
"InfoPaks" for all Facility Safety Coordinator (their collateral duty
safety personnel) and made them available on the USPS Intranet. Of
significance is the fact that the American Society for Training and
Development recognized the USPS with an "Excellence in Practice"
citation for the Facility Safety Coordinator Training Course, as
follows: "This self-study course targets 35,000 postal managers who are
assigned collateral safety duties. The product is available in both
web-based and hard copy formats. ASTD is the world's premiere
professional association in the field of workplace learning and
performance."
Currently, USPS is evaluating a prototype "Safety and Health Training
Decision Tree (SOHDT)" web based application that will enable managers
and supervisors to plan employee safety training requirements based on
their assigned tasks. Managers and supervisors will use the SOHDT to
identify employees that require training and select courses to meet OSHA
and Postal Service safety and health training requirements.
Each USPS Area/District/Plant safety office will answer a series of
initial profile questions. By answering the profile questions,
experienced safety professionals identify basic safety and occupational
health (SOH) training requirements for each USPS plant, facility or
installation. For example, the first profile covers asbestos. The first
profile question is "Does this facility have asbestos?" A safety
specialist answers the asbestos profile question. If the answer is
'Yes,' asbestos training is included on the list of training subjects
that managers and supervisors at that facility must address. If the
answer to the profile question is 'No,' asbestos is eliminated from the
SOH training requirements at that facility.
Upon completion of the profile questions, each identified manager and
supervisor with web access can view his/her facility-specific list of
SOH training requirements.
Accessing the list leads each manager/supervisor through a sequence of
queries and data entry forms, for each of the applicable,
facility-specific, OSHA training subjects. The queries and data entry
forms enable managers and supervisors to develop and update an annual
SOH training plan for each of his/her employees.
The annual training plan will roll up to various levels (e.g., work
unit, department, plant/facility, district and area) for review,
analysis and approval. Managers/supervisors execute their training plan,
monitor completion rates, and change or modify the training plan, as
necessary, throughout the year.
During the fiscal year, HQ USPS plans to visit each Area Office to
review completion of objectives and training targets and reports. At the
end of the year, HQ USPS and the Areas/District SOH Offices review
annual training plans for completion of objectives, and compare these
objectives against accident rates and other outcome measures to identify
potential successes in affecting accident rates. HQ USPS and the
Areas/District SOH Offices use the outcomes to update the SOHDT, the
USPS Safety and Health Program Evaluation Guide and facility action
plans and to choose objectives and metrics for the coming fiscal year.
### Recommendations
- Develop and publish safety training policy and procedures for all
employees in the NOAA Safety Manual.
- Establish training policy for Safety professionals to attend annual
training to maintain their technical skills and certifications (i.e.
CSP, PE, CIH).
- Implement a Job Hazard Analysis (JHA) program to evaluate each job
and identify job-specific training needs and hazards
- Develop an automated training tracking system for NOAA-wide
application, including a review of NWS, NMAO, and commercial
training tracking systems.
- Develop and Implement a new employee safety orientation training and
checklist for supervisors to use for new employees or when they
change positions.
- Analyze training options, including the course provider, course
names and content, cost, and the effectiveness of the training.
- Advertise the availability of (and provide access to) online safety
training on the NOAA and line office homepages.
- Evaluate training; recommend training programs; and purchase
training products and training courses for evaluation and
reporting).
- Host periodic safety workshops for the NOAA safety staff.
- Host Annual safety conference for the NOAA safety community.
- Implement ergonomics awareness training
- Provide STCW training for shipboard employees to meet new and
current federal and international requirements.
## Industrial Hygiene and Medical Surveillance
### Current State
NOAA conducts few industrial hygiene surveys to assure both management
and employees that unhealthful exposures are not occurring in the work
environment. The ability to conduct industrial hygiene surveys is
limited by the insufficient number of industrial hygiene personnel,
sampling equipment, travel funds and the costs of laboratory analysis.
A medical surveillance program is a process that follows the medical
condition of employees, over a period of time, who have been exposed to
significant on-the-job health hazards. It is also required for employees
who are required to wear respiratory protection or hearing protection.
NOAA does not have a consistent medical surveillance program across all
line offices to monitor health effects in exposed employees. As a
notable exception, NMAO provides medical surveillance supported by
extensive written protocols.
### Desired State
NOAA conducts industrial hygiene surveys consistent with "Best in Class"
criteria. Surveys are completed annually for high risk operations (e.g.,
research facilities, laboratories), biannually for medium risk
operations, and as needed for low risk operations.
NOAA performs targeted medical surveillance for employees to monitor for
the health effects of workplace exposures, and to ensure they are
qualified to perform assigned duties (e.g., wearing respirators,
performing fire fighting).
### Recommendations
- Develop an inventory of required industrial hygiene surveys by
location and frequency
- Conduct Industrial Hygiene surveys of work spaces identified by the
line office safety managers
- Perform medical surveillance as determined by the industrial hygiene
surveys.
## Outreach
### Current State
#### Professional Development
The DOC Manual, Chapter 4.02, states clear support for safety staff
participation in the Federal Advisory Council on Occupational Safety and
Health (FACOSH) and Field Federal Safety and Health Councils sponsored
by OSHA. Some of the NOAA safety staff participate in these and other
professional organizations.
NOAA schedules environment and safety meetings and conferences to
provide forums for NOAA Environmental Compliance and Safety (ECS)
professionals the opportunity to exchange information and plan
activities. One of these forums is the NOAA annual ECS Conference.
Unfortunately, due to funding constraints in FY03, NOAA cancelled this
conference.
#### Employee Information
The Department of Commerce and NOAA have safety websites. However, the
information posted on the websites requires more consistency. For
example, the website could provide consistent reporting to management
and employees of monthly, quarterly, and annual injury and illness rates
for NOAA and each line office.
Among the line offices, NMAO continues to evaluate other means to
improve prevention and outreach. NMAO periodically publishes and
distributes a safety newsletter to all NMAO employees. The newsletter
serves as a reminder to keep safety foremost in employees' minds and
actions and provides a means to disseminate safety information on topics
pertinent to ship and aircraft operations. It provides a means to report
on the status of safety-related projects, accident statistics, and other
areas of concern.
NWS conducts monthly conference calls with Regional and Operating Unit
Environmental/Safety Coordinators to discuss various issues related to
implementation of the safety program. The NWS Safety Officer
communicates with Environmental/Safety Coordinators via e-mails on a
daily basis. Other examples of NWS outreach include,
- NWS designed a safety awareness poster that is in stock at the
National Logistics Support Center.
- NWS has an environmental/safety web page that has NWS safety and
health policy, NWS safety manual, legal memoranda, and NOAA
information available for downloading.
NOAA outreach efforts also include Regional Safety Managers (RSM) who
conduct inspections and evaluations, and provide training and follow up
support, as resources permit. The following examples offer opportunities
to improve RSM outreach efforts.
- RSM's receive requests for support and funding directly from the
line offices. In those instances, if the line office does not have
funding, the RSM safety advisory support is further limited.
- Field activity visits indicate that many field facilities do not
post the OSHA poster and very few offices post additional safety
posters in their workplace. Furthermore, was common to find that
employees did not know their safety representatives.
Currently, the DOC Safety Manual does not address safety
awards/recognition. NOAA's safety awards and recognition program is
beginning.
### Desired State
NOAA's outreach efforts result in the following:
- Managers and employees know whom they can contact for assistance and
information.
- Managers and employees feel that they play a vital role in NOAA's
Safety Program.
- Employees are aware of the safety status of their work environment
and the steps that are being taken to ensure safe conditions.
- A fully developed NOAA safety awards and recognition program exists.
- Line offices and multi-agency facilities work together in a
coordinated fashion.
- Data analysis becomes the launching pad for numerous safety
initiatives.
- Facility employees interact with the communities surrounding them
and work with local safety groups/agencies.
- NOAA urges safety professionals and safety officials to attend
safety conferences.
- NOAA uses websites to serve as on-line safety offices, which provide
substantial safety related content.
#### NASA
NASA Headquarters and the Centers extensively use websites to serve as
virtual on-line safety offices with substantial safety related content.
NASA is currently putting in a new on-line system for incident reporting
and corrective actions.
#### NIST
The NIST intranet main page provides a direct link to a safety web page
maintained by OHSD. OHSD posts safety messages, training materials, and
a summary of recordable injuries for all NIST employees to view.
The NIST intranet main page provides a direct link to a "Staff Forum"
where NIST employees can provide feedback, suggestions, or other
comments on NIST operations, including reporting hazards and improving
safety. Employees can submit comments anonymously or identify themselves
for direct follow-up. The NIST "Program Office" is the executive-level
office that monitors employee submissions and refers comments to staff
offices to provide responses. The Program Office sends employee comments
about safety, including reported safety hazards, to OHSD for review and
response. The Program Office publishes staff office responses on the web
site for the viewing of all employees.
NIST communicates their safety vision and expectations clearly and
succinctly: "Safety will be a visible part of all activities at NIST.
All persons are expected to report all incidents, accidents, and unsafe
conditions. NIST management will communicate all accidents, near misses,
and root causes to everyone at NIST."
NIST also makes it clear that they recognize and reward safe behavior,
while noting "Unsafe behavior will be corrected promptly." The NIST
Administrative Manual is undergoing a revision that will increase
consequences for unsafe conduct and behavior.
### Recommendations
Enhance the ECS website as a one-stop location for employee safety
information. Publicize its existence.
Create an electronic safety suggestion box on the web.
Establish safety councils/committees at all facilities or have
membership on an established council/committee where NOAA is not the
responsible official.
Review and update the NOAA safety awards/recognition program and
investigate other safety awards offered by outside agencies.
Host NOAA safety days for NOAA employees
Encourage NOAA Safety professionals to participate on safety committees
and workgroups outside NOAA
Publish a NOAA Environmental, Health, Safety & Emergency Preparedness
Report
| en |
all-txt-docs | 175455 | SEC-303 -- ASSISTANCE FOR FIRST-TIME HOMEBUYERS.
(a) In General.-The Trust shall provide assistance payments for
first-time homebuyers (including homebuyers buying shares in limited
equity cooperatives) in the following manners:
(1) Interest rate buydowns.-Assistance payments so that the rate of
interest payable on the mortgages by the homebuyers does not exceed 6
percent.
(2) Downpayment assistance.-Assistance payments to provide amounts for
downpayments (including closing costs and other costs payable at the
time of closing) on mortgages for such homebuyers.
(b) Eligibility Requirements.-Assistance payments under this subtitle
may be made only to homebuyers and for mortgages meeting the following
requirements:
(1) First-time homebuyer.-The homebuyer is an individual who-
(A) (and whose spouse) has had no ownership in a principal residence
during the 3-year period ending on the date of purchase of the property
with respect to which assistance payments are made under this subtitle;
(B) is a displaced homemaker who, except for owning a home with his or
her spouse or residing in a home owned by the spouse, meets the
requirements of subparagraph (A); or
(C) is a single parent who, except for owning a home with his or her
spouse or residing in a home owned by the spouse while married, meets
the requirements of subparagraph (A).
(2) Maximum income of homebuyer.-The aggregate annual income of the
homebuyer and the members of the family of the homebuyer residing with
the homebuyer, for the 12-month period preceding the date of the
application of the homebuyer for assistance under this subtitle, does
not exceed-
(A) 95 percent of the median income for a family of 4 persons (adjusted
by family size) in the applicable metropolitan statistical area (or such
other area that the Board of Directors determines for areas outside of
metropolitan statistical areas); or
(B) 115 percent of such median income (adjusted by family size) in the
case of an area that is subject to a high cost area mortgage limit under
title II of the National Housing Act.
The Board of Directors shall provide for certification of such income
for purposes of initial eligibility for assistance payments under this
subtitle and shall provide for recertification of homebuyers (and
families of homebuyers) so assisted not less than every 2 years
thereafter.
(3) Certification.-The homebuyer (and spouse, where applicable) shall
certify that the homebuyer has made a good faith effort to obtain a
market rate mortgage and has been denied because the annual income of
the homebuyer and the members of the family of the homebuyer residing
with the homebuyer is insufficient.
(4) Principal residence.-The property securing the mortgage is a
single-family residence or unit in a cooperative and is the principal
residence of the homebuyer.
(5) Maximum mortgage amount.-The principal obligation of the mortgage
does not exceed the principal amount that could be insured with respect
to the property under the National Housing Act.
(6) Maximum interest rate.-The interest payable on the mortgage is
established at a fixed rate that does not exceed a maximum rate of
interest established by the Trust taking into consideration prevailing
interest rates on similar mortgages.
(7) Responsible mortgagee.-The mortgage has been made to, and is held
by, a mortgagee that is federally insured or that is otherwise approved
by the Trust as responsible and able to service the mortgage properly.
(8) Minimum downpayment.-For a first-time homebuyer to receive
downpayment assistance under subsection (a)(2), the homebuyer shall have
paid not less than 1 percent of the cost of acquisition of the property
(excluding any mortgage insurance premium paid at the time the mortgage
is insured), as such cost is estimated by the Board of Directors.
(c) Terms of Assistance.-
(1) Security.-Assistance payments under this subtitle shall be secured
by a lien on the property involved. The lien shall be subordinate to all
mortgages existing on the property on the date on which the first
assistance payment is made.
(2) Repayment upon sale.-Assistance payments under this subtitle shall
be repayable from the net proceeds of the sale, without interest, upon
the sale of the property for which the assistance payments are made. If
the sale results in no net proceeds or the net proceeds are insufficient
to repay the amount of the assistance payments in full, the Board of
Directors shall release the lien to the extent that the debt secured by
the lien remains unpaid.
(3) Repayment upon increased income.-If the aggregate annual income of
the homebuyer (and family of the homebuyer) assisted under this subtitle
exceeds the applicable maximum income allowable under subsection (b)(2)
for any 2-year period after such assistance is provided, the Board of
Directors may provide for the repayment, on a monthly basis, of all or
a portion of such assistance payments, based on the amount of assistance
provided and the income of the homebuyer (and family of the homebuyer).
(4) Repayment if property ceases to be principal residence.-If the
property for which assistance payments are made ceases to be the
principal residence of the first-time homebuyer (or the family of the
homebuyer), the Board of Directors may provide for the repayment of all
or a portion of the assistance payments.
(5) Available assistance.-The Trust may make assistance payments under
paragraphs (1) and (2) of subsection (a) with respect to a single
mortgage of an eligible homebuyer.
(d) Allocation Formula.-Amounts available in any fiscal year for
assistance under this subtitle shall be allocated for homebuyers in each
State on the basis of the need of eligible first-time homebuyers in each
State for such assistance in comparison with the need of eligible
first-time homebuyers for such assistance among all States.
| en |
markdown | 541370 | # Presentation: 541370
## Geographic Analysis and Exploration in the South Central United States
- Mark P. Widrlechner
- USDA-ARS
- North Central Regional Plant Introduction Station
- Ames, IA
## Acknowledgments
- ISU Media Graphics (Rex Heer) for moisture balance map
- Spatial Climate Analysis Service - Oregon State University for precipitation maps
- Cris Nass and Robert Stebbins for help with scanning
**Notes:**
Thank Galen for the invitation
## Outline of Presentation
- Overview
- Applying geographic factors to the South Central US
- Plants and potential sites
**Notes:**
Here’s an outline of the topics I’d like to cover today.
## Overview
- Location-specific factors influencing the adaptation of woody plants in the Midwest
- Photoperiod regimen
- Winter injury
- Moisture balance
- Soil type
**Notes:**
First, we’ll begin with an overview covering the following points (go to list)...
## Photoperiod Regimen
- Key factor to signal growth and the cessation of growth
- Directly correlated with latitude
- Plants evolve in response to the interaction of photoperiod and correlated events
## Winter Injury
- Three main aspects
- Timing of hardening
- Mid-winter low temperature survival
- Timing of dehardening
- Also, interaction with moisture conditions, especially for evergreens
- USDA Hardiness Zones (average annual minimum temperature) are an easily obtainable surrogate (especially for regions resembling the target environment)
## Moisture Balance
- Perhaps as important as winter hardiness (especially in low maintenance situations)
- Widrlechner et al. (1992) J. Environ. Hort. 10: 192-198 and J. Environ. Hort. 16: 27-32.
- Can visualize based on the Moisture Index of Mather and Yoshioka: Im = 100((mean annual precipitation/potential evapotranspiration)-1)
- From Widrlechner (1999) "A Zone Map for Mean Annual Moisture Balance in the North Central United States," Landscape Plant News 10(2): 10-14.
**Notes:**
Describe how this map was determined: January mean temperatures, moisture balance, which reflects the annual balance between total precipitation and potential evapotranspiration, and latitude, which is important for photoperiod regimen
## Valuable Soil Types
- pH (neutral to alkaline)
- High Ca or Na content
- Relatively poor drainage
- Thin (for drought tolerance)
**Notes:**
Probably not much need to explain
## Applying this Approach to the South Central United States
- Latitude (35 to 40° North)
- USDA Hardiness Zones (6a and b)
## Resulting Region
- Southern Kansas and northern Oklahoma on the west
- Eastern Kentucky and Tennessee on the east
## Adding the Moisture Balance Criterion
- Areas in the western two-thirds of Kansas and Oklahoma have negative moisture balances (too dry)
- Kentucky and Tennessee have high positive moisture balances (too wet)
- Parts of eastern Kansas and Oklahoma, Missouri, northwestern Arkansas, and southern Illinois have appropriate moisture balances
- (Im between 0 and 40)
## Working with the Moisture Balance Criterion
- In areas that are too dry, target extremely wet sites along rivers, lakes, springs and significant north-facing slopes
- In areas that are too wet, target limestone barrens and other drought-prone sites
- In areas that are a good match, one can be broader in collecting
## Too dry
**Too dry**
**I****m**** < 0**
**0 to 20**
**20 to 40**
**Too wet I****m**** > 40**
**Notes:**
White area is Zone 6. To west of red line is too dry; to south and east of blue line is too wet. You may not want to exclude sites in Zone 5b, but there will probably be a loss in target-species diversity without appreciable species gains.
## Can we find the “right” soils in this region?
- Neutral to alkaline, calcareous or saline soils
- Thin soils
- Poorly draining soils
## Can we find interesting woody plant populations?
- Plants adapted to appropriate soils
- Species reaching the northwest edge of their native ranges
- Endemic species
- Species with attractive aesthetic characteristics
**Notes:**
The handout with 50 target species goes here. It includes mostly limestone or floodplain species, some reaching the NW edge of range, endemic and aesthetically attractive species (see list)
## Oklahoma Soils
- Neutral to alkaline, calcareous soils
- Apperson, Catoosa, Foraker, Grainola, Labette, Lenapah, Mayes, Newtonia, Summit (mostly silty clay loams)
- Thin soils
- Shidler, Sogn, Talpa (mixed with limestone)
- Poorly drained soils
- Choska, Latanier, Lela, Miller, Osage, Wynona (clays)
**Notes:**
Avoid cherty limestone and sandstone
## Oklahoma Plants
- John E. Williams (1973) Atlas of the woody plants of Oklahoma (QK 155 W55 1973)
- Forrest L. Johnson and Bruce W. Hoagland (1999) Catalog of the Woody Plants of Oklahoma http://www.biosurvey.ou.edu/shrub/cover.htm
**Notes:**
Call number is in MBG Library
## Arkansas Soils
- Neutral to alkaline, calcareous soils
- Clareson, Mayes, Newtonia, Summit silt loams and silt clays
- Thin and rocky soils
- Arkana, Elsah, Moko, Sogn, Ventris mostly stony silt loams (often with rock outcrops)
- Alluvial soils
- Razort silt loam
**Notes:**
Avoid sandstone and most chert
## Arkansas Plants
- Gary E. Tucker (1976) Guide to the woody flora of Arkansas (QK 153 .T84 1976)
- Arkansas Biodiversity – The Vascular Flora
- http://www.csdl.tamu.edu/FLORA/arkansas/arkfamyy.htm
**Notes:**
Call number is in MBG Library
## Missouri Soils
- Neutral to alkaline, calcareous soils (rocky or thin)
- Blueye, Brussels, Cedargap, Gasconade, Hercules, Knobby, Moko
- Rock outcrops
- Dolomite and other non-cherty limestones
- Poorly drained soils
- Gasconade, Snead
**Notes:**
Lots of chert and sandstone to avoid. Avoid Vaccinium and Rhododendron.
## Missouri Plants
- Julian Steyermark (1963) Flora of Missouri (being revised and updated by George Yatskievych)
## Kansas Soils
- Neutral to alkaline, calcareous soils
- Apperson, Catoosa, Kenoma silt loam
- Thin and rocky soils
- Shidler, Sogn silty and rocky clay loam
- Poorly drained soils
- Clime, Lanton, Osage, Verdigris, Zaar silty loam and silty clay
## Kansas Plants
- H.A. Stephens (1973) Woody Plants of the North Central Plains
- Great Plains Flora Association (1977) Atlas of the Flora of the Great Plains
**Notes:**
Atlas has good maps for Kansas, SW Missouri, and OK, not so good for AR
## Illinois Soils
- Neutral to alkaline, some calcareous soils
- Bold silt loam, La Hogue loam, Hurst, Sable and Virden silty clay loam
- Upland natric (with sodium) soils
- Darmstadt, Grantfork, Huey, and Piasa silt loams and silty clay loams
- Thin soils
- Rare, isolated limestone outcrops in Jackson Co.
- Alluvial soils
- Ambraw, Beaucoup, Birds, Darwin, Dupo, Lawson, McFain, Nameoki, Tice, Titus, Wakeland
## Illinois Plants
- Works by Robert Mohlenbrock
- Series on the Flowering Plants of Illinois
- 2002 edition of the Vascular Flora of Illinois
- Mohlenbrock and Ladd (1978) Distribution of Illinois Vascular Plants
- Mohlenbrock and Voigt (1959) A Flora of Southern Illinois
## Some Potential Target Sites
- OK-KS
- E 1⁄2 of Kay Co., W 1⁄2 of Osage Co., W 1⁄2 of Chautauqua Co., and all of Cowley Co.
- Much of Rogers Co., W Craig Co., E Nowata Co., much of Labette Co., and E Montgomery Co.
- Mayes Co. (W side of Lake Hudson and SW of Locust Grove)
**Notes:**
Based on extent of favorable soils. Light color is OK, gold is KS.
## More Potential Target Sites
- AR-MO
- W edge of Fulton Co., N 1⁄2 of Baxter, Marion, and Boone Cos., SE 1⁄4 of Taney Co., and possibly S 1⁄2 of Ozark Co.
- W 2/3 of Carroll Co., SE 1⁄4 of Barry Co., and small parts of adjacent Benton and Madison Cos.
**Notes:**
Based on extent of favorable soils. Light color is AR, gold is MO.
## More Potential Target Sites
- MO-IL
- Mississippi floodplain from Perry Co. north towards St. Louis and Jackson to Monroe Cos. ( + limestone outcrops in Jackson Co.)
- Lower Kaskaskia River and tributaries
- Natric soils in E 1⁄2 of Madison, Bond, and Clinton Cos. and near Hecker in Randolph and St. Clair Cos.
**Notes:**
Based on extent of favorable soils. Light color is MO, gold is IL.
## And now a few maps...
**Notes:**
Lead into three maps (don’t have any maps prepared for IL-MO part)
**Notes:**
NE OK map
**Notes:**
SE Kansas map
**Notes:**
AR-MO map
**Notes:**
Natural Falls SP, OK, west of Siloam Springs, AK
Photo by Sharon Dragula, April 2000 | en |
converted_docs | 819813 | {width="2.497916666666667in"
height="2.2930555555555556in"}
**INSTRUCTION BOOKLET**
**GENERAL INFORMATION, INSTRUCTIONS, AND**
**DEFINITIONS FOR COMMISSION QUESTIONNAIRES**
**WELDED STAINLESS STEEL PRESSURE PIPE FROM CHINA**
**Investigation Nos. 701-TA-454 and 731-TA-1144 (Final)**
*[Further information]{.underline}.‑‑If you have any questions
concerning the enclosed*
*questionnaire(s) or other matters related to this investigation, you
may contact*
*the following members of the Commission=s staff (Fax 202-205-3205):*
*Elizabeth Haines, investigator (202‑205‑3200; E-mail
elizabeth.haines@USITC.GOV)*
*regarding general questions and trade and related information;*
*Justin Jee, auditor (202‑205‑3186, E-mail justin.jee@USITC.GOV)*
*regarding financial information; and*
*Clark Workman, economist (202‑205‑3248); E-mail
clark.workman@USITC.GOV)*
*regarding pricing, market, and related information.*
**[GENERAL INFORMATION]{.underline}**
***[Background]{.underline} \--***These investigations were instituted
in response to a petition filed on January 30,
2008, by Bristol Metals (Bristol, TN), Felker Brothers Corp.
(Marshfield, WI), Marcegaglia USA
Inc. (Munhall, PA), Outoukumpu Stainless Pipe, Inc. (Schaumburg, IL),
and the United Steel
Workers of America (Pittsburgh, PA). Countervailing and/or antidumping
duties may be assessed
on the subject imports as a result of these investigations if the
Commission makes an affirmative
determination of injury, threat, or material retardation, and if the
U.S. Department of Commerce
makes an affirmative determination of subsidization and/or dumping.
Questionnaires and other information pertinent to these investigations
are available at
<http://www.usitc.gov/trade_remedy/731_ad_701_cvd/investigations/2008/wss_pressure_pipe/finalphase.htm>.
Address all correspondence to the United States International Trade
Commission, Washington, DC 20436. Hearing‑impaired individuals can
obtain information regarding this investigation via the Commission=s TDD
terminal (202‑205‑1810).
***[Due date of questionnaire(s)]{.underline}***.‑‑Return the completed
questionnaire(s) to the United States International Trade Commission by
no later than October 28, 2008. Although the enclosed postpaid envelope
may be used to return the completed questionnaire, use of an overnight
mail service may be necessary to ensure that your response actually
reaches the Commission by October 28, 2008. If you do not use the
enclosed envelope, please make sure the completed questionnaire is sent
to the attention of Elizabeth Haines, Investigator. Return [only
one]{.underline} copy of the completed questionnaire(s), but please keep
a copy for your records so that you can refer to it if the Commission
staff contacts you with any questions during the course of the
investigations.
***[Service of questionnaire response(s)]{.underline}***.\--In the event
that your firm is a party to these investigations, you are required to
serve a copy of the questionnaire(s), once completed, on parties to the
proceeding that are subject to administrative protective order (see 19
CFR \' 207.7). A list of such parties is maintained by the Commission=s
Secretary and may be obtained by calling 202-205-1803. A certificate of
service must accompany the copy of the completed questionnaire(s) you
submit (see 19 CFR \' 207.7).
***[Confidentiality]{.underline}***.\--The commercial and financial data
furnished in response to the enclosed questionnaire(s) that reveal the
individual operations of your firm will be treated as confidential by
the Commission to the extent that such data are not otherwise available
to the public and will not be disclosed except as may be required by law
(see 19 U.S.C. \' 1677f). Such confidential information will not be
published in a manner that will reveal the individual operations of your
firm; however, nonnumerical characterizations of numerical business
proprietary information (such as discussion of trends) will be treated
as confidential business information only at the request of the
submitter for good cause shown.
***[Verification]{.underline}*.‑‑The information submitted in the
enclosed questionnaire(s) is subject to audit and verification by the
Commission. To facilitate possible verification of data, please keep all
your workpapers and supporting documents used in the preparation of the
questionnaire response(s).**
**[GENERAL INFORMATION]{.underline}‑‑*Continued***
***[Release of information]{.underline}***.\--The information provided
by your firm in response to the questionnaire(s), as well as any other
business proprietary information submitted by your firm to the
Commission in connection with the investigations, may become subject to,
and released under, the administrative protective order provisions of
the Tariff Act of 1930 (19 U.S.C. \' 1677f) and section 207.7 of the
Commission=s Rules of Practice and Procedure (19 CFR \' 207.7). This
means that certain lawyers and other authorized individuals may
temporarily be given access to the information for use in connection
with this investigation or other import-injury investigations conducted
by the Commission on the same or similar merchandise; those individuals
would be subject to severe penalties if the information were divulged to
unauthorized individuals.
**[INSTRUCTIONS]{.underline}**
***[Answer all questions]{.underline}***.‑‑Do not leave any question or
section blank unless a questionnaire expressly directs you to skip over
certain questions or sections. If the answer to any question is Anone,@
write Anone.@ **If information is not readily available from your
records in exactly the form requested, furnish carefully prepared
estimates‑‑designated as such by the letter AE@‑‑and explain the basis
of your estimates**. Answers to questions and any necessary comments or
explanations should be supplied in the space provided or on separate
sheets attached to the appropriate page of the questionnaire(s). If your
firm is completing more than one questionnaire in connection with this
investigation (i.e., a producer, importer, and/or purchaser
questionnaire), you need not respond to duplicated questions in the
questionnaires.
***[Consolidate all U.S. establishments]{.underline}***.‑‑Report the
requested data for your establishment(s) located in the United States.
**Firms operating more than one establishment should combine the data
for all establishments into a single report.**
***[Filing instructions]{.underline}***.---Questionnaires may be filed
either in paper form or electronically.
**[INSTRUCTIONS]{.underline}\--*Continued***
**OPTIONS FOR FILING IN PAPER FORM**
**• Overnight mail service**.---Mail to the following address:
**United States International Trade Commission**
**Office of Investigations, Room 615**
**500 E Street SW**
**Washington, DC 20024**
**• Fax**.---Fax to 202.205.3205.
**• U.S. mail**.---Mail to the address above, but use zip code 20436.
*This option is not recommended. U.S. mail sent to government offices
undergoes additional processing to screen for hazardous materials; this
additional processing results in substantial delays in delivery.*
**OPTIONS FOR FILING ELECTRONICALLY**
> This questionnaire is available as a "fillable" form in MS Word format
> on the Commission's website at
> <http://www.usitc.gov/trade_remedy/731_ad_701_cvd/investigations/2008/wss_pressure_pipe/finalphase.htm>.
> ***Please do not attempt to modify the format or permissions of the
> questionnaire document***. You may complete the questionnaire
> electronically, print it out, and submit it in paper form as described
> above, or you may submit it electronically through one of the
> following means:
**• By means of the Commission's Electronic Document Information System
(EDIS)**.---Follow the step-by-step instructions on the next page.
**• Compact disc (CD)**.---Copy your questionnaire onto a CD, include a
signed certification page (page 1) (either in paper form or scanned PDF
copied onto CD), and mail to the address above. *It is strongly
recommended that you use an **overnight mail service**. U.S. mail sent
to government offices undergoes additional processing which not only
results in substantial delays in delivery but may also damage CDs.*
**• E-mail**.---E-mail your questionnaire to the investigator identified
on page 1 of the Instruction Booklet; include a scanned PDF of the
signed certification page (page 1). Type the following in the e-mail
subject line: BPI Questionnaire, INV. NO. 701-454. *Please note that
submitting your questionnaire by e-mail may subject your firm's business
proprietary information to transmission over an unsecure environment and
to possible disclosure. If you choose this option, the Commission warns
you that any risk involving possible disclosure of such information is
assumed by the submitter and not by the Commission.*
Note: If you are a party to the investigation, and service of the
questionnaire is required, such service should be made in paper form.
**[INSTRUCTIONS]{.underline}\--*Continued***
**INSTRUCTIONS FOR FILING VIA EDIS**
**STEP 1: REGISTER AS A NEW USER IN EDIS** (current registered users may
skip this step)
- The authorized official whose name appears under the Certification
at the bottom of page 1 of the questionnaire should be the person
who completes the registration in EDIS
- Go to <https://eofpub.usitc.gov/edis-efile/app>
- Click on [Register]{.underline}
- Read and accept the Terms of Use Agreement
- Complete the EDIS Online User Registration form
- In the **Firm/Organization** field, select **Questionnaire
Respondent**
- Click **Submit Registration**
**STEP 2: ELECTRONICALLY SUBMIT YOUR QUESTIONNAIRE(S) IN EDIS**
- Click on [E-File Documents]{.underline}
- Under **Submitter Information**, type the name of your firm in the
**Filed On Behalf Of** field
- Under **Investigation Information**, click on **Find Investigation**
- For **Investigation Phase**, select **"Final"** and for
**Investigation Number**, type **"701-454"**; Click on **Find
Investigation**
- Click in the circle to the left of the investigation number that
appears, then click on **Select** and confirm by clicking **OK**
- Under **Document Filing Information**---
- For **Document Type**, select **Questionnaire -- Foreign
Producer**, **Questionnaire -- Importer**, **Questionnaire --
Purchaser**, or **Questionnaire -- U.S. Producer**, as
appropriate
- Leave **Document Title** field blank
- Under **Add Document Attachments for Electronic Submission**---
- In the **Attach File** field, click on **Browse**, locate your
MS Word questionnaire file, and double-click the file
- The **Attachment Title** field is optional
- Click on **Attach Files** (note that your file will be listed
below under **Attachments**)
- You must attach a scanned PDF of the signed certification page
(page 1). If you wish to attach any other files, i.e.,
supporting documents, do so at this time (unlike the
questionnaire itself, these additional documents
**[must]{.underline}** be PDFs). **[Only one questionnaire may
be filed at a time]{.underline}**.
- When you have attached all relevant files, click on **Submit
Document w/attachments**. An **EDIS Document Submission
Confirmation** screen will appear. Confirm the information and
click on **Accept Information**. An **EDIS Notice of Receipt of
Electronic Documents** will appear, which completes the process.
If you wish to electronically file another questionnaire, repeat
Step 2.
**[DEFINITIONS]{.underline}**
***[Subject merchandise - welded stainless steel pressure
pipe]{.underline}***.‑‑Circular welded austenitic stainless pressure
pipe not greater than 14 inches in outside diameter. This merchandise
includes, but is not limited to, the American Society for Testing and
Materials (ASTM) A--312 or ASTM A--778 specifications, or comparable
domestic or foreign specifications. ASTM A--358 products are only
included when they are produced to meet ASTM A--312 or ASTM A--778
specifications, or comparable domestic or foreign specifications. The
subject imports are normally classified in subheadings 7306.40.5005,
7306.40.5040, 7306.40.5062, 7306.40.5064, and 7306.40.5085 of the
Harmonized Tariff Schedule of the United States (HTSUS). They may also
enter under HTSUS subheadings 7306.40.1010, 7306.40.1015, 7306.40.5042,
7306.40.5044, 7306.40.5080, and 7306.40.5090.
*"Welded stainless steel pressure pipe" does [not]{.underline} include
welded stainless mechanical tubing, meeting ASTM A--554 or comparable
domestic or foreign specifications; (2) boiler, heat exchanger,
superheater, refining furnace, feedwater heater, and condenser tubing,
meeting ASTM A--249, ASTM A--688 or comparable domestic or foreign
specifications; and (3) specialized tubing, meeting ASTM A--269, ASTM
A--270 or comparable domestic or foreign specifications.*
**Please note: The Commission's questionnaires [do]{.underline} seek
certain information on other forms of welded stainless steel tubular
products:**
***[Nonsubject merchandise - welded stainless steel pressure pipe
exceeding 14 inches in diameter]{.underline}***.‑‑Circular welded
austenitic stainless pressure pipe greater than 14 inches in outside
diameter. This merchandise includes, but is not limited to, the American
Society for Testing and Materials (ASTM) A--312 or ASTM A--778
specifications, or comparable domestic or foreign specifications. ASTM
A--358 products are only included when they are produced to meet ASTM
A--312 or ASTM A--778 specifications, or comparable domestic or foreign
specifications.
***[Nonsubject merchandise - other varieties of welded stainless steel
tubular products (primarily welded pressure
tubes)]{.underline}***.\--These tubes include, but are not limited to,
ASTM A-249, A-269, A-270, and A-688 pressure tubes. Uses for these tubes
include, but are not limited to, boiler, super-heater, condenser, and
heat exchanger tubes, general corrosion-resistant service, dairy and
food applications, where cleanliness and corrosion-resistance is
important, and feed water heater units in power stations.
*[None]{.underline} of the product definitions provided above, whether
for pressure pipes or pressure tubes, include grade 409 or mechanical
tubing.*
***[Firm]{.underline}***.‑‑An individual proprietorship, partnership,
joint venture, association, corporation (including any subsidiary
corporation), business trust, cooperative, trustee in bankruptcy, or
receiver under decree of any court.
**[DEFINITIONS]{.underline}\--*Continued***
***[Related firm]{.underline}***.‑‑A firm that your firm solely or
jointly owned, managed, or otherwise controlled; a firm that solely or
jointly owned, managed, or otherwise controlled your firm; and/or a firm
that was solely or jointly owned, managed, or otherwise controlled by a
firm that also solely or jointly owned, managed, or otherwise controlled
your firm.
***[Establishment]{.underline}***.‑‑Each facility of a firm in the
United States involved in the production, importation, and/or purchase
of welded stainless steel pressure pipe (or other specified forms of
welded stainless steel tubular products) (as defined above), including
auxiliary facilities operated in conjunction with (whether or not
physically separate from) such facilities.
***[United States]{.underline}***.‑‑For purposes of these
investigations, the 50 States, Puerto Rico, the U.S. Virgin Islands, and
the District of Columbia.
***[Importer]{.underline}***.‑‑Any person or firm engaged, either
directly or through a parent company or subsidiary, in importing welded
stainless steel pressure pipe (or other specified forms of welded
stainless steel tubular products) (as defined above) into the United
States from a foreign manufacturer or through its selling agent.
***[Imports]{.underline}***.‑‑Those products identified for Customs
purposes as [imports for consumption]{.underline} for which your firm
was the importer of record (i.e., was responsible for paying any import
duty) or consignee (i.e., to which the merchandise was first delivered).
***[Import quantities]{.underline}***.‑‑Quantities reported should be
net of returns.
***[Import values]{.underline}***.‑‑Values reported should be landed,
duty-paid values at the U.S. port of entry, including ocean freight and
insurance costs, brokerage charges, and import duties (i.e., all charges
except inland freight in the United States).
***[Purchaser]{.underline}***.‑‑Any person or firm engaged, either
directly or through a parent company or subsidiary, in purchasing welded
stainless steel pressure pipe (or other specified forms of welded
stainless steel tubular products) (as defined above) from another firm
that produces, imports, or otherwise distributes welded stainless steel
pressure pipe (or other specified forms of welded stainless steel
tubular products) (as defined above). A retail firm that is the importer
of record may be considered a purchaser.
**[DEFINITIONS]{.underline}\--*Continued***
***[Purchases]{.underline}***.‑‑Purchases from all sources, NOT
including direct imports from foreign producers (which should be
reported in an importer questionnaire).
***[Purchase quantities]{.underline}***.‑‑Quantities reported should be
net of returns.
> ***[Purchase values]{.underline}***.‑‑Values reported should be net
> values (i.e., gross purchase values less all discounts, allowances,
> rebates, and the value of returned goods), delivered to your U.S.
> receiving point.
***[Shipments]{.underline}***.\--Shipments of products produced in or
imported by your U.S. establishment(s). Include shipments to the
contracting firm of product produced by your firm under a toll
agreement.
***[Shipment quantities]{.underline}***.‑‑Quantities reported should be
net of returns.
> ***[Shipment values]{.underline}***.‑‑Values reported should be net
> values (i.e., gross sales values less all discounts, allowances,
> rebates, prepaid freight, and the value of returned goods), f.o.b.
> your U.S. point of shipment. The value of domestic shipments to the
> contracting firm under a toll agreement is the conversion fee
> (including profit).
***[Types of shipments]{.underline}***:
> ***[U.S. shipments]{.underline}***.‑‑Commercial shipments, internal
> consumption, and transfers to related firms within the United States.
>
> ***[Commercial shipments]{.underline}***.\--Shipments, other than
> internal consumption and transfers to related firms, within the United
> States.
>
> ***[Internal consumption]{.underline}***.\--Product consumed
> internally by your firm.
>
> ***[Transfers to related firms]{.underline}***.‑‑Shipments made to
> related domestic firms.
>
> ***[Export shipments]{.underline}***.‑‑Shipments to destinations
> outside the United States, including shipments to related firms.
***[Inventories]{.underline}***.‑‑Finished goods inventory, not raw
materials or work‑in‑progress.
**The following definitions apply only to the PRODUCER QUESTIONNAIRE.**
***[Average production capacity]{.underline}***.‑‑The level of
production that your establishment(s) could reasonably have expected to
attain during the specified periods. Assume normal operating conditions
(i.e., using equipment and machinery in place and ready to operate;
normal operating levels (hours per week/weeks per year) and time for
downtime, maintenance, repair, and cleanup; and a typical or
representative product mix).
**[DEFINITIONS]{.underline}\--*Continued***
***[Toll agreement]{.underline}***.‑‑Agreement between two firms whereby
the first firm furnishes the raw materials and the second firm uses the
raw materials to produce a product that it then returns to the first
firm with a charge for processing costs, overhead, etc.
***[Production]{.underline}***.‑‑All production in your U.S.
establishment(s), including production consumed internally within your
firm and production for another firm under a toll agreement.
***[PRWs]{.underline}***.‑‑Production and related workers, including
working supervisors and all nonsupervisory workers (including group
leaders and trainees) engaged in fabricating, processing, assembling,
inspecting, receiving, storage, handling, packing, warehousing,
shipping, trucking, hauling, maintenance, repair, janitorial and guard
services, product development, auxiliary production for plant=s own use
(e.g., power plant), recordkeeping, and other services closely
associated with the above production operations.
***[Average number employed]{.underline}***.‑‑Add the number of
employees, both full‑time and part‑time, for the 12 pay periods ending
closest to the 15th of the month and divide that total by 12. For the
January‑September periods, calculate similarly and divide by 9.
***[Hours worked]{.underline}***.‑‑Include time paid for sick leave,
holidays, and vacation time. Include overtime hours actually worked; do
not convert overtime pay to its equivalent in straight‑time hours.
***[Wages paid]{.underline}***.‑‑Total wages paid before deductions of
any kind (e.g., withholding taxes, old-age and unemployment insurance,
group insurance, union dues, bonds, etc.). Include wages paid directly
by your firm for overtime, holidays, vacations, and sick leave.
***[Fiscal year]{.underline}***.‑‑The 12‑month period between settlement
of your firm=s financial accounts.
***[Purchases other than direct imports]{.underline}***.\--Purchases
from U.S. producers, U.S. importers, and other U.S. sources.
| en |
log-files | 642338 | run 90003 Thu Sep 25 06:15:36 2008 0.2 hours 1 lumiblocks release 14.2.21.4 smk 338 hltps 335 lvl1ps 470
run 90017 Thu Sep 25 06:44:26 2008 0.4 hours 2 lumiblocks release 14.2.21.4 smk 338 hltps 335 lvl1ps 470
run 90048 Thu Sep 25 07:46:43 2008 0.0 hours 1 lumiblocks release 14.2.21.4 smk 338 hltps 337 lvl1ps 476
run 90104 Thu Sep 25 10:53:41 2008 0.6 hours 3 lumiblocks release 14.2.21.4 smk 338 hltps 337 lvl1ps 476 474
run 90109 Thu Sep 25 12:02:47 2008 0.4 hours 3 lumiblocks release 14.2.21.4 smk 338 hltps 337 lvl1ps 476 474
run 90113 Thu Sep 25 12:42:40 2008 1.7 hours 8 lumiblocks release 14.2.21.4 smk 339 hltps 339 lvl1ps 474 477
run 90124 Thu Sep 25 15:46:13 2008 0.5 hours 2 lumiblocks release 14.2.21.4 smk 339 hltps 340 lvl1ps 478
run 90127 Thu Sep 25 16:37:08 2008 3.6 hours 14 lumiblocks release 14.2.21.4 smk 339 hltps 340 lvl1ps 479 477
run 90128 Thu Sep 25 20:37:14 2008 2.7 hours 10 lumiblocks release 14.2.21.4 smk 339 hltps 341 lvl1ps 477
run 90129 Thu Sep 25 23:52:40 2008 0.4 hours 3 lumiblocks release 14.2.21.4 smk 339 hltps 342 lvl1ps 477
run 90131 Fri Sep 26 01:01:42 2008 2.9 hours 11 lumiblocks release 14.2.21.4 smk 339 hltps 342 lvl1ps 477
run 90132 Fri Sep 26 04:52:19 2008 0.3 hours 2 lumiblocks release 14.2.21.4 smk 341 hltps 342 lvl1ps 480
run 90136 Fri Sep 26 05:28:09 2008 0.3 hours 2 lumiblocks release 14.2.21.4 smk 341 hltps 342 lvl1ps 481
run 90144 Fri Sep 26 06:15:37 2008 0.6 hours 3 lumiblocks release 14.2.21.4 smk 341 hltps 342 lvl1ps 480
run 90164 Fri Sep 26 07:18:32 2008 0.8 hours 4 lumiblocks release 14.2.21.4 smk 341 hltps 342 lvl1ps 480
run 90194 Fri Sep 26 09:23:06 2008 0.3 hours 2 lumiblocks release 14.2.21.5 smk 342 hltps 343 lvl1ps 480
run 90200 Fri Sep 26 10:16:43 2008 0.1 hours 1 lumiblocks release 14.2.21.5 smk 342 hltps 343 lvl1ps 480
run 90215 Fri Sep 26 11:28:24 2008 0.4 hours 2 lumiblocks release 14.2.21.5 smk 342 hltps 343 lvl1ps 480
run 90224 Fri Sep 26 13:03:40 2008 1.1 hours 5 lumiblocks release 14.2.21.5 smk 342 hltps 343 lvl1ps 480 482
run 90229 Fri Sep 26 14:56:11 2008 0.9 hours 5 lumiblocks release 14.2.21.5 smk 342 hltps 343 lvl1ps 480 482
run 90233 Fri Sep 26 16:13:20 2008 2.1 hours 10 lumiblocks release 14.2.21.5 smk 342 hltps 343 lvl1ps 480 482 482 483
run 90245 Fri Sep 26 19:02:19 2008 0.7 hours 3 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 484
run 90246 Fri Sep 26 20:18:12 2008 1.0 hours 4 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 484 485
run 90247 Fri Sep 26 21:57:02 2008 1.0 hours 5 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 484 486
run 90248 Fri Sep 26 23:09:53 2008 0.7 hours 3 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90251 Sat Sep 27 00:35:01 2008 1.1 hours 5 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 484
run 90252 Sat Sep 27 02:05:48 2008 1.3 hours 6 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 484 486 486
run 90257 Sat Sep 27 05:30:42 2008 0.3 hours 2 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 487
run 90258 Sat Sep 27 05:59:28 2008 0.3 hours 2 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 487
run 90260 Sat Sep 27 07:11:11 2008 0.5 hours 2 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90262 Sat Sep 27 09:01:50 2008 2.1 hours 8 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90264 Sat Sep 27 11:57:44 2008 3.1 hours 12 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90267 Sat Sep 27 15:59:07 2008 0.1 hours 1 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90268 Sat Sep 27 16:32:49 2008 0.2 hours 1 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90269 Sat Sep 27 17:23:58 2008 0.1 hours 1 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90270 Sat Sep 27 17:55:14 2008 4.0 hours 10 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486 488
run 90272 Sat Sep 27 22:27:42 2008 15.9 hours 58 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486 488
run 90275 Sun Sep 28 16:19:31 2008 12.5 hours 47 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486 489 488
run 90295 Mon Sep 29 07:30:54 2008 0.9 hours 4 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90300 Mon Sep 29 08:43:31 2008 0.8 hours 4 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90311 Mon Sep 29 11:09:50 2008 0.6 hours 3 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90329 Mon Sep 29 12:40:40 2008 1.1 hours 5 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90345 Mon Sep 29 15:01:42 2008 13.3 hours 48 lumiblocks release 14.2.21.5 smk 342 hltps 344 lvl1ps 486
run 90375 Tue Sep 30 08:30:26 2008 0.1 hours 1 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 491
run 90394 Tue Sep 30 11:11:11 2008 0.5 hours 3 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 491
run 90405 Tue Sep 30 13:14:06 2008 0.2 hours 1 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 492
run 90410 Tue Sep 30 15:21:33 2008 0.4 hours 3 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 492 493 494
run 90413 Tue Sep 30 16:20:26 2008 8.9 hours 33 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 495
run 90414 Wed Oct 1 01:42:28 2008 0.0 hours 1 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 495
run 90415 Wed Oct 1 01:52:17 2008 3.0 hours 2 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 495
run 90434 Wed Oct 1 06:24:35 2008 0.1 hours 1 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 496
run 90438 Wed Oct 1 06:53:31 2008 0.3 hours 2 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 496
run 90441 Wed Oct 1 07:15:00 2008 0.0 hours 1 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 496
run 90445 Wed Oct 1 07:38:50 2008 1.3 hours 5 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 496
run 90475 Wed Oct 1 10:08:41 2008 1.5 hours 7 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 497
run 90493 Wed Oct 1 11:53:05 2008 0.2 hours 1 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 497
run 90495 Wed Oct 1 12:19:05 2008 0.8 hours 3 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 497
run 90510 Wed Oct 1 13:37:21 2008 0.1 hours 1 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 498
run 90511 Wed Oct 1 14:17:59 2008 2.3 hours 11 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 498 499 500 501 502 503 504
run 90524 Wed Oct 1 17:36:45 2008 0.4 hours 3 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 498 504
run 90525 Wed Oct 1 18:28:26 2008 10.2 hours 37 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 504
run 90560 Thu Oct 2 07:33:51 2008 0.1 hours 1 lumiblocks release 14.2.21.5 smk 343 hltps 344 lvl1ps 496
run 90569 Thu Oct 2 08:16:16 2008 0.0 hours 1 lumiblocks release 14.2.21.6 smk 344 hltps 346 lvl1ps 496
run 90573 Thu Oct 2 08:36:18 2008 2.4 hours 9 lumiblocks release 14.2.21.6 smk 344 hltps 346 lvl1ps 496
run 90622 Thu Oct 2 14:21:07 2008 0.3 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 347 lvl1ps 505
run 90629 Thu Oct 2 15:38:25 2008 0.1 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 505 506
run 90630 Thu Oct 2 16:22:40 2008 0.8 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 508
run 90631 Thu Oct 2 17:44:13 2008 0.6 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90633 Thu Oct 2 18:39:36 2008 0.6 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90635 Thu Oct 2 19:23:55 2008 0.2 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90637 Thu Oct 2 20:21:58 2008 0.7 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90638 Thu Oct 2 21:18:20 2008 0.2 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90639 Thu Oct 2 22:02:57 2008 0.2 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90640 Thu Oct 2 22:39:59 2008 0.4 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90641 Thu Oct 2 23:14:22 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90642 Thu Oct 2 23:43:22 2008 0.3 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90645 Fri Oct 3 00:51:14 2008 0.2 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90646 Fri Oct 3 01:10:32 2008 0.2 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90649 Fri Oct 3 01:48:40 2008 0.0 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90662 Fri Oct 3 04:40:22 2008 0.3 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 348 lvl1ps 507
run 90668 Fri Oct 3 05:58:03 2008 0.3 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 349 lvl1ps 509
run 90675 Fri Oct 3 06:48:03 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 351 lvl1ps 509
run 90686 Fri Oct 3 07:36:57 2008 0.3 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 352 lvl1ps 509
run 90692 Fri Oct 3 08:23:21 2008 0.4 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 353 lvl1ps 509
run 90702 Fri Oct 3 10:09:26 2008 0.6 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 353 lvl1ps 510
run 90708 Fri Oct 3 11:54:43 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 353 lvl1ps 510
run 90711 Fri Oct 3 12:05:43 2008 1.5 hours 6 lumiblocks release 14.2.21.6 smk 345 hltps 353 lvl1ps 510
run 90719 Fri Oct 3 14:04:26 2008 0.6 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 353 lvl1ps 510
run 90721 Fri Oct 3 15:13:17 2008 0.2 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 353 lvl1ps 510
run 90722 Fri Oct 3 15:31:08 2008 0.3 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 353 lvl1ps 511 8
run 90724 Fri Oct 3 16:33:40 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 360 lvl1ps 513
run 90725 Fri Oct 3 17:21:21 2008 0.7 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90726 Fri Oct 3 19:09:57 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90727 Fri Oct 3 19:22:31 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90729 Fri Oct 3 20:22:27 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90731 Fri Oct 3 21:56:39 2008 0.6 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90732 Fri Oct 3 23:03:32 2008 1.1 hours 5 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90733 Sat Oct 4 00:37:20 2008 6.4 hours 24 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90736 Sat Oct 4 08:36:47 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90737 Sat Oct 4 08:48:51 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90738 Sat Oct 4 09:08:38 2008 0.3 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90739 Sat Oct 4 10:25:11 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90741 Sat Oct 4 10:42:01 2008 0.2 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90743 Sat Oct 4 11:17:22 2008 9.3 hours 34 lumiblocks release 14.2.21.6 smk 345 hltps 362 lvl1ps 513
run 90748 Sat Oct 4 21:17:20 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90749 Sat Oct 4 21:52:31 2008 2.4 hours 9 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90750 Sun Oct 5 01:01:33 2008 0.0 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90751 Sun Oct 5 01:12:56 2008 0.2 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90752 Sun Oct 5 01:43:14 2008 0.3 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90753 Sun Oct 5 02:36:47 2008 0.3 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90754 Sun Oct 5 03:13:50 2008 0.1 hours 1 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90755 Sun Oct 5 04:00:53 2008 0.5 hours 2 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90757 Sun Oct 5 05:20:40 2008 0.6 hours 3 lumiblocks release 14.2.21.6 smk 345 hltps 364 lvl1ps 513
run 90758 Sun Oct 5 07:15:27 2008 1.6 hours 6 lumiblocks release 14.2.21.6 smk 350 hltps 364 lvl1ps 513
run 90766 Sun Oct 5 09:26:59 2008 0.4 hours 2 lumiblocks release 14.2.21.6 smk 350 hltps 364 lvl1ps 513
run 90776 Sun Oct 5 11:00:17 2008 0.0 hours 1 lumiblocks release 14.2.21.8 smk 349 hltps 365 lvl1ps 513
run 90778 Sun Oct 5 11:10:12 2008 0.1 hours 1 lumiblocks release 14.2.21.8 smk 349 hltps 365 lvl1ps 513
run 90780 Sun Oct 5 11:21:37 2008 0.0 hours 1 lumiblocks release 14.2.21.8 smk 349 hltps 365 lvl1ps 513
run 90782 Sun Oct 5 11:31:53 2008 0.1 hours 1 lumiblocks release 14.2.21.8 smk 349 hltps 365 lvl1ps 513
run 90784 Sun Oct 5 11:59:25 2008 0.7 hours 3 lumiblocks release 14.2.21.8 smk 349 hltps 365 lvl1ps 513
run 90785 Sun Oct 5 13:14:55 2008 1.0 hours 4 lumiblocks release 14.2.21.8 smk 349 hltps 366 lvl1ps 513 514
run 90786 Sun Oct 5 15:00:37 2008 1.2 hours 6 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513
run 90787 Sun Oct 5 16:50:53 2008 0.0 hours 1 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513
run 90789 Sun Oct 5 17:04:01 2008 0.2 hours 1 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513
run 90790 Sun Oct 5 18:26:45 2008 0.2 hours 1 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513
run 90792 Sun Oct 5 19:36:12 2008 0.4 hours 2 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513
run 90793 Sun Oct 5 20:43:01 2008 6.8 hours 25 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513
run 90799 Mon Oct 6 05:00:44 2008 0.1 hours 1 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513
run 90801 Mon Oct 6 05:29:52 2008 2.8 hours 11 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513 515
run 90809 Mon Oct 6 08:57:20 2008 1.0 hours 5 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 513 515
run 90830 Mon Oct 6 12:17:15 2008 0.2 hours 1 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 515
run 90838 Mon Oct 6 13:18:39 2008 0.5 hours 2 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 515
run 90845 Mon Oct 6 14:24:10 2008 0.1 hours 1 lumiblocks release 14.2.21.8 smk 351 hltps 367 lvl1ps 515
run 90849 Mon Oct 6 15:33:20 2008 0.3 hours 2 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 513 516
run 90852 Mon Oct 6 16:53:06 2008 0.4 hours 2 lumiblocks release 14.2.21.9 smk 352 hltps 368 lvl1ps 513
run 90853 Mon Oct 6 17:52:40 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 352 hltps 369 lvl1ps 513
run 90854 Mon Oct 6 18:55:46 2008 0.5 hours 3 lumiblocks release 14.2.21.9 smk 352 hltps 370 lvl1ps 513 517
run 90855 Mon Oct 6 20:27:45 2008 7.7 hours 29 lumiblocks release 14.2.21.9 smk 352 hltps 371 lvl1ps 513 517 518
run 90868 Tue Oct 7 05:22:06 2008 0.0 hours 1 lumiblocks release 14.2.21.9 smk 352 hltps 371 lvl1ps 513
run 90913 Tue Oct 7 13:52:00 2008 1.4 hours 6 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 513
run 90924 Tue Oct 7 15:43:49 2008 0.5 hours 2 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 513
run 90933 Tue Oct 7 16:29:14 2008 0.0 hours 1 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 513
run 90941 Tue Oct 7 17:15:59 2008 0.5 hours 3 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 513
run 90943 Tue Oct 7 19:03:10 2008 9.2 hours 34 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 513
run 90969 Wed Oct 8 06:43:47 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 520
run 90975 Wed Oct 8 07:23:35 2008 1.2 hours 5 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 520
run 91001 Wed Oct 8 09:28:35 2008 0.0 hours 1 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 520
run 91003 Wed Oct 8 09:36:43 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 520
run 91007 Wed Oct 8 09:54:39 2008 4.6 hours 17 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 520
run 91043 Wed Oct 8 15:03:23 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 355 hltps 373 lvl1ps 520
run 91044 Wed Oct 8 15:27:12 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 351 hltps 369 lvl1ps 520
run 91045 Wed Oct 8 15:37:16 2008 0.3 hours 2 lumiblocks release 14.2.21.9 smk 351 hltps 369 lvl1ps 520
run 91047 Wed Oct 8 16:04:03 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 351 hltps 369 lvl1ps 520
run 91056 Wed Oct 8 16:42:37 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 351 hltps 369 lvl1ps 520
run 91059 Wed Oct 8 17:57:22 2008 0.4 hours 3 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 520 520 521
run 91060 Wed Oct 8 19:28:35 2008 8.9 hours 33 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 520 522 520
run 91077 Thu Oct 9 06:25:35 2008 0.2 hours 1 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 515
run 91086 Thu Oct 9 07:12:05 2008 0.3 hours 3 lumiblocks release 14.2.21.9 smk 351 hltps 368 lvl1ps 515 9
run 91112 Thu Oct 9 08:13:32 2008 0.2 hours 1 lumiblocks release 14.2.21.9 smk 357 hltps 356 lvl1ps 519
run 91139 Thu Oct 9 09:22:12 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 357 hltps 356 lvl1ps 523
run 91175 Thu Oct 9 09:51:41 2008 1.1 hours 4 lumiblocks release 14.2.21.9 smk 357 hltps 356 lvl1ps 523
run 91279 Thu Oct 9 11:46:31 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 357 hltps 356 lvl1ps 520
run 91305 Thu Oct 9 11:58:53 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 357 hltps 356 lvl1ps 520
run 91324 Thu Oct 9 12:41:19 2008 0.1 hours 1 lumiblocks release 14.2.21.9 smk 357 hltps 356 lvl1ps 520
run 91327 Thu Oct 9 13:15:07 2008 0.2 hours 1 lumiblocks release 14.2.21.9 smk 358 hltps 377 lvl1ps 520
run 91330 Thu Oct 9 13:44:03 2008 1.7 hours 7 lumiblocks release 14.2.21.9 smk 358 hltps 377 lvl1ps 520
run 91335 Thu Oct 9 15:50:33 2008 1.4 hours 6 lumiblocks release 14.2.21.9 smk 359 hltps 378 lvl1ps 520
run 91336 Thu Oct 9 17:59:51 2008 0.2 hours 2 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91337 Thu Oct 9 18:34:12 2008 0.0 hours 1 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91338 Thu Oct 9 18:58:59 2008 8.3 hours 31 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91342 Fri Oct 10 03:56:40 2008 0.3 hours 2 lumiblocks release 14.2.21.9 smk 359 hltps 356 lvl1ps 524
run 91344 Fri Oct 10 04:53:21 2008 0.7 hours 3 lumiblocks release 14.2.21.9 smk 359 hltps 356 lvl1ps 524
run 91347 Fri Oct 10 06:01:00 2008 0.0 hours 1 lumiblocks release 14.2.21.9 smk 359 hltps 356 lvl1ps 524
run 91348 Fri Oct 10 06:29:53 2008 0.9 hours 4 lumiblocks release 14.2.21.9 smk 359 hltps 356 lvl1ps 524
run 91351 Fri Oct 10 07:56:18 2008 2.2 hours 8 lumiblocks release 14.2.21.9 smk 360 hltps 377 lvl1ps 520
run 91354 Fri Oct 10 11:24:18 2008 0.8 hours 4 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91358 Fri Oct 10 13:27:43 2008 0.4 hours 3 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91359 Fri Oct 10 14:36:52 2008 1.5 hours 6 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91360 Fri Oct 10 17:50:41 2008 0.1 hours 2 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
# st005
run 91361 Fri Oct 10 18:17:14 2008 14.1 hours 51 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91387 Sat Oct 11 10:35:58 2008 24.6 hours 89 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91389 Sun Oct 12 12:34:50 2008 8.5 hours 31 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91390 Sun Oct 12 21:45:20 2008 1.5 hours 6 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91391 Mon Oct 13 00:50:38 2008 9.2 hours 34 lumiblocks release 14.2.21.9 smk 359 hltps 377 lvl1ps 520
run 91398 Mon Oct 13 12:39:32 2008 1.9 hours 8 lumiblocks release 14.2.21.9 smk 358 hltps 377 lvl1ps 520
run 91399 Mon Oct 13 15:08:59 2008 0.6 hours 3 lumiblocks release 14.2.21.9 smk 362 hltps 377 lvl1ps 520
run 91400 Mon Oct 13 16:27:09 2008 3.1 hours 12 lumiblocks release 14.2.21.9 smk 362 hltps 377 lvl1ps 520
run 91464 Mon Oct 13 20:18:40 2008 3.5 hours 13 lumiblocks release 14.2.21.9 smk 362 hltps 377 lvl1ps 520
run 91560 Tue Oct 14 00:37:28 2008 0.0 hours 1 lumiblocks release 14.2.21.9 smk 362 hltps 377 lvl1ps 520
run 91561 Tue Oct 14 01:02:26 2008 2.1 hours 8 lumiblocks release 14.2.21.9 smk 362 hltps 377 lvl1ps 520
run 91591 Tue Oct 14 04:57:38 2008 0.5 hours 2 lumiblocks release 14.2.23.1 smk 363 hltps 380 lvl1ps 516
run 91613 Tue Oct 14 06:09:58 2008 0.3 hours 2 lumiblocks release 14.2.23.1 smk 365 hltps 380 lvl1ps 524
run 91627 Tue Oct 14 07:10:50 2008 0.8 hours 3 lumiblocks release 14.2.23.1 smk 365 hltps 380 lvl1ps 524
not@bnl run 91636 Tue Oct 14 08:41:50 2008 5.0 hours 19 lumiblocks release 14.2.23.1 smk 365 hltps 381 lvl1ps 520
not@bnl run 91639 Tue Oct 14 14:59:02 2008 14.6 hours 53 lumiblocks release 14.2.23.1 smk 365 hltps 381 lvl1ps 520
run 91784 Wed Oct 15 07:15:06 2008 0.6 hours 3 lumiblocks release 14.2.23.1 smk 365 hltps 384 lvl1ps 520
run 91790 Wed Oct 15 09:02:28 2008 0.5 hours 2 lumiblocks release 14.2.23.1 smk 365 hltps 384 lvl1ps 520
run 91796 Wed Oct 15 11:53:37 2008 0.3 hours 2 lumiblocks release 14.2.23.1 smk 365 hltps 384 lvl1ps 520
run 91798 Wed Oct 15 12:21:32 2008 0.6 hours 3 lumiblocks release 14.2.23.1 smk 365 hltps 384 lvl1ps 520
run 91799 Wed Oct 15 13:39:38 2008 0.6 hours 3 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
run 91800 Wed Oct 15 14:45:47 2008 5.3 hours 20 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
run 91801 Wed Oct 15 20:37:10 2008 3.5 hours 13 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
run 91802 Thu Oct 16 00:27:32 2008 0.6 hours 3 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
run 91803 Thu Oct 16 01:25:12 2008 2.0 hours 8 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
run 91808 Thu Oct 16 04:21:54 2008 2.4 hours 9 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
run 91822 Thu Oct 16 06:57:09 2008 0.9 hours 4 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
run 91827 Thu Oct 16 08:55:39 2008 0.2 hours 2 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
run 91828 Thu Oct 16 09:48:09 2008 1.3 hours 5 lumiblocks release 14.2.23.1 smk 367 hltps 386 lvl1ps 520
not@bnl run 91860 Thu Oct 16 12:50:28 2008 4.0 hours 15 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
not@bnl run 91861 Thu Oct 16 17:40:10 2008 2.8 hours 11 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
not@bnl run 91862 Thu Oct 16 20:49:51 2008 8.5 hours 32 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
run 91870 Fri Oct 17 06:02:14 2008 2.3 hours 9 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
run 91881 Fri Oct 17 10:04:15 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
run 91884 Fri Oct 17 10:43:57 2008 0.2 hours 2 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
not@bnl run 91885 Fri Oct 17 11:22:56 2008 9.1 hours 33 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
run 91887 Fri Oct 17 20:47:50 2008 0.0 hours 1 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
not@bnl run 91888 Fri Oct 17 21:50:27 2008 6.8 hours 26 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
run 91889 Sat Oct 18 05:49:29 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
not@bnl run 91890 Sat Oct 18 06:49:33 2008 9.5 hours 35 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520 (magnets on)
not@bnl run 91891 Sat Oct 18 17:00:30 2008 9.0 hours 24 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
run 91892 Sun Oct 19 04:22:19 2008 0.1 hours 1 lumiblocks release - smk - hltps - lvl1ps 520
run 91893 Sun Oct 19 05:37:40 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
run 91894 Sun Oct 19 06:11:21 2008 0.2 hours 1 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520
run 91895 Sun Oct 19 06:42:25 2008 0.2 hours 2 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 520 525
run 91896 Sun Oct 19 07:17:36 2008 0.2 hours 2 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 525
run 91897 Sun Oct 19 07:51:44 2008 0.7 hours 3 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 525
run 91898 Sun Oct 19 08:46:19 2008 0.2 hours 1 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 525
run 91899 Sun Oct 19 09:19:09 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 525
not@bnl run 91900 Sun Oct 19 10:03:00 2008 13.9 hours 50 lumiblocks release 14.2.23.2 smk 368 hltps 388 lvl1ps 526
run 91943 Mon Oct 20 00:25:52 2008 0.2 hours 1 lumiblocks release 14.2.23.2 smk 369 hltps 390 lvl1ps 527
run 91944 Mon Oct 20 01:01:45 2008 1.7 hours 7 lumiblocks release 14.2.23.2 smk 369 hltps 390 lvl1ps 527
run 91946 Mon Oct 20 03:00:27 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 369 hltps 390 lvl1ps 527
run 91949 Mon Oct 20 03:25:12 2008 1.1 hours 4 lumiblocks release 14.2.23.2 smk 369 hltps 390 lvl1ps 527
run 92041 Mon Oct 20 15:01:39 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 369 hltps 390 lvl1ps 526
run 92042 Mon Oct 20 15:43:17 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 369 hltps 388 lvl1ps 526
run 92043 Mon Oct 20 16:53:01 2008 0.6 hours 3 lumiblocks release 14.2.23.2 smk 369 hltps 392 lvl1ps 526
run 92044 Mon Oct 20 17:36:20 2008 0.0 hours 1 lumiblocks release 14.2.23.2 smk 369 hltps 392 lvl1ps 526
nofields run 92045 Mon Oct 20 18:15:51 2008 5.1 hours 19 lumiblocks release 14.2.23.2 smk 369 hltps 388 lvl1ps 526
run 92047 Mon Oct 20 23:43:46 2008 0.3 hours 2 lumiblocks release 14.2.23.2 smk 369 hltps 388 lvl1ps 526
run 92048 Tue Oct 21 01:03:49 2008 5.0 hours 18 lumiblocks release 14.2.23.2 smk 369 hltps 388 lvl1ps 526
run 92051 Tue Oct 21 06:28:36 2008 3.5 hours 13 lumiblocks release 14.2.23.2 smk 369 hltps 388 lvl1ps 526
run 92054 Tue Oct 21 10:28:36 2008 0.9 hours 4 lumiblocks release 14.2.23.2 smk 369 hltps 388 lvl1ps 526
run 92055 Tue Oct 21 11:40:07 2008 0.2 hours 8 lumiblocks release 14.2.23.2 smk 369 hltps 388 lvl1ps 526
nofields run 92057 Tue Oct 21 12:10:59 2008 16.6 hours 61 lumiblocks release 14.2.23.2 smk 369 hltps 388 lvl1ps 526
run 92058 Wed Oct 22 06:29:56 2008 0.5 hours 3 lumiblocks release 14.2.23.2 smk 370 hltps 388 lvl1ps 526
run 92059 Wed Oct 22 07:32:24 2008 0.6 hours 3 lumiblocks release 14.2.23.2 smk 373 hltps 393 lvl1ps 528
run 92060 Wed Oct 22 08:29:55 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528
run 92061 Wed Oct 22 09:19:06 2008 0.0 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528
run 92062 Wed Oct 22 09:24:37 2008 0.0 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528
run 92063 Wed Oct 22 09:59:48 2008 0.3 hours 2 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528
run 92065 Wed Oct 22 11:02:44 2008 0.8 hours 3 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528
run 92067 Wed Oct 22 12:07:28 2008 0.0 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528
run 92069 Wed Oct 22 12:23:55 2008 1.0 hours 4 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528
run 92072 Wed Oct 22 13:47:43 2008 0.6 hours 3 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528 529 530
run 92073 Wed Oct 22 14:36:59 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528
run 92074 Wed Oct 22 14:52:45 2008 0.8 hours 3 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 528 529
run 92075 Wed Oct 22 16:54:30 2008 0.2 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529
run 92076 Wed Oct 22 17:08:39 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529
run 92077 Wed Oct 22 17:20:35 2008 0.8 hours 3 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529
run 92078 Wed Oct 22 18:56:17 2008 1.2 hours 6 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529
run 92079 Wed Oct 22 20:11:34 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529
run 92080 Wed Oct 22 20:35:59 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529
run 92081 Wed Oct 22 21:02:31 2008 0.6 hours 3 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529
run 92082 Wed Oct 22 21:58:37 2008 5.2 hours 19 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529 (toroids off)
run 92092 Thu Oct 23 06:10:42 2008 1.1 hours 5 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 529 531
run 92094 Thu Oct 23 07:26:57 2008 0.0 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 531
run 92095 Thu Oct 23 07:36:19 2008 0.7 hours 5 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 531 530 533
run 92097 Thu Oct 23 08:27:26 2008 0.4 hours 2 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 533
run 92098 Thu Oct 23 08:58:00 2008 0.9 hours 5 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 533 530 533
run 92099 Thu Oct 23 10:25:23 2008 0.8 hours 3 lumiblocks release 14.2.23.2 smk 373 hltps 394 lvl1ps 535
run 92100 Thu Oct 23 12:02:43 2008 1.2 hours 5 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 533
run 92101 Thu Oct 23 13:27:56 2008 0.0 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 533
run 92102 Thu Oct 23 13:49:57 2008 0.0 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 533
run 92103 Thu Oct 23 13:57:41 2008 0.2 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 533
run 92104 Thu Oct 23 14:27:40 2008 0.1 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 530
run 92106 Thu Oct 23 14:40:18 2008 0.2 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 530
run 92107 Thu Oct 23 14:56:49 2008 1.9 hours 7 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 530
run 92108 Thu Oct 23 17:16:42 2008 0.3 hours 2 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 530
run 92109 Thu Oct 23 17:58:57 2008 0.5 hours 2 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 530
run 92111 Thu Oct 23 18:46:54 2008 0.2 hours 1 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 530
run 92112 Thu Oct 23 19:07:58 2008 9.3 hours 34 lumiblocks release 14.2.23.2 smk 373 hltps 396 lvl1ps 530 (toroids off)
run 92123 Fri Oct 24 06:03:07 2008 0.3 hours 2 lumiblocks release 14.2.23.2 smk 373 hltps 397 lvl1ps 530
run 92125 Fri Oct 24 07:59:05 2008 0.5 hours 4 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 530
run 92127 Fri Oct 24 09:17:23 2008 0.8 hours 4 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 530
run 92128 Fri Oct 24 10:31:19 2008 0.1 hours 1 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 533
run 92130 Fri Oct 24 11:28:18 2008 0.5 hours 3 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 533 530
run 92132 Fri Oct 24 12:06:40 2008 0.0 hours 1 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 530
run 92134 Fri Oct 24 14:05:35 2008 1.2 hours 6 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 530 533
run 92137 Fri Oct 24 15:50:29 2008 0.1 hours 1 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 533
run 92139 Fri Oct 24 18:46:50 2008 0.5 hours 2 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 530
run 92140 Fri Oct 24 19:44:32 2008 2.5 hours 9 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536
run 92143 Fri Oct 24 22:57:24 2008 1.7 hours 7 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 531
run 92146 Sat Oct 25 02:26:44 2008 0.1 hours 1 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536
run 92147 Sat Oct 25 02:48:47 2008 0.4 hours 2 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536
run 92148 Sat Oct 25 03:20:11 2008 0.4 hours 2 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536
run 92149 Sat Oct 25 05:16:49 2008 0.9 hours 4 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536
run 92153 Sat Oct 25 07:05:22 2008 0.7 hours 3 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536
run 92157 Sat Oct 25 07:59:55 2008 2.4 hours 9 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536 (toroids off)
run 92159 Sat Oct 25 11:47:40 2008 0.1 hours 3 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 530
run 92160 Sat Oct 25 13:32:59 2008 19.3 hours 70 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536 (toroids off)
run 92223 Sun Oct 26 10:25:43 2008 0.4 hours 2 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536
run 92226 Sun Oct 26 11:15:59 2008 14.9 hours 54 lumiblocks release 14.2.23.3 smk 374 hltps 399 lvl1ps 536
run 92314 Mon Oct 27 12:09:30 2008 0.0 hours 1 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 537
run 92319 Mon Oct 27 12:30:01 2008 0.1 hours 1 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 537
run 92328 Mon Oct 27 12:58:39 2008 15.1 hours 55 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 537
run 92520 Tue Oct 28 10:06:01 2008 0.1 hours 1 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 537
run 92543 Tue Oct 28 11:27:31 2008 2.2 hours 9 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 537
run 92560 Tue Oct 28 14:32:53 2008 0.1 hours 1 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 537
run 92561 Tue Oct 28 14:55:04 2008 12.9 hours 47 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 537
run 92670 Wed Oct 29 13:22:53 2008 0.2 hours 1 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 538
run 92673 Wed Oct 29 13:43:29 2008 0.1 hours 1 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 538
run 92674 Wed Oct 29 13:58:34 2008 0.5 hours 2 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 538
run 92676 Wed Oct 29 14:41:09 2008 1.1 hours 4 lumiblocks release 14.2.23.3 smk 369 hltps 390 lvl1ps 538
| en |
converted_docs | 014912 | {width="6.602777777777778in" height="0.75in"}
{width="2.3in" height="1.6909722222222223in"}
Iberville Street Entrance
All of our tastefully decorated guestrooms have 12' ceilings offering
the most spacious rooms in the French Quarter. All feature color TV with
movies, minibar, iron/ironing board, high-speed internet access, and
some feature French doors and balconies overlooking our garden or pool
courtyards or world-famous Bourbon Street.
{width="2.3291666666666666in"
height="1.8208333333333333in"}
**Lafitte Rooms A and B**
Celebrated Chef Kurtis Jantz prepares cuisine for all tastes from casual
fun to sophisticated elegance. Our banquet rooms and garden courtyards
are the perfect setting for an intimate dinner party, a wedding for 200
or cocktail reception for 300.
{width="2.2916666666666665in"
height="1.761111111111111in"}
**Pool and Pool Bar**
In the French Quarter, yet bordering Canal Street and the Central
Business District, Chateau Sonesta Hotel offers a perfect location for
both the leisure and business visitor. The hotel offers 251 guestrooms
and 11 suites, 3 restaurants and 3 bars including Ralph Brennan's Red
Fish Grill and Quint Davis' Storyville District Jazz Club
{width="2.2916666666666665in"
height="1.7722222222222221in"}
**Guestroom overlooking Courtyard**
Over 10,000 square feet of flexible meeting space can accommodate
meetings from 10 to 250 people. All meeting rooms are located on the
lobby level and feature high-speed internet access. With
state-of-the-art audio visual equipment and an Executive Business
Center, planning a meeting was never easier.
{width="2.3291666666666666in"
height="1.6722222222222223in"}
Orleans Room
The hotel offers many amenities including a heated swimming pool and
pool bar, fitness room (offered complimentary), room service and a full
service concierge, all of which will ensure an enjoyable stay with us.
| en |
markdown | 536477 | # Presentation: 536477
## “...intellectual freedom is essential to human society -- freedom to obtain and distribute information, freedom for open-minded and unfearing debate and freedom from pressure by officialdom and prejudices.” Andre Sakharov, 1968, “Reflections on progress, coexistence and intellectual freedom”
***Irving A. Lerch***
***APS Forum on International Physics***
***lerch@aps.org***
## Overview of the Visa Regime
***of approximately 30 million foreign visitors who enter the US each year, roughly a half million come as students on F, M and J visas. And approximately 175,000 of these come to study science***
***jointly directed by State and Homeland Security (visa authority is now shared between the departments)***
***"Patriot Law" has already authorized the implementation of the Student and Exchange Visitor Information System (SEVIS) to monitor those who come to the US under the Student Exchange and Visitor Program (SEVP). The Patriot Act has also imposed a two-tier review system over consular officers***
**Notes:**
The proposed Interagency Panel on Advanced Science Security seeks to impose a security regiment on the nation’s recruitment of S&T talent. Making such a system work within the uncertainties of the day will pose a formidable task. Already proposals for organizing the new Department of Homeland Security include provisions from removing authority over visas from the State Department. With the reorganization of INS, the potential for confusion and increased viscosity in the system poses a real danger to the health of the nation’s S&T enterprise.
## 4.4m, 26% rej.
- 263k, 20% rej.
- 2.6m, 32% rej.
- 216k, 25% rej.
## 342,113
- 586,323
**Net Contribution to U.S. Economy by**
**Foreign Students and their Families: $12,851,000,000**
*Source: Open Doors 2003, Institute of International Education Online Survey*
## What do the personal tragedies portend for the international and domestic enterprises?
- Students prevented from returning from foreign meetings or after attending to urgent family business (many denied or delayed at the outset).
- Colleagues unable to pursue major long-term research owing to visa restrictions.
- Colleagues subjected to summary imprisonment for minor violations of immigration laws.
- Colleagues denied or delayed visas to attend meetings (often after giving up their passports for unconscionably long periods).
- Colleagues at risk in authoritarian states denied sanctuary.
## 74,603
***74,603***
***51,519***
***8,076***
***12,801***
***64,757***
***6,238***
***10,432***
***34,803***
***6,595***
***9,982***
## AAU Summarizes 2003 Visa Survey, November 14, 2003:
**49% reported research delays**
**67% reported lengthening time to degree**
**28% reported classes without instructors**
**44% reported lost fellowships for foreign students**
**13% reported students missing major conferences**
**74% reported institutional financial loss**
**44% reported foreign students choosing another country**
## NAFSA/AAU/NASULGC Survey
**64% report steady or declining enrollments**
**36% indicate an increase (usually smaller than decline)**
**Reasons for decline:**
**69% noted increase in visa denials**
**65% visa delays (interview delays)**
**59% decrease in applications**
**32% delays for security advisories**
**25% applicant went to another country**
## Graduate school applications from international students declined 32% over the last year ... according to a Council of Graduate Schools survey. ... This survey generated responses from 113 graduate schools [which] enroll nearly one-half of all international graduate students in the U.S.
***Over 90% of U.S. graduate schools ... responding to the survey reported an overall decrease in international graduate student applications. ***
***Total international applications in the responding graduate schools for Fall 2004 declined 32% from Fall 2003.***
***76% reported declines from China and 58% reported declines from India, the two largest sending countries.***
***Forty-seven percent of responding institutions reported a decline from Korea, 33% a decline from Taiwan, 30% a decline from Western Europe, 31% a decline from the Middle East, and 36% from all other countries.***
***Thirty-two of the 50 research institutions with the largest international student ... reported particularly severe declines, with all but one reporting decreases in international graduate student applications. ***
***International applications declined across all major fields, but the most striking decreases came in engineering, physical sciences, and biological sciences. ***
***Among the top 50 research institutions, an even greater percentage reported declines in all major fields, compared to the full survey. Over 90% of these graduate schools reported decreases in international applications for engineering programs, and 80% for the physical sciences.***
## Before 9/11, 100,000 Chinese
***Before 9/11, 100,000 Chinese***
***Students took the TOEFL/year.***
***Since, the numbers dropped to***
***30,000 in 2002 and 10,000 this year.***
## Slide 11
## Slide 12
## Visa Problems for Delegates to the International Symposium in Lepton Photon Interactions Fermi Lab
- At LP-1999 held at Stanford, 12 of 16 invited Chinese citizens and 7 of 25 invited citizens of the former Soviet Union attended. At LP-2003 only one of about 20 invited Chinese and 5 of 20 invited Russians attended. Almost all of Russians who did attend traveled with multi-entry visa or were already in the US.
## Slide 14
## Conclusions/Inferences for BNL (Susan White-DePace, Brookhaven National Lab)
- Approximately 20% of users work at more than one facility
- The average percentage of non-US users is slightly less than 50%
- Approximately 13% of users come from sensitive countries
- Total number of users exceeds 10,000
## The International Connection: A Sketch
**The 3 weapons laboratories--Los Alamos, Lawrence Livermore and Sandia--received some 6,398 foreign visitors or assignees (stays from 30 days to 2 years) in 1998 including 1,824 visitors from sensitive countries.**
**In addition, employees traveled to foreign laboratories or scientific conferences encompassing 5,799 trips to include 1,814 trips to sensitive countries.**
***Result: enhanced access to the 70-75% unclassified work needed to progress in weapons-related research, open scientific research, and cooperative international programs.***
**Notes:**
The importance of exchange programs to the work of the weapons labs is clear in this overhead which illustrates the size of both the travel and visitors programs. Any abridgement of these programs cannot help but impose a deleterious burden on the productivity of the labs. Yet abridgements there have been.
## The Introduction of More Restrictive Measures
**New classifications for material already in the public domain.**
**Special identity badges for foreign nationals.**
**New restrictions on access to unclassified facilities.**
**Attempts to place non-classified facilities under restrictive controls.**
**Increased dependence on procedures of doubtful value--ie, polygraph testing.**
**New and more draconian classification procedures that threaten to restrict the distribution of scientific information.**
**Complex management schemes that further dissipate lines of responsibility and authority.**
**Impose security regimens on non-weapons labs. The “tier system” is now dead.**
**Notes:**
And as security considerations become the preeminent political and administrative focus, steps are proposed and instituted which threaten to further denigrate the scientific enterprise.
## Slide 18
| Laws | Executive Orders/ Advisories/Directives | Consequences |
| --- | --- | --- |
| 1994 Foreign Relations Security Act |
| Holds consular officials liable if terrorists slip in. |
|
| VISAS Mantis
| Technology theft/WMD Proliferation |
| 1996 INA
|
| Defines criminal penalties for consular misconduct |
|
| VISAS Condor
-Country Groups | National Security/Extends watch to certain countries |
| 2002 Enhanced Border Security and Visa Entry Reform Act | | Imposes border control (INS) on DHS |
|
| Terrorism List
Export Control Posts
Technology Alert List | 7 nations special scrutiny
Prevent proliferation
Military and Economic |
| 2002 Patriot Act
|
May 03 Memo Expanding personal interviews | SEVIS, Consular Authority split (State/DHS)
Everyone between 16 and 60
previous clearance irrelevant |
## LISTS
***State Sponsors of Terrorism list (Cuba, Libya, Iran, ******Iraq******, North Korea, Sudan and Syria)***
***Non-Proliferation Export Control Posts (China, India, Israel, Pakistan, and Russia***
***Visas Mantis (Technology, WMD)***
***Visas Condor List (classified countries list)***
***Technology Alert list contains 16 categories****** ******(munitions, warheads and projectiles, nuclear, missiles, aircraft and missile propulsion, navigation and guidance, chemical engineering and biotechnology, remote imaging and reconnaissance, advanced computers, materials, cryptography, lasers and directed energy systems, acoustic and sensors technologies, marine technology, robotics, ceramics, high performance metals and alloys)***
- Visas Mantis and Visas Condor
- Directives from the Secretary of State
**Notes:**
Thus domestic and international science policy is held hostage by a security system designed to run on “remote control.” Since the foreign service mechanisms are almost without S&T expertise, guidance is provided in the form of lists which vagaries and generalities can have devastating impact.
Consular officials are guided by directives published by the State Department. Visa Mantis, released during Secretary Albright’s tenure directed consular officials to seek guidance if applicants came from designated countries or sought to participate in exchanges on specific topics. Visa Condor, released by Secretary Powell, enlarged the watch list to include applicants from other countries.
## GAO Analysis of Visa Delays for Security Reviews Electronic Industries Alliance: “Unfortunately, the U.S.’s ability to adapt, compete and innovate alongside emerging workforces in countries such as China and India is threatened by a systematically weak education system, a dearth of R&D funding, visa policy that discourages the brightest foreign minds and a business climate heavy with regulatory and tax burdens. If the U.S. wants to remain the world’s innovation leader, we must adopt positive policy solutions, rather than isolationist or protectionist measures, to address these problems.”
**GAO Analysis of Visa Delays for Security Reviews**Electronic Industries Alliance:“***Unfortunately, the U.S.’s ability to adapt, compete and innovate alongside emerging workforces in countries such as China and India is threatened by a systematically weak education system, a dearth of R&D funding, visa policy that discourages the brightest foreign minds and a business climate heavy with regulatory and tax burdens. If the U.S. wants to remain the world’s innovation leader, we must adopt positive policy solutions, rather than isolationist or protectionist measures, to address these problems.”***
## Special Scrutiny
- The first group of individuals subject to Special Registration included:
**Iran, ****Iraq****, Libya, Sudan**, or **Syria**
- The second group of individuals subject to Special Registration included:
**Afghanistan, Algeria, Bahrain, Eritrea, Lebanon, Morocco, North Korea, Oman, Qatar, Somalia, Tunisia, United Arab Emirates**, or **Yemen**
- The third group of individuals subject to Special Registration includes:
**Pakistan **or **Saudi Arabia**
- The fourth group of individuals subject to Special Registration includes:
**Bangladesh, Egypt, Indonesia, Jordan, **or **Kuwait**
***These in addition to the Technology Alert Post countries***
## May 3, 2003, State Department Memo to Embassies: BORDER SECURITY ‐ WAIVER OF PERSONAL APPEARANCE FOR NONIMMIGRANT VISA APPLICANTS ‐ REVISION TO THE REGULATIONS
***the visa interview is a crucial tool—in many cases the key tool—in determining visa eligibility. ... we have revised substantially the Code of Federal Regulations and ... guidelines on when personal appearance and interview can be waived for nonimmigrant visa applicants. ******This is the next step in preparing for the eventual fingerprinting****** ...***
***the requirement for personal appearance for nonimmigrant visa applicants can in general be waived by a consular officer only for a person who the consular officer concludes presents no national security concerns requiring an interview and who: ******(5) Is an applicant who within twelve months of the expiration of the applicant's previously issued visa is seeking re‐issuance of a nonimmigrant visa in the same classification at the consular post of the alien's usual residence, and for whom the consular officer has no indication of visa ineligibility or noncompliance with U.S. immigration laws and regulations******. ... ******Let me emphasize strongly, however, that consular officers are not required to waive interview in such cases.***
## US-VISIT (United States Visitor and Immigrant Status Indicator Technology) Program
***automated entry/exit system to,***
- Collect, maintain, and share information, including biometric identifiers (fingerprints, photos), through a dynamic system, on foreign nationals ...
- Enhance traffic flow for individuals entering or exiting the U.S. for legitimate purpose ...
## US-VISIT Program
- The US-VISIT system ... information will be stored in databases maintained by DHS and the Department of State as part of an individual's travel record.
- The information in the US-VISIT system will be available to inspectors at ports of entry, special agents in the Bureau of Immigration and Customs Enforcement (ICE), adjudications staff at immigration services offices, U.S. consular offices, and other law enforcement agencies.
## Reaction of colleagues:
**“****This is an Orwellian nightmare. If a visit to Fermi Lab implies fingerprinting, I'll stay at home.”**
- *German colleague currently at FNAL*
## Slide 26
## Needed Changes
***Time limits for security reviews for visiting students and scholars (those subject to Visa Mantis and Visa Condor scrutiny).***
***Modify application of 214(b) for J-1, F-1 and B visa applications by scientific students and visitors.***
***Classify as "returning scholars" all employees, students and long-time visitors supported by government funds (DoE, NSF, NASA, etc). ***
***Extend parole by Bureau of Citizenship and Immigration Services of the Department of Homeland Security to students and scholars.***
***Consular officials should not be held liable for such post-hoc charges as “criminal negligence.”***
***Widen the visa waiver program to provide for extended visits for J-1 and H-1B scholars and their families.***
## Statement and Recommendations on Visa Problems: Harming America's Scientific, Economic, and Security Interests
- ***Problem***: Inefficient visa renewal process that causes lengthy delays. ***Recommendation***: Establish a timely process by which exchange visitors holding F and J visas can revalidate their visas, or at least begin the visa renewal process, before they leave the United States to attend academic and scientific conferences, visit family, or attend to personal business. A visa renewal process that allows individuals to at least initiate the process before leaving the country would greatly diminish, and in many cases eliminate, lengthy visa delays, and it would allow them to continue their studies and work uninterrupted.
- ***Problem****: *Lack of transparency and priority processing in the visa system. ***Recommendation****: *Create a mechanism by which visa applicants and their sponsors may inquire about the status of pending visa applications, and establish a process by which applications pending for more than 30 days are given priority processing. Implementing these measures would greatly add to the transparency of the visa process and would help to ensure that applications do not get buried at the bottom of the pile or lost.
- ***Problem***: Inconsistent treatment of visa applications. ***Recommendation***: Provide updated training of consular staff, establish clear protocols for initiating a Visas Mantis review, and ensure that screening tools are being used in the most appropriate manner. We recognize that the government is pursuing efforts to enhance training, and we encourage this. Consular staff need the best available tools and training to perform their vital responsibilities. Additional training and guidance for consular staff could greatly enhance security while simultaneously reducing the number of applications submitted for Visas Mantis reviews, thereby alleviating potential delays.
- ***Problem***: Repetitive processing of visa applications for those with a proven track record. ***Recommendation***: Revise visa reciprocity agreements between the United States and key sending countries, such as China and Russia, to extend the duration of visas each country grants citizens of the other, thereby reducing the number of times that visiting international students, scholars, and scientists must renew their visas. We recognize that renegotiating bilateral agreements is a time-consuming process, and we believe it should be pursued as a long-term measure that allows the government to focus its visa screening resources by reducing the number of visa renewals that must be processed.
- ***Problem***: Potential new impediment to international students, scholars, and scientists entering the U.S. created by proposed SEVIS fee collection mechanism. ***Recommendation***: Implement a fee collection system for the Student and Exchange Visitor Information System (SEVIS) that allows for a variety of simple fee payment methods that are quick, safe, and secure, including payment after the individual arrives in the United States.
**Notes:**
Statement published May 12 by a consortium of academic, scientific and engineering organizations.
## Why U.S. Leadership Will Be Challenged
***More nations are acquiring high-end innovation capabilities with concerted investment in research and development (R&D) and technical talent.****** Other nations are acquiring fast-follower capabilities to rapidly commercialize innovation originating elsewhere.***
***The supply of scientists, engineers and technicians is growing substantially faster abroad than in the United States.***
***The U.S. first-mover advantage in information technology (IT) is diminishing with aggressive IT investment and deployment overseas.***
**Notes:**
The challenge enunciated by the Council is clearly stated here. The US is losing its competitive advantage as scholars seek European and even Asian venues.
## Natural sciences and engineering doctoral degrees
***Europe Data not accurate before 1989***
**Notes:**
The U.S. is accounting for a declining share of all doctoral degrees awarded in natural science and engineering fields, as the numbers of such degrees awarded in other countries are growing more rapidly. The U.S. grants roughly 35% of its Ph.D.s to foreign students in all of the natural sciences and engineering (this is approximately 50% in the physical sciences). With the decline in foreign student recruitment, both European and Asian production of scientists is beginning to exceed production of such scholars in the U.S.
## Correlation between Federal R&D expenditures and bachelors’ student production in the physical sciences, math, and engineering 1953 to 2000
***Correlation between Federal R&D expenditures and bachelors’ student production in the physical sciences, math, and engineering 1953 to 2000***
## Growth trends in scientific and technical publications by region: 1986–99
**Notes:**
In the last decade of the 90s, both sub-Saharan Africa and Eastern Europe have declined as contributing sources to the scientific literature (and there has been a decline in US contributions as well). This is coincident with real losses in research support in these regions.
## Scientific publications: regional share of world output
**Notes:**
This figure demonstrates the overall status of the various regions as sources of intellectual publication. Note that in 1986 the largest contributor to the intellectual literature was the U.S. with almost 40% of the world total. By the end of the millennium, the U.S. contribution had declined with Europe occupying the dominant position. Eastern Europe has declined in response to economic exigencies. Very small contributions from developing regions have demonstrated little change with the exception of Latin America.
## The Dangers to the National Interest
**Stifle vital international exchange**
***non-defense research***
***defense-related research***
***visitors programs***
**Impair University and lab productivity and morale**
***create suspicion and resentment***
***institutionalize racism***
**Impose cosmetic solutions while ignoring the real threat**
***focus on ethnicity rather than deed***
***failure to implement meaningful reform***
**Denigrate standards of justice and equal protection**
**Sacrifice the future**
***recruitment***
***loss of experienced researchers***
***declines in appointments and visitors***
**Notes:**
Weapons development, safeguards, weapons stewardship, test ban, non-weapons research are all dependent upon international exchange. Unlike the immediate post-war period, a greater portion of work in the physical sciences is being accomplished outside the US. In addition, US programs are dependent upon immigrant and non-immigrant scientists.
Recruitment, retention and morale are becoming serious problems at all the labs--not simply the weapons labs. Affiliated universities also suffer as access becomes restrained.
And because of the growing suspicion that ethnicity is being used to prevent scholars from advancement, the numbers if Asian-American and naturalized US citizens applying for positions is declining. | en |
converted_docs | 537107 | STATEMENT OF
DR. P. PATRICK LEAHY
ASSOCIATE DIRECTOR FOR GEOLOGY
U.S. GEOLOGICAL SURVEY
U.S. DEPARTMENT OF THE INTERIOR
BEFORE THE
COMMITTEE ON NATURAL RESOURCES
SUBCOMMITTE ON ENERGY AND MINERAL RESOURCES
AND
SUBCOMMITTEE ON NATIONAL PARKS, FORESTS, AND PUBLIC LANDS
U.S. HOUSE OF REPRESENTATIVES
HEARING ON
THE FUTURE OF FOSSIL FUELS:
GEOLOGICAL AND TERRESTRIAL SEQUESTRATION OF CARBON DIOXIDE
MAY 1, 2007
Messrs. Chairmen and Members of the Subcommittees, thank you for the
opportunity to present testimony on terrestrial sequestration and
geologic capture and storage of carbon dioxide and their role in
reducing atmospheric carbon. In addition to these topics, I also plan to
discuss in my statement today the role of science in evaluating the
potential geologic storage capacity for industrial carbon dioxide and in
furthering our understanding of the carbon cycle.
**Introduction**
Let me begin by saying that the challenges of addressing carbon dioxide
accumulation in the atmosphere are significant. Fossil fuel usage, a
major source of carbon dioxide emissions to the atmosphere, will
continue in both industrialized and developing nations. Therefore, a
variety of strategies are being investigated to reduce emissions and
remove carbon dioxide from the atmosphere. Such strategies include the
facilitated sequestration of carbon from the air to terrestrial biomass,
including soils and the capture and storage of carbon dioxide in
geologic formations.
The current atmospheric carbon dioxide concentration is approximately
380 parts per million volume and rising at a rate of approximately 2
parts per million volume annually, according to the most recent
information from the Intergovernmental Panel on Climate Change (IPCC).
The fraction of carbon emissions from all sources that must be
eliminated or sequestered to impact the magnitude of climate change is
large. For example, to stabilize carbon dioxide concentrations at about
550 parts per million volume, the extent to which carbon dioxide
emissions would need to be reduced may be as much as 70 percent.
Reductions of this magnitude could involve implementation of several
mechanisms, including geologic storage and biological sequestration,
fuel shifts from fossil sources to renewable biological sources,
increased electricity generation from solar and wind systems and nuclear
power, and increased efficiency of power generation, transmission, and
end use. Each of these mechanisms has distinct geological,
hydrological, ecological, economic and social implications that should
be assessed on a wide range of scales, from molecular to basin scales,
to allow informed policy discussions and decisions on implementation and
deployment of technologies.
**Geologic Storage of Carbon**
The 2005 IPCC Special Report on *Carbon Dioxide Capture and Storage*
concluded that, in emissions reductions scenarios striving to stabilize
global atmospheric carbon dioxide concentrations at targets ranging from
450 to 750 parts per million volume, the global storage capacity of
geologic formations may be able to accommodate most of the captured
carbon dioxide. However, geologic storage capacity may vary on a
regional and national scale, and a more refined understanding of
geologic storage capacity is needed to address this knowledge gap.
Geological storage of carbon dioxide in porous and permeable rocks
involves injection of carbon dioxide into a subsurface rock unit and
displacement of the fluid or formation water that initially occupied the
pore space. This principle operates in all types of potential
geological storage formations such as oil and gas fields, deep saline
water-bearing formations, or coal beds. Because the density of injected
carbon dioxide is less than the density of formation water, carbon
dioxide will be buoyant in pore space filled with water and rise
vertically until it is retained beneath a nonpermeable barrier (seal).
A critical issue for evaluation of storage capacity is the integrity
and effectiveness of these seals.
**Terrestrial Carbon Sequestration**
Terrestrial carbon sequestration practices seek to effect the transfer
of carbon between the atmosphere and terrestrial biosphere (the earth
and the living organisms that inhabit it) to reduce atmospheric carbon
dioxide concentrations. Land management practices in the United States
can affect the transfer of carbon from terrestrial systems into the
atmosphere. Land conversion, especially deforestation, continues to be a
significant source of global carbon dioxide emissions. Good land
stewardship practices can reverse this and enhance biological uptake of
carbon dioxide from the atmosphere, an approach termed terrestrial
sequestration. Many of these practices, including tree planting and
conservation tillage, are widely adopted and well understood. The
Department of Agriculture is promoting the adoption of these practices
through conservation programs implemented under the Farm Bill. The
knowledge gained on the benefits of terrestrial sequestration will
improve our understanding of the duration and extent to which the
biological uptake of atmospheric carbon dioxide can be enhanced to
reduce atmospheric concentration of carbon dioxide.
**Role of the U.S. Geological Survey**
While the USGS currently has no experience assessing the national
geologic storage capacity, USGS-generated data and information were
included in the Carbon Sequestration Atlas of the United States and
Canada developed by the Department of Energy. In addition, our
experience with national and international assessments of natural
resources could allow USGS to develop geologically based methodologies
to assess the National capacity for geologic storage of carbon dioxide.
We envision the national geologic carbon dioxide storage assessment
methodology would be largely analogous to the peer-reviewed
methodologies used in USGS oil, gas, and coal resource assessments. In
addition, the USGS' knowledge of regional groundwater aquifer systems
and groundwater chemistry would allow USGS to develop methods to assess
potential carbon storage in saline aquifers. Previous studies have
postulated the existence of very large carbon dioxide storage capacities
in saline aquifers, but the extent to which these capacities can be
utilized remains unknown.
The USGS could create a scientifically based, multi-disciplinary
methodology for geologic carbon dioxide storage assessment that can be
consistently applied on a national scale. Some potential areas for
further study include understanding the capabilities of seals to retain
carbon dioxide and the role of abandoned wells that may act as migration
pathways for carbon dioxide and formation water; defining the potential
for mobilization of trace metals and organic materials by carbon dioxide
reactions with minerals or dissolution of organic compounds; and
understanding the role of bacteria and other microorganisms in
water-rock-carbon dioxide interactions relevant to storage.
There are also a number of potential issues for further study pertaining
to terrestrial sequestration, including the natural processes that
affect carbon cycling. It is now widely recognized that the global
carbon cycle and climate varied together, before human influence, as
interactive components in a highly complex system of global feedbacks.
These feedbacks have profound implications for the response of climate
to anthropogenic carbon dioxide emissions, and for the potential
response of the carbon cycle to changes in climate.
Along with our partners in the Department of Agriculture and other
agencies, ongoing USGS research addresses these issues. In particular,
USGS research on soil carbon dynamics focuses on soil development and
the buildup and stabilization of soil organic matter, a large carbon
reservoir in the terrestrial biosphere, which play key roles in water
distribution, and in turn control both sediment transport and carbon
production and respiration. This research is critically important in
explaining the processes affecting the flow of carbon dioxide from
soils. The response of soils to human land use is a significant
component in the global carbon dioxide budget, and their response to
climate change may cause significant feedback on a global scale. Land
use -- particularly agriculture -- significantly alters patterns of
terrestrial carbon storage and transport, nutrient cycles, and erosion
and sedimentation. Current models of the terrestrial carbon cycle do not
adequately account for the interactions among changes in erosion,
sedimentation, and soil dynamics. Additional research on variable scales
(local to global) of carbon flow would provide a more thorough
understanding of the carbon cycle.
**Conclusion**
It is clear that addressing the challenge of reducing atmospheric carbon
dioxide and understanding the effect of global climate change is a
complex issue with many interrelated components. A better understanding
of geologic storage potential for carbon dioxide combined with research
to understand the implications of terrestrial carbon sequestration on
the carbon cycle would provide a scientific foundation for future
decisions regarding carbon management. We believe additional study of
geologic and terrestrial opportunities will better prepare decision
makers as they deal with these issues. Thank you for the opportunity to
present this testimony. I am pleased to answer questions you and other
Members of the Committee might have.
| en |
converted_docs | 028950 | **Before the**
**Federal Communications Commission**
**Washington, D.C. 20554**
In re Application of )
)
**Michael Radio Group,** )
**Assignor** )
)
and ) File No. BAPH-20001101ABD
)
**Clear Channel Broadcasting Licenses, Inc.,** )
**Assignee** )
)
For Assignment of the Construction Permit )
of Station KDAM(FM),[^1] Hope, North Dakota ) Facility ID No. 88502
**MEMORANDUM OPINION AND ORDER**
**Adopted: September 30, 2004 Released: December 2, 2004**
By the Commission: Commissioners Copps and Adelstein dissenting and
issuing a joint statement.
1\. The Commission has before it an Application for Review filed by
Monterey Licenses, L.L.C. ("Monterey") on June 25, 2001. Monterey seeks
review of the May 24, 2001, decision by the Media Bureau ("Bureau")
denying Monterey's petition to deny and granting an application to
assign the construction permit of station KDAM(FM) (at the time,
KCHY(FM)), Hope, North Dakota, from Michael Radio Group ("MRG") to Clear
Channel Broadcasting Licensees, Inc. ("Clear Channel").[^2] On July 12,
2001, Clear Channel filed an Opposition to the Application for Review,
to which Monterey filed a Reply on July 20, 2001. The Commission also
has before it Monterey's January 15, 2002, motion to stay the
effectiveness of the Staff Decision and Clear Channel's January 22,
2002, Opposition to the motion. For the reasons set forth below, we deny
the Application for Review and dismiss the Motion for Stay as moot.[^3]
2\. Monterey is the licensee of several radio stations that compete with
Clear Channel's stations in the Fargo, North Dakota, market.[^4]
Monterey reiterates the arguments it made to the staff, as follows: (1)
in the Fargo, North Dakota-Moorhead, Minnesota metropolitan area as
defined by Arbitron (the "Fargo Metro"), Clear Channel controlled six of
the market's fourteen stations, including station KRVI(FM), Detroit
Lakes, Minnesota, and was thus already at its statutory ownership
limit;[^5] (2) an alternative prediction methodology to plot the contour
for KRVI(FM) is justified by the anomalous terrain in the area and
results in KRVI(FM) being counted against Clear Channel's ownership
limit; (3) Clear Channel already controlled 53.2% of the advertising
revenue in the Fargo Metro, and thus *any* increase in Clear Channel's
market share when KDAM(FM) commenced operations would be problematic;
and (4) the Commission's definition of a "radio market" does not comport
with economic reality and the KDAM(FM) application should be deferred
until the Commission has completed its rule making on defining radio
markets.[^6] In its Application for Review, Monterey requests that the
Commission "reverse the Bureau's decision and deny the MRG/Clear Channel
assignment application or at a minimum defer action on the application
until the Commission resolves \[the issues raised in *Market Definition
NPRM*\]."
3\. The staff correctly rejected Monterey's contention that the KDAM(FM)
acquisition violates the numerical limits contained in the Commission's
local radio ownership rule. Under the ownership rules then in effect,
both the definition of a "radio market" and the number of stations
counted as being in that market were based on signal contours, not on an
Arbitron-based or other geographic-based methodology. As in its Petition
to Deny, Monterey argues that the transaction's compliance with the
ownership limits should be evaluated in the context of the Fargo
Arbitron Metro, where only 14 commercial stations are listed as "home."
In a 14-station market, Clear Channel may only own up to five stations,
with up to three in the same service. Monterey's reliance on the
Arbitron-defined Fargo Metro to calculate the number of stations in the
market is simply misplaced, however. Although the Commission adopted in
mid-2003 a geographic-based methodology for stations in Arbitron rated
markets,[^7] it did not do so until long after the staff had approved
(on May 24, 2001) and the parties had consummated (on January 22, 2002)
the sale of KDAM(FM). We do not generally apply changes in ownership
rules retroactively so as to require divestiture of existing
combinations, as suggested by Monterey, and we did not do so when we
revised the local radio rule.[^8] Thus, examining the subject
transaction under the contour-based methodology set forth in the local
radio ownership rule in effect at the time of the staff decision, we
confirm the staff's finding that the KDAM(FM) acquisition complied with
that rule.
4\. At the same time that Monterey argues for use of the Arbitron Metro,
it reiterates that the Commission should apply an alternative signal
contour prediction methodology for one station because the terrain at
issue differs widely from that assumed by the normal prediction
methodology.[^9] Monterey acknowledges that, under the Commission's
definition of a "radio market" in effect at the time the subject
application was analyzed, Clear Channel's KRVI(FM), Detroit Lakes,
Minnesota, is not counted as one of the stations Clear Channel owns in
the same market as the subject stations.[^10] Use of the alternative
methodology, Monterey contends, demonstrates that the principal
community contour of KRVI(FM) overlaps that of KDAM(FM) and, thus, that
the two stations are in the same "market." Consequently, Monterey
argues, Clear Channel's acquisition of KDAM(FM) will exceed both the
total number of stations and the number of FM stations permitted under
Section 73.3555(a).
5\. In declining to consider Monterey's use of an alternative prediction
methodology to demonstrate that KRVI(FM) should be considered part of
the subject "market" here \-- a methodology that would carry Clear
Channel over the number of FM stations, but not over the total number of
stations, it can own in the market \-- the staff stated that it had
previously rejected the use of supplemental engineering showings in the
context of multiple ownership compliance demonstrations, whether from
petitioners[^11] or from applicants.[^12] Consistent with that
precedent, the staff was not persuaded that a departure from the
standard prediction methodology was warranted for KRVI(FM). Monterey
argues that the staff decisions cited by the Bureau, such as *Battle
Ground,*[^13] can be afforded little or no weight in light of the
Commission's acceptance of alternative contour-prediction methodologies
to demonstrate that television stations' signals do not overlap for
purposes of applying the multiple ownership rules. Monterey cites three
Commission decisions in cases involving television stations \--
*Heritage Media Services, Inc.*, *John H. Phipps, Inc.*, and *Southern
Oregon Broadcasting Co.*[^14] \-- in support of its position.
6\. It is our current and express policy not to apply an alternative
prediction methodology in the context of evaluating compliance with the
local radio ownership rule.[^15] In the *Technical Streamlining NPRM,*
discussing specifically the point-to-point ("PTP") alternative
prediction methodology, we explained our position as follows:
> In instances involving major radio markets, multiple ownership studies
> often involve dozens of stations. Selective application of the PTP
> method to some, but not all, stations in a relevant market would
> invite disputes where contradictory results would occur. Conversely,
> in light of the sometimes radical differences between PTP calculations
> and standard predicted contours, utilizing the PTP method for all
> stations could affect these ownership studies in ways not anticipated
> when the current multiple ownership rules were adopted. We believe
> that, in most instances, the use of the PTP methodology could
> significantly alter the definition of stations included in a
> particular market and use of this methodology in this context would
> serve no useful function in administering our ownership policies.[^16]
We are unpersuaded that, because we accepted the use of an alternative
prediction methodology in the context of the television duopoly rules in
*Heritage, Phipps,* and *Southern Oregon,*[^17] we must or should do so
here. In each of the cases cited by Monterey, the Commission accepted
and analyzed an alternative contour prediction showing to determine
whether or not there was overlap between two television stations. To
determine how many stations are "in" a radio market using alternative
contours, we would need to study those contours for dozens of
stations.[^18] As we stated in the *Technical Streamlining NPRM*, this
could affect radio ownership studies in ways not anticipated when the
current ownership rules were adopted.[^19] We therefore agree with the
staff's conclusion that it was not appropriate to accept Monterey's
supplemental engineering study demonstrating overlap between KDAM(FM)
and KRVI(FM) based on an alternative contour-prediction model.[^20]
7\. We also disagree with Monterey's claim that the transaction raised
antitrust concerns warranting denial or deferral of action on the
application. The staff's independent analysis at the time[^21] indicated
that Clear Channel already controlled stations in the Fargo Metro
garnering 53.6% of the advertising revenue share, and that the combined
revenue share of Clear Channel and Monterey, the second largest radio
owner in the market, was 92.6%. The staff further noted that the
post-transaction revenue shares would remain the same: as an unbuilt
station, KDAM(FM) had no reported revenue share. Rather, KDAM(FM)
constituted new capacity in the Fargo Metro that would provide new
choices for listeners and advertisers.
8\. Since grant of the subject assignment application, Clear Channel's
advertising revenue share has fallen to 50.1%, notwithstanding the
addition of KDAM(FM) to its station group in the Fargo Metro, and the
combined revenue share of Clear Channel and Monterey has decreased to
90.4%.[^22] Although Clear Channel maintains a significant market
position in the Metro today, it appears, according to the BIA data base,
that Forum Communications, Tom Ingstad, Triad Broadcasting, and Vision
Media offer sufficient alternative sources so that advertisers can "buy
around" a number of the formats offered by Clear Channel. These
opportunities should constrain the ability of Clear Channel to exercise
market power against advertisers in the Fargo Metro. Additionally, the
rivalry offered by the non-Clear Channel stations should provide an
incentive for Clear Channel to compete by pricing its advertising
efficiently. Such rivalry may also result in Clear Channel's
introduction of innovative advertising services and packages that will
improve the overall quality of radio advertising services available in
the Fargo Metro. In view of these conclusions, we find that Monterey has
not raised a substantial and material question of fact warranting
further inquiry on this issue.
9\. Monterey's final claim is that staff action on the application was
contrary to our pronouncements on deferral in the *Market Definition
NPRM*. In support, Monterey cites, *inter alia,* to the following
excerpt:
As a general matter, we will continue to process applications under the
existing standards, unless and until they are changed in this
proceeding. In cases raising concerns about how we count the number of
stations a party owns in a market, however, we will defer decision
pending resolution of that issue in this proceeding. As we concluded in
the 1998 Biennial Review Report, the "shifting market definition" in our
counting methodology "appears illogical and contrary to Congress'
intent."[^23]
Monterey argues that the cited language indicates that we will defer
action on any case in which, for example, the Commission's computation
of the number of stations in a "market" differs from the count listed by
Arbitron or BIA.[^24] This is incorrect. As explained in the Staff
Decision,[^25] pending the conclusion of the radio market rule making
proceeding, the Commission will defer acting on applications if
compliance with the local radio ownership rule depends on the inclusion
of certain attributable station interests of the applicant in the total
count of stations in the market.[^26] There is no such issue in this
case.
10\. Accordingly, the June 25, 2001, Application for Review filed by
Monterey Licenses, L.L.C. IS DENIED, and its January 15, 2002, Motion
for Stay IS DISMISSED AS MOOT.
FEDERAL COMMUNICATIONS COMMISSION
Marlene H. Dortch
Secretary
DISSENTING STATEMENT OF
COMMISSIONERS MICHAEL J. COPPS AND JONATHAN S. ADELSTEIN
*Re:* *Michael Radio Group, Assignor and Clear Channel Broadcasting
Licenses, Inc., Assignee For Assignment of Construction Permit of
Station KDAM(FM), Hope, North Dakota*
In this case, the majority approves Clear Channel's acquisition of a
radio station in a market in which Clear Channel already controls over
50 percent of the market and Clear Channel and the next largest owner
together control over 90 percent. Given this extreme level of market
concentration, we cannot support grant of this transfer absent
additional information on the public interest benefits of the
transaction. Yet, here, the majority has not even considered the public
interest benefits or harms. We are troubled by the trend toward greater
and greater consolidation of the media, particularly in smaller radio
markets, and this Commission's acceptance of such levels of
concentration with hardly any analysis. For a robust marketplace of
ideas to survive, every community deserves to have a diversity of
sources of information available to its members - not just those who
live in the largest cities. We find that the amount of concentration at
issue here is potentially very harmful to competition, to the listening
public and to America\'s deeply held values of localism and diversity.
[^1]: The call sign of the subject station was changed from KCHY(FM) to
KDAM(FM) effective October 8, 2002.
[^2]: *See Letter to Paul A. Cicelski, Esq. and Christopher L. Robbins,
Esq.* (MMB May 24, 2001) ("Staff Decision").
[^3]: Monterey moves that we stay the effectiveness of the Staff
Decision to preserve the *status quo* and prevent any "irreparable
injury" resulting from Clear Channel's acquisition of KDAM(FM)
pending final action on the Application for Review. Given our action
here denying the Application for Review, we need not reach the
motion for stay. *See Rebecca Radio of Marco*, 5 FCC Rcd 2913, 2914
n.5 (1990).
[^4]: Monterey is the licensee of stations KQWB(FM) and KVOX(FM),
Moorhead, Minnesota; KLTA(FM), Breckenridge, Minnesota; KPFX(FM),
Fargo, North Dakota; and KQJD(AM) and KQWB(AM), West Fargo, North
Dakota. Clear Channel is the licensee of three radio stations
licensed to Fargo (KFGO(AM)/-FM and WDAY-FM) as well as three
stations licensed to nearby communities: KVOX(AM), Moorhead,
Minnesota, KULW(FM), Kindred, North Dakota, and KRVI(FM), Detroit
Lakes, Minnesota.
[^5]: *See* 47 C.F.R. § 73.3555(a) (promulgated pursuant to Section
202(b)(1) of the Telecommunications Act of 1996).
[^6]: When Monterey filed its Petition to Deny, the Commission's rule
making proceeding focusing on radio market definition was pending.
*See Definition of Radio Markets*, MM Docket No. 00-224, 15 FCC Rcd
25077 (2000) ("*Market Definition NPRM*"). That proceeding was
subsequently incorporated into an omnibus rule making addressing
various broadcast cross-ownership and multiple ownership rules. The
Commission released its Order in that omnibus proceeding on July 2,
2003. *See* *2002 Biennial Regulatory Review, (\"Ownership Report
and Order\"),* 18 FCC Rcd 13620 (2003), *aff\'d in part and remanded
in part, Prometheus Radio Project, et al. v. FCC,* 373 F.3d 372
(2004) (*\"Prometheus Remand Order\"*), *stay modified on
rehearing*, No. 03-3388 (3d Cir. Sept. 3, 2004)
(*\"Prometheus Rehearing Order\"*). The *Notice of Proposed Rule
Making* included in the *Ownership Report and Order* sought comment
on developing a geographic-based methodology to evaluate local radio
ownership in markets not rated by Arbitron, and that proceeding
remains pending. On September 3, 2003, the United States Court of
Appeals for the Third Circuit, which is hearing the consolidated
appeals of the *Ownership Report and Order*, granted a stay of the
effective date of the new ownership rules adopted in that *Order,*
stating that "the prior ownership rules remain in effect pending
resolution of those proceedings." *Prometheus Radio Project, et al.
v. F.C.C.*, No. 03-3388, slip op. at 3 (3d Cir. Sept. 3, 2003) (*per
curiam*). In the *Prometheus Rehearing Order*, however, the Court of
Appeals lifted the stay for the local radio ownership rule
revisions, including using Arbitron Metro markets to define local
markets.
[^7]: *See Ownership Report and Order, supra,* 18 FCC Rcd at 13725-30 ¶¶
273-86.
[^8]: *See, e.g., id.* at 13807-09 ¶¶ 482-86 (grandfathering existing
station combinations). *See also FCC v. National Citizens Committee
for Broadcasting*, 436 U.S. 775, 802-815 (1978) (upholding
Commission decision to require divestiture of newspaper/broadcast
combinations only in egregious cases).
[^9]: Monterey indicates that the subject terrain is "quite flat,"
sloping from the transmitter site to the Red River Valley in which
Fargo lies.
[^10]: Clear Channel's multiple ownership study, using the Commission's
prescribed contour-prediction methodology, demonstrates that the
contour for KRVI(FM) does not overlap that of any other station
proposed to be commonly owned by Clear Channel as a result of this
transaction. Clear Channel therefore did not include KRVI(FM) in the
defined radio market in this case. Monterey correctly notes that the
contours of KDAM(FM) and KRVI(FM), computed according to the
standard prediction methodology set forth in 47 C.F.R. § 73.313, are
separated by 0.2 kilometers.
[^11]: *See WIIZ(FM), Battle Ground, Indiana*, 10 FCC Rcd 3159 (MMB
1995) ("*Battle Ground*").
[^12]: *See WZNY(FM), Augusta, Georgia*, 13 FCC Rcd 9467 (MMB 1998)
("*Augusta*").
[^13]: *See supra* note 11.
[^14]: *Heritage Media Services, Inc.*, 13 FCC Rcd 5644 (1998); *John H.
Phipps, Inc.*, 11 FCC Rcd 13053 (1996); *Southern Oregon
Broadcasting Co.*, 9 F.C.C.2d 241 (1967).
[^15]: *See 1998 Biennial Regulatory Review -- Streamlining of Radio
Technical Rules in Parts 73 and 74 of the Commission's Rules*,
*Notice of Proposed Rule Making and Order,* 13 FCC Rcd 14849, 14865
(1998) ("*Technical Streamlining NPRM*") (seeking comment on a
supplemental point-to-point ("PTP") prediction model designed to
provide a more accurate prediction of FM radio interfering signal
contours and stating our proposal not to allow use of the PTP
methodology in multiple ownership showings).
[^16]: *Id*. In a subsequent order, we deferred adoption of our proposed
PTP methodology on the basis of comments raising issues regarding
the accuracy and reliability of the proposed signal propagation
prediction model. *See 1998 Biennial Regulatory Review --
Streamlining of Radio Technical Rules in Parts 73 and 74 of the
Commission's Rules*, *Second Report and Order*, 15 FCC Rcd 21649,
21652-53 ¶¶ 7-9 (2000).
[^17]: *See supra* note 14.
[^18]: Monterey proposes the use of an alternative contour analysis only
with respect to KRVI(FM). That is exactly the kind of "selective"
use which the staff appropriately rejected in *Augusta, supra* note
13.
[^19]: T*echnical Streamlining NPRM*, 13 FCC Rcd at 14865.
[^20]: In refusing to accept Monterey's supplemental showing, we do not
intend to give premature effect to the proposal in our *Technical
Streamlining NPRM* but merely to emphasize that rule making's
recognition of existing practice. *See supra* note 15 and
accompanying text.
[^21]: The Commission had not yet adopted the *Order* in which it
announced an "Interim Policy" establishing a specific framework for
evaluating the competition aspects of proposed radio transactions.
*See Rules and Policies Concerning Multiple Ownership of Radio
Broadcast Stations in Local Markets*, 16 FCC Rcd 19861, 19894-97 ¶¶
84-89 (2001).
[^22]: A number of factors may explain Clear Channel\'s reduced revenue
share, such as, for example, Tom Ingstad\'s new station KDJZ-FM,
which began its operations in the Fargo Metro in 2001, and the
improved performance of Forum Communications\' WDAY(AM), which rose
to become the fourth-highest rated station in the latest ratings
period.
[^23]: *Market Definition NPRM,* 15 FCC Rcd at 25082 ¶ 14.
[^24]: Application for Review at 8.
[^25]: *See* Staff Decision at 6.
[^26]: *E.g., Pine Bluff Radio, Inc.,* 14 FCC Rcd 6594 (1999).
| en |
converted_docs | 288479 | +-------+---+------------------------------------------------------+---+
| # O | # | | # |
| | # | | |
| ## | # | | |
| | # | | # |
| | | | |
| | A | | |
| | L | | # |
| | | | # |
| | 2 | | |
| | 0 | | |
| | 0 | | |
| | 1 | | |
| | - | | |
| | - | | |
| | 4 | | |
+-------+---+------------------------------------------------------+---+
| | * | | |
| | * | | |
| | O | | |
| | C | | |
| | C | | |
| | A | | |
| | D | | |
| | V | | |
| | I | | |
| | S | | |
| | O | | |
| | R | | |
| | Y | | |
| | L | | |
| | E | | |
| | T | | |
| | T | | |
| | E | | |
| | R | | |
| | * | | |
| | * | | |
+-------+---+------------------------------------------------------+---+
| ## Co | | | |
| mptro | | | |
| ller | | | |
| of th | | | |
| e Cur | | | |
| rency | | | |
| | | | |
| > Adm | | | |
| inist | | | |
| rator | | | |
| > of | | | |
| > Nat | | | |
| ional | | | |
| > | | | |
| Banks | | | |
+-------+---+------------------------------------------------------+---+
| # | | ## Identity Theft and Pretext Calling | |
| # Sub | | | |
| ject: | | | |
+-------+---+------------------------------------------------------+---+
**TO:** Chief Executive Officers of All National Banks, Department and
Division Heads, and All Examining Personnel
**I. PURPOSE**
This advisory letter informs national banks about two areas of consumer
bank fraud---identity theft and pretext calling---and advises them about
measures to prevent and detect these types of fraud. The
Gramm--Leach--Bliley Act (GLBA), enacted in 1999, directs the federal
banking agencies (the Agencies) to ensure that banks have policies,
procedures, and controls in place to prevent the unauthorized disclosure
of customer financial information and to deter and detect fraudulent
access to such information.[^1] The Agencies recently adopted guidelines
for the safeguarding of customer information by financial
institutions.[^2] The advisory letter supplements those guidelines by
focusing on the protection of customer information specifically against
identity theft and pretext calling.
Identity theft is the fraudulent use of an individual's personal
identifying information. Often, identity thieves will use another
individual's personal information such as a social security number,
mother's maiden name, date of birth, or account number to fraudulently
open new credit card accounts, charge existing credit card accounts,
write checks, open bank accounts or obtain new loans. They may obtain
this information through a number of means, including
- Stealing wallets that contain personal identification information
and credit cards,
```{=html}
<!-- -->
```
- Stealing financial institution statements from the mail,
```{=html}
<!-- -->
```
- Diverting mail from its intended recipients by submitting a change
of address form,
```{=html}
<!-- -->
```
- Rummaging through trash for personal data,
```{=html}
<!-- -->
```
- Stealing personal identification information from workplace records,
or
```{=html}
<!-- -->
```
- Intercepting or otherwise obtaining information transmitted
electronically.
Pretext calling is a fraudulent means of obtaining an individual's
personal information. Pretext callers may contact financial institution
employees, posing as their customers, in order to access customers'
personal account information. Information obtained from pretext calling
may be sold to debt collection services, attorneys, and private
investigators for use in court proceedings. Identity thieves may also
engage in pretext calling to obtain personal information for use in
creating fraudulent accounts.
This advisory letter provides background information on identity theft
and pretext calling and informs banks about: (1) relevant federal laws;
(2) measures to take to reduce their risk of loss and protect their
customers against these types of fraud; (3) how to report to law
enforcement known or suspected federal criminal violations related to
these types of fraud; and (4) the importance of consumer education to
prevent fraud and assist individuals who have been victims of pretext
calling and identity theft.[^3]
**II. BACKGROUND**
According to the Federal Bureau of Investigation, identity theft is one
of the fastest growing white-collar crimes in the nation.[^4] More than
500,000 consumers are victimized each year by identity theft. This
growing crime has a devastating effect on financial institution
customers and a detrimental impact on the banks.[^5] Four of the top
five consumer complaints regarding identity theft involve financial
services---new credit card accounts opened, existing credit card
accounts used, new deposit accounts opened, and newly obtained
loans.[^6] Banks absorb much of the economic losses from bank fraud
associated with the theft of their customers' identities. Individuals
who become victims of identity theft also pay, at a minimum,
out-of-pocket expenses to clear their names and may spend numerous hours
trying to rectify their credit records.[^7]
Identity theft may go undetected for months and even years. Victims of
identity theft may not realize that someone has stolen their identity
until they are denied credit or until a creditor attempts to collect an
unpaid bill.
Pretext calling is also difficult to detect. While information brokers
and private investigators routinely advertise on the Internet and
elsewhere their ability to locate and provide specific information about
individual bank accounts, banks and their customers are likely to be
unaware that they have been the victims of pretexting (*i.e.,* the use
of some form of pretext to obtain customer information). Unless the
pretexting ultimately leads to identity theft, it may go undetected
altogether.
**III. SUMMARY OF RELEVANT FEDERAL LAWS**
**Identity theft---**In 1998, Congress passed the Identity Theft and
Assumption Deterrence Act (18 USC 1028) (the Act). The Act makes it a
crime to knowingly use, without lawful authority, a means of
identification of another person with the intent to commit a crime,
among other things. The unauthorized use of another individual's name,
social security number, or date of birth to apply for a credit card is
punishable by fine or imprisonment under this Act. The Act also requires
the Federal Trade Commission (FTC) to establish a central complaint
system to receive and refer identity theft complaints to appropriate
entities, including law enforcement agencies and national credit
bureaus.
Schemes to commit identity theft may also involve violations of other
federal statutes such as the prohibition against fraudulent tax refund
claims (18 USC 287), credit card fraud (18 USC 1029), computer fraud (18
USC 1030), mail fraud (18 USC 1341), wire fraud (18 USC 1343), or bank
fraud (18 USC 1344). A number of states also have passed laws related to
identity theft.
**Pretext calling**---The GLBA prohibits the making of false or
fraudulent statements or representations to an officer, employee, or
agent of a financial institution, or to a customer of a financial
institution, to obtain customer information (15 USC 6821). The GLBA also
prohibits anyone from requesting a person to obtain customer information
of a financial institution, knowing that the person will use fraudulent
methods to obtain information from the institution. Section 523 of the
GLBA (15 USC 6823) imposes criminal penalties for knowing and
intentional violations of these provisions.
While this statute is generally aimed at persons who victimize banks and
their customers by attempting to obtain customer information through
pretexting, banks could themselves be in violation of this statute if
they use the services of any person who obtains customer information in
violation of the statute. Although the statute maintains that an
institution must "know" that the person will use artifice to obtain
customer information, safe and sound banking practices dictate that a
bank exercise reasonable diligence in selecting a third party to gather
customer information. In this regard, banks should familiarize
themselves with the methods used by third parties to collect customer
information on their behalf. Banks should not the use the services of
anyone the bank suspects may be engaging in pretexting to obtain
customer information.
**Security standards**---Section 501(b) of the GLBA (15 USC 6801(b))
requires the Agencies to establish appropriate standards for banks
relating to the administrative, technical, and physical safeguards of
customer information. Banks are expected to take appropriate measures in
accordance with the Guidelines for Safeguarding Customer Information to
protect customer information against identity theft and pretext calling.
**IV. MEASURES TO PREVENT IDENTITY THEFT AND PRETEXT CALLING**
**A. Identity theft**
Identity thieves use a number of methods to obtain financial services in
the name of another individual. For instance, an identity thief may
request that a bank change the address on an existing credit card
account, thereby diverting billing statements from the true account
holder. Alternatively, an identity thief may order new checks on an
existing account and have them sent to a mail drop, rather than the true
account holder's address. An identity thief may use the personal
information of another individual to apply for a new checking or credit
card account.
Banks should employ a variety of methods to safeguard customer
information and reduce the risk of loss from identity theft, including
(1) verifying personal information to establish the identity of
individuals applying for financial products, (2) establishing adequate
procedures to detect possible fraud in new accounts, (3) verifying the
legitimacy of change of address requests on existing accounts, and (4)
maintaining adequate security standards.
**1. Verification procedures for new accounts**
To reduce the risk of fraudulent applications, banks should establish
verification procedures to ensure the accuracy and veracity of
application information. In conjunction with their existing account
opening procedures, banks should consider how best to independently
verify information provided on account applications to detect incidents
of identity theft. Verification of personal information may be
accomplished in a number of ways. Some alternatives to consider include:
(a) *positive verification* to ensure material information provided by
an applicant is accurate; (b) *logical verification;* and (c) *negative
verification* to ensure information provided has not previously been
associated with fraudulent activity.[^8]
*a. Positive verification* entails consulting third-party sources to
assess the veracity of information submitted by a consumer. For example,
an identity thief may provide the true name of an individual and a
correct phone number, but an erroneous address. An institution could
detect this discrepancy simply by checking a telephone directory. Under
appropriate circumstances, a bank may obtain an individual's consumer
report that would permit more detailed verification. Banks should
consider calling a customer to confirm that the individual has opened a
credit card or checking account, using a telephone number that has been
verified independently. A phone call to a customer may alert an
individual that his or her identity has been stolen. Additionally, a
bank could contact an applicant's employer. An identity thief may
provide the name of a legitimate employer, but may not provide the
correct telephone number. A bank should attempt to contact an employer
using an independently verified telephone number. Contacting an employer
may expose a fraudulent application.
b\. *Logical verification* entails assessing the consistency of
information presented in an application. Such steps may reveal
inconsistencies in the information provided by an applicant. For
instance, a bank could verify if the zip code and telephone area code
provided on the application cover the same geographical area. Products
currently available from service providers can assist banks in verifying
logical zip and area codes.
c\. *Negative verification* entails ensuring that information provided
on an application has not previously been associated with fraudulent
activity.
**2. Other new account procedures**
Consumer reports can be an important source for preventing fraud. When
processing an application for a new account, a bank may rely on a
consumer report from a consumer reporting agency. A consumer report of a
victim of identity theft may be issued with a fraud alert.[^9] When a
bank has an automated system for credit approval, these systems should
be designed to identify fraud alerts. Banks should not process an
application when there is an existing fraud alert without contacting the
individual in accordance with instructions that usually accompany a
fraud alert *(i.e.,* a victim's statement), or otherwise employing
additional steps to verify the individual's identity. The bank should
have procedures in place to share a fraud alert across its various lines
of business.
Consumer reports also may be a source for detecting fraud. Signs of
possible fraudulent activity that may appear on consumer reports include
late payments on a consumer's accounts in the absence of a previous
history of late payments, numerous credit inquiries in a short period of
time, higher-than-usual monthly credit balances, and a recent change of
address in conjunction with other signs.
Finally, when an applicant fails to provide all requested information on
an application, a bank should not process the incomplete application
without further explanation.
**3. Verifying change of address requests**
A change of address request on an existing account may be a sign of
fraudulent activity. A bank should verify the customer information
before executing an address change and send a confirmation of the
address change to both the new address and the address of record. If an
institution gets a request for a new credit card or new checks in
conjunction with a change of address notification, the bank should
verify the request with the customer within a reasonable period of time
after receiving the request.
**4. Security standards**
The Guidelines for Safeguarding Customer Information require banks to
implement a comprehensive information security program that includes
appropriate administrative, technical, and physical safeguards for
customer information. Information security programs must be designed to
ensure the security and confidentiality of customer information, protect
against anticipated threats or hazards to the security or integrity of
the information, and protect against unauthorized access to or use of
such information that could result in substantial harm or inconvenience
to customers.
Banks should take steps to secure the transmission and storage of
electronic information to prevent identity thieves from gaining access
to such information. This may include the use of encryption, firewalls,
and other electronic data security systems and preventative measures.
Identity thieves may also seek access to information that an institution
discards. For instance, identity thieves may rummage through trash to
collect customer information (dumpster diving). A bank should implement
appropriate measures to restrict access to its customer records, such as
by shredding documents, to protect against dumpster diving and other
forms of unauthorized access.
Banks and their service providers should implement appropriate controls
and procedures to limit access to customer records. Because insiders may
be identity thieves a bank should consider conducting background checks
for its employees, in accordance with applicable law. Where indicated by
its risk assessment, a bank should also monitor its service providers to
confirm that they have implemented appropriate measures to limit access
to customer records.[^10]
**B. Pretext calling**
Pretext callers use pieces of personal information to impersonate an
account holder in order to gain access to that individual's account
information. Armed with personal information, such as an individual's
name, address, and social security number, a pretext caller may try to
convince a bank's employee to provide confidential account information.
While it may be difficult to spot, there are measures banks can take to
reduce the incidence of pretext calling, such as limiting the
circumstances under which customer information may be disclosed by
telephone.[^11]
The Guidelines for Safeguarding Customer Information require banks to
establish written policies and procedures to control risks to customer
information, and consider access controls on customer information as
part of these policies and procedures. Banks should take appropriate
precautions against the disclosure of customer information to
unauthorized individuals such as (1) limiting the circumstances under
which employees may disclose customer information over the telephone,
(2) training employees to recognize and report fraudulent attempts to
obtain customer information, and (3) testing to determine the
effectiveness of controls designed to thwart pretext callers.
**1. Limiting telephone disclosures**
There are a number of ways in which banks may limit access to customer
information. One way is to permit employees to release information over
the telephone only if the individual requesting the information provides
a proper authorization code.[^12] The code should be different than
other commonly used numbers or identifiers, such as social security
numbers, savings, checking, loan, or other financial account numbers, or
the maiden name of the customer's mother. The authorization code should
be unique to, and capable of being changed readily by, the authorized
account holder. To be most effective, the authorization code should be
used in conjunction with other customer and account identifiers.
Another means of preventing unauthorized disclosures of customer
information is to use a caller identification system (*i.e.,*
CallerID™). If the telephone number displayed differs from that in the
customer's account records, it may be an indication that the request is
not legitimate and the employee should not disclose the requested
account information without taking additional steps to verify that the
true customer is making the request. In the absence of a caller
identification system, banks could require employees who receive calls
for account information to ask the caller for the number from which he
or she is calling, or for a call-back number. If the individual refuses
to provide the number, or it doesn't match the information in the
customer's records, the employee should not disclose the information
without additional measures to verify that the caller is the true
customer.[^13]
**2. Employee training**
Banks should train staff to recognize unauthorized or fraudulent
attempts to obtain customer information. In addition to an employee's
inability to match a caller's telephone number with that on file, there
may be other indicators of a pretext call. For instance, a caller who
cannot provide all relevant information requested, or a caller who is
abusive, or who tries to distract the employee, may be a pretext caller.
Employees should be trained to recognize such devices and, under such
circumstances, protect customer information through appropriate
measures, such as by taking additional steps to verify that the caller
is a bona fide customer.
Employees should be trained to implement the bank's written policies and
procedures governing the disclosure of customer information, and should
be informed not to deviate from them. Moreover, employees must know to
whom and how to report suspicious activity that may be a pretext call.
Banks may have a fraud department or contact to whom the employee
reports suspicious activities, or may establish another means for
reporting possible fraud. Known or suspected federal criminal violations
should be reported to law enforcement in accordance with the procedures
discussed below.
**3. Testing**
Banks should test the key controls and procedures of their information
security systems and consider using independent staff or third parties
to conduct unscheduled pretext phone calls to various departments to
evaluate the institution's susceptibility to unauthorized disclosures of
customer information. Any weaknesses should be addressed through
enhanced training, procedures, or controls, or a combination of these
elements.
**V. REPORTING SUSPECTED IDENTITY THEFT AND PRETEXT CALLING**
OCC regulations currently require banks to report all known or suspected
criminal violations to law enforcement and the OCC by the use of the
Suspicious Activity Report ("SAR").
Criminal activity related to identity theft or pretext calling has
historically manifested itself as credit or debit card fraud, loan or
mortgage fraud, or false statements to the bank, among other things.
Presumably, banks have been reporting such known or suspected criminal
violations through the use of the SARs, in accordance with existing
regulations.
As a means of better identifying and tracking known or suspected
criminal violations related to identity theft and pretext calling, a
bank should, in addition to reporting the underlying fraud (such as
credit card or loan fraud) on a SAR, also indicate within the SAR that
such a known or suspected violation is the result of identity theft or
pretext calling. Specifically, when identity theft or pretext calling is
believed to be the underlying cause of the known or suspected criminal
activity, banks should, consistent with the existing SAR instructions,
complete a SAR in the following manner:
- In Part III, Box 35, of the SAR check all appropriate boxes that
indicate the type of known or suspected violation being reported
and, **in addition,** in the "Other" category, write in "identity
theft" or "pretext calling," as appropriate.
```{=html}
<!-- -->
```
- In Part V of the SAR, in the space provided for the narrative
explanation of what is being reported, include the grounds for
suspecting identity theft or pretext calling in addition to the
other violation being reported.
```{=html}
<!-- -->
```
- In the event the only known or suspected criminal violation detected
is the identity theft or pretext calling, then write in "identity
theft" or "pretext calling," as appropriate, in the "Other" category
in Part III, Box 35, and provide a description of the activity in
Part V of the SAR.
Consistent with the SAR instructions, in situations involving violations
requiring immediate attention, such as when a reportable violation is
ongoing, a bank should immediately notify, by telephone, the OCC and
appropriate law enforcement, in addition to filing a timely suspicious
activity report.
**VI. CUSTOMER ASSISTANCE**
**Teaching prevention**
Educating consumers about preventing identity theft and identifying
potential pretext calls may help reduce their vulnerability to these
fraudulent practices. Banks should consider making available to their
customers brochures, newsletters, or notices posted in their lobbies or
on their Web sites describing preventative measures consumers can take
to avoid becoming victims of these types of fraud. Banks are strongly
encouraged to inform their customers of the following precautionary
measures that law enforcement recommends to protect against identity
theft and pretext calling:
*Do not give personal information, such as account numbers or social
security numbers, over the telephone, through the mail, or over the
Internet unless you initiated the contact or know with whom you are
dealing.*
*Store personal information in a safe place and tear up old credit card
receipts, ATM receipts, old account statements, and unused credit card
offers before throwing them away.*
*Protect your PINs and other passwords. Avoid using easily available
information like your mother's maiden name, your birth date, the last
four digits of your social security number, your phone number, etc.*
*Carry only the minimum amount of identifying information and the number
of credit cards that you need.*
*Pay attention to billing cycles and statements. Inquire of the bank if
you do not receive a monthly bill; it may mean the bill has been
diverted by an identity thief.*
*Check account statements carefully to ensure all charges, checks, or
withdrawals were authorized.*
*Guard your mail from theft. If you have the type of mailbox with a flag
to signal the box contains mail, do not leave bill payment envelopes in
your mailbox with the flag up. Instead, deposit them in a post office
collection box or at the local post office. Promptly remove incoming
mail.*
*Order copies of your credit report from each of the three major credit
bureaus once a year to ensure they are accurate. The law permits the
credit bureaus to charge \$8.50 for a copy of the report (unless you
live in a state that requires the credit bureaus to provide you with one
free copy of your report annually).*
*If you prefer not to receive preapproved offers of credit, you can opt
out of such offers by calling 1-888-5-OPT OUT.*
*If you want to remove your name from many national direct mail lists,
send your name and address to:*
*DMA Mail Preference Service*
*P.O. Box 9008*
*Farmingdale, NY 11735-9008*
*If you want to reduce the number of telephone solicitations from many
national marketers, send your name, address and telephone number to:*
*DMA Telephone Preference Service*
*P.O. Box 9014*
*Farmingdale, NY 11735-9014.*
**Assistance for Victims**
There are a number of measures banks can take to assist victims of such
fraud. These include:
\(1\) having trained personnel respond to customer calls regarding
identity theft or pretext calling;
\(2\) determining if it is necessary to close an account immediately
after a customer reports unauthorized use of that account, and issuing
the customer a new credit card, ATM card, debit card or checks, as
appropriate. Where a customer has multiple accounts with an institution,
the institution should assess whether any other account has been the
subject of potential fraud; and
\(3\) educating customers about appropriate steps to take if they have
been victimized.
The following are measures banks may advise their customers to take if
they are the victims of identity theft.
*Contact the fraud departments of each of the three major credit bureaus
to report the identity theft and request that the credit bureaus place a
fraud alert and a victim's statement in your file. The fraud alert puts
creditors on notice that you have been the victim of fraud and the
victim's statement asks them not to open additional accounts without
first contacting you. The following are the telephone numbers for the
fraud departments of the three national credit bureaus: Trans Union:
1-800-680-7289; Equifax: 1-800-525-6285; Experian: 1-888-397-3742.*
*You may request a free copy of your credit report. Credit bureaus must
provide a free copy of your report if you have reason to believe the
report is inaccurate because of fraud and you submit a request in
writing.*
*Review your report to make sure no additional fraudulent accounts have
been opened in your name, or unauthorized changes made to your existing
accounts. Also, check the section of your report that lists "inquiries"
and request that any inquiries from companies that opened the fraudulent
accounts be removed.*
*Contact any financial institution or other creditor where you have an
account that you think may be the subject of identity theft. Advise them
of the identity theft. Request that they restrict access to your
account, change your account password, or close your account if there is
evidence your account has been the target of criminal activity.*
*File a report with your local police department.*
*Contact the FTC's Identity Theft Hotline toll-free at 1-877-ID-THEFT
(438-4338). The FTC puts the information into a secure consumer fraud
database and shares it with local, state, and federal law enforcement
agencies.*
The above measures are contained in a consumer brochure available on the
OCC's Web site at www.occ.treas.gov/idtheft.pdf. Banks may download this
information in the form of a trifold brochure and provide it to their
customers.
Questions relating to this advisory should be directed to Amy Friend,
assistant chief counsel, at (202) 874-5200.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Nanette G. Goulet
Acting Deputy Comptroller
Community and Consumer Policy
**APPENDIX: LIST OF OCC ISSUANCES REGARDING INFORMATION SECURITY**
- Interagency Guidelines Establishing Standards for Safeguarding
Customer Information, 66 *Fed. Reg.* 8616, 8632 (February 1, 2001),
to be codified at 12 CFR Part 30, App. B
```{=html}
<!-- -->
```
- OCC Alert 2000-09:Protecting Internet Addresses of National Banks
(July 19, 2000)
```{=html}
<!-- -->
```
- OCC Bulletin 2000-14: Infrastructure Threats--Intrusion Risks (May
15, 2000)
```{=html}
<!-- -->
```
- OCC Alert 2000-01: Internet Security: Distributed Denial of Service
Attacks (February 11, 2000)
```{=html}
<!-- -->
```
- "Internet Banking" booklet in *Comptroller's Handbook* (October
1999)
```{=html}
<!-- -->
```
- OCC Bulletin 99-9: Infrastructure Threats from Cyber-Terrorists
(March 15, 2000)
```{=html}
<!-- -->
```
- Check Fraud--A Guide to Avoiding Losses (February 2000)
```{=html}
<!-- -->
```
- OCC Bulletin 98-38: Technology Risk Management: PC Banking (August
24, 1998)
```{=html}
<!-- -->
```
- OCC Advisory Letter 98-11: Pretext Phone Calling (August 20, 1998)
```{=html}
<!-- -->
```
- OCC Advisory Letter 91-4 :Use of Social Security Numbers for
Automated Call Systems (July 24, 1991)
```{=html}
<!-- -->
```
- OCC Banking Circular 229: Information Security (May 31,1988)
```{=html}
<!-- -->
```
- Banking Circular 226 :End-User Computing (January 25, 1988)
[^1]: 15 USC 6825. GLBA also contains specific prohibitions against
obtaining customer information from a financial institution by false
pretenses. *Id.* at 6821.
[^2]: *See* Interagency Guidelines for Establishing Standards for
Safeguarding Customer Information, 66 *Fed. Reg.* 8616 (February 1,
2001). The OCC's standards are codified at 12 CFR Part 30, App. B
(hereinafter, referred to as the "Guidelines for Safeguarding
Customer Information").
[^3]: At the end of the advisory letter is an appendix that lists other
OCC guidance regarding information security.
[^4]: Reasons cited for this increase in identity theft include the
increased availability of personal information in the marketplace,
the ability of identity thieves to use this information to, for
instance, apply for credit under cover of anonymity afforded by
remote channels, and the nearly instantaneous and ready availability
of credit. *See, e.g.,* Testimony of the United States Secret
Service to the House Committee on Banking and Financial Services,
September 13, 2000.
[^5]: For example, the American Bankers Association (ABA) 1998 Check
Fraud Survey found that \$3 out of every \$4 lost by a community
bank to check fraud was due to some form of identity theft. In its
2000 Check Fraud Survey, the ABA found that *attempted* check fraud
doubled in the past two years, exceeding \$2.2 billion dollars. The
survey further indicated that one-third of fraud cases and fraud
losses were due to forgery.
[^6]: On November 1, 1999, the Federal Trade Commission (FTC)
established a toll-free telephone hotline,
1-877-ID-THEFT (438-4338), for consumers to report identity theft
and seek counseling. Information from complainants is stored in a
central database and used as an aid in law enforcement and
prevention. In testimony delivered on September 13, 2000, at a
hearing on identity theft held by the House of Representatives
Committee on Banking and Financial Services, the FTC reported that
its identity theft hotline received over 1000 calls a week in July
and August 2000. More recent public statements by FTC officials
indicate that the number of calls to the hotline have more than
doubled since then, to over 2000 calls a week. *See,* *e.g.,*
Statement of Jodie Bernstein, director of the FTC's Bureau of
Consumer Protection, to the President's Information Technology
Advisory Committee, February 7, 2001. Information in the FTC
database collected from hotline calls for the year 2000 indicate the
most common forms of identity theft reported to the FTC include:
*Credit card fraud---*Fifty percent of complainants reported that a
credit card account had been opened in their name, or an identity
thief had taken over their existing account. Seventy-one percent of
these complaints involved the establishment of a new account;
twenty-five percent involved the takeover of an existing account.
(Roughly four-and-a-half percent of complaints in this category were
unspecified.)
*Checking or savings account fraud---*Sixteen percent of
complainants reported a savings or checking account had been opened
in their name or fraudulent checks had been written on existing
accounts. Forty-nine percent of these complaints involved using
unauthorized checks; twenty-seven percent involved establishing new
checking accounts; seventeen percent involved unauthorized
electronic fund transfers. (About seven percent of the complaints in
this category were unspecified).
*Loan fraud*---Nine-and-a-half percent of complainants reported the
identity thief had obtained a loan in their name.
*See* FTC Web site at www.consumer.gov/idtheft/. Click on FTC
workshop and then on report charts.
[^7]: For example, under Regulation Z, in instances involving identity
theft, a consumer could incur liability for the unauthorized use of
the consumer's credit card account up to \$50. Under Regulation E, a
consumer's liability for unauthorized electronic fund transfers
involving his or her account varies depending upon the precise
circumstances of the unauthorized use and the consumer's timeliness
in reporting unauthorized transactions or the loss or theft of an
access card, number, or other device.
[^8]: Some databases used for verification purposes may be provided by
consumer reporting agencies and their use may raise issues under the
Fair Credit Reporting Act.
[^9]: A fraud alert is a statement that accompanies an individual's
consumer report informing creditors that an individual's account has
been the subject of fraud. Each of the major credit bureaus will
voluntarily place a fraud alert on a consumer report upon request.
[^10]: For additional information on managing relationships with
third-party service providers, *see* FFIEC guidance on technology
outsourcing, "Risk Management of Outsourced Technology Services,"
(November 28, 2000).
[^11]: A bank should consider appropriate procedures and limits for
disclosing information through any communication channel (*e.g.,*
e-mail or wireless devices) that the institution uses. As the use
and acceptance of e-mail, Internet banking, and electronic account
statements increase, banks should develop procedures to verify the
identity of the sender of a message. In many cases e-mail may not be
an appropriate channel to communicate certain types of account
information. E-mail can be easily forged, hijacked, or read by
people other than the intended recipient. Additionally, a forger may
be difficult to trace particularly if the message is relayed through
intermediate mail servers.
[^12]: *See, e.g.,* OCC Advisory Letter 98-11 (August 20, 1998).
[^13]: There may be other circumstances in which a caller is seeking
access to customer account information, such as a merchant
attempting to verify whether the bank's customer has sufficient
funds to cover a check. Banks should not permit their employees to
provide a customer's account information without taking steps to
verify the identity of the caller. For instance, banks could direct
their employees to request a call back number to verify the
merchant's identity. Additionally, where a bank uses an automated
telephone response system to verify funds availability, the system
should be password protected.
| en |
all-txt-docs | 163496 | IML-2 Public Affairs Status Report #05
6:00 p.m. CDT, July 10, 1994
2/6:17 MET
Spacelab Mission Operations Control
Marshall Space Flight Center
The experiment-packed second International Microgravity Laboratory mission
is staying "remarkably near schedule" after two days in orbit, according to
Mission Manager Lanny Upton. Crew members and ground controllers worked
together to complete a variety of experiments and resolve some of the
challenges associated with keeping a complex science payload up and running.
Payload Commander Rick Hieb successfully adjusted a communications cable
this morning to establish data downlink from the Japanese life sciences
equipment. The repair allowed the Japanese team to receive information from
their Real-Time Radiation Monitoring Device for the first time in the flight.
The device actively measures the high-energy cosmic radiation which enters the
Spacelab in orbit, then transmits those measurements to the ground. Signals
also are being transmitted to remote centers for comparison with current
radiation information, such as optical and X-ray observations. The IML-2
device is a first step toward creation of a space weather-forecasting network
which eventually could warn astronauts on long flights to take shelter from
radiation storms.
Payload Specialist Chiaki Mukai reported that the medaka fish in the
Animal Aquatic Experiment Unit are more active than they had been the first day
of the mission, but they still seem disoriented in microgravity. She counted
10 medaka eggs in the aquarium and gave the fish their first scheduled feeding.
Mukai made the first videotapes of fruit flies in Dr. Roberto Marco's study of
microgravity's effect on the aging process. Scientists have observed that
flies age more quickly in space than on Earth. This experiment tests a theory
that premature aging is linked to increased activity as the flies attempt to
move in microgravity, along with excessive respiration.
Mission Specialist Don Thomas completed an experiment in the Slow Rotating
Microscope Centrifuge, or NIZEMI, facility that studies how a green algae
called chara responds to varying levels of gravity. "We knew from sounding
rocket flights that gravity-sensing crystals in the plants would move from
their normal position, but we didn't know how long they would keep moving or
how far they would go. One surprise was that the movement stopped at a certain
place, suggesting there must be something which dictates how far the crystals
can move," said Co-investigator Dr. Brigitte Buchen, of the University of Bonn,
Germany. "I admire the speed and certainty with which crew members have
selected the best cells for study under the NIZEMI microscopes," she added.
The next two NIZEMI experiments searched for gravity thresholds of a simple
plant organism called Euglena gracilis and a unicellular organism called
Loxodes straitus. Knowing how simple organisms respond to gravity can help
scientists interpret behavioral responses in more complex organisms and even
humans.
Early this morning, scientists used the Electromagnetic Containerless
Processing Facility (or TEMPUS, for its German name) to study an oscillating
sphere of melted gold. "We got some very interesting measurements of viscosity
and surface tension above the melting point," said Dr. Georg Lohoefer, a
colleague of Principal Investigator Dr. Ivan Egry. Scientists can deduce the
viscosity, or internal friction, of the liquid by the rate at which the drop
returned to a spherical shape after being disturbed. Surface tension, the
force that keeps a liquid together in a drop, can be determined by the
frequency at which the sample oscillated before it stabilized to a sphere. A
better understanding of the properties of liquid metals is of interest to
electronics and manufacturing industries as well as to theoretical scientists.
The TEMPUS team decided not to melt their next sample, a nickel/tin alloy, when
video views from the top of the experiment chamber revealed that the metal
sphere was not centered in the sample cage.
TEMPUS is the first electromagnetic containerless processing facility to
fly in space for more than a few minutes. As is often the case with any
complex, new space hardware, the team is fine-tuning methods for controlling
their equipment during its initial days of operation in orbit. "We expected we
would have to complete calibration of this facility during the mission, since
there is no way to do it in gravity on Earth," said IML-2 Program Scientist Dr.
Brad Carpenter. After recalibration, another experiment which uses a gold and
copper alloy to study viscosity and surface tension went on as planned.
The mission's first Critical Point Facility experiment drew to a close this
afternoon after 43 hours of operation. Designed by Dr. Hermann Klein of the
German Space Agency, the investigation aims to determine how long it takes a
fluid to stabilize, or reach equilibrium, after it has been disturbed. Klein
studied these density equilibration time scales in normal fluids aboard German
Spacelabs D-1 and D-2. On this mission, he is making similar observations in a
fluid near its critical point, where it behaves like a liquid and a gas at the
same time. At that point, a small interference may cause large changes.
According to Co-investigator Dr. Rainer Nhle, it appears stabilization took
longer than had been expected. If this holds true after post-flight analysis,
it could affect the way future investigations are designed. Nhle said IML-2
controllers gave his team more than double the real-time video they had
expected, greatly increasing the scientific outcome.
Hieb spent part of the afternoon as the subject of a Lower Body Negative
Pressure Experiment. His lower body was encased in a fabric bag, sealed at the
waist, in which a partial vacuum can be created. Mukai monitored his blood
pressure and heart rate as pressure within the bag was slightly lowered, then
raised again. This so-called negative pressure pulls fluids back into the
legs. Mukai is now taking her turn as test subject . The tests will be
repeated on both crew members three more times during the mission to monitor
their adaptation to space flight.
| en |
markdown | 678453 | # Presentation: 678453
## FEMA USFA
## ASSISTANCE TO FIREFIGHTERS GRANT PROGRAM
- NUMBER OF APPLICATIONS PACKAGES RECEIVED
- APPLICATIONS/
- CATEGORIES ENTERED IN DATA-BASE
- OVER 19,775
- AS OF 5/31/01
- 30,583
- DOLLAR AMOUNT OF GRANT REQUEST RECEIVED
- $3,156,198,390.85
## DOLLAR AMOUNT RECEIVED FOR EACH CATEGORY
- FIREFIGHTING VEHICLES
- PERSONAL PROTECTIVE EQUIPMENT
- 134 M CAREER
- 1.934 B VOL/COMB
- 2.068 B TOTAL
- 38.1 M CAREER
- 391.3 M VOL/COMB
- 429.4 M TOTAL
## DOLLAR AMOUNT RECEIVED FOR EACH CATEGORY
- FIREFIGHTING EQUIPMENT
- HEALTH AND WELLNESS
- 68.2 M CAREER
- 339.7 M VOL/COMB
- 407.9 TOTAL
- 26.3 M CAREER
- 25.5 M VOL/COMB
- 51.8 M TOTAL
## DOLLAR AMOUNT RECEIVED FOR EACH CATEGORY
- FIRE PREVENTION
- TRAINING
- 24.5 M CAREER
- 47.3 M VOL/COMB
- 71.8 M TOTAL
- 33.4 M CAREER
- 74.7 M VOL/COMB
- 108.1 M TOTAL
## TOTAL NUMBER OF DISQUALIFIED APPLICATIONS 167
## United States
**United States**
**Fire Administration**
**NETC Management**
**And Operations**
**National Fire**
**Data Center**
**National Fire**
**Academy**
**National Fire**
**Programs**
## Slide 10
## U. S. Fire
**U. S. Fire**
**Administrator**
**Chief Operating**
**Officer**
**Data Collection and**
**Analysis**
**Applied Research and**
**Technology**
**Information**
**Dissemination**
**National Fire**
**Data Center**
**National**
**Fire**
**Academy**
**National Fire**
**Programs**
**On-Campus**
**Off-Campus**
**Response**
**Mitigation**
**Intelligent**
**Risk**
**Consequence**
**Management**
**Community**
**Risk**
**Human Behavior-**
**Professional Dev.**
**NETC**
**Management & **
**Operations**
**Educational &**
**Academic Support**
**Operations &**
**Facility Support**
## Operational Objectives for the Next 5 Years
- Reduce the loss of life from fire related hazards by 15%.
** ****-**** ****By reducing by 25% the loss of life of **** ****the age group 14 years old and below.**
** ****-**** ****By reducing by 25% the loss of life of **** ****the age group 65 years old and above.**
** ****-**** ****By reducing by 25% the loss of life of **** ****firefighters.**
## Operational Objectives for the Next 5 Years
**2500 communities will have a comprehensive multi-hazard risk reduction plan led by or including the local fire service.**
**To respond appropriately in a timely manner to emergent issues.** | en |
markdown | 489833 | # Presentation: 489833
## Formation of an Interactive Plant Outreach Database with Integration of Clinostat Data for Space Life Sciences Education
- Rachel Naegele1, Chinyere Nwokeabia2, Peter Chetirkin3, William Payne4
- 1University of Hawaii Manoa, 2California State University, Long Beach, 3Dynamac Corporation, 4Matrix Information Systems Incorporated
## INITIAL DESCRIPTION
- An interactive plant outreach database (IPOD) would increase the accessibility of data to researchers, teachers and the general public. To demonstrate how future experiments can be integrated into IPOD, a 5 week experiment using clinostats was performed. The clinostats tested the effects of simulated microgravity upon *Brassica rapa* and the growth characteristics of BIONA, a Russian made substrate.
## MAIN STORY
- Educational outreach is a very important aspect of NASA. One such endeavor by the Space Biology Outreach Program (SBOP) is the formation of an interactive plant outreach database (IPOD). IPOD would pull the experimental data and results from Biomass Production Chamber (BPC) experiments and other experiments grown in environmental growth chambers (EGCs). To demonstrate this integration, two students from NASA’s Spaceflight and Life Sciences Training Program conducted a 5 week experiment using clinostats. The experiment tested the difference between two versions of BIONA and *Brassica rapa* growth in clinostats. The clinostats were divided into 4 groups (3 bottles in each): static control, static experimental, vertical experimental and horizontal experimental (Fig. 1). A square of BIONA was added to each bottle as well as three *Brassica rapa* seeds. The plants were grown to maturity and harvested. Measurements of plant height, leaf and flower count, and mass were taken for each bottle. The measurements were examined for existing trends and characteristics (Fig.2). The information from this experiment was integrated into the database and made accessible to teachers, students and researchers. SBOP is also providing the same materials to teachers. Teachers will be able to perform similar experiments in their classrooms, and students will be able to add their data to IPOD and compare it with existing data.
- This research was conducted as part of the 2004 Spaceflight and Life Sciences Training Program funded by the National Aeronautics and Space Administration. The authors recognize the support of the Dynamac Corporation, the NASA Spaceflight and Life Sciences Training Program Academic Partner Alliance and the United States Department of Agriculture.
## Figure 1. Experimental setup with clinostat and static groups
**Vertical experimental treatment**
**Horizontal experimental treatment 90****°**** to gravity**
**Static control treatment**
**Static experimental treatment**
- Figure 2. Comparison of the water loss between Static BIONA V3 and Static control BIONA V4 | en |
all-txt-docs | 383427 | Douglas Isbell
Headquarters, Washington, DC. Sept. 17, 1997
(Phone: 202/358-1753)
Diane Ainsworth
Jet Propulsion Laboratory, Pasadena, CA
(Phone: 818/354-5011)
Bill Steigerwald
Goddard Space Flight Center, Greenbelt, MD
(Phone: 301/286-7277)
RELEASE: 97-204
MARS GLOBAL SURVEYOR DETECTS MARTIAN MAGNETIC FIELD AS AEROBRAKING
BEGINS
Scientists have confirmed the existence of a planet-wide
magnetic field at Mars using an instrument on-board NASA's Mars
Global Surveyor orbiter, as the spacecraft began to circle and
study the planet from a highly elliptical orbit.
"Mars Global Surveyor has been in orbit for only a few days,
yet it already has returned an important discovery about the Red
Planet," said Vice President Al Gore. "This is another example of
how NASA's commitment to faster, better, cheaper Mars exploration
that began with Mars Pathfinder is going to help answer many
fundamental questions about the history and environment of our
neighboring planet, and the lessons it may hold for a better
understanding of life on Earth."
The spacecraft's magnetometer, which began making
measurements of Mars' magnetic field after its capture into orbit
on Sept. 11, detected the magnetic field on Sept. 15. The
existence of a planetary magnetic field has important implications
for the geological history of Mars and for the possible
development and continued existence of life on Mars.
"Preliminary evidence of a stronger than expected magnetic
field of planetary origin was collected and is now under detailed
study," said Dr. Mario H. Acuna, principal investigator for the
magnetometer/electron reflectrometer instrument at NASA's Goddard
Space Flight Center, Greenbelt, MD. "This was the first
opportunity in the mission to collect close-in magnetic field
data. Much more additional data will be collected in upcoming
orbits during the aerobraking phase of the mission to further
characterize the strength and geometry of the field. The current
observations suggest a field with a polarity similar to that of
Earth's and opposite that of Jupiter, with a maximum strength not
exceeding 1/800ths of the magnetic field at the Earth's surface."
This result is the first conclusive evidence of a magnetic
field at Mars. "More distant observations obtained previously by
the Russian missions Mars 2,3 and 5 and Phobos 1 and 2 were
inconclusive regarding the presence or absence of a magnetic field
of internal origin," said Acuna.
The magnetic field has important implications for the
evolution of Mars. Planets like Earth, Jupiter and Saturn generate
their magnetic fields by means of a dynamo made up of moving
molten metal at the core. This metal is a very good conductor of
electricity, and the rotation of the planet creates electrical
currents deep within the planet that give rise to the magnetic
field. A molten interior suggests the existence of internal heat
sources, which could give rise to volcanoes and a flowing crust
responsible for moving continents over geologic time periods.
"A magnetic field shields a planet from fast-moving,
electrically charged particles from the Sun which may affect its
atmosphere, as well as from cosmic rays, which are an impediment
to life," Acuna said. "If Mars had a more active dynamo in its
past, as we suspect from the existence of ancient volcanoes there,
then it may have had a thicker atmosphere and liquid water on its
surface."
It is not known whether the current weaker field now results
from a less active dynamo, or if the dynamo is now extinct and
what the scientists are observing is really a remnant of an
ancient magnetic field still detectable in the Martian crust.
"Whether this weak magnetic field implies that we are
observing a fossil crustal magnetic field associated with a now
extinct dynamo or merely a weak but active dynamo similar to that
of Earth, Jupiter, Saturn, Uranus and Neptune remains to be seen,"
Acuna said.
Mars Global Surveyor's magnetometer discovered the outermost
boundary of the Martian magnetic field -- known as the bow shock --
during the inbound leg of its second orbit around the planet, and
again on the outbound leg.
The discovery came just before Mars Global Surveyor began its
first aerobraking maneuver to lower and circularize its orbit
around Mars, said Glenn Cunningham, Mars Global Surveyor project
manager at NASA's Jet Propulsion Laboratory (JPL), Pasadena, CA.
"This first 'step down' into the upper atmosphere was
performed in two stages," Cunningham said. "On Sept. 16, during
the farthest point in the spacecraft's orbit, called the apoapsis,
the spacecraft fired its main engine for 6.5 seconds, slowing
Global Surveyor's velocity by 9.8 miles per hour (4.41 meters per
second). This maneuver lowered the spacecraft's orbit from 163
miles (263 kilometers) to 93 miles (150 kilometers) above the
surface of the planet.
At its closest approach to Mars this morning, known as the
periapsis, the spacecraft dipped into the upper fringes of the
Martian atmosphere for 27 seconds, allowing the drag on its solar
panels to begin the long aerobraking process of circularizing its
orbit."
Mars Global Surveyor will continue aerobraking through the
Martian atmosphere for the next four months, until its orbit has
been circularized and it is flying about 234 miles (378
kilometers) above the Martian surface. All systems and science
instruments onboard the spacecraft continue to perform normally
after six days in orbit around the red planet.
Additional information about the magnetic field discovery and
the Mars Global Surveyor mission is available on the World Wide
Web by accessing the JPL home page at:
http://www.jpl.nasa.gov
or at the Goddard Space Flight Center magnetometer site at:
http://mgs-mager.gsfc.nasa.gov
Meanwhile, NASA's Hubble Space Telescope (HST) has continued
monitoring the atmospheric conditions on Mars to help planning for
the Mars Global Surveyor aerobraking activity. The latest HST
Mars image, taken Sept. 12 with the Wide Field Planetary Camera 2
under the direction of Phil James of the University of Toledo and
Steve Lee of the University of Colorado, is available on the
Internet at the following URLs:
http://oposite.stsci.edu/pubinfo/PR/gif/mars0609.gif (GIF),
http://oposite.stsci.edu/pubinfo/PR/jpeg/mars0609.jpg (JPEG)
and via links in:
http://oposite.stsci.edu/pubinfo/PR/97/31.html
Mars Global Surveyor is the first mission in a sustained
program of robotic Mars exploration, known as the Mars Surveyor
Program. The mission is managed by the Jet Propulsion Laboratory
for NASA's Office of Space Science, Washington, DC. JPL's
industrial partner is Lockheed Martin Astronautics, Denver, CO,
which developed and operates the spacecraft. JPL is a division of
the California Institute of Technology, Pasadena, CA.
| en |
all-txt-docs | 178061 | June 2006
DRAFT ENVIRONMENTAL ASSESSMENT
REPLACEMENT OF THE ST. GEORGE ISLAND STATE PARK RESTROOMS AND BATH HOUSES
FEMA Orlando Long Term Recovery Office
FEMA-1595-DR-FL
TABLE OF CONTENTS
Description
Page
TABLE OF CONTENTS i
Section 1 - Introduction 1
1.1 Project Authority 1
1.2 Project Location 1
1.3 Purpose and Need 2
1.4 Existing Facility 2
1.5 Project Description 3
Section 2 - Alternatives 4
2.1 No - Action Alternative 4
2.2 Replace Reduced Facilities at Alternate Location (Preferred Alternative) 4
2.3 Restore to Pre-Disaster Locations with Elevated Facilities 6
2.4 Alternatives Eliminated from Further Consideration 7
2.4.1 Restore to Pre-Disaster Locations and Conditions 7
2.4.2 Replace Identical Facilities at Alternate Location 8
2.4.3 Replace Reduced Facilities at a Remote Location 9
2.4.4 Replace and Relocate Outside the Floodplain 9
Section 3 - Affected Environment and Environmental Consequences 10
3.1 Physical Environment 10
3.1.1 Topography and Soils, Geology, Seismicity (including Executive Order 12699) 10
3.1.1.1 No-Action Alternative 12
3.1.1.2 Preferred Alternative 12
3.1.1.3 Restore to Pre-Disaster Locations with Elevated Facilities 12
3.1.2 Water Resources and Water Quality 12
3.1.3 Floodplain Management (Executive Order 11988) 14
3.1.3.1 No-Action Alternative 15
3.1.3.2 Preferred Alternative 15
3.1.3.3 Restore to Pre-Disaster Locations with Elevated Facilities 16
3.1.4 Air Quality 16
3.1.4.1 No-Action Alternative 17
3.1.4.2 Preferred Alternative 17
3.1.4.3 Restore to Pre-Disaster Locations with Elevated Facilities 18
3.1.5 Coastal Zone Management 18
3.1.5.1 No-Action Alternative 18
3.1.5.2 Preferred Alternative 18
3.1.5.3 Restore to Pre-Disaster Locations with Elevated Facilities 19
3.1.6 Coastal Barriers Resources 19
3.2 Biological Environment 19
3.2.1 Terrestrial and Aquatic Environment 19
3.2.1.1 No-Action Alternative 19
3.2.1.2 Preferred Alternative 19
3.2.1.3 Restore to Pre-Disaster Locations with Elevated Facilities 19
3.2.2 Wetlands (Executive Order 11990) 20
3.2.3 Threatened and Endangered Species 20
3.2.3.1 No-Action Alternative 21
3.2.3.2 Preferred Alternative 21
3.2.3.3 Restore to Pre-Disaster Locations with Elevated Facilities 22
3.3 Hazardous and Special Waste Materials 22
3.4 Socioeconomics 22
3.4.1 Zoning and Land Use 22
3.4.1.1 No-Action Alternative 23
3.4.1.2 Preferred Alternative 23
3.4.1.3 Restore to Pre-Disaster Locations with Elevated Facilities 23
3.4.2 Aesthetics and Visual Resources 23
3.4.2.1 No-Action Alternative 24
3.4.2.2 Preferred Alternative 24
3.4.2.3 Restore to Pre-Disaster Locations with Elevated Facilities 24
3.4.3 Noise 24
3.4.3.1 No-Action Alternative 25
3.4.3.2 Preferred Alternative 25
3.4.3.3 Restore to Pre-Disaster Locations with Elevated Facilities 25
3.4.4 Public Services and Utilities 25
3.4.4.1 No-Action Alternative 26
3.4.4.2 Preferred Alternative 26
3.4.4.3 Restore to Pre-Disaster Locations with Elevated Facilities 26
3.4.5 Traffic and Circulation, Volume, Parking, and Access 26
3.4.5.1 No-Action Alternative 27
3.4.5.2 Preferred Alternative 27
3.4.5.3 Restore to Pre-Disaster Locations with Elevated Facilities 27
3.4.6 Environmental Justice (Executive Order 12898) 27
3.4.6.1 No-Action Alternative 28
3.4.6.2 Preferred Alternative 28
3.4.6.3 Restore to Pre-Disaster Locations with Elevated Facilities 29
3.4.7 Public Health and Safety (including Executive Order 13045) 29
3.4.7.1 No-Action Alternative 29
3.4.7.2 Preferred Alternative 29
3.4.7.3 Restore to Pre-Disaster Locations with Elevated Facilities 30
3.5 Cultural Resources 30
3.5.1 Historic Architecture 31
3.5.2 Archaeological Resources 31
3.5.1 Indian Coordination and Religious Sites 32
Section 4 - Public Participation 37
Section 5 - Mitigation Measures and Permits 38
5.1 Mitigation Measures 38
5.2 Permits 39
Section 6 - Consultations , References and Credits 41
6.1 Consultations 41
6.2 References 42
6.3 Credits for Photographs, Maps and Plans 43
Section 7 - Secondary and Cumulative Impacts 44
Section 8 - List of Preparers 45
Tables
Table 1 Affected Environment and Consequences - Impact Summary
Appendices
Appendix A Exhibits (including Location Map), Photographs, Preferred Plans
Appendix B Acronyms
Appendix C Agency Correspondence
Appendix D Public Notice
Appendix E Public Comments (relative to meetings, hearings, etc)
Appendix F Permits
Section 1 - Introduction
1.1 Project Authority
Hurricane Dennis was an unusually strong July major hurricane that left a trail of destruction from the
Caribbean Sea to the northern coast of the Gulf of Mexico. Dennis formed from a tropical wave that
moved westward from the coast of Africa and followed a west-northwest course across the Caribbean
Sea. Dennis reached hurricane strength early on July 7, 2005, and then rapidly intensified into a
Category 4 hurricane before making landfall in southeastern Cuba. Hurricane Dennis continued
northwest across the Gulf of Mexico before it made landfall on Santa Rosa Island, Florida. Hurricane
Dennis landed between Navarre Beach and Gulf Breeze on July 10, 2005 with sustained winds of 120
mph. Dennis produced a storm surge of six to seven feet above normal tide levels on Santa Rosa
Island, near where the center made landfall. The storm surge washed over Santa Rosa Island near and
to the west of Navarre Beach. Dennis continued north-northwestward after landfall, with the center
moving across the western Florida Panhandle into southwestern Alabama before it weakened into a
tropical storm.
As a result of the landfall of Hurricane Dennis and its impacts on the State of Florida, Governor Jeb
Bush requested a disaster declaration for the State of Florida.
President George W. Bush issued a major disaster declaration (FEMA - 1595 DR - FL) on the same
day as requested, in conformance with the Robert T. Stafford Disaster Relief and Emergency
Assistance Act, as amended by Public Law 106-390, the Disaster Mitigation Act of 2000.
Subsequently, the Florida Department of Environmental Protection has petitioned the Federal
Emergency Management Agency (FEMA) for 406 Public Assistance funding under the provisions of
the same act. In accordance with the National Environmental Policy Act of 1969 (NEPA), the Council
on Environmental Quality (CEQ) regulations implementing NEPA (40 Code of Federal Regulations
[CFR] Parts 1500 through 1508), and FEMA regulations for NEPA compliance (44 CFR Part 10),
FEMA requires an evaluation of alternatives, and a discussion of the potential environmental impacts
of a proposed federal action, as part of the Environmental Assessment (EA) process for federal
funding. The purpose of this EA is to meet FEMAs responsibilities under the NEPA and to determine
whether to prepare a Finding of No Significant Impact (FONSI) or an Environmental Impact
Statement (EIS) for the proposed project.
1.2 Project Location
The Florida Department of Environmental Protection (FDEP), State Park Service, has applied for a
federal grant to fund the demolition and replacement of the Hurricane Dennis storm damaged public
restrooms and bath house facilities at the Dr. Julian G. Bruce St. George Island State Park (St. George
Island State Park). St. George Island State Park is situated on the Gulf Barrier Chain and is a narrow
island created by wind and storm deposited sands; it is located along the southern edge of the
Apalachicola Coastal Lowlands of the Gulf Barrier Chain within Franklin County, FL. The eastern
eight to nine miles of the island comprise the St. George Island State Park.
Refer to the series of Location maps in Appendix A - Exhibits 1 and 2. The island is located south of
Apalachicola and East Point, and surrounded by Apalachicola Bay to the north and the Gulf of
Mexico to the south. Access to St. George Island is via County Highway 300, carried on a bridge from
the Village of East Point, east of the City of Apalachicola, to the island.
1.3 Purpose and Need
The objective of FEMAs Public Assistance Program is to reduce the impacts of natural disasters on
the built environment; assist the community in recovering from damages caused by disasters; reduce
future losses resulting from natural disasters; and protect the health, safety and welfare of citizens.
The purpose of the action presented in this EA is the replacement of the FDEPs St. George Island
State Park public beach restrooms and bath house / shower facilities that were destroyed by Hurricane
Dennis. The need is to provide public restrooms, showers and bathing facilities that meet the safety
and health needs consistent with the demand for public outdoor recreation along the beaches for the
local area residents and visitors to St. George Island State Park.
1.4 Existing Facility
The park is very linear, accessed by approximately five miles of a paved two-lane roadway paralleling
the Gulf of Mexico, and provides park visitors opportunities for camping, picnicking, swimming and
beach activities. The primary recreational resources of the park are its shorelines on the Gulf of
Mexico and Apalachicola Bay. Over 200,000 visitors used the beach area, camping area and trails in
the park in fiscal year 1999-2000. The management of this volume of public use on the shoreline areas
of the park is the greatest challenge in the FDEP Division of Recreation and Parks management of
the area.
Two large day-use areas for beach visitors are located within the park, the day-use areas are
approximately one mile apart along the shoreline. A privately-owned and operated potable water
system provides water service to the park; however, no such sewage disposal systems are available.
All of the parks sewage needs were satisfied by onsite sewage treatment and disposal systems (septic
tanks and drain-fields).
The two day-use areas on St. George Island State Park are the East Slough Beach Use Area and the
Sugar Hill Beach Area. The East Slough Beach Use Area consists of three large picnic shelters, two
restroom and bathhouse / shower facilities (damaged / destroyed beyond repair by Hurricane Dennis
storm surges), two connected paved parking lots totaling 220 parking spaces, and a system of
connecting boardwalks totaling approximately 850 linear feet. The Sugar Hill Beach Use Area
consists of precisely the same facilities and layouts as at the other area, although the damage from the
Hurricane Dennis storm surge was less intense. The repairs added up to less than 50% of the
replacement costs, but FDEP has elected to demolish and replace them. The facilities as they existed
are illustrated in Appendix A Exhibit 2. These areas will be referred to as East Beach Use Area
(Sugar Hill) and West Beach Use Area (East Slough) throughout the remainder of this EA
document.
Photographs of the existing facilities, including damages caused by Hurricane Dennis, can be seen in
Appendix A, Photographs, Collections 1 and 2.
Subsequent to the storm surge from Hurricane Dennis, extensive damage was done to all four of the
restroom and shower facilities. In addition, the primary dune system was destroyed. All four buildings
were closed, and this entire area of the State Park was closed. Though the Park is closed to motoring
vehicles, park patrons can walk the beaches or take boats to the two beach use areas. It was therefore
determined that the damaged structures were hazards, and the Franklin County Health Department
determined that the four existing septic systems were no longer safe to use. The FDEP had the four
buildings and septic systems removed due to the hazards they presented to park patrons. This decision
was made by the Florida Parks Service in coordination with investigations and evaluations involving
the Park Service, FDEP, Franklin County and FEMA representatives. Following the demolition, the
primary dune system that had been destroyed as a result of Hurricane Dennis is undergoing natural
processes and is beginning to establish a new primary dune in an area previously located by the old
restrooms and bath house / shower facilities.
1.5 Project Description
St. George Island State Park is a state-owned park that is utilized extensively by the public for access
to the Gulf of Mexico. The storm damaged public restrooms and bath house facilities at the park were
the only publicly owned and accessible buildings with restrooms and shower facilities for the users of
St. George Island State Park. Hurricane Dennis heavily damaged all four restrooms at two locations
and caused moderate damage to the picnic pavilions. As a result, all four restrooms were demolished
after inspection by FEMA personnel. The pavilions, most notably the boardwalk access to them, will
require repair. Project worksheets have been developed for those damages. The sewage systems
serving the restrooms were also damaged and, after concurrence by the local Health Department
authorities, were also removed. At St. George Island State Park, public outdoor recreation and
conservation is the designated use of the property. These storm damaged public facilities were located
at two sites on the beach, located between paved parking lots and the Gulf of Mexico.
The project consists of the replacement of the damaged public restrooms and bathing facilities at two
sites within St. George Island State Park. This includes replacement of the structures, as well as the
sewage disposal systems. Repair of the pavilion boardwalks will also occur.
Section 2 - Alternatives
Alternative courses of action were explored in depth. The restroom and bath house / shower facilities
were heavily damaged by Hurricane Dennis, as were the sewage disposal systems. Two of the
restrooms and bath house / shower facilities originally built in 1982 were a complete loss, while the
other two restrooms and bath house / shower facilities, also built in 1982, were heavily damaged. All
of the alternatives were evaluated based upon engineering constraints, environmental impacts,
architectural considerations, structure longevity and visitor services criteria for St. George Island State
Park. Budgetary impacts were considered, but were not the controlling factor. The analysis, thought
processes and decisions leading to a Preferred Alternative were reviewed with FEMA personnel
during the damage assessment phase, the FDEP, Bureau of Beaches and Coastal Systems during the
Coastal Construction Control Line (CCCL) permitting phase and the Franklin County Building
Department during the plan development phase. In addition, the United States Fish and Wildlife
Service (USF&WS) and the Florida Fish and Wildlife Conservation Commission (FF&WCC)
personnel have participated in informal consultations during the project evaluation process. Those
discussions continue and remain on-going.
2.1 No - Action Alternative
The No-Action Alternative consists of not replacing or permanently relocating public beach restrooms
and bath house / shower facilities at the West Beach Use Area and the East Beach Use Area of St.
George Island State Park. None of these public services are currently being provided, and this portion
of the Park is closed to visitors. The No-Action Alternative would result in there being no permanent
structures available to service the sanitation and public health needs of the St. George Island State
Park beach visitors. This No-Action Alternative does not fulfill the purpose and need of the project.
Selection of this option would make services at this coastal recreational park unavailable to the
visiting public and a decision would have to be made as to whether or not to keep this portion of the
Park permanently closed, or bring in portable chemical toilets. Full restroom facilities are preferable to
accommodate regular and concentrated visitation. Further discussions related to this alternative will
refer to it as the No-Action Alternative.
2.2 Replace Reduced Facilities at Alternate Location (Preferred Alternative)
The Replace Reduced Facilities at Alternate Location consists of combining the two structures that
were previously located at both the West Beach and East Beach Use Areas into one structure at each
facility. The new facilities would be located between the parking lots that are located approximately
80 feet landward of the previous facilities locations. The structures would be approximately 1,225
square feet in size and elevated 15 feet above sea level on concrete piling foundations. Access ramps
would be constructed to provide access to the facilities; the ramps would be placed primarily within
the adjacent parking lots. A lift system would be installed to provide handicapped access in
compliance of the American with Disabilities Act (ADA). The parking lots would require minor re-
configuration in order to accommodate the new facilities. Photographs of the pre-disaster lay-out of
the West Beach Use Area, as well as the area between the parking lots where the new facility would
be placed, can be seen in Appendix A, Photographs, Collection 1. Appendix A Preferred Plans,
Sheets 1 & 2 contains the site plans which indicate the proposed locations and layouts described here.
The East Beach Use Area would be identical in layout.
Under this alternative, the facilities at both the West Beach and East Beach Use Areas would be
composed of one structure that houses both a mens restroom/bath house and a womens
restroom/bath house. A new aerobic treatment disposal system would be installed to handle the
effluent from the single facility at each site. With double the usage for each system (one system at
each beach use area instead of the two separate systems at each beach use area which previously
occurred), and with modern codes and standards related to the deposition of sewage waste materials,
state-of-the-art systems were designed to handle the sewage and wastewater. The selected system
collects the wastes from the restrooms/showers in a pre-treatment tank. From there it moves the waste
to a pair of aerobic treatment tanks, and then on to a 3,000 gallon dosing tank. The sewage treatment
system at each location would be located within the parking lot median area, immediately west of the
new raised facility, and surrounded by a wooden fence. The sewage treatment elements of the plan are
shown on Sheets 3, 4 & 5 of Appendix A Preferred Plans.
From the dosing tank, treated waste would move under the parking lot to mounded trench drain fields
via new underground pressure mains (3-inch in diameter). The drain fields would be located in the
approximate location of the previous facilities drain field locations. In the East Beach Use Area, the
drain field would be northeast of the parking lot, while in the West Beach Use Area it would be to the
southwest. In both locations, the drain fields would be two-foot high mounds, measuring
approximately 125-feet long (perpendicular to the beach) and approximately 65-feet wide (parallel to
the beach). The sands would taper up at a four to one slope to form the twofoot high mounds. Within
these mounds, the treated liquids would be pumped into a series of perforated pipes for distribution
into and through filter fabrics, graded aggregate and native sands. The mounded drain field areas
would also be fenced for protection. The sites selected for the drain fields are off to the side of the
parking lots, in areas not typically populated by beach visitors.
In the evaluation of this alternative, two options for placement of the advanced aerobic treatment
disposal system were considered. A study was conducted to see if the new sewage systems could be
placed within the central islands of the parking lots. It was determined that the central island was not
large enough to accommodate the new, enlarged sewage treatment systems. It was therefore
determined that the most practicable solution was to install the new treatment systems within the same
general vicinity as the previous drain fields, adjacent to the parking areas.
The location of the new facilities would require a reconfiguration of the parking lot in order to
accommodate the structure itself, as well as the access ramps. Each new restroom and bath house /
shower facility would be placed in the central, unpaved island between the two paved parking areas,
with a minimal reduction in parking (ten standard parking spaces). Each new restroom and bath house
/ shower facility would be centrally located for the convenience of all beach visitors at each beach use
area. Since the new facilities would be located within 80 feet landward of the previous locations, a
reasonable walking distance would be maintained for beach users.
Constructing a modern restroom and bath house / shower facility at the proper elevation at these
locations would require extensive pedestrian access accommodations to comply with State and
Federal ADA regulations (36 CFR 1191). Pedestrian access routes would be established within the
parking lot central islands, thereby reducing the potential for environmental impacts along the beach
use area. This alternative would also incorporate a lift system for ADA access, thus further reducing
the environmental impacts associated with long ramped pedestrian access routes.
This Replace Reduced Facilities at Alternate Location Alternative was determined by the FDEP to be
the most practical, cost-effective and environmentally-responsible solution to meet the Purpose and
Need. This alternative would provide modern restroom and bath house / shower facilities within two
structures versus the pre-storm four structures; the facilities would be built in accordance with current
Statewide Building Code requirements. The 15-foot elevation on concrete pilings would minimize
future storm surge and flood damage, and is required by Franklin County building codes. The
construction would require normal low rise construction equipment and/or drilling machinery. With
the work site close to the existing paved parking lots and previously removed septic drain-fields, most
of the equipment and materials storage, as well as lay down areas, would be in previously disturbed
sand areas, between the parking lots or within the parking lot paved areas.
The replacement as proposed incorporates a reduced number of elevated boardwalk systems. The
boardwalk system would be located in a way that is the least disruptive to shorebird and sea turtle use
areas. Any dune areas in the immediate vicinity would be protected from construction activity
disturbance, in consultation with the USF&WS and the FF&WCC. Protected areas would be called
out in the construction contract plans and specifications, as well as on the job site with signs
identifying an area of No Intrusion areas and/or To Be Protected . In addition, compatible beach-
quality sands would be placed on the beach between the Gulf and the construction sites. These beach
sands would be placed and shaped to mimic naturally occurring dunes and would prevent sea turtles
from crawling up the beach and into the construction sites. It is intended that this dune-like feature
would extend approximately 500-feet in length and overlap the proposed construction areas.
Further discussions throughout this document related to this Replace Reduced Facilities at Alternate
Location Alternative will refer to it as the Preferred Alternative.
2.3 Restore to Pre-Disaster Locations with Elevated Facilities
The Restore to Pre-Disaster Locations with Elevated Facilities Alternative consists of replacing the
damaged restrooms and bath house / shower facility structures as closely as possible to their pre-storm
locations. Four structures would be installed, two each at the East Beach Use Area and the West
Beach Use Area. The structures would be placed on piles, of sufficient length and strength to hold the
structures above anticipated storm surges, with boardwalks and stairs providing access. The
replacement septic systems would have to be upgraded over the pre-disaster systems to meet the
current Franklin County Health Department codes. The Franklin County Health Department has
indicated that current codes and standards require an aerobic treatment system with a low-pressure
dosing system and more square footage for the septic fields than what is available in the existing
locations. The new sewage systems would therefore occupy the same area on the property as the pre-
disaster systems, with some septic drain-field enlargement to meet the current requirements. The
location of the drain fields would be in the same location as the previous buildings, which is the same
as the two proposed for the Preferred Alternative. Because there is one additional building at each
beach use area with this alternative, two more drain fields would be required and would be placed on
the opposite sides of the parking lots. All four systems would be smaller than the two for the
Preferred Alternative, but would provide approximating the same overall capacity. The holding tanks,
aerobic treatment tanks, dosing tanks and pumps would be located immediately adjacent to the
buildings, putting them 80 feet closer to the Gulf of Mexico than the Preferred Alternative, and
subjecting them to more tidal and wave action. Force mains to the new drain field areas would be
necessary, as would a mounded system of piping, filters, geo-fabrics and gravels and sands.
The location of the facilities within the West Beach Use Area would be as shown on the first
photograph in Appendix A Photographs Collection 1. The restrooms and bath house / shower
facilities are identified as units 2 and 4. The layout at the East Beach Use Area would be identical.
The Restore to Pre-Disaster Locations with Elevated Facilities Alternative would place four rebuilt
structures on the beach, displacing the new primary dune that has developed. The location is closer to
the Gulf than the Preferred Alternative, making it more vulnerable to storm surges and flooding from
the Gulf of Mexico. The elevation of the structures to approximately 15 feet above sea level, per
current building code and permit requirements, would help alleviate some of the risk to the structures.
Pedestrian access routes would be established within the parking lot central islands, thereby reducing
the potential for environmental impacts along the beach use area. This alternative would also
incorporate a lift system for ADA access, thus further reducing the environmental impacts associated
with long ramped pedestrian access routes. This alternative would require a more extensive boardwalk
system them the Preferred Alternative because the grade elevation is approximately four feet lower at
this location. Placing the new facilities 15-feet above sea level would make access to them somewhat
more difficult. Typically, ramped walkways not exceeding 5% up slopes are required with flat areas
every 30-inches (measured in the vertical). The total length of ramped walkway would exceed 300
lineal feet, covering a great deal more area than with the Preferred Alternative. As with the Preferred
Alternative, this alternative would also incorporate a lift system for ADA access, thus reducing the
environmental impacts associated with long ramped pedestrian access routes. The proximity to the
storm surges would have to be taken into consideration when designing the lift system, possibly
making it more expensive to armor against storm surges.
The Coastal Construction Control Line (CCCL) lies landward of the south edge of the parking lot. The
original sites that would be reused with this alternative lie seaward of that line. Thus, a CCCL permit
would have to be obtained from the FDEP to build these four buildings in a controlled area. The
placement of septic systems seaward of the CCCL line may make it difficult to obtain a CCCL permit.
2.4 Alternatives Eliminated from Further Consideration
This section identifies and provides a brief description of those alternatives that were eliminated from
further consideration because they did not meet the Purpose and Need or because they were
impracticable, not feasible, economically unreasonable, or had significant adverse environmental,
public safety and public health impacts. The three alternatives considered but eliminated from further
study are discussed below.
2.4.1 Restore to Pre-Disaster Locations and Conditions
Replacement of the damaged restrooms and bath house / shower facility structures at their exact pre-
storm location is physically possible. The location of the facilities within the West Beach Use Area
would be as shown on the first photograph in Appendix A Photographs Collection 1. The
restrooms and bath house / shower facilities are identified as units 2 and 4. A Restore to Pre-disaster
Locations and Conditions Alternative would place four rebuilt structures on the beach, displacing the
new primary dune. The structures would be placed on short piles, just as with the old buildings, with
boardwalks and stairs providing access. The septic systems have been removed and would need to be
replaced by new systems (four with this alternative). The septic systems would be located in similar
locations as the Restore to Pre-Disaster Locations with Elevated Facilities Alternative, and they
would be similarly sized and configured.
The Coastal Construction Control Line (CCCL) lies landward of the south edge of the parking lot. The
original sites that would be reused with this alternative lie seaward of that line. Thus, a CCCL permit
would have to be obtained from the FDEP to build these four buildings in a controlled area. Some
elements of this alternative may not be acceptable under the current requirements of the CCCL.
Additionally, current Franklin County building codes require structures to be elevated 15-feet above
sea level, which this alternative does not do.
At the completion of this alternative review, it was felt that the negatives involving the inadequacy of
the room for replacement structures, the non-conformance to current construction codes, the exposure
of the facilities to storm surges and the environmental impacts to the new primary dune system were
significant enough to eliminate this alternative from further consideration. Therefore, the Restore to
Pre-disaster Locations and Conditions Alternative was dropped from further consideration and not
carried forward in the study process.
2.4.2 Replace Identical Facilities at Alternate Location
Replacing identical facilities at alternate locations was considered. Two such project layout options
were considered.
The first layout option considered locating the restrooms and bath house / shower facility structures
approximately 80-feet landward of the destroyed facilities, immediately to the east and west of the
parking lot. This first layout option would still provide a relatively short walking distance to the
shoreline for beach visitors and would maintain an identical number of restroom and bath house /
shower facility amenities as the pre-storm condition, while maintaining the parking lot capacities. The
existing sewage disposal systems would require complete replacement and the septic drain fields
would be located landward of the restroom facility structures.
The second layout option considered moving the restrooms and bath house / shower facility
structures approximately 300 feet landward of the destroyed facilities, immediately to the east and
west of the parking lot. This second layout option would require a relatively long walking distance
to the shoreline for the public beach user, but would maintain an identical number of restroom and
bath house / shower facility amenities as the pre-storm condition and maintain the existing parking lot
capacities. The existing sewage disposal systems would require complete replacement and the septic
drain fields would be located landward of the restroom facility structures.
It was determined that the restrooms and bath house / shower facility structures could not be located
within the existing paved parking lot, as it would require a reduction in parking spaces that would
likely exceed 20 standard parking spaces. This was deemed excessive and inconsistent with the parks
level of service need for projected visitation. Therefore, either of these layout options would require
placement of the new construction within undisturbed, pristine beach areas, albeit immediately
adjacent to previously-disturbed areas associated with the parking lot construction. Further,
constructing a modern restroom and bath house / shower facility at the proper elevation at these
locations would require extensive pedestrian access accommodations to comply with State and
Federal ADA regulations, possibly leading to adverse environmental impacts along the beach use
area. For those reasons, these layout options were determined to have potential adverse environmental
impacts. Additionally, the second layout option was thought to locate the restroom and bath house /
shower facility too distant from the beach use area while providing no appreciable benefits. Upon
further consideration, it was determined that the replacement of the septic fields and bringing them to
conformance with current codes for either layout option resulted in excessive construction costs and
resulted in potential shorebird habitat impacts For these reasons, and because these options did not
possess any advantages over the alternatives taken forward for further consideration, the Replace
Identical Facilities at Alternate Location Alternative was dropped from further consideration.
2.4.3 Replace Reduced Facilities at a Remote Location
This alternative was under consideration to combine the benefits of the Preferred Alternative by
reducing the number of structures and by placing them in previously disturbed areas, and the added
benefit of a greater setback from the shore to reduce future wave and storm surge actions. The remote
location under consideration was the center island of the parking lots, similar to the Preferred
Alternative, however at the extreme landward end of that island.
The Hurricane Dennis storm surge carried beach sands all the way to the dune line north of the
roadway. Thus, this alternative, while more remote that the Preferred Alternative, and reducing the
future damage potential, would not result in a significant reduction to future damage. The negative
impacts of such a remote location are similar to those discussed with the second layout option
discussed in Section 2.4.2, above. The slight increase in storm surge protection was determined to be
not sufficient enough to outweigh the negatives of being too distant from the beach to be used
effectively. For these reasons this alternative was dismissed from further consideration.
2.4.4 Replace and Relocate Outside the Floodplain
Since the pre-existing restrooms and bath house / shower facility structures were located within a
mapped 100-year floodplain, and since all the other alternative locations considered are also in the
floodplain, relocation to a site out of a mapped 100-year floodplain was examined. A check of Flood
Insurance Rate Maps (FIRM maps) revealed that there is no land within the beach area sites of St.
George Island State Park that is outside of the floodplain. All land on the St. George barrier island is
within the 100-year floodplain. This alternative was therefore dismissed from further consideration.
Section 3 - Affected Environment and Environmental Consequences
This section addresses specific information related to environmental resources, sensitive issues,
locations of interest, obstructive features, avoidance measures, and impacts that may occur as a result
of the project. Tabular data, as appropriate, and a Summary Table are included to provide a more
comprehensive picture and understanding of the issues for the repair or replacement of the storm
damaged public restrooms and bath house beach facilities. Environmental resource issues and areas
identified as potentially impacted by the proposed action, or that require discussion pursuant to
applicable laws and regulations, are addressed in this section. Proposed mitigation is referenced and/or
discussed within the respective environmental issue area.
3.1 Physical Environment
3.1.1 Topography and Soils, Geology, Seismicity (including Executive Order 12699)
Topography
St. George Island State Park is situated on the Gulf Barrier Chain and is a narrow island created by
wind and storm deposited sands; it is located along the southern edge of the Apalachicola Coastal
Lowlands of the Gulf Barrier Chain. The eastern eight to nine miles of the island comprise the St.
George Island State Park. The low dunes and over wash areas occupy most of the shoreline, sand
dunes and adjacent communities along the Gulf side of the island. The undulating dunes range from
two to 25-feet. Many of the larger dunes were damaged during hurricane Opal (1995) and Dennis
(2005) with some height having been lost. The dunes are and will recover some size, but progress is
and will continue to be slow.
On the sound side of the island, Rattlesnake Point Peninsula is an area of ancient dune activity where
relict dunes range from about five to ten feet above sea level with one relict dune reaching 21-feet.
The eastern end of the island is accreting. The topography here is low and highly dynamic. As time
goes on, these dunes are expected to grow beyond the three to five feet currently exhibited.
Exhibits 4 and 5 (Appendix A) contain the USGS topographic maps for the project area.
No impacts to topography are anticipated from any of the alternatives considered.
Seismicity
The project area is located in northwestern Florida along a belt of mostly seaward-facing normal faults
that border the northern Gulf of Mexico in westernmost Florida, southwestern Alabama, and southern
Mississippi, all of Louisiana, southernmost Arkansas, and eastern and southern Texas (Ewing and
Lopez, 1991 #2023). This belt of gulf-margin normal faults from Florida through Texas has strikingly
low historical seismicity; the stress field and seismogenic potential of the underlying crust are
unknown; the ability of the fault belt to generate significant seismic ruptures that could cause
damaging motion is unclear. Accordingly, the fault belt is assigned to Class B . The project area is
identified as being in the lower hazard zone (2-4%g) for ground shaking, as indicated in Ground
Shaking Hazards of Earthquakes (Appendix A - Exhibit 6). This exhibit shows the peak acceleration
(%g) with 2% probability of exceedance in 50 years, as identified in the zone of 2-4%g. Generally, the
earthquake frequency expected throughout the entire State of Florida is the same as the project area.
The most recent Florida earthquake occurred on November 18, 1952, a slight tremor was felt by many
at Quincy, a small town about 20 miles northwest of Tallahassee. Windows and doors rattled, but no
serious effects were noted. Because of the extremely low ground shaking hazard, Executive Order
12699 (EO 12699), Seismic Safety of Federal and Federally Assisted or Regulated New Building
Construction, does not apply. Special seismic related design criteria are not required for construction
projects in this project area. There are no adverse seismic impacts associated with any of the
alternatives considered.
Geology
A structural feature known as the Apalachicola embayment has influenced the geology of St. George
Island. This embayment feature has existed since at least the Miocene, or approximately 30 million
years before present (mybp), and has been accumulating sediments since that time. The limestone
beds lay approximately 300-feet below the current surface of St. George Island. The deeper, older
Bruce creek and St. Marks formations of the late Oligocene to middle Miocene (20-30 mybp) are
composed of limestone built from calcareous shells of mostly mollusks, but also ostracods, bryozoans,
algae, corals, sea urchins and benthic and planktonic foraminifera. The species assemblage present in
these limestones suggest that they were deposited under near-shore, warm, shallow, sometimes
shoaling seas that were very similar to those occurring around the present-day Florida Keys.
The overlying Intra-coastal formation of the late Miocene to middle Pliocene (5-20 mybp) is
composed largely of poorly consolidated, sandy limestone. The variable faunal assemblages indicate
diverse maritime conditions during deposition. The prevalence of planktonic foraminifera in the lower
portions of this formation indicates that it was probably deposited under deeper seas, perhaps as deep
as 300 to 600-feet. The presence of other fossils and a deposition hiatus suggest that sea levels
fluctuated substantially during this time, but generally were receding until near-shore estuarine and
marine conditions again prevailed during the late Pliocene and early Pleistocene (2-5 mybp) when the
molluscan-rich Chipola and Jackson Bluff formations were deposited. These formations were
subsequently covered by 50 to 70-feet of unconsolidated, cross-bedded and inter-bedded sands, clays
and other clastics, which are typical of a prograding delta and fluctuating sea levels.
St. George Island did not exist in its present form until relatively recently, as the presence of mollusk
reefs 10 to 20-feet below the surface in many areas indicates that estuarine conditions prevailed where
the island now stands. Estuarine and fluvial sediments 30 to 40-feet below the surface have been
radiocarbon dated at around 28,000 to 40,000-years old. In general, the oldest portion of the island,
the Gap Point Peninsula, is estimated to be less than 3000-years old.
The island initially developed from two offshore shoals, which emerged during slightly lower sea
levels. Three separate small islands which were present less than 1000-years ago slowly merged into
the current island configuration. These dynamic changes in its recent geologic history indicate that
continued alterations in St. George Islands shape, size and topography are inevitable. St. George
Island is expected to continue on a slow migration landward as sea levels rise.
Soils
Seven soil types have been identified on St. George Island. These include Beaches, Dirego and Bayvi
Tidal Soils, Corolla Sand, Duckston sand, Rutledge fine sand, Newhan Corolla complex, Duckston-
Rutledge-Corolla complex and Ductston-Bohicket-Corolla complex. Most of the island is comprised
of highly dynamic beach and dune systems. The two proposed replacement and relocation areas West
Beach Use Area and East Beach Use Area are located in Corolla Sand areas. Corolla Sand is
somewhat poorly drained, nearly level or gently sloping soil on flats and small dunes and in swales on
large dunes along the gulf coast beaches. The Corolla soil has a seasonal high water table at a depth of
18 to 36 inches for three to six months in most years. Flooding can occur during severe coastal storms.
The available water capacity is low. Permeability is very rapid. Natural fertility and the content of
organic matter are low. Management activities would follow generally accepted Best Management
Practices (BPMs) established in the Florida Department of Agriculture and Consumer Services
(FDA&CS) 1993 Sericulture Best Management Practices to prevent soil erosion and conserve soil and
water resources on site. There are likely to be no impacts to this soil type, regardless of the alternative
course of action chosen.
A soils map of St. George Island State Park can be found in Appendix A as Exhibit 7.
Prime Farmland
The Farmland Protection Policy Act (FPPA) [PL 97-98, Sec. 1539-1549; 7 USC 4201, et seq.], which
states that federal agencies must minimize the extent to which federal programs contribute to the
unnecessary conversion of farmland to nonagricultural uses, was considered in this EA. No
farmlands of any type are located near the project location. Further, the entire St. George Island is
made up of quartz sands, a nonagricultural use. No further consideration of FPPA is required.
3.1.1.1 No-Action Alternative
The No-Action Alternative would have no impacts on topography, soils, or prime farmland.
There would be no seismicity impacts.
3.1.1.2 Preferred Alternative
The Preferred Alternative would have no impacts on topography, soils, or prime farmland.
There would be no seismicity impacts.
3.1.1.3 Restore to Pre-Disaster Locations with Elevated Facilities
The Restore to Pre-Disaster Locations with Elevated Facilities would have no impacts on soils
or prime farmland; there would be no seismicity impacts. This Alternative would have impacts
on topography, however, because it would interfere with the accretion of the primary dune that
is currently developing at this location.
3.1.2 Water Resources and Water Quality
Surface Water
St. George Island is located at the southern edge of the Apalachicola River Drainage Basin and serves
as a protective barrier between the marine waters of the Gulf of Mexico and the estuarine waters of
Apalachicola and St. George Sound. The Apalachicola River discharges an average of 16 billion
gallons per day into the Apalachicola Bay. These Apalachicola River waters are identified as Class II
waters. Florida Surface Water Classifications are established according to designated uses. Class II
waters are those designated as Shellfish Propagation or Harvesting according to their present and
future most beneficial uses. The large influx of fresh water substantially lowers the salinity of the bay
side of the island.
Class I surface waters are Potable Water Supplies, while Class III waters are classified as
Recreation, Propagation and Maintenance of a Healthy, Well-Balanced Population of Fish and
Wildlife. Class III is the statewide default classification intended to meet the goal of the federal
Clean Water Act (i.e., all waters should be fishable/swimmable).
The water quality reported by the Florida Department of Health for the public beach areas along the
Gulf of Mexico side of St. George Island State Park during March of 2006 was Good for
Enterococcus [0-35 Enterococcus sp per 100 ml of marine water], Enterococcus Geometric Mean [0-
35 CFU/100mL Enterococcus sp Geometric Mean], and fecal coliform [0-99 fecal Coliform
organisms per 100ml of marine water].
Due to the extensive porosity of the overlying sands, drainage on the island is almost exclusively
subsurface. Only occasional surface waters are present. These typically occur as elongated inter-dune
swales of relict dune systems on the older portions of the island. In addition to these depression
marshes, a large, shallow coastal Dune Lake lies near the eastern tip of the island. Two deep borrow
pits have succeeded into what are essentially small lakes near the campground, but they are not in the
vicinity of the East Beach Use Area or West Beach Use Area.
Storm water runoff drains to the surrounding Gulf of Mexico and estuarine waters of Apalachicola
Bay and St. George Sound waters and/or percolates through the area soils and beach sands.
The estuarine and marine waters that surround the island subject the shorelines to tidal influences.
Mean high and mean low tides normally vary about 2.6-feet daily, but may substantially exceed this
during tropical storms and hurricanes. Five to six foot storm surges are expected about every ten years
and eight to ten foot storm surges are expected every 50 to 100-years. Storm tides significantly affect
the islands ground and surface waters, as well as estuarine areas behind the island.
None of the alternatives would involve waters regulated by Section 404 of the Clean Water Act. A
U.S. Army Corps of Engineers (USACOE) Section 404 Permit would not be required for any of the
alternatives.
None of the alternatives, if built, would have any measurable affect on surface waters. The
permeability of the beach sands and the proximity of the Gulf of Mexico would absorb any and all
runoffs. The small impervious area associated with each of the proposed structures is virtually
miniscule when compared to the surface area of St. George Island State Park, St. George Island, the
Gulf of Mexico and Apalachicola Bay.
Temporary construction activities would also have no measurable negative impacts on surface waters.
Most of the construction activities would be either based on the paved parking lots, or be supported by
concrete piles placed into the sand. The excavations for the various parts of the sewage systems would
remove the surface sands and expose the underlying sands for the time necessary to install the
equipment. They would then be recovered by beach sands. The contractor would be responsible for
guaranteeing that no accidental spills that could migrate to the waters of the Gulf of Mexico would
occur, and would likely do so with Best Management Practices (BMPs). Appropriate erosion control
and BMPs will be utilized to minimize any impacts resulting from parking lot runoff, erosion and/or
sedimentation during construction. Possible BMPs that could be implemented include siltation fences,
impervious barriers, and/or straw bales to prevent or contain spills or excessive flows. The FDEP has
the expertise for the work, for the locale, and for the industry to identify BMPs for the contractor and
to evaluate any suggestions for alternates from the contractor.
Groundwater
The Floridan Aquifer underlies the entire region. At St. George Island State Park, it is approximately
50 to 75-feet below sea level, occurring primarily within the Bruce Creek limestone and the
intracoastal formation. Slightly permeable shell beds and then relatively impermeable clays overlie
these strata. The clays may act as an aquiclude and impart artesian characteristics to the underlying
aquifer, but also restrict surface water recharge to the aquifer. Because freshwater recharge is absent
and because the island is surrounded by marine and estuarine waters, the Floridan Aquifer under St.
George Island is infiltrated with salt water and is generally non-potable. The most significant ground
water sources on St. George Island are the shallow water table aquifers occurring within the upper 25
to 30-feet of sands, underlain with an impermeable clay layer. This aquifer is completely dependent
on rainfall directly on the island, which averages about 56-inches annually. Depletion of this aquifer is
a possibility, especially during extensive droughts.
There are no wells on St. George Island State Park; a privately-owned and operated potable water
system provides water service to the park through water mains from the mainland and carried across
the Apalachicola Sound on the County Highway 300 Bridge from Eastpoint to the island.
None of the alternatives are expected to measurably impact groundwater. The structures will not
impact groundwater directly. The septic system is not expected to impact groundwater because the
drain fields contain clean, treated water only. There is a potential for stormwater pollution impacts
from the septic system and drain fields, but these impacts are not probable. The septic systems will be
properly maintained to ensure that no discharge of contaminated water occurs to the drain fields. With
properly maintained septic systems, no contaminated water will be discharged to the shallow water
table.
Impacts during construction will be minimized through the use of BMPs to prevent the discharge of
contaminated surface waters which could impact the shallow aquifer. If an accidental spill were to
occur during construction, the contractor will be responsible for minimizing the amount spilled and
for any clean-up required. Federal and state regulations regarding the reporting and clean-up of
accidental spills will be complied with.
3.1.3 Floodplain Management (Executive Order 11988)
Executive Order 11988 (EO 11988) requires federal agencies to take action to minimize occupancy
and modification of the floodplain. Specifically, EO 11988 prohibits federal agencies from funding
construction in the 100-year floodplain unless there are no practicable alternatives. FEMAs
regulations for complying with EO 11988 are promulgated in 44 CFR Part 9.
FEMA applies the Eight-Step Decision-Making Process to ensure that it funds projects consistent
with EO 11988. The NEPA compliance process involves essentially the same basic decision-making
process to meet its objectives as the Eight-Step Decision-Making Process.
3.1.3.1 No-Action Alternative
The location of the West Beach Use Area and the East Beach Use Area are both within the
100-year floodplain of the Gulf of Mexico. Please refer to Appendix A Exhibit 9, Flood
Insurance Rate Map (FIRM) 12037C0559E for the West Beach Use Area, and Appendix A -
Exhibit 10, Flood Insurance Rate Map FIRM 12037C0576E for the East Beach Use Area.
Appendix A - Exhibit 11, Table Explaining Zones of FIRM maps, can be referenced for
explanations. The former public restrooms / bath house facilities were located in Zones AE
and VE, flood insurance rate zones that corresponds to areas that have a 1-percent chance of
coastal flooding within any year, and have additional hazards associated with storm waves.
The No-Action Alternative would have no adverse effect on the floodplain. The Corolla Sands
would accept and absorb storm waters as beach sands do.
3.1.3.2 Preferred Alternative
The locations of the facilities proposed by the Preferred Alternative are within the general
vicinity of the previous facilities, identified by the FIRM maps referenced above. The
Preferred Alternative places the facilities within the floodplain, exposing the new public
restrooms / bath house structures to future flood and storm wave action events. The proposed
replacement and relocation areas for the public restrooms / bath house facilities, along with
their existing parking lots, remain located within the same FIRM Zones, AE and VE.
The West Beach Use Area Site Plan, included as Appendix C - Sheet 1, shows the restroom
and bath house shower facility structure to be generally within FEMA Flood Zone VE and the
septic system drain fields and paved parking lot within FEMA Flood Zone AE. The East
Beach Use Area Site Plan, included as Appendix C - Sheet 2, shows the restroom and bath
house shower facility structure, as well as the septic system drain fields and paved parking lot
to be generally within FEMA Flood Zone VE This information is also available from the
FEMA FIRM maps, Appendix A Exhibits 9 & 10, with an explanation of the codes as
Exhibit 11.
The risks to the structures from flood events would be minimized by ensuring that local
construction codes and the regulatory floodplain requirements for the AE and VE zones are
followed. The facilities would have specified minimum floor elevations required by the local
floodplain ordinance and by local codes. While the entire island can be flooded with a 100-
year storm event, all practicable measures have been taken to place and construct the public
facilities in a location and at an elevation that are consistent with the publics needs and for the
use of the beach areas, and conform to codes, regulations and sound engineering.
Impacts resulting from the replacement and relocation of these facilities to the floodplain
include minor amounts of fill and the resulting negligible loss of stormwater storage. This fill
amount would be insignificant compared to the amount of storage available for St. George
Island and the Gulf of Mexico. Short term impacts to the floodplain may occur as a result of
construction activities. Appropriate erosion control and BMPs would be utilized to minimize
any impacts.
There are no practicable alternatives to building in the floodplain for these facility
replacements that meet the purpose and need for public recreational use of the beaches. The
entire St. George Island State Park is located within the 100-year floodplain. Avoidance of the
100-year floodplain therefore does not allow for accomplishing the Purpose and Need of this
project. During a flood event, these public use facilities would not likely be called upon for
use. The facilities would be designed to withstand the onslaughts of weather with sufficient
resilience to be put back into service in a short time.
3.1.3.3 Restore to Pre-Disaster Locations with Elevated Facilities
The location of the facilities under this alternative places them precisely where they were prior
to Hurricane Dennis, but at an elevation that would keep the decks and restrooms above the
anticipated wave and storm surge elevations.
Wind blown and tidal surge driven waters would not affect the facilities themselves, but the
sewage disposal system, at least the parts above ground, would be susceptible to water
damages. The pre-treatment tanks, the aeration tanks and the dosing tanks would be just at
ground level on the beach, and at risk. The piping to and the drain fields would be below
grade, and therefore protected.
The risks to the structures from flood events for this alternative are greater than those for the
Preferred Alternative because they are 80 feet closer to the Gulf of Mexico. Risks would be
minimized by ensuring that local construction codes and the regulatory floodplain
requirements for the AE and VE zones are followed. The facilities would have specified
minimum floor elevations required by the local floodplain ordinance and by local codes.
During a flood event, these public use facilities would not likely be called upon for use. The
facilities would be designed to withstand the onslaughts of weather with sufficient resilience to
be put back into service in a short time.
Impacts resulting from the replacement and relocation of these facilities to the floodplain are
similar to the Preferred Alternative and include minor amounts of fill and the resulting
negligible loss of stormwater storage. The fill amount would be insignificant compared to the
amount of storage available for St. George Island and the Gulf of Mexico. Short term impacts
to the floodplain may occur as a result of construction activities. Appropriate erosion control
and BMPs would be utilized to minimize any impacts
Per 44 CFR Part 9, the full 8-step process is required for this project and has been incorporated into
the NEPA process as part of this EA. Disaster-wide initial public notice was published state wide,
with publication in the Pensacola News Journal on September 21, 2005. Final public notice will be
published in the Apalachicola Times on 06/29/2006.
3.1.4 Air Quality
The National Ambient Air Quality Standards (NAAQS), established by the U.S. Environmental
Protection Agency (USEPA), set maximum allowable concentration limits for six criteria air
pollutants to protect the public health, safety, and welfare as a result of the Federal Clean Air Act of
1970 (CAA). The Clean Air Act Amendments of 1990 (CAAA), [42 USC 7401, et. seq.], mandated a
reduction in the emissions of the following six criteria pollutants: nitrogen dioxide (NO2), sulfur
dioxide (SO2), carbon monoxide (CO), lead (Pb), ozone (O3), and particulate matter (PM, microscopic
solid or liquid particles suspended in air). Areas in which air pollution levels persistently exceed the
NAAQS may be designated as non-attainment. States in which a non-attainment area is located
must develop and implement a State Implementation Plan (SIP) containing policies and regulations
that will bring about attainment of the NAAQS.
No portion of this project is within a designated non-attainment area for any of the criteria air
pollutants (http://www.epa.gov/region4/air/naaqs/naaqs.htm) per the USEPA Region 4 web site, as
last updated on Friday, October 19th, 2005. The project does not involve increasing automobile traffic
in the area or increasing traffic capacity, and does not have the potential to change emissions;
therefore, an air quality conformity determination under "Criteria and Procedures for Determining
Conformity to State or Federal Implementation Plans of Transportation Plans, Programs, and
Projects Funded or Approved under Title 23 USC or the Federal Transit Act [40 CFR Part 93] is
not required.
3.1.4.1 No-Action Alternative
There would be no replacement, relocation, or construction activities associated with this
alternative. The No-Action Alternative would not affect air quality.
3.1.4.2 Preferred Alternative
The Preferred Alternative has the potential to have short-term air quality impacts due to
construction equipment. The air quality impacts would be short-term, occurring only while
construction work is in progress. Replacement, permanent relocation and construction of the
public restroom / bath house structures would require grading for the preparation of the sites
and the septic system drain-field and mound locations. Construction equipment would
generate a minimal amount of fugitive dust (particulate matter). Other emissions would be
from the exhaust of construction equipment. Vehicles used by construction crews to reach the
work site would also generate engine exhaust emissions; these would be expected to be
insignificant. Although significant air quality issues associated with the implementation of this
alternative are not expected to occur, the project should incorporate appropriate measures to
control fugitive dust.
Dust and airborne dirt generated by construction activities shall be controlled through general
dust control BMPs or a specific dust control plan could be developed if warranted. The
contractor and St. George Island State Park personnel will meet to review the nature and extent
of potential and known dust-generating activities and will cooperatively develop specific types
of control techniques that may be appropriate to the project and local situations. Some of the
techniques that may warrant consideration include measures such as minimizing the tracking-
out of soil onto nearby publicly-traveled roads, reducing speed on unpaved surfaces, covering
(tarpaulin-covered) haul vehicles, and applying water to exposed surfaces, particularly those
on which construction vehicles travel. Any burning of materials, vegetation or debris would be
undertaken according to relevant State of Florida, local laws and ordinances, including, but not
limited to, the current St. George Island State Park ordinances or regulations of the FDEP.
Appropriate traffic control plans may also serve to limit localized concentrations of airborne
emissions during construction.
If project activities include the stockpiling of sands on-site, the project applicant will be
required at the direction of the engineer to cover these sands to help prevent fugitive dust and
erosion. Fencing and straw/hay bales should be installed to reduce loss. Following
construction activities, exposed, compacted sands would be graded and restored.
No permanent air quality impacts are expected from the operation of the facility. The
Preferred Alternative would not change the total regional emissions of pollutants. The area to
be covered by the facilitys services remains the same and the distribution of trips within and
outside St. George Island State Park and the beach areas are not expected to change as a result
of constructing the Preferred Alternative; there should be no significant statistical difference in
the distances traveled annually.
The Preferred Alternative does not have the potential for long-term, adverse air quality effects
and none are anticipated.
3.1.4.3 Restore to Pre-Disaster Locations with Elevated Facilities
The impacts of implementing the Restore to Pre-Disaster Locations with Elevated Facilities
are precisely the same as with the Preferred Alternative, as discussed above.
3.1.5 Coastal Zone Management
The Coastal Zone Management Act (CZMA) encourages states to preserve, protect, develop, and,
where possible, restore or enhance valuable natural coastal resources. Participation by states in the
CZMA is voluntary. To encourage states to participate, the act makes federal financial assistance
available to any coastal state or territory that is willing to develop and implement a comprehensive
coastal management program. The federal government has accepted that each state that develops and
implements a program to protect their coastal zones has the ability and right to issue permits for any
project that could impact these areas, even if the project is a federally-aided or a federally
implemented one.
Federal consistency has become a prime concern with the regulatory agencies, and ways and means to
obtain consistency are being implemented in all jurisdictions. From the Florida State Statutes, Chapter
380, Section 380.23, the following is related to Federal consistency: When a federally licensed or
permitted activity subject to federal consistency review requires a state license, the issuance or
renewal of a state license shall automatically constitute the state's concurrence that the licensed
activity or use, as licensed, is consistent with the federally approved program.
The Coastal Construction Control Line Program (CCCL) is an essential element of Florida's coastal
management program. It provides protection for Florida's beaches and dunes while assuring
reasonable use of private property. This program establishes a line along sandy beaches within the
State for which any work occurring seaward of the line requires a FDEP permit. The line is
established on each beach based on a 100-year storm event and establishes the landward limit of
jurisdiction. The CCCL line for the project area is shown on the Site Plans for each Use Area,
Appendix A, Preferred Plans, Sheets 1 & 2. In both areas, the CCCL line is landward of the entire
parking lot, with only small portions of the roadway bypassing the parking lots lying landward of the
CCCL line.
3.1.5.1 No-Action Alternative
The No Action Alternative would have no impacts on Coastal Zone Management issues.
3.1.5.2 Preferred Alternative
The Preferred Alternative is located seaward of the CCCL at both beach use areas, and thus is
in need of a permit from the FDEP. Permit number FR-805 has already been issued by the
FDEP. By issuance of this permit, FDEP and all of the cooperating and reviewing agencies
have agreed that the Preferred Alternative is in compliance with the CZMA. A copy of this
permit is contained as Item No. 1 in Appendix F. Special conditions have been developed in
cooperation between the FDEP, the FWC, FEMA and the USF&WS, and have been
incorporated into the permit requirements.
3.1.5.3 Restore to Pre-Disaster Locations with Elevated Facilities
The Restore to Pre-Disaster Locations with Elevated Facilities Alternative is located seaward
of the CCCL at both beach use areas, and thus is in need of a permit from the FDEP. No
permit has been reviewed or issued by the FDEP for this alternative. If this alternative were
chosen, a CCCL permit would have to be applied for,
3.1.6 Coastal Barriers Resources
While portions of Saint George Island are located within Coastal Barrier Resources Act (CBRA)
units, the areas impacted by the replacement buildings within the state park are not located within a
CBRA unit, rather they are in an Otherwise Protected Area. Exhibit 12 in Appendix A indicates that
the Santa Rosa Island Units (CBRA Unit FL-90) western border is located approximately one mile
east of the replacement building. A CBRA Otherwise Protected Area (Unit FL-90P, Saint George
Island) is located approximately two miles to the west, a mile and a half to the north, and over four
miles to the east of the replacement buildings. There are no impacts to CBRA units from any of the
alternatives.
3.2 Biological Environment
3.2.1 Terrestrial and Aquatic Environment
The local terrestrial and aquatic environment consists mainly of sandy beach and the associated Gulf
of Mexico.
Found within St. George Island State Park are a number of natural communities. The upland natural
communities include beach dune, scrub, scrubby flatwoods, coastal grasslands and mesic flatwoods.
The wetland communities include wet flatwoods, depression marsh, estuarine tidal marsh, coastal
dune lake and estuarine mollusk reef. These features and communities provide for a broad array of
recreational and educational opportunities for park visitors.
3.2.1.1 No-Action Alternative
The No-Action Alternative would not involve the terrestrial or aquatic environment.
3.2.1.2 Preferred Alternative
Since the Preferred Alternative area and relocation site is disturbed from the presence of the
paved parking lots and the demolition of the former storm damaged public restrooms and bath
house facilities, no impacts to the terrestrial or aquatic environment are anticipated at the
replacement structure locations. The new septic fields would be constructed in and around one
of the two drain fields previous locations at each beach site location. These areas have been
previously disturbed.
3.2.1.3 Restore to Pre-Disaster Locations with Elevated Facilities
Since the Restore to Pre-Disaster Locations with Elevated Facilities beach sites are disturbed
from the presence and demolition of the previous restrooms and bath house shower facility
structures, no impacts to the terrestrial or aquatic environment are anticipated at the
replacement structure locations. The new septic fields would be constructed in and around two
of the two previously disturbed areas at each beach site location.
3.2.2 Wetlands (Executive Order 11990)
Executive Order 11990 (EO 11990), Protection of Wetlands, requires federal agencies to take action
to minimize the loss of wetlands. FEMAs regulations for complying with EO 11988 are promulgated
in 44 CFR Part 9. The NEPA compliance process also requires the identification of any direct or
indirect impacts to wetlands which may result from federally funded actions.
FEMA applies the Eight-Step Decision-Making Process to ensure that it funds projects consistent
with EO 11990. This process is the same process as required for compliance with EO 11988
(Floodplain Management). The NEPA compliance process involves essentially the same basic
decision-making process to meet its objectives as the Eight-Step Decision-Making Process.
The National Wetland Inventory (NWI) map depicting wetlands in Franklin County, Florida by the
USF&WS Geocortex Internet Mapping Framework Wetlands Online Mapper was examined for
information related to the presence of wetlands within the project area. The NWI maps (Goose Island
and Sugar Hill Quadrangle) indicate that there are no wetlands involved with the proposed sites.
Additionally, the soil type present at the proposed sites is Corolla sand, 0 to 5-percent slopes, rarely
flooded (U.S. Natural Resource Conservation Service (NRCS) Soil Survey of Franklin County). This
soil is not on the state hydric soils list. An environmental resource map indicating the NWI identified
wetlands located in the project vicinity can be found in Appendix A Exhibit 13.
Photographs were taken during a site visit and are shown in Appendix A, Photographs, Collections 1
and 2. From the photographs, soil survey, and the NWI data, a Professional Wetland Scientist
confirmed that wetlands are not directly or indirectly associated with the proposed site. Thus, wetlands
are not involved with nor impacted by the project.
3.2.3 Threatened and Endangered Species
The West Beach Use Area and the East Beach Use Area of St. George Island State Park have been
routinely visited by and utilized for nesting by sea turtles. Loggerhead (Caretta caretta) [threatened],
green (Chelonia mydas mydas) [endangered], and leatherback (Dermocheyls coriacea) [endangered]
sea turtles are those most often encountered. The loggerheads and greens are known to utilize the
beach, and many nests have occurred here over the years.
Two other federally protected species are also known to utilize St. George Island State Park. Piping
plovers (Charadrius melodus) [threatened] utilize the park in the winter for foraging. The park is
located within an area designated as critical habitat by USF&WS for this species (FL-9 unit). Bald
eagles (Haliaeetus leucocephalus) [threatened] are known to utilize the park between October 1st and
May 1st for nesting.
In addition to federally protected species, there are several state protected species that utilize St.
George Island State Park. Snowy plovers (Charadrius alexandrinus tenuirostris) [threatened] are
known to nest and forage within the park, least terns (Sterna antillarum) [threatened] are known to
nest within the park, and American oystercatchers (Haematopus palliates) [species of special concern]
are known to nest and forage within the park.
The USF&WS works closely with the FDEP to establish ways to protect and preserve endangered
species habitat. Currently biologists patrol the approximate eight miles of St. George Island State Park
beach in the early mornings of the nesting season looking for any evidence of sea turtle activity. When
a nest is discovered, it is located by GPS and the biologists take steps to fence it off from predators
and human interference, so as to minimize intrusion into the natural maturation process. No turtles
have ever been known to ascend to the area where the proposed construction would occur, in an area
beyond the berm and parallel to the shore.
Pursuant to the Endangered Species Act (ESA) and/or the Fish and Wildlife Coordination Act
(F&WCA), FEMA has requested informal consultation with the USF&WS. The USF&WS and
National Marine Fisheries Service share Federal jurisdiction for sea turtles; USF&WS has lead
responsibility on the nesting beaches and the National Marine Fisheries Service is responsible for the
marine environment. USF&WS has provided information on the projects potential to impact federally
protected species. Additionally, FEMA has obtained information on the potential for the presence of
any state protected species from the FFWCC. The FFWCC classifies listed species in three categories
endangered, threatened and species of special concern. Copies of correspondence requesting
consultation and information from these agencies, as well as their responses, can be found in
Appendix C.
3.2.3.1 No-Action Alternative
The No-Action Alternative would not impact threatened or endangered species in the area, or
critical habitat.
3.2.3.2 Preferred Alternative
The Preferred Alternative is not likely to adversely affect threatened or endangered species. To
date, no turtles have been known to ascent to the beach area where the proposed construction
would occur. With regards to nesting and foraging birds, the new facilities would be
constructed within disturbed areas located between parking lots, thereby minimizing the
probability that these areas would be utilized by birds.
In addition, FDEP has agreed to comply with mitigation measures suggested by USF&WS.
These measures include:
1. Monitoring of shorebird presence and activities by Park staff from January 27, 2006 until
project construction is complete.
2. Daily sea turtle nesting surveys, beginning on May 1, 2006 by park staff, to continue until
September 1st.
3. Tarps or plastic material will be placed over the proposed sites for the two sewage disposal
drain fields and will be accomplished by the park staff or the contractor as soon as the state
permit notice-to-proceed is issued.
4. Disturbance Free Zones will be posted away from the construction areas where potential
bird resting and nesting may occur, and will be conducted by park staff prior to
commencement of construction.
5. Post and rope will be placed to delineate the beach access areas from each of the beach
pull-off parking areas. This will be done by the general contractor when these pull-off
parking areas are improved and opened for public use.
6. Additional compatible beach-quality sand will be placed in areas just seaward of the two
beach use area sites to construct a continuous dune system approximately 500-feet in
length and overlapping the proposed construction areas. This will form a dune-like
feature that will discourage crawling of sea turtles into the construction areas. This will be
performed by park staff or by the general contractor prior to May 1, 2006.
7. A Hurricane Ivan Dune Restoration Planting Project will be conducted during the months
of April and May 2006 to enhance the beach dune community, thereby providing a benefit
to both shorebirds and nesting sea turtle habitat. This will be done by landscape contractors
and monitored by Division Staff along with the environmental engineering consultants.
Because of the reasons previously stated, and because FDEP has agreed to comply with
USF&WS suggested mitigation measures, the project is not likely to adversely affect federal
or state protected species. USF&WS has concurred that the project is not likely to adversely
affect nesting sea turtles, non-breeding piping plovers, and designated critical habitat for the
piping plover in their February 28, 2006 letter (Appendix C - Contact 4).
3.2.3.3 Restore to Pre-Disaster Locations with Elevated Facilities
The Restore to Pre-disaster Conditions Alternative is not likely to adversely affect threatened
or endangered species, although it has a greater potential to impact nesting sea turtles than the
Preferred Alternative. This alternative would result in the reconstruction of the facilities within
the same footprint, though elevated, which is more seaward than the Preferred Alternative.
Since this location is closer to the Gulf of Mexico, nesting sea turtles could be expected to visit
the construction zone. Additionally, because of the more seaward location, a berm
discouraging the crawling of sea turtles would not be practicable. Such a berm would interfere
with beach use by the public.
The project would incorporate other mitigation measures, including daily monitoring for
shorebirds and turtles. Any sea turtle nests that were encountered would be relocated. Tarps
would be placed over sewage disposal drain fields, disturbance free zones would be
established and beach access areas would be established. With these mitigation measures in
place, the project is not likely to adversely affect protected species.
3.3 Hazardous and Special Waste Materials
In general hazardous materials are substances that are classified as either corrosive, ignitable,
reactive, or toxic. The proposed project location is not located near any identified Comprehensive
Environmental Response, Compensation, and Liability Information System (CERCLIS) sites included
in the USEPA CERCLIS listing last updated as of 28 October 2005.
3.4 Socioeconomics
3.4.1 Zoning and Land Use
The St. George Island State Park area is not incorporated and, as such, US Census data specific to this
area are not available. As a vacation destination, the population at any one time may consist of a
majority of tourists and vacationers, rendering the value of numbers, and percentages less than
helpful. Of more value is a concentration on land uses rather than permanent residents.
St. George Island State Park is inhabited year-round. It has visitor oriented beaches with parking and
picnic shelters, it previously had restroom and bath house facilities; all of these amenities are oriented
to day visitors. All the property in the immediate vicinity of the project is publicly owned. The
mission of the FDEP State Park Service is to provide resource-based recreation while preserving,
interpreting and restoring natural and cultural resources. Operations at St. George Island State Park
fully support this mission. Latest data show over 200,000 visitors used the beach area, camping area
and trails in the park in fiscal year 1999-2000. The management of this volume of public use on the
shoreline areas of the park continues to be the greatest challenge in the FDEP State Park Services
management of the area. The St. George Island State Park Detailed Park Map (Appendix A
Exhibit 2) identifies the park amenities.
3.4.1.1 No-Action Alternative
Under this alternative, existing land use would be disrupted because there would be no
restrooms or bath facilities to service the visitors. This could impact the number of visitors the
St. George Island State Park receives each year and the ability of the State Park Service to
fulfill their mission to the extent it has in the past. No impacts to zoning would occur,
however.
3.4.1.2 Preferred Alternative
Under the Preferred Alternative, construction would take place in a location where this type of
public facility has been since 1982. The construction of the facility would support current land
use. No impacts to zoning would occur.
3.4.1.3 Restore to Pre-Disaster Locations with Elevated Facilities
Under this alternative, construction would take place in a location where this type of public
facility has been since 1982. The construction of the facility would support current land use.
No impacts to zoning would occur.
3.4.2 Aesthetics and Visual Resources
St. George Island is a long and narrow island off the coast of Floridas Panhandle. The entire island
lies within the 100-year floodplain, with waves, tides and storm surges easily intruding well past the
beaches. This constant interaction with the water has resulted in a southern perimeter of white quartz
sands, with dunes and beaches defending the interior and the mainland.
The St. George Island State Park is a major tourist destination for day trips to the beach. The St.
George Island area is a popular area, considering the numbers of visitors present and their density.
Located just across the bay from historic Apalachicola, Florida, St. George Island offers superior
beach vacation accommodations. This twenty-nine mile stretch of land is no wider than a mile at its
widest point, providing access to both the excellent fishing waters of Apalachicola Bay and the
emerald green waters of the Gulf of Mexico. Strict building codes and low density zoning regulations
have preserved the beauty of St. George Island. Wildlife abounds on the island, affording bird
watching opportunities. Shell collectors enjoy miles of pristine white sand beaches with excellent
shelling opportunities.
The beaches are preserved in their natural state, for the enjoyment of all, today and into the future.
The landward edge of the beach area has been altered to handle the crowds, to serve and satisfy the
tourists and to accommodate the statutory requirements. The aesthetic and visual resources of St.
George Island State Park are significant. The white sand beaches and Gulf of Mexico provide for
considerable aesthetics. Photographs of the specific locations within the Park where the restrooms and
bath house facilities will be located can be seen in Collection 1 in Appendix A, Photographs.
3.4.2.1 No-Action Alternative
The No-Action Alternative would not impact visual resources.
3.4.2.2 Preferred Alternative
The Preferred Alternatives proposed one-story restroom and bath house shower facility
structure would be approximately the same size as either of the previous buildings. The design
for the structure is intended to provide a structure that blends into the type of structures
typically found in this environment. The facility should be aesthetically acceptable.
Being located within the footprint of the pre-existing parking lot area, very little view of the
beach will be lost. The mass of the structure at each facility will be essentially half that which
existed before with two structures. The view from the proposed building would be notable,
allowing the beach front vista to be seen. Overall, the aesthetics of the area will be enhanced
over pre-existing conditions because of the reduced number of structures and improved
aesthetic appeal of the new structure.
3.4.2.3 Restore to Pre-Disaster Locations with Elevated Facilities
The Restore to Pre-disaster Conditions would result in the installation of two structures at
each facility. The facilities would be less aesthetically acceptable, being located at an elevation
significantly higher than the adjacent pavilion buildings, yet within the footprint of the pre-
existing structures. The views from the proposed buildings would be notable, allowing the
beach front vista to be seen. On the other hand, the taller buildings would block more of the
views from further landward perspectives. The aesthetics of the area would be less than the
Preferred Alternative, however because of the greater number of structures and the increased
height of them.
3.4.3 Noise
Noise, defined for the purposes of this discussion as undesirable sound, is federally regulated by the
Noise Control Act (NCA) enacted in 1972 (PL 92-574). Although the NCA gives the USEPA
authority to prepare guidelines for acceptable ambient noise levels, it only charges federal agencies
that operate noise-producing facilities or equipment to implement noise standards. The USEPA
guidelines, and those of many federal agencies, state that outdoor sound level in excess of 55 dBA
(decibels, A-weighted noise scale) are normally unacceptable for noise-sensitive residential land
uses such as residences, schools and hospitals, especially when there is identified outside human
activity. The range of human hearing is from approximately 20 dBA (the threshold of hearing) to 120
dBA (the threshold of pain). Under most conditions, persons with normal hearing would require a
change of 5 dBA, either more or less, before a noticeable change in the noise environment would
occur. A change of 3 dBA, either more or less, would be at the lower end of barely perceptible
change. The affects of noise on people usually result in general annoyance, disturbance with sleep,
and interference with vocal communication.
3.4.3.1 No-Action Alternative
The No-Action Alternative would not generate any construction or operating noise. This
alternative would not result in any changes in the existing or future ambient noise of the
recreational beach areas.
3.4.3.2 Preferred Alternative
The existing ambient noise levels in the vicinity of the location of the Preferred Alternative are
consistent with levels experienced throughout the public use beach areas of St. George Island
State Park. Occupied and operating public restrooms and bath house facilities will not
normally generate or directly contribute to the ambient noise levels in the area. The facility is
situated in the immediate vicinity of park access road along the beachs two large parking lots.
These features, the access road and parking lots, are the ambient noise generators of the area.
Short-term, sporadic noise generation may be associated with the necessary and critical
function of the emergency, first-aid and public safety services that might be drawn to the
facilities for the protection of human life, however. This emergency services response noise
would be the result of sirens being activated on responding vehicles.
Construction noise is expected to be generated from the site as a result of pile driving,
machinery and truck traffic necessary for the supply of materials and building erection. The
construction noise would be greatest during the pile-driving phase during the first few weeks
of the construction schedule. All of the construction noises would be of short duration and
would not have a sustained affect on the surrounding recreational users of the beach.
Construction equipment, delivery and storage would be located in already disturbed areas (the
parking lots and service drive/areas) away from occupied beach activities. Because of the short
durations of noise generated, and the fact that the beach area will remain closed to the public
until construction is substantially completed, there would be no significant adverse noise
impacts resulting from the alternative.
3.4.3.3 Restore to Pre-Disaster Locations with Elevated Facilities
The Restore to Pre-disaster Conditions Alternative would have the same noise impacts as the
Preferred Alternative. The access road and parking lots would be the ambient noise generators
of the area. Short term, sporadic noise would occur from emergency service response. Short
term noise impacts would occur during the construction phase. Because of the short term
duration of the construction noise, no significant adverse noise impacts would result from this
alternative.
3.4.4 Public Services and Utilities
The concept of Public Service, when discussed with potential projects, generally refers to police, fire,
ambulance, transit, etc. A roadway project can facilitate access. A commercial building or shopping
center can cause congestion on the streets and require more public services. This project is quite
different; it is the public service of providing basic health and sanitation facilities to the general public
using the public beaches of St. George Island State Park.
The public services and utilities currently existing at the State Park are:
* There are only a few sanitary sewers on the island, and only associated with higher end
condominium developments. There are none within the St. George Island State Park. All
sewerage is handled by septic fields or aerobic systems.
* Electrical power is supplied by Florida Power out of their Apalachicola facilities.
* Gas service is generally propane, with individual tanks at each user location. There are none at
either of the two proposed construction sites.
* Potable water is supplied to the Park (and to the rest of the island) by Water Management
Services, St. George Island. Their water comes from four wells on the mainland and is pumped
in pipes attached to the County Highway 300 bridge over Apalachicola Sound.
* Emergency services are supplied by the St. George Island Volunteer Fire Department and the
Franklin County Sheriff, St. George Island Sub-station.
The service that was provided by the pre-disaster West Beach Use Area and East Beach Use Area
restrooms and bath house facilities is not adequately provided for any longer. The proposed project
intends to combine restrooms and bath house facilities services into a single facility, accessible to the
beach, and accessible to landward support from the paved parking lots and connected access road
transportation.
3.4.4.1 No-Action Alternative
If the No-Build Alternative is selected, the public services will be poorly provided for
(portable, chemical toilets) or not provided for at all. The No-Action Alternative would
maintain the current negative impact on the visiting public and the St. George Island State
Park community.
3.4.4.2 Preferred Alternative
Under the Preferred Alternative, public services would be restored to a level that was present
before Hurricane Dennis. The implementation of the Preferred Alternative would have
benefits to the St. George Island State Park and local community.
3.4.4.3 Restore to Pre-Disaster Locations with Elevated Facilities
Under the Restore to Pre-Disaster Locations with Elevated Facilities Alternative, public
services would be restored to a level that was present before Hurricane Dennis. The
implementation of this alternative would have benefits to the St. George Island State Park and
local community.
3.4.5 Traffic and Circulation, Volume, Parking, and Access
The park is located approximately 76 miles southwest of Tallahassee on County Highway 300, on St.
George Island, ten miles southeast of Eastpoint. Traffic onto St. George Island must use US 98/319 to
the municipality of Eastpoint, and then the causeway carrying County Highway 300 across St. George
Sound from Eastpoint to the island. County Highway 300 then heads to the northeast end of the island,
and the eight-mile State Park.
Privately owned residential and commercial properties are located south of County Highway 300,
including most tourist related industries such as homes and condominiums for rent. Similar
developments occur between County Highway 300 and the State Park. Once within the State Park,
County Highway 300 is the only linear roadway; it ends at the East Beach Use Area (see Appendix A
Exhibit 2 and Appendix A, Photographs first photo in Collection 1).
The bridge leading to and from the peninsula and Eastpoint is a two-lane facility. During peak travel
periods, the single lane of traffic could get congested and traffic speeds would be reduced. Local
access is provided along the island via private automobiles and bicycles.
At each of the Beach Use Areas, a large paved parking lot is present to accommodate day visitors to
the beaches and off shore waters.
3.4.5.1 No-Action Alternative
No impacts to traffic or public transportation are anticipated under the No-Action Alternative.
It is possible that the number of visitors to the Park would decline if the restroom and bathing
facilities were not replaced. Future use of the Park cannot be predicted with certainty, but
usage changes are not anticipated to cause significant impacts to traffic.
3.4.5.2 Preferred Alternative
The Preferred Alternative would not result in long term impacts to traffic or public
transportation under the proposed action. The buildings are support facilities rather than
attractions in themselves. The replacement of the demolished bathhouses will permit the State
Park to reopen to visitors, the purpose for which they were dedicated. It will draw no
additional traffic other than those already coming to the beaches. Traffic to and from the
facility is on foot.
Short term impacts during construction should cause no disturbance to the access roads as the
park is closed due to lack of public facilities.
3.4.5.3 Restore to Pre-Disaster Locations with Elevated Facilities
Impacts from the Restore to Pre-disaster Conditions would be the same as for the Preferred
Alternative. The facilities would not result in increases in traffic. No short term impacts during
construction would occur because the park is closed due to lack of facilities.
3.4.6 Environmental Justice (Executive Order 12898)
On February 11, 1994, President Clinton signed Executive Order 12898 (EO 12898), entitled,
Federal Actions to Address Environmental Justice in Minority Populations and Low-Income
Populations. This EO directs federal agencies, to make achieving environmental justice part of its
mission by identifying and addressing, as appropriate, disproportionately high and adverse human
health or environmental effects of its programs, policies, and activities on minority populations and
low-income populations in the United States . . . . Its goals are to achieve environmental justice,
fostering non-discrimination in federal programs that substantially affect human health or the
environment, and to give minority or low-income communities greater opportunities for public
participation in and access to public information on matters relating to human health and the
environment.
Approximately 2,334 persons reside in the community of Apalachicola and 2,158 persons reside in the
community of Eastpoint (CENSUS 2000), on the mainland of Florida. This is in dramatic contrast to
the yearly tourist and recreational population of approximately one-million persons passing through
the Apalachicola, Eastpoint and St. George Island area, with a significant proportion using or visiting
the beach areas of St George Island State Park. In general, for the Apalachicola area:
* Median household income is below state average,
* Unemployed percentage is below state average,
* Black race population percentage is significantly above state average,
* Hispanic race population percentage is significantly below state average,
* Foreign-born population percentage is significantly below state average,
* Institutionalized population percentage is above state average, and.
* Percentage of population with a bachelor's degree or higher is below state average.
In general, for the Eastpoint area:
* Median household income is below state average,
* Unemployed percentage is below state average,
* Black race population percentage is significantly below state average,
* Hispanic race population percentage is significantly below state average,
* Median age is above state average,
* Foreign-born population percentage is significantly below state average,
* House age is significantly below state average,
* Percentage of population with a bachelor's degree or higher is significantly below state
average, and
* Population density is below state average for cities.
In compliance with FEMAs policy implementing EO 12898, Environmental Justice, the
socioeconomic conditions and potential effects related to the No-Action Alternative, the Preferred
Alternative and the Restore to Pre-Disaster Conditions Alternative have been reviewed.
3.4.6.1 No-Action Alternative
The No-Action Alternative course of action will affect all persons using the public beach areas
of St. George Island State Park because there would be a continuation of the lack of public
restrooms that was previously provided for. The No-Action Alternative would not have a
disproportionately high impact on the minority or low-income populations of the communities
that use the public beaches.
3.4.6.2 Preferred Alternative
The construction of the Preferred Alternative will affect all the users of the public beaches
equally. There will be no disproportionately high or adverse impacts on minority or low-
income populations of the communities that use the public beaches. Public restrooms and bath
facilities would be available to all populations of the communities that use the public beaches.
The Preferred Alternative would benefit the entire population that uses the public beaches
because of the restrooms and bath house facilities equally available to all.
3.4.6.3 Restore to Pre-Disaster Locations with Elevated Facilities
The Restore to Pre-disaster Conditions with Elevated Facilities Alternative would, similar to
the Preferred Alternative, have no disproportionately high or adverse impacts to minority or
low-income populations. This alternative would benefit the entire population that uses the
public beaches.
3.4.7 Public Health and Safety (including Executive Order 13045)
The purpose and need of this project is to address the loss of the public facilities that housed the only
permanent, publicly accessible restrooms and showers on St. George Island State Park.
On 21 April 1997, President Clinton signed Executive Order 13045 (EO 13045) entitled Protection
of Children from Environmental Health Risks and Safety Risks. EO 13045 directs federal agencies to
make it a high priority to identify and assess environmental health risks and safety risks that may
disproportionately affect children and to ensure that its policies, programs, activities, and standards
address disproportionate risks to children that result from environmental health risks or safety risks.
EO 13045 does apply to the project because the alternatives affect the safety and security children.
When Hurricane Dennis damaged the exiting facilities, the damaged structures were a public safety
hazard. Authorities, after assessing the damages and opportunities, elected to demolish the shells of
the restroom and shower facilities and clean the area for the immediate protection of all concerned.
No hazardous materials or special wastes exist at the site. Seismic preparedness is not an issue in this
geological area (see Section 3.1.1). Periodic flooding is an issue, as discussed in Section 3.1.3. Local
codes require a three-foot freeboard above the 100-year storm elevation, and the proposed facility
complies with that code.
The premier health issues for this project are sanitation and the preservation of the clean beachfront.
Without the restrooms and bath houses, these services are not being provided for to a level that meets
the health and safety needs of the beach user. Temporary use of portable chemical toilets may be
implemented, but they can be tipped over in storms or as pranks, resulting in localized contamination.
The lack of showers for personal hygiene would not be addressed.
3.4.7.1 No-Action Alternative
The No-Action Alternative results in adverse impacts to the general public and children
because of the lack of permanent sanitation facilities. The No-Action Alternative would not
result in construction impacts that could adversely affect the population in general. There
would therefore be no potential risks to the safety of construction personnel during
construction activities.
3.4.7.2 Preferred Alternative
The implementation of the Preferred Alternative will have beneficial impacts on public health
and safety by providing permanent sanitation facilities.
During construction of the facility, the Preferred Alternative could present safety risks to those
performing the construction activities. To minimize risks to safety and human health, all
construction activities will be performed using qualified personnel trained in the proper use of
the appropriate equipment, including all appropriate safety precautions; additionally, all
activities will be conducted in a safe manner in accordance with the standards specified in
Occupational Safety and Health Act (OSHA) regulations. The construction site is located
within a portion of the Park that is currently closed to the public. Potential safety impacts to
children during construction would therefore not occur, and EO 13045 would not apply
because of construction impacts.
3.4.7.3 Restore to Pre-Disaster Locations with Elevated Facilities
The potential safety impacts of the Restore to Pre-Disaster Locations with Elevated Facilities
are the same as that for the Preferred Alternative. The overall project will provide health
benefits with the restoration of restrooms and bathing facilities. There would be no impacts
during construction because this portion of the Park is closed and will be closed during
construction.
3.5 Cultural Resources
As one of the considerations of NEPA, impacts to historic properties are to be considered and
protected under Section 106 of the National Historic Preservation Act (NHPA), as amended, and
implemented by 36 CFR Part 800. Additionally, Executive Order # 13175 - Consultation and
Coordination With Indian Tribal Governments (EO 13175) must be considered with regards to
cultural resources. EO 13175 was issued in order to establish regular and meaningful consultation and
collaboration with tribal officials in the development of Federal policies that have tribal implications,
to strengthen the United States government-to-government relationships with Indian tribes, and to
reduce the imposition of unfunded mandates upon Indian tribes. These and other related statutes
require Federal agencies to look at the potential consequences of their decisions, and to incorporate
into their actions measures to avoid, minimize or mitigate any adverse impacts to historic or cultural
resources resulting from such actions, to the maximum extent possible or practicable.
FEMA must determine, in consultation with the appropriate State Historic Preservation Officer
(SHPO) and Tribal Historic Preservation Officer (THPO), what effect, if any, their actions will have
on historic properties and determine if the project will have an adverse effect on these properties.
FEMA must consult with the appropriate agencies on ways to avoid, minimize, or mitigate the adverse
effect. To comply with and expedite the review process under Section 106, the Florida SHPO, State of
Florida Department of Community Affairs (FDCA), Division of Emergency Management (DEM) and
FEMA have entered into a Programmatic Agreement (PA) for the administration of FEMA programs
in Florida. In accordance with this agreement, when FEMA is determined to be the lead agency,
FEMA will coordinate the Section 106 review activities with all Federal agencies and Tribes that
participate.
Enabling Legislation for the cultural and historic review in this EA includes, but is not limited to the
following:
* National Historic Preservation Act of 1966, as amended, Historic and Cultural Resources:
Section 106 [16 USC 470(f) et seq.];
* Archeological Resources Protection Act of 1977 [16 USC 470(aa)-11];
* Archeological and Historic Preservation Act [16 USC 469-469(c)];
* Native American Grave Protection and Repatriation Act (NAGPRA) [25 USC 3001-3013]:
and,
* EO 13175 - Consultation and Coordination With Indian Tribal Governments
3.5.1 Historic Architecture
In accordance with the PA, a FEMA historic specialist has reviewed this project. The National Park
Services National Register of Historic Places database, Florida Master Site File, and the FEMA-EST
databases were consulted and no historic buildings or structures are located or were identified within
the Area of Potential Effect (APE) or immediately adjacent areas. Based on this information, FEMA
has determined that this undertaking will have no adverse effects on historic buildings or structures.
The Florida SHPO has concurred with these findings in a letter dated February 2, 2006 with a finding
of no effect on historic properties.
3.5.2 Archaeological Resources
FEMA conducted a field inspection of the St. George Island activity areas at the West and East Beach
Use Areas. No areas of prehistoric or historical archaeological interest were observed. A review of the
Florida Master Site File, and the FEMA-EST database indicated that no archaeological sites are
located within the APE; however three archaeological sites were identified in the immediately
adjacent areas (Appendix C Contact No. 1, Page 4). These sites are:
* Site FR 840, Rattlesnake Gove, a prehistoric shell midden is located approximately 2.17 miles
southeast of the West Beach Use Area.
* Site FR 845, Midden, this is a low density artifact scatter located approximately 2.0 miles
southeast of the West Beach Use Area.
* Site FR 846, Rattlesnake Cove #2, unspecified by recorder, is located approximately 1.9 miles
southeast of the West Beach Use Area.
FEMA has reviewed the existing data and based on available information has determined that the
proposed undertaking will not adversely affect any known archaeological resources within the APE or
adjacent areas. The Florida SHPO has concurred with these findings in a letter dated February 2, 2006
with a finding of no effect on historic properties. To ensure that during the construction process any
items of archaeological, historical or architectural interest are protected, the FDEP, Division of
Recreation and Parks and its contractors shall monitor excavation activities. In the event any items of
interest are discovered, FDEP should make all reasonable efforts to protect the items and to avoid
further harm to the items until the significance of the discovery can be determined. The FDEP shall
notify FEMA and the SHPO immediately.
3.5.1 Indian Coordination and Religious Sites
Under the Section 106 review process, agency officials are required to consult with any federally
recognized Indian tribe that attaches religious or cultural significance to historic properties that may
be affected by an undertaking, and invite them to become consulting parties. Consultation with Indian
tribes is a unique legal relationship and is recognized as a government to government relationship.
Requests for evaluation of the presence or absence of known archaeological or Indian Religious sites
within the proposed project areas were submitted to both of the federally recognized tribal groups in
Florida. The two federally recognized Florida tribes are the Seminole Tribe of Florida and the
Miccosukee Tribe of Indians of Florida. Ongoing coordination with the two federally recognized
Native American Indian Tribes is included in Appendix C, Contact 1 (Miccosukee Indian Tribe of
Florida) and Contact 2 (Seminole Tribe of Florida). The Miccosukee Tribe of Indians of Florida has
expressed their desire to be a consulting party on this project (letter dated March 7, 2006).
Consultation is ongoing.
Affected Environment and Consequences - Table 1 Impact Summary
The following table summarizes the summary of the issues and anticipated impacts for the
replacement of the St George Island State Park restrooms and bath house shower facility structures at
West Beach Use Area and East Beach Use Area from the various alternatives.
AFFECTED ENVIRONMENT and CONSEQUENCES
Table 1 Impact Summary
Affected Environment Issue Areas Physical Environment
Location in Text (Section) 3.1
Affected Environment Issue Areas Topography and Soils, Seismicity & Prime Farmland (E.O. 12699)
Location in Text (Section) 3.1.1
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None
Restore to Pre-Disaster Locations with Elevated Facilities
Impacts due to interference with accretion of primary dune which is developing.
Affected Environment Issue Areas Water Resources and Water Quality: Surface Water & Groundwater
Location in Text (Section) 3.1.2
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
Short term impacts to surface waters may occur as a result of construction activities. Appropriate erosion control
and BMPs would be utilized to minimize any impacts. Potential for stormwater pollution impacts from the septic
system and drain fields exist, but impacts are not probable.
Restore to Pre-Disaster Locations with Elevated Facilities
Short term impacts to surface waters may occur as a result of construction activities. Appropriate erosion control
and BMPs would be utilized to minimize any impacts. Potential for stormwater pollution impacts from the septic
system and drain fields exist, but impacts are not probable.
Affected Environment Issue Areas Floodplain Management (E.O. 11988)
Location in Text (Section) 3.1.3
Summary of Impacts - Alternatives
No-Action
Restores minimal amount of floodplain storage; removes potential stormwater pollution source from septic system
and drain fields.
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
Impacts from this alternative result in minor amounts of fill within the floodplain and the resulting negligible
loss of stormwater storage. This fill amount would be insignificant compared to the amount of storage available
for St. George Island and the Gulf of Mexico. Short term impacts to the floodplain may occur as a result of
construction activities. Appropriate erosion control and BMPs would be utilized to minimize any impacts. Potential
for impacts to stormwater pollution from the septic system and drain fields exist, but are not probable.
Restore to Pre-Disaster Locations with Elevated Facilities
Impacts from this alternative result in minor amounts of fill within the floodplain and the resulting negligible loss
of stormwater storage. This fill amount would be insignificant compared to the amount of storage available for
St. George Island and the Gulf of Mexico. Short term impacts to the floodplain may occur as a result of construction activities. Appropriate erosion control
and BMPs would be utilized to minimize any impacts. Potential for impacts to stormwater pollution from the septic
system and drain fields exist, but are not probable.
Affected Environment Issue Areas Air Quality
Location in Text (Section) 3.1.4
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
This alternative has the potential to have
short-term air quality impacts due to construction equipment. The air quality impacts would be short-term, occurring
only while construction work on the restrooms and bath house shower facility structures is in progress. Dust
and airborne dirt generated by construction activities shall be controlled through general dust control
BMPs or a specific dust control plan could be developed if warranted. No permanent air quality impacts are
expected from the operation of the facility.
Restore to Pre-Disaster Locations with Elevated Facilities
This alternative has the potential to have short-term air quality impacts due to construction equipment. The air
quality impacts would be short-term, occurring only while construction work on the restrooms and bath house shower
facility structures is in progress. Dust and airborne dirt generated by construction activities shall be controlled
through general dust control BMPs or a specific dust control plan could be developed if warranted. No permanent air
quality impacts are expected from the operation of the facility.
Affected Environment Issue Areas Coastal Zone Management
Location in Text (Section) 3.1.5
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None - Permit number FR-805 has already been issued by the FDEP.
Restore to Pre-Disaster Locations with Elevated Facilities
Unknown - Permit needed for compliance with the CZMA; none has been issued or reviewed.
Affected Environment Issue Areas Coastal Barriers Resources
Location in Text (Section) 3.1.6
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None
Restore to Pre-Disaster Locations with Elevated Facilities
None
Affected Environment Issue Areas Biological Environment
Location in Text (Section) 3.2
Affected Environment Issue Areas Terrestrial and Aquatic Environment
Location in Text (Section) 3.2.1
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
Since the Replace Reduced Facilities at Alternate Location beach sites are disturbed from the presence and
demolition of the previous restrooms and bath house shower facility structures, no impacts to the terrestrial
or aquatic environment are anticipated at the replacement structure locations. New septic fields would be
constructed in and around one of the two previously disturbed areas resulting from the demolition and removal
of the original septic fields at each beach site location.
Restore to Pre-Disaster Locations with Elevated Facilities
Since the Restore to Pre-Disaster Locations with Elevated Facilities beach sites are disturbed from the presence
and demolition of the previous restrooms and bath house shower facility structures, no impacts to the terrestrial
or aquatic environment are anticipated at the replacement structure locations. New septic fields would be constructed
in and around two of the two previously disturbed areas resulting from the demolition and removal of the original
septic fields at each beach site location.
Affected Environment Issue Areas Wetlands (E.O. 11990)
Location in Text (Section) 3.2.2
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None
Restore to Pre-Disaster Locations with Elevated Facilities
None
Affected Environment Issue Areas Threatened and Endangered Species
Location in Text (Section) 3.2.3
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
Would install a dune-like feature and extend the in progress natural reforming dune system that has been developing
since Hurricane Dennis. The continuous dune system would discourage crawling turtles from entering construction areas.
Not Likely to Adversely Affect (NLAA) regarding nesting sea turtles, non-breeding piping plover, designated critical
habitat for the piping plover and bald eagle. The FDEP would incorporate site specific agreed upon mitigation measures.
Restore to Pre-Disaster Locations with Elevated Facilities
The physical placement of facilities would disrupt or eliminate the in progress natural reforming dune system that
has been developing since Hurricane Dennis. Construction areas open to crawling sea turtles. Not Likely to Adversely
Affect (NLAA) regarding nesting sea turtles, non-breeding piping plover, designated critical habitat for the piping
plover and bald eagle. The FDEP would incorporate site specific agreed upon mitigation measures.
Affected Environment Issue Areas Hazardous and Special Waste Materials
Location in Text (Section) 3.3
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None
Restore to Pre-Disaster Locations with Elevated Facilities
None
Affected Environment Issue Areas Socio-Economics
Location in Text (Section) 3.4
Affected Environment Issue Areas Zoning and Land Use
Location in Text (Section) 3.4.1
Summary of Impacts - Alternatives
No-Action Land use changes may occur due to a change in the number of visitors to the Park.
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None
Restore to Pre-Disaster Locations with Elevated Facilities
None
Affected Environment Issue Areas Aesthetics and Visual Resources
Location in Text (Section) 3.4.2
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
The view of the structure from the beach would be more pleasing on one hand over that which pre-existed, due
to the reduction in the number of structures and relocation further away from the beach water edge into the
paved parking lot area. Overall, the aesthetics of the area would be enhanced over pre-existing conditions.
Restore to Pre-Disaster Locations with Elevated Facilities
The facilities would be less aesthetically acceptable than the Preferred Alternative, being located at an
elevation significantly higher than the adjacent pavilion buildings. The taller buildings would block more
of the views from further landward perspectives. The quality of aesthetics of the area would be less because
of the greater number of structures and the increased height of them.
Affected Environment Issue Areas Noise
Location in Text (Section) 3.4.3
Summary of Impacts - Alternatives
No-Action None.
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
Construction noise is expected to be generated from the site as a result of pile driving, machinery and truck
traffic necessary for building erection and supply of materials. All of the construction noises would be of short
duration and would not have a sustained affect on the surrounding adjacent areas of St. George Island State Park
or the recreational users of West Beach Use Area and East Beach Use Area. No significant adverse noise impacts
would result from this alternative.
Restore to Pre-Disaster Locations with Elevated Facilities
Construction noise is expected to be generated from the site as a result of pile driving, machinery and truck
traffic necessary for building erection and supply of materials. All of the construction noises would be of short
duration and would not have a sustained affect on the surrounding adjacent areas of St. George Island State Park
or the recreational users of West Beach Use Area and East Beach Use Area. No significant adverse noise impacts
would result from this alternative.
Affected Environment Issue Areas Public Service
Location in Text (Section) 3.4.4
Summary of Impacts - Alternatives
No-Action Impacts public services at the Park by not providing for restroom or bathing facilities.
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
Consolidating public health services in one convenient and central location at each public beach area with ADA
compliance features meets the need for public service of the St. George Island State Park patrons.
Restore to Pre-Disaster Locations with Elevated Facilities
Consolidating public health services in one convenient and central location at each public beach area with ADA
compliance features meets the need for public service of the St. George Island State Park patrons.
Affected Environment Issue Areas Traffic and Circulation, Volume, Parking and Access
Location in Text (Section) 3.4.5
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
The Preferred Alternative would not result in long term impacts to traffic or public transportation under
the proposed action.
Restore to Pre-Disaster Locations with Elevated Facilities
Impacts from the Restore to Pre-disaster Conditions would be the same as for the Preferred Alternative.
Affected Environment Issue Areas Environmental Justice (E.O. 12898)
Location in Text (Section) 3.4.6
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred) - None
Restore to Pre-Disaster Locations with Elevated Facilities - None
Affected Environment Issue Areas Public Health and Safety (E.O. 13045)
Location in Text (Section) 3.4.7
Summary of Impacts - Alternatives
No-Action
Impacts public health and safety by failing to provide adequate restrooms and bath house shower facilities
for the public beach areas.
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
This alternative would provide beneficial public health and safety features to the St. George Island State Park visitors by providing needed
bathroom and bathing facilities. There would be no impacts during construction because this portion of the
Park is closed and would be closed during construction.
Restore to Pre-Disaster Locations with Elevated Facilities
This alternative would provide beneficial public health and safety features to the St. George Island State Park
visitors by providing needed bathroom and bathing facilities. There would be no impacts during construction
because this portion of the Park is closed and would be closed during construction.
Affected Environment Issue Areas Cultural Resources
Location in Text (Section) 3.5
Affected Environment Issue Areas Historic Architecture
Location in Text (Section) 3.5.1
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None
Restore to Pre-Disaster Locations with Elevated Facilities
None
Affected Environment Issue Areas Archaeological Resources
Location in Text (Section) 3.5.2
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None
Restore to Pre-Disaster Locations with Elevated Facilities
None
Affected Environment Issue Areas Indian Coordination and Religious Sites
Location in Text (Section) 3.5.3
Summary of Impacts - Alternatives
No-Action None
Replace Reduced Facilities at Alternate Location Alternative (Preferred)
None
Restore to Pre-Disaster Locations with Elevated Facilities
None
Section 4 - Public Participation
Disaster-wide initial public notice was published state wide, with publication in the Pensacola News
Journal on September 21, 2005. No comments were received from that notice. Final public notice will
be published in the Apalachicola Times on 06/29/2006. The public will be advised on the project and
the fact that a Draft EA has been developed. The public will be advised on how to obtain copies of the
EA and invited to comment.
The FDEP CCCL permit requires that St. George Island State Park provide notice of the FDEPs
action to adjacent property owners and interested parties in Franklin County. This was done by FDEP
early in the CCCL permitting process. A letter was sent out January 17, 2006 requesting public
comment. No comments were received.
The Draft EA will be made available to interested parties through publication on FEMAs website
(http://www.fema.gov/plan/ehp/envdocuments/index.shtm) and by distribution within the adjacent
community. The Draft EA will be distributed to interested parties and the following locations.
Franklin County Library
Apalachicola Program Center
148 8th St.
Apalachicola, FL 32329
Franklin County Library
Eastpoint Branch
29 Island Dr.
PO Box 722
Eastpoint, FL 32328
Apalachicola Municipal Library
72 6th Street
Apalachicola, FL 32320
St. George Island State Park
Park Headquarters
1900 E. Gulf Beach Dr.
St. George Island, FL
The public will be invited to comment on the proposed project.
Section 5 - Mitigation Measures and Permits
5.1 Mitigation Measures
In accordance with the special conditions attached to the CCCL permit (see Appendix E, Item 1) all
excavated material shall be maintained seaward of the CCCL. It must remain on-site and be
distributed at locations identified by the engineer seaward of the CCCL.
Appropriate erosion control and BMPs will be utilized to minimize any impacts resulting from
parking lot runoff, erosion and/or sedimentation during construction.
Dust and airborne dirt generated by construction activities shall be controlled through general dust
control BMPs or a specific dust control plan could be developed if warranted. The contractor and St.
George Island State Park personnel will meet to review the nature and extent of potential and known
dust-generating activities and will cooperatively develop specific types of control techniques
appropriate to the project and local situations. Some of the techniques that may warrant consideration
include measures such as minimizing the tracking-out of soil onto nearby publicly-traveled roads,
reducing speed on paved roads or unpaved areas, covering (tarpaulin-covered) haul vehicles, and
applying water to exposed surfaces, particularly those on which construction vehicles travel. Any
burning of materials, vegetation or debris would be undertaken according to relevant local laws and
ordinances, including, but not limited to, the current St. George Island State Park and FDEP
ordinances or regulations of the FDEP. Appropriate public traffic control plans may also serve to limit
localized concentrations of airborne emissions during construction.
\
If project activities include the stockpiling of sands on-site, the project applicant will be required at
the direction of the engineer to cover these sands to help prevent fugitive dust and erosion. Fencing
and straw/hay bales should be installed to reduce loss. Following construction activities, exposed,
compacted sands would be graded and restored.
If an accidental spill occurs during construction, the contractor will be responsible for minimizing the
amount spilled and any clean-up required. Federal and state regulations regarding the reporting and
clean-up of accidental spills will be complied with.
To avoid impacts to threatened or endangered species, FDEP will comply with mitigation measures
suggested by USFWS. These measures include:
1. Monitoring of shorebird presence and activities by Park staff from January 27, 2006 until
project construction is complete.
2. Daily sea turtle nesting surveys, beginning on May 1, 2006 by park staff, to continue until
September 1st.
3. Tarps or plastic material will be placed over the proposed sites for the two sewage disposal
drain fields and will be accomplished by the park staff or the contractor as soon as the state
permit notice-to-proceed is issued.
4. Disturbance Free Zones will be posted away from the construction areas where potential
bird resting and nesting may occur, and will be conducted by park staff prior to
commencement of construction.
5. Post and rope will be placed to delineate the beach access areas from each of the beach
pull-off parking areas. This will be done by the general contractor when these pull-off
parking areas are improved and opened for public use.
6. Additional compatible beach-quality sand will be placed in areas just seaward of the two
beach use area sites to construct a continuous dune system approximately 500 feet in
length and overlapping the proposed construction areas. This will form a dune-like
feature that will discourage crawling of sea turtles into the construction areas. This will be
performed by park staff or by the general contractor prior to May 1, 2006.
7. A Hurricane Ivan Dune Restoration Planting Project will be conducted during the months
of April and May 2006 to enhance the beach dune community, thereby providing a benefit
to both shorebirds and nesting sea turtle habitat. This will be done by landscape contractors
and monitored by Division Staff along with the environmental engineering consultants.
To minimize risks to safety and human health, all construction activities will be performed using
qualified personnel trained in the proper use of the appropriate equipment, including all appropriate
safety precautions; additionally, all activities will be conducted in a safe manner in accordance with
the standards specified in Occupational Safety and Health Act (OSHA) regulations.
To ensure that during the construction process any items of archaeological, historical or architectural
interest are protected the FDEP, Division of Recreation and Parks and its contractors shall monitor
excavation activities. In the event any items of interest are discovered, FDEP should make all
reasonable efforts to protect the items and to avoid further harm to the items until the significance of
the discovery can be determined. The FDEP shall notify FEMA and the FL SHPO immediately.
5.2 Permits
The following permit issues have been evaluated for need and, where required, have been obtained by
the FDEP, Division of Recreation and Parks for the implementation of the Preferred Alternative.
Those that have been obtained are noted below and copies included in Appendix F.
Section 404 Permit
A U.S. Army Corps of Engineers Section 404 permit is not required. There are no wetlands located
within the project vicinity, nor are there Waters of the U.S. involved in the project.
NPDES Permit
A National Pollutant Discharge Elimination System (NPDES) construction permit is not required.
Less than one acre of ground disturbance will occur.
Florida Department of Environmental Protection (FDEP) CCCL Permit
A FDEP CCCL permit is required. The St. George Island State Park has already applied for and
received. This permit (permit number FR-805, dated February 14, 2006. The Permit FR-805 is
provided as Item 1 in Appendix F. Compliance with all permit conditions is required as a condition of
FEMAs funding of this project. Compliance with permit conditions will minimize environmental
impacts. See Item 1, Appendix E for the full permit and conditions.
Building Permit Franklin County, FL
Building Permit No: 18865; dated February 14, 2006 has been issued by Franklin County, Florida
from the Franklin County Inspection Department for the repair of the access road and replacement of
two bathhouse facilities. See Item 3, Appendix F for the full permit and conditions.
Florida Department of Health - Septic Permits
The State of Florida Department of Health Onsite Sewage Treatment and Disposal System
Construction Permit; CENTRAX #: 19-S1-02691, OSTDSNBR: 05-0412-N for a new system has
been secured. Dated January 01, 2006, a copy of this permit can be found as Item 3, Appendix F and
can be referenced for the full permit and conditions.
Florida Department of Environmental Protection (FDEP) Stormwater Discharge Permit
General Permit 19-0232602-002-RG, dated January 6, 2006 has been secured for St. George Island
State Park Hurricane Dennis Repair Stormwater Discharge Franklin County. See Item 4, Appendix F
for the full general permit and conditions.
Section 6 - Consultations , References and Credits
6.1 Consultations
Coordination has occurred with various resource and regulatory agencies. In addition, the following
agencies and organizations were sent the Draft EA for their comments.
Federal Emergency Management Agency
Mr. Richard Myers
Regional Environmental Officer
100 Sunport Lane
Orlando, FL 32809
(407) 858-2705
Federal Emergency Management Agency
Joseph Hudick
Environmental Liaison Officer
100 Sunport Lane
Orlando, FL 32809
(407) 850-7550
US Fish & Wildlife Service
Gail Carmody, Project Leader
Panama City Field Office
1601 Balboa Avenue
Panama City, FL 32405-3721
(850) 769-0552
Florida Fish and Wildlife Conservation
Commission
Farris Bryant Building
c/o Office of the Executive Director
620 South Meridian Street
Tallahassee, FL 32399-1600
(850) 487-3796
Dale Quick
Florida Dept. of Environmental Protection
Senior Management Analyst
Parks Department - Design & Construction
3540 Thomasville Road
Tallahassee, FL 32309
(850) 488-5372
Kevin Jones
Florida Dept. of Environmental Protection
Park Manager
St. George Island State Park
1900 E. Gulf Beach Drive
St. George Island, FL 32328
(850) 932-5956
Jim Brewer
Deputy Public Assistance Officer
State of Florida, SERT
33 Brent Lane
Pensacola, FL 32503
(540) 742.4903
John Bente, Chief Biologist District One
Florida Dept. of Environmental Protection
Florida Park Service
4620 State Park Lane
Panama City, FL 32408
(850) 233-5110
Rich Trnka
Seminole Tribe of Florida
Assistant Historic Preservation Officer
Ah-Tah-Thi-Ki Museum
HC 61 Box 21 - A
Clewiston, FL 33440
(863) 902-1113
Steve Terry
NAGARA & Section 106 Representative
Miccosukee Tribe of Indians of Florida
P.O. Box 440021
Tamiami Station
Miami, FL 33144
(305) 223-8380
Mr. Mitchell Cypress, Chairman
Seminole Tribe of Florida
6300 Stirling Road
Hollywood, FL 33024
Mr. Billy Cypress, Chairman
Miccosukee Tribe of Indians of Florida
Tamiami Station, P.O. Box 440021
Miami, FL 33144
Ms. Nita Molsbee
Customer Service Representative
Water Management Services
St. George Island, FL
(850) 927-2648
Mr. Charles Savering
FDEP, Bureau of Design & Construction
3540 Thomasville Road
Tallahassee, FL 32309
(850) 488-5372
6.2 References
Comprehensive Environmental Response Compensation and Liability Act (CERCLA), [42
USC 6901 et seq.], and the Resource Conservation act, [42 USC 6901 et seq.], as amended
Designated Sole-Source Aquifers in USEPA Region 4; http://www.epa.gov/safewater/
swp/ssa/reg4.html
Earthquake History of Florida; http://neic.usgs.gov/neis/states/florida/florida_history.html
EO 12898; signed 11 February 1994; 59 FR 7629, 16 February 1994; amends EO 12250, 2
November 1980; amended by: E.O 12948, 30 January 1995.
EO 13045; signed 21 April 1997; [62 FR 19885], 23 April 1997; revoked EO 12606, 2
September 1987; amended by: EO 13229, 9 October 2001; EO 13296, 18 April 2003
Ewing, T.E., and Lopez, R.F., 1991, #2032, Principal structural features, Gulf of Mexico
basin, in Salvador, A., ed., The Gulf of Mexico basin: Boulder, Colorado, Geological Society
of America, The Geology of North America, v. J, plate 2, scale 1:2,500,000
FEMA regulations for NEPA compliance [44 CFR Part 10]
Florida Statutes Chapter 373, Part IV, http://www.dca.state.fl.us/fdcp/dcp/Coastal/index.cfm
Gulf-margin normal faults, Alabama and Florida (Class B) No. 2654; http://qfaults.cr.usgs.gov
Mehta, Madan; Johnson, James; Rocafort, Jorge: Architectural Acoustics Principles and
Design; Prentice Hall, 1999
National Environmental Policy Act of 1969 (NEPA)
National Register of Historic Places (NRHP) [36 CFR 60.4]
Robert T. Stafford Disaster Relief and Emergency Assistance Act, as amended by Public Law
106-390, the Disaster Mitigation Act of 2000
Stewart, Stacy R.; Tropical Cyclone Report Hurricane Dennis 2-24 September 2004,
National Oceanic & Atmospheric Administration (NOAA), National Weather Service,
National Hurricane Center 16 December 2004, Revised: 3 June 2005
The Council on Environmental Quality (CEQ) regulations implementing NEPA [40 CFR Parts
1500 through 1508]
The State of Floridas Master Site File (Archeology & Historic Buildings)
USEPA established air quality standards (http://wwwepa.gov/oarqps/greenbk
6.3 Credits for Photographs, Maps and Plans
Environmental Assessment
Cover
All Photos FEMA, Orlando, FL
Appendix A Exhibits
Exhibit 1 Location Maps Yahoo Maps & Google Earth
Exhibit 2 Detail map of St. George Island State Park Florida DEP
Exhibit 3 St. George Island S.P. Natural Communities Map Florida DEP
Exhibit 4 Topographic Map Goose Island Quad USGS
Exhibit 5 Topographic Map Sugar Hill Quad USGS
Exhibit 6 National Seismic Hazard Map USGS
Exhibit 7 St. George Island S.P. Soils Map Florida DEP
Exhibit 8 Water Quality Monitoring Apalachicola Sound Florida DOH
Exhibit 9 FIRM Map for East Beach Use Area FEMA
Exhibit 10 FIRM Map for West Beach Use Area FEMA
Exhibit 11 FIRM Map explanation of Zones FEMA
Exhibit 12 USFWS CBRA Zone Map USF&WS
Exhibit 13 USFWS NWI Wetland Maps USF&WS
Appendix B Photo Collections
Collections 1-2 Photos of St. George Island State Park FEMA, Orlando, FL
& Florida DEP
Appendix C Preferred Plans
Sheets 01 thru 05 Florida DEP, State Park Service
Section 7 - Secondary and Cumulative Impacts
This section addresses the secondary and cumulative impacts of the proposed action. Secondary
effects are those impacts which are . . . caused by an action and are later in time or further removed
in distance but are still reasonably foreseeable (40 CFR 1508.8), such as a new development attracted
to the vicinity of an intersection created by a new highway facility. Cumulative effects are those . . .
impacts which result from the incremental consequences of an action when added to other past and
reasonably foreseeable future actions (40 CFR 1508.7). An example of a cumulative effect would be
the degradation of a streams water quality by several developments which taken individually would
have minimal effects, but as a collective action would cause a measurable negative impact.
As this project consists of the replacement of existing facilities, there are no planned or anticipated
actions, consequences or impacts associated with implementation of the proposed action. All activities
that would be associated with an implementation are already taking place or have taken place in the
immediate locale of West Beach Use Area and East Beach Use Area.
As this project consists of the replacement of existing facilities, and consolidation of public facilities
and activities which are currently lacking in the same area, there are no secondary or cumulative
impacts anticipated. All activities that would be associated with the Preferred Alternative or the
Restore to Pre-Disaster Locations with Elevated Facilities are already taking place in the immediate
locale.
Section 8 - List of Preparers
This EA was prepared by:
Consoer Townsend Envirodyne Engineers Inc. (CTE)
303 East Wacker Drive, Suite 600
Chicago, IL 60601-5276
Developed with contributions by:
Brian Smith, Senior Project Manager QC/QA, Natural Resources CTE
Charles (Chick) Savering, Senior Project Manager - FDEP
Cheryl Nash, Senior Project Scientist EA Manager, QC/QA CTE
Dale Quick, Senior Management Analyst FDEP
John Bente, Senior Biologist District One FDEP
Kenneth Hemstreet, Senior Project Engineer Environmental / Planning CTE
Lisa Sagami, Senior Project Engineer GIS, Graphics, Research CTE
William Barbel, Senior Project Scientist Environmental / Planning CTE
Questions and comments can be directed to:
Richard Myers, Environmental Officer
FEMA Long Term Recovery Office
100 Sunport Drive
Orlando, FL 32809
Richard.Myers@dhs.gov
(407) 858-2705
Details and specifics can be found in Section 6 Mitigation Measures and Permits.
Information on the affected environment extracted and paraphrased from the Dr. Julian G. Bruce St. George Island State Park Unit Management Plan; State of Florida Department of Environmental Protection, Division of Recreation and Parks, February 7, 2003.
Gulf-margin normal faults, Alabama and Florida (Class B) No. 2654; http://qfaults.cr.usgs.gov . Class B is defined as: Geologic evidence demonstrates the existence of Quaternary deformation, but either (1) the fault might not extend deeply enough to be a potential source of significant earthquakes, or (2) the currently available geologic evidence is too strong to confidently assign the feature to Class C but not strong enough to assign it to Class A.
G or g is the force of gravity (an acceleration equal to 9.78 meters/second2). When there is an earthquake, the forces caused by the shaking can be measured as a percent of the force of gravity, or percent g.
USGS website http://earthquake.usgs.gov/hazmaps/products_data/2002/2002April03/US/US5hz2500v4.pdf
Water Body Classifications Nutrient TAC meeting May 27, 2004, Florida Surface Water Classifications.
The Florida Department of Health; Beach Water Sampling Franklin County, St. George Island State Park, January 2006 through March 2006.
Op. cit., Dr. Julian G. Bruce St. George Island State Park Unit Management Plan; State of Florida Department of Environmental Protection, Division
of Recreation and Parks, February 7, 2003
Those substances defined by Comprehensive Environmental Response Compensation and Liability Act (CERCLA), [42 USC 6901 et seq.], and the
Resource Conservation Act, [42 USC 6901 et seq.], as amended.
Op. cit., Dr. Julian G. Bruce St. George Island State Park Unit Management Plan; State of Florida Department of Environmental Protection,
Division of Recreation and Parks, February 7, 2003
E.O 12898; signed 11 February 1994; 59 FR 7629, 16 February 1994; amends E.O 12250, 2 November 1980; amended by: E.O 12948, 30 January
1995.
EO 13045; signed 21 April 1997; 62 FR 19885, 23 April 1997; revoked E.O 12606, 2 September 1987; amended by: EO 13229, 9 October 2001; EO 13296, 18 April 2003.
The FEMA-EST database was established as a disaster recovery response tool. The database is intended to provide decision making support to emergency response personnel. The FEMA-EST tools and reports provide information and analysis and help determine the potential impact on environmental and historic resources. - The FEMA-EST is a customized version of the FL DOT's Efficient Transportation Decision Making (ETDM) Environmental Screening Tool.
Appendix E, Letter from FL. SHPO to FL Department of Environmental Protection (DHR file No. 2006-599)
Appendix E, Letter from FL. SHPO to FL Department of Environmental Protection (DHR file No. 2006-599)
Seminole Tribe of Florida; http://www.seminoletribe.com/
Miccosukee Tribe of Indians of Florida; http://www.miccosukeeresort.com/tribe.html
APPENDICES
Appendix A - EXHIBITS
June 2006
DRAFT ENVIRONMENTAL ASSESSMENT
REPLACEMENT OF THE ST. GEORGE ISLAND STATE PARK RESTROOMS AND BATH HOUSES
FEMA Orlando Long Term Recovery Office
FEMA-1595-DR-FL
List of Exhibits
Each of the exhibits in this appendix is a map. Each is generally described in this listing.
Exhibit # 1 Location Maps
Exhibit # 2 Detail Map of St. George Island State Park
Exhibit # 3 Natural Communities Map
Exhibit # 4 USGS Topo Map Goose Island Quad
Exhibit # 5 USGS Topo Map Sugar Hill Quad
Exhibit # 6 Ground Hazard Shaking of Earthquakes Map
Exhibit # 7 Soils Map
Exhibit # 8 Water Quality Monitoring Apalachicola Sound
Exhibit # 9 Firmette Map Number 12037C 576E East Beach Use Area
Exhibit # 10 Firmette Map Number 12037C 559E West Beach Use Area
Exhibit # 11 Table Explaining Zones on FIRM Maps
Exhibit # 12 Coastal Zone Management Map
Exhibit # 13 US FWS National Wetland Inventory Maps
A P P E N D I X A
List of Appendix A Exhibits
i
APPENDIX A - PHOTOS
June 2006
List of Photo Collections
Collection # 1 Top Left Aerial view of East Beach Use Area before Dennis
Bottom Left View of Beach Use Area from approach roadway
Bottom Right View of Units 3, 2 & 1, after Dennis
Collection # 2 Top Left External view of damaged facility after Dennis
Top Right Debris and damaged walkway foundations after Dennis
Bottom Left Exposed septic tank after Dennis
Bottom Right Damaged restroom facility, after Dennis, and
still buried with displaced beach sand
A P P E N D I X A
List of Appendix A Photo Collections
ii
A P P E N D I X A - Preferred Plans
List of Preferred Plans
Sheet # 1 West Beach Use Area Site Plan
Sheet # 2 East Beach Use Area Site Plan
Sheet # 3 East Beach Use Area Sewage System Site Plan (Typical)
Sheet # 4 Restroom Buildings Sewage Treatment Plan & Profile (Typical)
Sheet # 5 Drainfield Plan, Details, Sections & Specifications
A P P E N D I X A
List of Appendix A - Preferred Plans
iii
A P P E N D I X B
NOT INCLUDED
A P P E N D I X C
Selected elements of Apopendix C are included here.
CTE
303 East Wacker Drive, Suite 600, Chicago, IL 60601-5276
T 312.938.0300 F 312.938.1109 www.cte.aecom.com
February 3, 2006
U.S. Fish & Wildlife Service
Gail Carmody, Project Leader
Panama City Field Office
1601 Balboa Avenue
Panama City, FL 32405-3721
Re: Endangered Species Act Consultation
Florida Department of Environmental Services
State Park Service
Franklin County, St. George Island, Florida
FEMA1595DR-FL, PWs 702 & 704
Dear Ms. Carmody:
On behalf of the Federal Emergency Management Agency (FEMA), CTE is hereby requesting informal consultation pursuant to the Endangered Species Act and/or the Fish and Wildlife Coordination Act. In July of 2005, Hurricane Dennis made landfall along the Florida Gulf Coast causing damage in a wide geographic area. Destroyed during this storm were the only publicly owned and accessible buildings with restrooms and shower facilities at two locations for the users of St. George Island State Park. The State of Florida Department of Environmental Protection (FDEP) is proposing to replace these structures. FEMA is proposing funding the demolition of the four storm damaged public restroom / bath house structures within St. George Island State Park, Franklin County, Florida, and funding the replacement and permanent relocation of these former four restroom / bath house structures in two locations with a single new structure at each location situated along the median area between the two parking areas. An
Environmental Assessment (EA) process is being conducted to document potential influences and impacts from proposed alternative courses of action and determine the ultimate selection of repairs and effects at the two areas.
These two areas for the new single structures are known and identified as the Sugar Hill or West Beach Use Area [Lat: 29.70362, Long: -84.76146], and the East Slough or East Beach Use Area [Lat: 29.7246, Long: -84.7381]. The two areas were identified as part of the natural communities inventory as developed comprising approximately 63 acres in the Dr. Julian G. Bruce St. George Island State Park Unit Management Plan, February 7, 2003.
FEMA is aware of the presence of sea turtles, Loggerhead sea turtle (Caretta caretta) and Green sea turtle (Chelonia mydas), along the approximately 8.5 miles of State Park beach during the nesting season, in the project vicinity and has made a determination that the project is not-likely to adversely affect sea
turtles. The proposed replacement and relocation sites for each structure are removed from the areas of historic and known sea turtle visitation. While no grid is set out on the beach as is done on other more turtle-active beaches, the beach is patrolled and surveyed daily during turtle nesting season by Park
Service employees and trained volunteers of the Florida Wildlife Commission. If and when new turtle nests are identified and located their positions are GPSd, signed for no intrusion, metal screen protected, and information sent to district biologists.
There had been patches of sea oats (Uniola paniculata) near all of the former structures on the beach, public restrooms and bath houses. All of the patches of sea oats were washed away from all of the beach use area
structures. Most of the existing remaining patches of sea oats are still quite a distance from the new structures replacement and permanent relocation construction areas. FEMA has made a determination that the project is not-likely to adversely affect existing and emergent repopulating stands of sea oats.
Contact No. 4 USF&WS
Page 1 of 5
One nest of the piping plover (Charadrius melodus) was sighted within the St. George Island State Park in the last 5 years, but no where near (not within a mile) of any of the structures replacement and permanent relocation new construction areas. FEMA has made a determination that the project is not-likely to adversely affect the piping plover.
No other T&E species are known to inhabit or visit the structure replacement and permanent relocation site areas. We are hereby requesting information on the potential for the presence of any other Federal-listed threatened or endangered species, or any species of concern, or identified critical habitat to be present at or within the influence of the project area for structure replacement and permanent relocation. We are in the process of coordinating with Florida Fish and Wildlife Conservation Commission in order to receive concurrence with not-likely to adversely affect determinations.
Attached are site plans and composite plan with aerial background layouts of the two areas, the West Beach Use Area and the East Beach Use Area, that identify the four storm damaged public restroom/bath house structures, remaining picnic/shelters, the vehicle parking areas, proposed location of the replacement restroom/bath house with the sewer system layout.
In conclusion, FEMA has made a determination that the project is not-likely to adversely affect sea turtles, sea oats, or piping plover. We are hereby requesting information on the potential for the presence of any other Federal-listed threatened or endangered species, or any species of concern, to be present in the project area and a determination of affect.
Please feel free to contact me at either office 312.373.6825 or cell 630.337.7539 telephone or via e-mail at william.barbel@cte.aecom.com if you have any questions.
Sincerely:
William Barbel
CTE
Senior Project Scientist
Environmental Specialist for FEMA
Attachments: St George Island State Park Hurricane Dennis Repairs
9 sheets
Topo Map East Slough 1 sheet
Topo Map Beacon Hill 1 sheet
cc: Jeanne Millin, Regional Environmental Officer, FEMA
A P P E N D I X C
Contact No. 4 USF&WS
Page 2 of 5
APPENDIX C
United States Department of the Interior
Fish and Wildlife service
Field Office
1601 Balboa Avenue
Panama City, FL 32405-3721
Tel: (850) 369-0552
Fax: (850) 763-2173
February 28, 2006
Mr. William Barbel
CTE
303 East Wacker Drive Suite 600
Chicago, Illinois 60601-5726
Re: FWS Log No. 4-P-06-126
Date Started: February 3, 2006
Applicant: FEMA Florida Park service
Project: St. George Island State Park
Reconstruction Post Hurricane Dennis
Location: Gulf of Mexico Beachfront
Ecosystem: NE Gulf
County: Franklin County, Florida
Dear Mr. Barbel:
The Fish and Wildlife Service (Service( has reviewed your request dated February 3, 2006, on behalf of the Federal Emergency Management Agency (FEMA) for informal consultation regarding the storm-damaged facilities at St. George Island State Park, Franklin County, Florida, and potential impacts to federally protected species. FEMA is proposing to fund the demolition of four storm-damaged restroom facilities and the replacement and permanent relocation of the facilities into two structures to a more landward location. FEMA has determined these projects are not likely to adversely affect (NLAA) nesting female adults and hatchlings of the threatened loggerhead sea turtle (Caretta caretta), the endangered green sea turtle (Chelonia mydas mydas), the endangered leatherback sea turtle (Dermocheyls coriacea ), and the endangered Kemps ridley sea turtle (Lepidochelys kempii), and the non-breeding piping plover (Charadrius melodus) and critical habitat designated for the piping plover.
Your letter provided information concerning the presence of the subject species, and additional information was provided by the Florida Park Service (FPS) and the Florida Fish and Wildlife Conservation Commission (FWCC). The Florida Park Service provided conservation measures via e-mail on February 16, 2006. These measures are to minimize the project impacts to the subject species during the construction. The Florida Park Service has also included provisions for protection of nesting shorebirds. Our response is provided in accordance with section 7 of the Endangered Species Act of 1973, as amended (ESA) (87 Stat 84; 16 U.S.C. 153 I et seq.).
Contact No. 4 USF&WS
Page 3 of 5
We have summarized the construction measures to be implemented by the Florida park Service as indicated in the e-mail. The measures are to be conducted before and during the construction period to minimize the impacts to nesting sea turtles, non-breeding piping plover, and nesting shorebirds.
1. Monitoring of shorebird presence and activities were started by Park staff on January 27, 2006, and will continue during the project construction.
2. Daily sea turtle nesting surveys will begin on May 1, 2006, by Park staff and continue until September 1.
3. Tarps or plastic material will be place over the proposed sites for the two Sewage Disposal Drain Fields and will be accomplished by the Park staff or the contractor as soon as the State Permit Notice-To-Proceed is issued.
4. Disturbance Free Zones will be posted away from the construction areas where potential bird resting and nesting may occur, and will be conducted by the Park staff prior to commencement of construction.
5. Post and rope will be placed to delineate the beach access in the areas just seaward of the beach Pull-Off Parking Areas. This will be done by the General Contractor when these Pull-Off Parking Areas are improved and open for public use.
6. Additional compatible beach-quality sand will be placed in the areas just seaward of the two beach use area sites to construct a continuous dune system approximately 500 feet in length and overlapping the proposed construction areas. This would form a dune-like feature that discourages crawling of sea turtles into the construction areas. This will be performed by the Park staff or by the General Contractor prior to May 1, 2006.
7. The Hurricane Ivan Dune Restoration Planting Project will be conducted during the months of April and May 2006 to enhance the beach community, thereby providing a benefit to both shorebirds and nesting sea turtle habitat. This will be done by Landscape Contractors and monitored by Division staff along with the Environmental Engineering Consultants.
Based on the information provided in your letter and the above commitment from the Florida Park Service, the service concurs with FEMAs determination of NKLAA regarding nesting sea turtles, non-breeding piping plover, and designated critical habitat for the piping plover.
Contact No. 4 USF&WS
Page 4 of 5
We appreciate the cooperation between FEMA and the Florida Park Service. If you have any questions regarding this consultation, please contact Ms. Lorna Patrick ay ext. 229.
Sincerely Yours
Janet Mizzi
Deputy Field Supervisor
Cc:
Cheryl Nash, FEMA, Orlando, FL
John Hines and Brad Smith, FWC, Non-game Program, Panama City, FL
Robbin Trindell, FWC, Imperiled Species Mgt., Tallahassee, FL
John Bente, FPS, District One Office, PCB, FL
Jim Ross, FPS, Recreation and Planning, Tallahassee, FL
Contact No. 4 USF&WS
Page 5 of 5
CTE
303 East Wacker Drive, Suite 600, Chicago, IL 60601-5276
T 312.938.0300 F 312.938.1109 www.cte.aecom.com
January 27, 2006
Florida Fish and Wildlife Conservation Commission
Farris Bryant Building
CO Office of the Executive Director
620 South Meridian Street
Tallahassee, FL 32399-1600
Re: Endangered Species Act Consultation
Florida Department of Environmental Services
State Park Service
Franklin County, St. George Island, Florida
FEMA1595DR-FL, PWs 702 & 704
Dear Sir/Madam:
On behalf of the Federal Emergency Management Agency (FEMA), CTE is hereby requesting information related to the potential for the presence of state protected species to be located within the vicinity of one of our project areas. In July of 2005, Hurricane Dennis made landfall along the Florida Gulf Coast causing damage in a wide geographic area. Destroyed during this storm were the only publicly owned and accessible buildings with restrooms and shower facilities at two locations for the users of St. George Island State Park. FEMA is proposing funding the demolition of the four storm damaged public restroom / bath house structures within St. George Island State Park, Franklin County,
Florida, and funding the replacement and permanent relocation of these former four restroom / bath house structures in two locations with a single new structure at each location situated along the median area between the two parking areas.
These two areas for the new single structures are known and identified as the Sugar Hill or West Beach Use Area [Lat: 29.70362, Long: -84.76146], and the East Slough or East Beach Use Area [Lat: 29.7246, Long: -84.7381]. The two areas were identified as part of the natural communities inventory as developed comprising approximately 63 acres in the Dr. Julian G. Bruce St. George Island State Park Unit Management Plan, February 7, 2003.
FEMA is aware of the presence of sea turtles, Loggerhead sea turtle (Caretta caretta) and Green sea turtle (Chelonia mydas), along the approximately 8.5 miles of State Park beach during the nesting season, in the project vicinity and has made a determination that the project is not-likely to affect sea
turtles. The proposed replacement and relocation sites for each structure are removed from the areas of historic and known sea turtle visitation. While no grid is set out on the beach as is done on other more turtle-active beaches, the beach is patrolled and surveyed daily during turtle nesting season by Park
Service employees and trained volunteers of the Florida Wildlife Commission. If and when new turtle nests are identified and located their positions are GPSd, signed for no intrusion, metal screen protected, and information sent to district biologists. We are in the process of coordinating with U.S. Fish and
Wildlife Service in order to receive concurrence with a not-likely to adversely affect sea turtles determination.
There had been patches of sea oats (Uniola paniculata) near all of the former structures on the beach, public restrooms and bath houses. All of the patches of sea oats were washed away from all of the beach use area structures. Most of the existing remaining patches of sea oats are still quite a distance from the
new structures replacement and permanent relocation construction areas. FEMA has made a determination that the project is not-likely to adversely affect existing and emergent repopulating stands of sea oats.
Contact No. 5 Florida F&WCC
Page 1 of 4
One nest of the piping plover (Charadrius melodus) was sighted within the St. George Island State Park in the last 5 years, but no where near (not within a mile) of any of the structure replacement and permanent
relocation new construction areas. FEMA has made a determination that the project is not-likely to adversely affect the piping plover.
No other T&E species are known to inhabit or visit the structure replacement and permanent relocation site areas. We are hereby requesting information on the potential for the presence of any other state-listed
threatened or endangered species, or any species of concern, or identified critical habitat to be present at or within the influence of the project area for structure replacement and permanent relocation.
Attached are site plans and composite plan with aerial background layouts of the two areas, the West Beach Use Area and the East Beach Use Area, that identify the four storm damaged public restroom / bath house structures, remaining picnic/shelters, the vehicle parking areas, proposed location of the
replacement restroom/bath house with the sewer system layout.
In conclusion, FEMA has made a determination that the project is not-likely to adversely affect sea turtles, sea oats, or piping plovers. We are hereby requesting information on the potential for the
presence of any other state-listed threatened or endangered species, or any species of concern, to be present in the project area and a determination of affect.
Please feel free to contact me at either office 312.373.6825 or cell 630.337.7539 telephone or via e-mail at william.barbel@cte.aecom.com if you have any questions.
Sincerely:
William Barbel
CTE
Senior Project Scientist
Environmental Specialist for FEMA
Attachments: St George Island State Park Hurricane Dennis Repairs 9 sheets
Topo Map East Slough 1 sheet
Topo Map Beacon Hill 1 sheet
c: Jeanne Millin, Regional Environmental Officer, FEMA
A P P E N D I X C
Contact No. 5 Florida F&WCC
Page 2 of 4
Florida Fish and Wildlife Conservation Commission
Rodney Barreto, Miami Sandra T. Kaupe, Palm Beach
H. A. Herky Huffman, Enterprise David K. Meehan, St. Petersburg
Kathy Barco, Jacksonville Richard A. Corbett, Tampa
Brian S. Yablonski, Tallahassee
Kenneth D. Haddad, Executive Director
Victor J. Heller, Assistant Executive Director
Mary Ann Poole, Director
Office of Policy and Stakeholders Coordination
(850) 488-6661 TDD (850) 488-9542
FAX (850) 923-5679
February 20, 2006
Mr. William Barbel
CTE
303 East Wacker Drive Suite 600
Chicago, IL 60601-5276
RE: FEMA-1595-DR-FL, PWS 702 & 704
St. George Island State Park, Franklin County
Dear Mr. Barbel:
Staff in the Florida Fish and Wildlife Conservation Commission (FWCC) has reviewed your request for information on state-protected species within St. George Island State Park. As noted in your letter, the sandy beach fronting the Gulf of Mexico and along the inlet are sea turtle nesting beaches used by threatened loggerhead (Caretta caretta), and green sea turtles (Chelonia mydas). Marine turtle nesting season in the Florida Panhandle is May 1 through October 31. No construction activities, material storage, or operation of heavy equipment should occur on the sandy beach during that time. There should also be no temporary lighting of the construction site that could be seen from the beach.
Other state-listed species known to occur in or near the proposed construction sites in St. George Island State Park include snowy plovers (nesting [Feb. 15 Aug. 31] and wintering), piping plovers (wintering only); the nest found within the last five years is almost certainly a snowy plover nest), least terns (nesting only [Apr. 1 Aug. 31]), bald eagles (nesting only [Oct. 1 May 1]), and American oystercatchers (nesting [Feb. 15 Aug. 31]) and wintering). Direct disturbance from construction workers, vehicles, and equipment, disturbance leading to an increase in predator: and loss of nesting habitat (and the dune vegetation therein) from the construction itself would be primary effects of this project. Please note that this area is within federally designated piping plover critical habitat (FL-9 unit), and the entire area is within a designated Coastal Barrier Resource (COBRA) unit.
Contact No. 5 Florida F&WCC
Page 3 of 4
Thank you for the opportunity to comment on this project. If you or your staff would like to coordinate further on this, please contact me at 850-499-6661 or e-mail me at maryann.poole@MyFWC.com and I will be glad to help make the necessary arrangements. If your staff has any specific questions regarding this information, please contact Dr. Robbin Trindell at 850-922-4330 or by e-mail at robbin.trindell@MyFWC.com .
Sincerely
Mary Ann Poole, Director
Office of Policy and Stakeholder Coord.
Cc:
Lorna Patrick, FWS-PC
John Himes, FWC
Robbin Trindell, FWC
Mark Latch. DEP
John Bente, DEP
Contact No. 5 Florida F&WCC
4 of 4
From: Ross, Jim [Jim.Ross@dep.state.fl.us]
Sent: Thursday, February 16, 2006 7:58 AM
To: Lorna_Patrick@fws.gov; Patricia_Kelly@fws.gov
Cc: Trindell, Robbin; Himes, John; Bente, John; Bowman, Ed; Jones, Daniel R.; Quick, Dale; Savering, Chick; Jones, Kevin; Hemstreet
Ken; Barbel, William
Subject: Dr. Julian G. Bruce St. George Island State Park - Hurricane Dennis
Repairs Project
The main goal of the repair project at St. George Island State Park is to re-establish the two main public beach use areas of the park while protecting the natural resource environment. These two use areas along with the access road and associated park utilities were heavily impacted by the storm-surge associated with Hurricane Dennis. During the process of assessing the damage and producing the plans required for these repairs, it was decided to use this opportunity to reduce the man-made impacts at these two use areas.
We decided to remove the two damaged beach bathhouses at each use area that were
constructed 25 years ago and replace them with a single restroom. These new restrooms will be centrally located within the confines of the parking area median and sited approximately 80 landward of the old bathhouses. We also decided to replace the previous five elevated walkways with only three in each use area. All these changes will enable us to restore the primary dune system in the location where it needs re-build with the new beach profile.
In order to reduce the potential impact of nesting birds and sea turtles, we, in concert with District I biological staff, concur with the implementation of the following conservation measures before and during the construction period:
*Monitoring of shorebird presence and activities. On-gong by Park Staff since January 27, 2006
*Daily monitoring for Sea Turtle nesting sites. Beginning May 1st by Park Staff.
*Placement of tarps or plastic material over the proposed sites for the two Sewage Disposal Drain Fields. This may be done by Park Staff or by the General Contractor if he is issued a construction Notice-To-Proceed.
*Posting of Disturbance-Free Zones away from the construction areas where potential bird resting and nesting may occur. This can be done by the Park Staff prior to commencement of construction.
*Placement of Post and Ropes to delineate the beach access areas from each of the beach Pull-Off Parking Areas. This can be done by the General Contractor when these Pull-Off Parking Areas are improved and opened for public use.
*Placement of additional compatible beach-quality sand in the areas just seaward of the two beach use areas sites in order to construct a continuous dune system approximately 500 in length (overlapping the proposed construction areas). This would form a dune-like barrier to discourage crawling Sea Turtles from entering the construction areas.
Contact No. 6 Florida DEP to USF&WS
Page 1 of 2
This can be performed by the Park Staff or by the General Contractor prior to the May 1st season.
*The Hurricane Ivan Dune Restoration Planting Project will be conducted during the months of April and May to enhance the beach dune community and thereby providing a benefit to both Shorebirds and Nesting Sea Turtles. This will be done by Landscape Contractors and monitored by Division Staff along with Environmental Engineering Consultants.
Although it is our goal to restore the public access and use of this popular beach use park, we also are guided by the need to protect and enhance the natural resources of the area. We believe that the above outlined measures will enable us to proceed with the proposed park improvements project with no, or very limited detrimental impact on the resource and associated protected species. We continue to work with FEMA on the environmental assessment of the potential impact of the repairs to the park facilities that were in place
prior to Hurricane Dennis. We shall also continue to coordinate these protective measures with the USFWS and FWCC through John Bente and the District park biological staff as deemed necessary. Again, our goal is to make these repairs in a timely manner so that these facilities are once again available for public use and enjoyment while providing as much protection as possible to the resource with its associated flora and fauna.
Please advise if this communication should be provided in a formal letter and, if so, what determination should we request.
Jim Ross
Florida Division of Recreation & Parks
Department of Environmental Protection
Phone: (850) 488-5372
SC: 278-5372
Visit The Real Floridasm at http://www.floridastateparks.org
A P P E N D I X C
Contact No. 6 Florida DEP to USF&WS
Page 2 of 2
Letter from Florida Department of State
FLORIDA DEPARTMENT OF STATE
Sue M. Cobb
Secretary of state
DIVISION OF HISTORICAL RESOURCES
February 2, 2006
Mr. Fred Hand
Bureau of design and recreation services
Division of Recreation and Parks
Department of Environmental Protection
3540 Thomasville Road
Tallahassee, Florida 32309
Re: St. George Island State Park
Hurricane Dennis Repairs: Park Drive & Two Restroom Replacements
Franklin County
DHR Project File No. 2006-599
Dear Mr. Hand:
In accordance with this agencys responsibilities under Section267.061, Florida Statutes,
we reviewed the referenced project.
The proposed project activities will be undertaken as a result of hurricane Dennis
damage, and we note that the park drive was relocated sat least one other time because of
storm damage. A review of the Florida Master Site File indicates that there are three
recorded archaeological sites along Rattlesnake Cove, but none within the project area.
Because of the project locations and/or nature, it is unlikely that historic properties will
be affected. Therefore, it is the opinion of this office that the proposed project will have
no effect on historic properties listed, or eligible for listing in the National Register of
Historic Places, or otherwise of historical or archaeological value.
If you have any questions concerning our comments, please do not hesitate to contact
Susan Harp at (850) 245-6333. Thank you for your interest in protecting Floridas
historic resources.
Sincerely
Frederick P. Gaske, Director
Xc: Mr. Steve Martin, DEP
Mr. Kevin Jones, Park Manager
Contact No. 7 Florida DEPARTMENT OF STATE
Page 1 of 1
| en |
converted_docs | 886016 | {width="6.302083333333333in" height="1.125in"}
# Legislative Bulletin........................................................April 15, 2008
**Contents:**
**H.R. 5719**---Taxpayer Assistance and Simplification Act
H.R. 5719---Taxpayer Assistance and Simplification Act (*Rangel, D-NY*)
**[Order of Business]{.underline}**: The bill is scheduled to be
considered on Tuesday, April 15^th^, subject to a closed rule (H.Res.
1102), which neither makes nor allows any amendments.
**[Summary]{.underline}**: In addition to provisions that would impose
additional restrictions on Health Savings Accounts (HSAs) and prohibit
the Internal Revenue Service (IRS) from using the private sector to help
collect tax debts, H.R. 5719 contains an assortment of miscellaneous
tax-code provisions regarding tax compliance, as summarized below. Some
of these provisions have already passed the House in 2007 as part of
H.R. 1677 and H.R. 3056.
To see the RSC Legislative Bulletin on H.R. 1677, go here:
<http://www.house.gov/hensarling/rsc/doc/LB_041707_suspensions.doc>.
To see the RSC Legislative Bulletin on H.R. 3056, go here:
<http://www.house.gov/hensarling/rsc/doc/lb_101007_taxcollectors.doc>.
Highlights of H.R. 5719 are as follows:
- [Tax Preparer Liability]{.underline}. This provision would modify
the penalty on the understatement of a taxpayer's liability by a
paid tax return preparer (increased recently by Public Law 110-28)
so that return preparers could more easily avoid penalty through
proper explanation and justifications of their actions on behalf of
the taxpayer. ***Saves taxpayers \$22 million over ten years.***
- [Removal of Cell Phone Substantiation]{.underline}. This provision
would eliminate the special requirements for individuals to keep
detailed records of calls made on employer-provided cell phones to
substantiate the business use (and thus the tax deductibility) of
such devices. ***Saves taxpayers \$237 million over ten years.***
```{=html}
<!-- -->
```
- [Withholding Delay]{.underline}. Delays by one year (from December
31, 2010 to December 31, 2011) the date after which a three-percent
withholding requirement would become effective on certain government
payments to persons providing qualifying property or services to
such government (any level of government, including federal, state,
and local). Payments subject to the three-percent withholding
include any payment made in connection with a government voucher or
certificate program that functions as a payment for property or
services (such as many agriculture programs). ***Saves taxpayers
\$316 million over ten years.***
- [Elderly and Disabled Programs Tax Liability]{.underline}. This
provision would make the fiscal administrators of state and local
government programs liable for paying the employment taxes on
amounts paid by government programs to in-home care workers
providing care to elderly and disabled persons. ***Negligible
revenue effect.***
- [Low-Income Taxpayer Clinics]{.underline}. This provision would
allow IRS employees to refer taxpayers needing assistance with tax
cases to qualified low-income taxpayer clinics and would increased
the ceiling for authorized marching-fund grants to such clinics from
\$6 million a year to \$10 million a year. ***Negligible revenue
effect and a \$40 million authorization increase over ten years.***
- [Volunteer Income Tax Assistance Program]{.underline}. Creates a new
\$10-million-a-year matching-funds program for the development,
expansion, or continuation of volunteer income tax assistance
programs. ***No revenue effect and a \$100 million authorization
over ten years (though CBO only scores this new program at \$3
million in the first year and \$2 million a year thereafter).***
```{=html}
<!-- -->
```
- [Earned Income Tax Credit Notification]{.underline}. This provision
would direct the IRS to expand its annual notice requirements
relating to potential eligibility for the Earned Income Tax Credit
(EITC)---and its possible refundability---to all potentially
eligible taxpayers ("to the extent possible"), regardless of whether
they have filed a tax return for the applicable tax year, and as
long as the time limitation for claiming the credit has not expired
(three years from the time the relevant tax return was filed, two
years from the time the related tax was paid, or, if no tax return
was filed by the taxpayer, then two years after the tax was paid).
Such notices would have to be in writing and mailed to the
taxpayer's last known address. ***No revenue effect*.**
> In current law, low-income taxpayers can be eligible for the
> refundable EITC, based primarily on the number of children in the
> taxpayer's family, adjusted gross income, and earned income. The EITC
> generally equals a specified percentage of earned income up to a
> maximum dollar amount (over a certain income range and diminishing to
> zero over a specified phase-out range). For more on the EITC, go to
> this webpage:
> <http://www.irs.gov/individuals/article/0,,id=96456,00.html>.
- [IRS Debt Indicators for Predatory Loans]{.underline}. This
provision would prohibit the Secretary of the Treasury from
providing a debt indicator to any person with respect to any refund
anticipation loan when the Secretary determines that the business
practices of such person involve refund anticipation loans and
related charges and fees that are "predatory" (not defined in the
bill). In other words, this provision would seek to make it harder
for so-called predatory lenders to reduce their risk in making
refund anticipation loans. A "debt indicator" is defined in the bill
as a notification provided to a tax practitioner or financial
institution that a taxpayer's refund will be offset to repay debts
for delinquent federal or state taxes, student loans, child support,
or other federal agency debt. A "refund anticipation loan" is
defined in the bill as a "loan of money or any other thing of value
to a taxpayer secured by the taxpayer's anticipated receipt of a
federal tax refund." ***No revenue effect.***
[]{.mark}
- [Study on Electronic Delivery of Tax Refunds]{.underline}. This
provision would direct the Secretary of the Treasury, in
consultation with the National Taxpayer Advocate, to study and
report to Congress on the feasibility of delivering tax refunds on
debit cards, prepaid cards, and other electronic means. ***No
revenue effect.***
```{=html}
<!-- -->
```
- [Return of Wrongly Seized Property]{.underline}. This provision
would extend, from nine months to two years, the period for:
> \--The IRS to return money and the proceeds from the sale of property
> that has been wrongfully levied; and
>
> \--The wronged taxpayer to bring a civil action for wrongful levy.
***Negligible revenue effect.***
- [Wrongful Levy on Individual Retirement Accounts]{.underline}. This
provision would allow an individual to recontribute to an Individual
Retirement Account (IRA) the amounts withdrawn pursuant to a
wrongful or premature IRS levy and returned by the IRS (plus
interest) within 60 days of receipt by the individual, regardless of
the current-law limits on IRA contributions and rollovers. Interest
paid under this provision would be excludable from gross income for
tax purposes, once deposited in an IRA, and the returned amounts
would not yield any new income tax (if deposited in an IRA).
***Negligible revenue effect.***
```{=html}
<!-- -->
```
- [Notification of Suspected Identity Theft]{.underline}. This
provision would direct the Secretary of the Treasury, if (in the
course of an investigation relating to tax fraud, false statements,
fraudulent tax returns, or other fraudulent tax-related documents)
he believes that there may have been unauthorized use of the
identity of a taxpayer or his dependents, to notify the taxpayer
("as soon as practicable and without jeopardizing such
investigation"). The Secretary would also have to notify the
taxpayer of any criminal charge that was the result of the
investigation. In current law, information gathered by the IRS in
connection with a tax-fraud investigation is subject to
confidentiality restrictions. ***No revenue effect.***
```{=html}
<!-- -->
```
- [Prohibition on Private-Sector Debt Collectors for the
IRS]{.underline}. This provision would strike the authority for the
IRS to enter into, extend, or renew contracts for tax collection
with private entities, retroactive to contracts signed on or after
March 1, 2008. Contracts in effect before this date would remain in
force, as long as they have not been altered since March 1, 2008.
Under current law, the IRS may use private debt collection companies
to contact taxpayers who owe any tax and to arrange payment of such
tax liabilities. The IRS is currently authorized to pay these
collection companies (up to 25% of the amount collected) and to
reserve another 25% of the collections for collection enforcement
activities at the IRS.
> This provision would also affirmatively deem as void any such tax
> collection contract entered into on or after March 1, 2008. ***Reduces
> revenues by \$552 million over ten years and reduces mandatory
> spending by \$261 million over those same ten years.***
>
> [NOTE]{.underline}: According to the Republican staff of the Ways &
> Means Committee, the IRS has contracted with private debt collectors
> only to collect smaller tax-debts when the amount owed is not in
> question (i.e. when the taxpayer has filed a correct tax return). The
> IRS does not use private tax collectors to collect larger tax-debts or
> when the amount of tax liability is in question.
- [IRS Unclaimed Refunds]{.underline}. This provision would allow the
IRS to use any means of "mass communication" to notify taxpayers of
undelivered refunds. In current law, when the IRS is unable to find
a taxpayer due a tax refund, the IRS can use "the press or other
media" to notify the taxpayer of the refund. The IRS has interpreted
this definition to exclude the Internet. ***No revenue effect.***
- [Misuse of Treasury Names and Symbols]{.underline}. This provision
would clarify that any electronic mass communication (including
"phishing," misleading domain names, etc.) that could reasonably be
interpreted as falsely conveying a connection to, or approval by,
the Treasury Department (or any of its parts), are subject to the
current-law civil penalty of \$25,000 per violation and criminal
penalty of \$50,000 per violation, presently applicable to
broadcasts and telecasts. The provision would also clarify that the
use of the words, abbreviations, titles, letters, symbols, or
emblems associated with the Department of the Treasury (or any of
its parts) [in an Internet domain name]{.underline} is covered by
the current-law prohibition against such misuse in general.
(Disclaimers that the private entity is not affiliated with the IRS
do **[not]{.underline}** relieve such entities from liability under
this provision.) ***No revenue effect*.**
- [HSA Substantiation]{.underline}. This provision would require the
"substantiation" of all Health Savings Accounts (HSA) transactions
from an independent third party, to ensure that money withdrawn from
an HSA pays for qualified medical expenses. Specifically, the
section would make the income tax deduction associated with HSA
contributions contingent on substantiation of all withdrawals,
beginning in 2011. This oversight of every single account
transaction would make HSAs similar to Flexible Spending
Arrangements (FSAs), an earlier consumer-driven health care model.
The provision also would require HSA trustees to annually report
expenses not substantiated. **[See the "Conservative Concerns"
section below]{.underline}.** ***Costs taxpayers \$308 million over
eight years.***
- [Tax Treatment of Employees of Foreign Subsidiaries of U.S.
Companies]{.underline}. This provision would impose employment taxes
on employers for wages paid for services performed by employees of
foreign subsidiaries of U.S. parent companies under U.S. government
contracts. In other words, this provision would treat certain
non-American employers as if they were American employers. ***Costs
taxpayers \$860 million over eleven years and increases mandatory
spending by \$14 million over those same eleven years.***
```{=html}
<!-- -->
```
- [Corporate Estimated Tax Timing Gimmick]{.underline}. This provision
would increase the estimated tax payments that certain corporations
must remit to the federal government. Under current law,
corporations with assets of at least \$1 billion must make equally
divided estimated tax payments for each quarter. This legislation
would increase the payment due for the third quarter of 2013 by 0.25
percentage points. The payment due for the fourth quarter of 2013
would be reduced accordingly so that the corporations pay no net
increase in estimated payments in 2013. This provision is merely a
revenue timing shift, a gimmick used to comply with the House's
PAYGO rules, yet could have real-world implications, as it forces
certain companies to pay more of their tax payments earlier. ***No
[net]{.underline} revenue effect beyond fiscal year 2014, but would
force corporations to pay \$147 million in additional tax payments
in FY2013 instead of FY2014 .***
**[RSC Bonus Fact]{.underline}:** Treasury Benefits Tax Counsel Tom
Reeder testified before the House Ways & Means Committee last week that
8.4% of HSA account holders self-declare at least some portion of their
distributions as *taxable* income.
**[Committee Action]{.underline}**: On April 8, 2008, H.R. 5719 was
introduced and referred to the Ways & Means Committee, which, on the
subsequent day, marked up the bill and ordered it reported to the full
House by a party-line vote of 23-17.
**[Possible Conservative Concerns]{.underline}**: Some conservatives
have expressed concerns about the HSA substantiation provision. In
addition to increased inconvenience for account holders, introducing a
new step of independent "substantiation" may well increase costs for
banks and account administrators, who are likely to either pass these
costs onto employers and/or consumers, or to exit the HSA space
altogether.
The Joint Committee on Taxation would not reveal whether its estimate of
increased revenues from this provision comes from reducing fraud or from
a reduced number of HSAs in the marketplace---or both. Additionally,
some conservatives have noted the lack of consistent data quantifying
the problem of HSAs being used for non-qualified expenditures.
Some conservatives may also be concerned at the application of FSA
procedures to HSAs. The Internal Revenue Code makes clear that FSA
accounts are held by ***employers***, while HSA funds remain exclusively
the property of the ***employee***. This distinction explains why unused
FSA funds in an employee's account at the time of departure revert back
to the employer, while HSA funds always remain with the employee, and
remain portable from job to job and into retirement. Some conservatives
may be concerned about the potential implications of transferring a
"substantiation" system designed for employer-owned FSAs to
individually-owned HSAs---both in terms of the legal liabilities placed
on employers and administrators to verify transactions, and the
restrictions placed on individuals to control their HSA account dollars.
Some conservatives may also be concerned that H.R. 5719 would eliminate
a successful program that the IRS has used to collect smaller tax-debts,
debts that the IRS has said it would not otherwise be cost-effective to
try to collect. Additionally, some conservatives may be concerned at the
motivation behind this provision---limiting the ability for the federal
government to use private contractors and increasing the use of
government-union-only services.
**The scores for the HSA substantiation provision and the IRS debt
collection provision almost perfectly offset each other, thus one could
argue that this bill** **would** **require individual
HSA-account-holders to use third parties to get their promised tax
benefits** **in order to pay for** **preventing the IRS from using third
parties for debt collection.**
Some conservatives may be concerned at the bill's expansion of the IRS'
outreach effort on the Earned Income Tax Credit. In the past,
conservatives have expressed concerns about the notion of the IRS as tax
advisor and about the EITC itself (because of its refundability and its
ability to turn taxpayers into welfare benefit recipients).
Additionally, some conservatives may be concerned about the
private-sector mandate on Internet domain names.
Some conservatives may also be concerned at the provision imposing
employment taxes on employers for wages paid for services performed by
employees of foreign subsidiaries of U.S. parent companies under U.S.
government contracts---thus treating certain non-American employers as
if they were American employers.
[]{.mark}
Lastly, some conservatives may be concerned at the ongoing use of a
corporate tax-timing shift, which some Members would regard as a budget
gimmick to meet PAYGO rules.
**[Administration Position]{.underline}**: The Administration has issued
a Statement of Administration Policy (SAP), indicating that the
President's senior advisers would recommend that he veto the bill, based
on the HSA and IRS private debt-collection provisions. To read the SAP,
visit this webpage:
<http://www.whitehouse.gov/omb/legislative/sap/110-2/saphr5719-r.pdf>.
**[Cost to Taxpayers]{.underline}**: The Joint Committee on Taxation and
CBO estimate that H.R. 5719 would increase revenues by \$75 million over
six years and by \$41 million over eleven years. The bill would decrease
mandatory spending by \$119 million and \$247 million, respectively,
over the same timeframes. Lastly, the bill would increase authorizations
by \$61 million over ten years.
**[Does the Bill Expand the Size and Scope of the Federal
Government?]{.underline}**: Yes, among other things, the bill would
treat certain non-American employers as American employers for
employment tax purposes and would require that the government directly
do more of its own tax-debt collection, rather than contract it out to
the private-sector.
**[Does the Bill Contain Any New State-Government, Local-Government, or
Private-Sector Mandates?]{.underline}**: Yes, there is one
private-sector mandate: the prohibition from anyone using words,
abbreviations, titles, or letters associated with the Treasury
Department (or its components) as a part of an Internet domain address
in a manner which could be "reasonably" interpreted as conveying the
false impression that the domain address is connected to, or authorized
by, the Department (regardless of whether it features a disclaimer that
the private entity is not affiliated with the IRS).
CBO notes that "the costs of the mandate would be the expenditures
incurred to bring the Internet domain address into compliance added to
any loss of net income associated with those changes."
**[Does the Bill Comply with House Rules Regarding Earmarks/Limited Tax
Benefits/Limited Tariff Benefits?]{.underline}**: House Report 110-584,
which presumably contains an earmark/limited tax benefit/limited tariff
benefit statement, was not available at press time.
**[Constitutional Authority]{.underline}**: House Report 110-584, which
presumably contains a constitutional authority statement, was not
available at press time.
**[Outside Organizations]{.underline}**: A partial list of organizations
[opposing]{.underline} the HSA substantiation provision includes:
- America's Health Insurance Plans;
- Business Roundtable;
- Credit Union National Association;
- Financial Services Roundtable;
- HSA Council (part of the American Bankers Association);
- International Franchise Association;
- National Association of Health Underwriters;
- National Association of Manufacturers;
- National Federation of Independent Business;
- National Restaurant Association;
- National Retail Federation;
- National Taxpayers Union; and
- U.S. Chamber of Commerce.
**[RSC Staff Contacts]{.underline}**:
- (All provisions except HSA substantiation) Paul S. Teller,
<paul.teller@mail.house.gov>, (202) 226-9718
- (HSA substantiation) Chris Jacobs,
<christopher.jacobs@mail.house.gov>, (202) 226-8585
| en |
all-txt-docs | 506557 | September 79, 1929.
Dear Dr. md Mrs. `Forkmr,
Your cnrd with the lovely Freiburg Cathedral, :Aich I love so
-a St-a& on my desk a oonetxnt reminder of where you Care and you letter wae moot,
wslcomQ. It quite took me back to the days long before the war when 1 waS there too.
The &yin& of m-terials for tkre laboratory was in my day too; I remmember buying all
my own glassw~6, alooBOf znd everything, both there <and in Leipzig. Y.Ioesn*t it
make you realiae haz free everything is hers.
?e xre in our ne@ quqrters and they are not as bad as my fancy painted t&g,
but they nre not as #ce as o3.A old rooms. ?%e boys th?t thnt its easier to do the sv(l
work in them, but they zre so muOh rxore dirty that they have to spenti a lot of time
cleaning up. "3. $'linn worked vep: h-.rd On th%m aild R'PdS them #Wt a$ nice as pOS&
ble so that the only foula zre the lnck of sunshine r?nd the noi& and dirt of tha
new bufldings. The new InstSutcs Xo~th Buildiq is all up in skzeleton foml rnd
all the rivlting :aas done durin;= the summ8r. The Cornell Buildings are still awaiting
six months of blasting whiti now drives m&St nrg ?xucocyte off 42x3 field.
38 went right to wWk on tile -gapers czl.1 semn of them. The one on the
giant cells in the blood s8ems to me all ready ns it is and very nice indeed, I think
that it will $o in f9ith your n,ams alone; Br. llhan e&rees <and that S88ms to be 2 good
WCJ t0 settP% that mRtt8r; the other giant cell pper seems to !ne a little thin&
I think th.3.t ';lr. Docan would l&e to do some r8writing on that one. rye wil2'both
aoz% over it and send you a cmbon before ne Submit it for putilication. 2heth8r we
shall get one or both colored plnter I do not yet Imow. The work smm to ne very fins
to settle the problem ar,d to ex+ain all the transitions of section8 50 that I
greatly hop8 for the two colored plntes. I have hnd one tn.1:~ with Ihr. Flexner about
it ur@g their yablicnt ion. Ii8 has 2md lo&5 of complications over papers this
mS5sner and his problem is to Satisfy ovaryone or as n?,:rly as T>ossibbe so \7e can only
wait and ~8.
Of the other five papers, four are practically ready; the tirst the phosphatkl
is all ready; the ssoond the fatty acids all but the final copy. The third 191s
controls needs a lot of re-qritfn& It to0 WQS much tO0 thin ,ana not logically
written: In or&r ti even the length I had to tranefer all the disou$eidn to this
third paper; the rewriting is to put some logic intt, the story of the controls.
Ve had planned a$ you retmm8mber to try 12 doses of dead tubercle bacilli in the
amount quaivalent to the phos&&id. Tie ehall not do it for the first dose
kills the rabbits. Too much protein involve& 'Yaentt that interesting ? The
WB tri8d half the Bose and that killed too but it wasn't a clean experiment for there
was a nick in the wall of the intestine but on the under side. This w88k oqht
to 8ee the finish of all' five of the papers. The first three are to go in one number
of the journal if they are accepted and Dr. Rous thinks that ti?sre ~7111 be no trouble.
Then next we8k w8 shall start on ths giant cell'pa:>ers ?nd &ive them th8 final
rkvisibnn, as I said above, Gractiallg limiting any additions to the general on8.
' Dr. Deans work this tnmner was Q gr nt ins;?iration to hip, and a great gain to
the depmt'-:mnt. Ha cazte '&CM& quite content win. Petroff has tisociatad all thrree
stasins into R virulent 2nd avirulent stran. The avirulent form hzxl morelipoid
axI is more acid f,ast .znd mare like the ty$cal fo~ns mor;l!hologicnlly. The virulent
one in some prelimin?,r;y tests he ~4. Toan mF.de more like a septicemia. Ge 2re going
after it hot foot. It modifi8s OUr PlZnS PrOfOtUKlly. f t seem to m8 that it BIOW
is ;&ssible to repeat our sqaration of toxic protein ndnd tissue-forming li;>oid
action witch these two living forms. Cur bovine B 1 strain naS perhaps 90 $
&he avirulent form abd 10;; virulent type. The pzrt of Petroffs work given last
spring at the meetings has been publisherd in the Amer. Rev of TB. ??hiS nBw8r
idea not. Es is 8war to co-operate with us .and we are now innoculnti~ only
from pure colonies.` ti. B&n is also to work with theSe disociatied straine.
Dr. Chit8 iS to come to See us 800n* Just How he mill react I cm not quite surb,
but I am convincsd that Retroffto work makes the n&t hopeful step.
?3r. l?ieeman, the new man from Indienopolis is fine. Yhils he was waiting
around for us to &ad pnpem5 hs de.cided to play with the crg&als nnd ha8 provea
vex-y nicely that they care on the slide before me put the drop of blood on. They
&re either from an imgurity in the brtrhromstte or from the Bew York tap water.
Nei'Llslber@r says that the Eew York water has lots of calcium. ftn't th,at rather of
a jok8 on us, Par his own problem he is to study inJections of embryonic
tissue juice into t,he peritoneum followed'by embryohic liver *and other things that
ueem hopeful to study the primitive cells and &her rextions, I ,m are that he wili
work well. T: hm?i planned for him to work on the pigeone, but 3r. Doan will not be
ready to start them for too long.
Dr. Miller has not yet c-me; he is to be here about the f irot of B&?m8ber.
DrJ Swift'0 dep,artment is to be int8r@sted in the supravital through
Dr. l&tJwen who worked with Wsh#@o warm bojt all summr. Dr. River8 has a new man
coming who is-to fol:ottr the blood in measrls with the sugravital so the work ~OWW
cxr first plans are the follow the biological renctione in rabbits with the
two new &rains from the bovine and titih in chickens with the two strains fram the
avian a6 our first adventure. The reps&t the immunity work with Smaller &iSeS of
organiranrr.
There iis to be a big meeting in Hew i&ven soon on the BCC). ?Jr Park from the
?Tew York &ard of Wealth is to lead the discussion for the Calmetts ride ,a.nd
Fetroff for the QbBer. I think that the whole depzrtment will Co up to hear the
discusrsion; it'ou&ht to be pretty finh
The new work of Avery La.nd Ceobal just about to come out in the JEM sounds
to me veFJ wonderful. Don't miss it; its wonderful chemical work with the sugars.
Dr. l!Zexner nsked me to write tq? the story of the tantire Y% work from the
begining for the Fall rsport. ft is for the General 3oard of Mreotors and I havs
put a lot of time on it, I will send you a cogy if I can get enough oarbone.
Xt was.rather good fun writing it.
Your friend MrS. R8sor certa&nly puts things through ~?xX!i non 1 sit
awaiti% and &readiw the publicity. The photogrhphers came !?riday and took
a lot of pictures in the new big laborab$#ry which ze dlbd not get; they .v8
supposed to have a lot of 10~2 color. I h=Lven't seen her yet but hov8 had faa
tdks with thw poor wornah who his to write sometMnC: about me. ft is still a
?eilSrst. $!r, Vance, the head of the Fictbrial Review, has had a hemorrhage which
soundsto me as if from n gastric ulcer. 3c do not believe that he will get back
to the ,QBffiae a0 soon as they seem to ex-ect. I fe,lr th?t it ~~a.2 be yite serious.
I unclarstand that the yellow fever workers are qread over the virus now.
Dr. Mull~r has OUT old room and Mise Tilden who is now on the Staff hal W."xloaU
old office. k new man, Dr. Irrpin,'w&king with Dr. Vebsb6r has the room the blood
counts were made in, All of the third floor has been given over to work that
16 dirfjotly uakw m. Z%sners su-oervision and thet I judge was the reason for th.8
extensive moviq this summer.
3 am awfully sorry not to hl~e you here in the Laboratory: it was a very
great pleasure to me to have $0~ for two years end I sk\,zll keep on ho?izq thAt th&ngs
may turn out 30 that you will come back to the Instfitute soaa time. At any rate
I shall follow youx work with the gredest pride anO interest. You knw the real, thing
for r8S~,lrbh.
The qoans send their veq bast Q-C! nil your friends here inquire often to know
if I have head. from you. Let us 'knon ezll the interesting things goin& on with you.
Did you know that Besnikoff is to work with Shilling; in Berlin this winter; he
sailed a fen days qo. The last JAR,& has an zrticle by him to the sffedt that the
S&illirq: differential is of more importVulce thd th rest of the blood count.
V8X7 cordially yours,
| en |
converted_docs | 033242 | **OSHA 1926 Proposed Rules - HBR Comments**
**Section 1926.1401 Definitions**
It is observed there is a definition for Qualified Rigger. It is also
observed there are sections that address Operator Qualification and
Certification and a section that addresses Signal Person Qualification.
*Comment: There is no section that addresses Rigger
qualification/certification by level. Many crane accidents are
associated with bad rigging practices and should be included in the
document.*
**Section 1926.1410 (d)(4) Insulating Link/Device**
Section (d )states "At a minimum, these procedures shall include:
(4)(i) An insulating link/device installed at a point between the end of
the load line (or below) and the load.
*Comment: Due to limitations of insulator links, i.e. voltage rating
capacity (33 kv max), WLL capacity (60 tons), size/overhead clearance
restrictions, we recommend that, in circumstances where compliance
becomes an issue, the owner should be allowed to develop a specific
procedure by qualified person(s) so work can be performed safely without
the use of an insulator link (suggest reference ASME B30.5 2007,
5-3.4.5.4(a)).*
**Section 1926.1413 (a)(4)(iii)(E) Alternative measures for a Category
II deficiency**
Section (4)(E) currently states "The workers who will conduct shift
inspections are informed of this deficiency and the measures taken under
this paragraph."
*Comment: We recommend the following rewording: "The [competent
person]{.mark} who will conduct the shift inspections [shall]{.mark} be
informed [in writing]{.mark} of this deficiency and the measures taken
under this paragraph."*
**HBR, page 2 (cont'd.)**
**Section 1926.1416 (d) (3)(ii)(C) Exception**
*Comment: Recommend removing "concrete bucket" from the exception
verbiage.*
*We agree with exception verbiage as exists for pile driving operations,
etc. (too broad -- needs clarification).*
**Section 1926.1417 (j) Operation**
*Comment: Recommend the following:*
*"The operator shall be familiar with the equipment and its proper
operation. If adjustments or repairs are necessary, the operator shall
promptly inform the person designated by the employer to receive such
information [by written communication]{.mark} and, where there are
successive shifts, to the next operator. "*
**Section 1926.1427 (j)(1)(i)(E) Certification Criteria**
*Comment: Recommend the following:*
*Technical knowledge [from a qualified person]{.mark} applicable to:*
| en |
all-txt-docs | 256408 | This is Dataplot data file YOUDEN31.DAT
Paper Thickness
Source--Youden, William John (Jack) (1962).
Experimentation and Measurement.
National Science Teachers Association.
Vistas of Science
1201 16th St., NW, Washington, DC
Table 2, page 31.
Number of observations = 96
Number of variables per line iamge = 3
Order of variables on a line image--
1. Response Variable = Thickness (in mm)
2. Factor 1 = Measurer/Operator/Girl (1 to 24)
3. Factor 2 = Replication (1 to 4)
Statistical Categories--Univariate
Distributional Analysis
Comparative
Control Charts
To read this file into Dataplot--
SKIP 25
READ YOUDEN31.DAT Y X
Thickness Girl Replication
------------------------------
.0757 1 1
.0762 1 2
.0769 1 3
.0746 1 4
.0808 2 1
.0793 2 2
.0781 2 3
.0821 2 4
.0811 3 1
.0772 3 2
.0770 3 3
.0756 3 4
.0655 4 1
.0683 4 2
.0714 4 3
.0746 4 4
.0741 5 1
.0710 5 2
.0748 5 3
.0711 5 4
.0756 6 1
.0772 6 2
.0776 6 3
.0759 6 4
.0775 7 1
.0785 7 2
.0760 7 3
.0761 7 4
.0747 8 1
.0765 8 2
.0735 8 3
.0776 8 4
.0719 9 1
.0762 9 2
.0802 9 3
.0713 9 4
.0734 10 1
.0833 10 2
.0833 10 3
.0783 10 4
.0755 11 1
.0740 11 2
.0714 11 3
.0743 11 4
.0788 12 1
.0817 12 2
.0794 12 3
.0766 12 4
.0731 13 1
.0716 13 2
.0726 13 3
.0714 13 4
.0833 14 1
.0794 14 2
.0783 14 3
.0788 14 4
.0767 15 1
.0775 15 2
.0765 15 3
.0793 15 4
.0787 16 1
.0798 16 2
.0864 16 3
.0817 16 4
.0784 17 1
.0799 17 2
.0789 17 3
.0802 17 4
.0784 18 1
.0820 18 2
.0796 18 3
.0818 18 4
.0830 19 1
.0796 19 2
.0778 19 3
.0767 19 4
.0741 20 1
.0680 20 2
.0733 20 3
.0723 20 4
.0759 21 1
.0766 21 2
.0772 21 3
.0466 21 4
.0810 22 1
.0812 22 2
.0789 22 3
.0776 22 4
.0777 23 1
.0759 23 2
.0795 23 3
.0790 23 4
.0784 24 1
.0786 24 2
.0797 24 3
.0859 24 4
| en |
markdown | 791631 | # Presentation: 791631
## Industrial Cogeneration or Combined Heat and Power in Bangladesh - Technology
- Zia Haq
- US Department of Energy
- Energy Information Administration
- January, 2004
## Introduction
- Combined heat and power technology description, cost
- Cost data for illustrative purposes only
- Local manufacture and learning can substantially reduce costs
- Policy environment that has facilitated the growth of CHP in India
- Potential for CHP in Bangladesh
- Case studies – Bangladesh, India, Thailand, Indonesia, Malaysia
- Recommendations for future actions
## What is Combined Heat and Power?
- Sequential generation of two different forms of energy from a single energy source – electrical, thermal
- Conventional electricity generation efficiency 33%, separate heat and power system 45%, CHP 85%
- Large and medium industrial CHP systems – “process industries” petroleum refining, pulp and paper, chemicals, capacities > 25 MW, steam generation rates measured in thousands of pounds of steam/hr
- Small industrial – boilers providing process steam to manufacturing plants, 50 kW to 25 MW, can repower existing boilers or install new systems
- Small commercial and institutional – reciprocating engines, small combustion turbines, building electrical and heating/cooling, starting at about 25 kW, restaurants, large commercial buildings
## CHP Technologies (Reciprocating Engine)
| Technology | Typical size | Sectors | Equipment |
| --- | --- | --- | --- |
| Reciprocating engine | 100 kW | Commercial | MAN 80 kW |
| Reciprocating engine | 300 kW | Commercial | Cummins QSK19G |
| Reciprocating engine | 1 MW | Commercial | Cummins QSV91G |
| Reciprocating engine | 3 MW | Commercial, industrial | Caterpillar G3616 LE |
| Reciprocating engine | 5 MW | Commercial, industrial | Wartsilla 18V34SG |
## CHP Technologies (Gas Turbines)
| Technology | Typical size | Sectors | Equipment |
| --- | --- | --- | --- |
| Gas turbine | 1 MW | Commercial | Solar Saturn 20 |
| Gas turbine | 5 MW | Commercial, industrial | Solar Taurus 60 |
| Gas turbine | 10 MW | Commercial, industrial | Solar Mars 100 |
| Gas turbine | 25 MW | Industrial | GE LM2500 |
| Gas turbine | 40 MW | Industrial | GE LM6000 |
## Reciprocating Engine Based CHP Systems
- Low first cost, easy startup, proven reliability when properly maintained, good load-following characteristics
- Well-suited for packaged CHP in commercial and light industrial applications of 20 kW to 5+ MW
- Ability to produce steam is limited due to waste heat being rejected in jacket water at low temperatures
- Jacket water generally suitable for production of hot water
- Good for food and manufacturing industries that do not require high pressure steam but use large quantities of wash water and low pressure steam
- Other systems – high pressure boilers, steam turbines, combined cycle systems
## Gas Turbine or Combustion Turbine Based CHP Systems
- Produces high quality heat that can be used to generate steam for additional power (combined cycle) or on-site steam use
- Can burn natural gas, diesel, or be dual-fuel capable
- Low maintenance cost
- Good for > 5 MW applications
- Industrially sized CHP plant is a complex process with many inter-related subsystems
- Construction for larger sizes can take over 2 years
## Benefits of CHP Systems
- Lower fuel consumption and lower electricity costs leading to reduced operating costs
- Boilers, turbines and other components are available in the region Bangladesh, India, Thailand, Malaysia
- Increases reliability of industry reduces the impact of energy supply disruptions
- Small size, rural location, can reduce transmission and distribution system losses by 8-10%
- Financial burden can be shared by industry and utilities
- Can improve the quality of power supply for local utility
- Can delay the need for peak demand driven capacity expansion
- Diversification of energy supply
- Reduced dependence on imported sources of energy
## Comparison of CHP Technologies I
| Property | Reciprocating engine | Steam turbine | Combustion turbine | Combined cycle |
| --- | --- | --- | --- | --- |
| Electric efficiency (LHV) | 25-45% | 15-25% | 25-40% | 40-50% |
| Size (MW) | 0.05-5 | Any | 1-100 | 25-300 |
| Footprint (sqft/kW) | 0.2-0.3 | <0.1 | 0.02-0.6 | 0.6 |
| Installed cost ($/kW) | 800-1,500 | 800-1,000 | 700-900 | 600-800 |
| O&M cost ($/kWh) | 0.007-0.015 | 0.004 | 0.002-0.008 | 0.002-0.008 |
| Availability | 92-97% | Near 100% | 90-98% | 90-98% |
| Hours of operation between overhauls | 24,000 – 60,000 | >50,000 | 30,000 – 50,000 | 30,000 – 50,000 |
## Comparison of CHP Technologies II
| Property | Reciprocating engine | Steam turbine | Combustion turbine | Combined cycle |
| --- | --- | --- | --- | --- |
| Start-up time | 10 sec | 1 hr – 1 day | 10 min – 1 hr | 10 min – 1 hr |
| Fuel pressure (psi) | 1 – 45 | Not applicable | 120 – 500 may require compressor | 120 – 500 may require compressor |
| Fuels | Natural gas, biogas, propane | All | Natural gas, biogas, propane, distillate oil | Natural gas, biogas, propane, distillate oil |
| Noise | Moderate to high (requires building enclosure) | Moderate to high (requires building enclosure) | Moderate (enclosure supplied with unit) | Moderate (enclosure supplied with unit) |
| NOx emissions (lb/MWh) | 2.2 – 28 | 1.8 | 0.3 – 4.0 | 0.3 – 4.0 |
| Uses for heat recovery | Hot water, LP steam, district heating | LP-HP steam, district heating | Direct heat, hot water, LP-HP steam, district heating | Direct heat, hot water, LP-HP steam, district heating |
| CHP thermal output (Btu/kWh) | 1,000 – 5,000 | 5,000 – 25,000 | 3,400 – 12,000 | 2,000 – 8,000 |
| Useable temperature (F) | 300 – 500 | Not applicable | 500 – 1,100 | 500 – 1,100 |
## Cost and Performance of Reciprocating Engine CHP Systems
| | 100 kW | 300 kW | 1 MW | 3 MW | 5 MW |
| --- | --- | --- | --- | --- | --- |
| Installed cost, power only (year 2003 $/kW) | 1,050 | 800 | 700 | 700 | 680 |
| Total installed cost, CHP (year 2003 $/kW) | 1,350 | 1,160 | 940 | 935 | 890 |
| Heat rate (Btu/kWh), HHV | 11,375 | 10,967 | 10,035 | 9,746 | 9,213 |
| Overall CHP efficiency | 79% | 77% | 76% | 75% | 75% |
| Engine speed (rpm) | 1,800 | 1,800 | 1,200 | 900 | 720 |
| Total heat recovery (MMBtu/hr) | 0.56 | 1.5 | 4.2 | 11.1 | 18.1 |
| Power to heat ratio | 0.61 | 0.68 | 0.81 | 0.92 | 0.95 |
**Notes:**
Availability = 96% (continuous duty), equipment life = 20 years, economic life = 20 years
## Capital and O&M Cost for Reciprocating Engine CHP Systems (Year 2003 $)
| | 100 kW | 300 kW | 1 MW | 3 MW | 5 MW |
| --- | --- | --- | --- | --- | --- |
| Engine generator cost ($/kW) | 500 | 350 | 370 | 440 | 450 |
| Heat recovery ($/kW) | Inc | 180 | 90 | 65 | 40 |
| Electric interconnect ($/kW) | 250 | 150 | 100 | 75 | 65 |
| Total equipment ($/kW) | 750 | 680 | 565 | 580 | 555 |
| Labor and materials ($/kW) | 413 | 306 | 240 | 220 | 210 |
| Project and construction mgmt ($/kW) | 75 | 70 | 56 | 58 | 55 |
| Engineering and fees ($/kW) | 75 | 70 | 56 | 48 | 44 |
| Project contingency ($/kW) | 38 | 34 | 28 | 28 | 28 |
| Total installed cost ($/kW) | 1,350 | 1,160 | 940 | 935 | 890 |
| Non-fuel O&M ($/kWh) | 0.018 | 0.013 | 0.009 | 0.0085 | 0.008 |
**Notes:**
Equipment costs based on manufacturers price estimates (public information) – cost to end user
Installation costs based on manufacturers data, review of recent installations, and internal experience
Installation estimates based on assumptions of minimal site preparation, parallel to grid (synchronous generator)
O&M costs based on manufacturers estimates
Total installed cost about double the cost of basic engine generator and heat recovery equipment
Smallest system more expensive and have higher added costs for installation
Multi-megawatt engines operate at medium to slow speed (600-900 rpm) whereas smaller engines operate at higher speeds (1,200 – 1,800 rpm) which may impact operating and maintenance costs
Smaller systems better packaged and require less site work than larger systems but this effect overcome by economies of scale
Cost of interconnection switchgear as example of economy of scale
## Cost and Performance of Combustion Turbine CHP Systems
| | 1 MW | 5 MW | 10 MW | 25 MW | 40 MW |
| --- | --- | --- | --- | --- | --- |
| Installed cost, power only (year 2003 $/kW) | 1,400 | 780 | 705 | 660 | 590 |
| Total installed cost, CHP (year 2003 $/kW) | 1,910 | 1,024 | 930 | 800 | 702 |
| Heat rate (Btu/kWh), HHV | 15,580 | 12,590 | 11,765 | 9,945 | 9,220 |
| Overall CHP efficiency | 68% | 69% | 71% | 73% | 74% |
| Turbine exhaust temp (F) | 950 | 950 | 915 | 950 | 854 |
| CHP heat output (MMBtu/hr) | 7.1 | 26.6 | 49.6 | 89.9 | 128.5 |
| Power to heat ratio | 0.48 | 0.64 | 0.69 | 0.89 | 0.99 |
**Notes:**
Availability = 98%+, equipment life = 20 years, economic life = 20 years
Electrical efficiency increases as size increases
Power to steam ratio changes as size increases
Changing power to steam ratio impacts project economics which have to be matched to customer needs
## Capital and O&M Cost for Combustion Turbine CHP Systems (Year 2003 $)
| | 1 MW | 5 MW | 10 MW | 25 MW | 40 MW |
| --- | --- | --- | --- | --- | --- |
| Gas turbine package cost ($/kW) | 660 | 380 | 370 | 365 | 340 |
| Heat recovery ($/kW) | 245 | 100 | 75 | 45 | 35 |
| Fuel gas compressor ($/kW) | 120 | 65 | 65 | 50 | 50 |
| Water treatment ($/kW) | 25 | 20 | 14 | 9 | 5 |
| Controls/interconnect ($/kW) | 125 | 65 | 50 | 42 | 32 |
| Total equipment ($/kW) | 1,175 | 630 | 574 | 511 | 462 |
| Labor and materials ($/kW) | 476 | 255 | 232 | 184 | 148 |
| Project and construction mgmt ($/kW) | 118 | 63 | 57 | 51 | 46 |
| Engineering and fees ($/kW) | 82 | 44 | 36 | 28 | 23 |
| Project contingency ($/kW) | 59 | 32 | 29 | 26 | 23 |
| Total installed cost ($/kW) | 1,909 | 1,024 | 929 | 800 | 702 |
| Non-fuel O&M ($/kWh) | 0.01 | 0.006 | 0.006 | 0.005 | 0.004 |
**Notes:**
Equipment costs based on manufacturers price estimates
Installation costs based on manufacturers data and review of recent installations
Installation estimates based on assumptions of minimal site preparation, parallel to grid (synchronous generator), unfired HRSG (150 psig)
Non-fuel O&M costs based on manufacturers estimates
Smaller system more expensive and have higher added costs for installation
Cost of interconnection switchgear as example of economy of scale
## Reciprocating Engine O&M Requirements
- Routine maintenance includes replacement of engine oil, coolant, and spark plugs
- Oil analysis is done to monitor engine wear
- Top end overhaul is recommended between 12,000-15,000 hours of operation that entails cylinder head and turbocharger rebuild
- Major overhaul performed after 24,000-30,000 hours of operation and involves piston/cylinder replacement, crankshaft inspection, bearings and seals
## Gas Turbine O&M Requirements
- Routine maintenance includes on-line running maintenance, predictive maintenance, plotting trends
- Inspections include on-site hot gas path borescope inspections, non-destructive component testing using dye penetrant and magnetic particle techniques to ensure integrity of components
- Overhaul is complete inspection and rebuild of components to restore gas turbine to original or upgraded performance standards
- Maintenance costs can vary depending on quality and diligence of preventative maintenance program and operating conditions
- Cycling – gas turbines can be cycled but maintenance costs can triple for gas turbine cycled every hour versus gas turbine that is operated for intervals of 1,000 hours or more
- Over capacity operation – significant operation over rated capacity will dramatically increase number of hot path inspections and overhauls
- Liquid fuels – extended operation on liquid fuels will result in higher than average overhaul intervals
**Notes:**
Other routine maintenance items: performance testing, fuel consumption, heat rate, vibration analysis and preventative maintenance procedures
Routine maintenance required to ensure turbine is free of excessive vibration due to worn bearings, rotors, or damaged blade tips
Combustion path has to be inspected for fuel nozzle cleanliness and wear along with integrity of hot gas path components
Overhaul consists of dimensional inspection, product upgrades, testing of turbine and compressor, rotor removal, inspection of thrust and journal bearings, blade inspections, clearances, and setting packing seals
## Application Issues
- Industrial sector
- Most favorable application in pulp and paper, chemicals and petroleum refining industries
- Construction lead times for larger systems can be 2 years or more
- Cogeneration for fertilizer, process plants, refineries, tea industry
- Commercial sector
- Typical applications at: colleges/universities, government buildings, hospitals
- Disadvantages of commercial sector CHP applications
- On average commercial sites smaller than industrial sites, technologies for smaller applications more expensive and less efficient than larger systems
- Commercial establishments operate fewer hours per year and have lower load factors, providing fewer hours of operation in which to pay back their higher capital cost
- Unlike the majority of industrial sites that can absorb the entire thermal output of CHP systems on-site, many commercial sites have either an inadequate thermal load or a highly seasonal load such as space heating
- The best overall efficiency and economics come from a steady thermal load
**Notes:**
Other commercial sector applications include: solid waste facilities, offices, airports, water treatment facilities, prisons, apartments, warehousing and storage, hotels, schools, stores, and restaurants
## Criteria for Selecting CHP Technology
- Amount of power needed
- Duty cycle
- Space constraints
- Thermal needs
- Emission regulations
- Fuel availability
- Utility prices and interconnection issues
**Notes:**
Define power to steam ratio
## When Should Cogeneration Be Considered?
- When it makes economic sense to the industry
- Is the cost of electricity supplied by the utility greater than the cost of electricity from the cogeneration system?
- Is the utility not able to provide reliable power causing inconvenience or loss of production to the industry?
- Is the power quality inferior?
- When there are gains to be made from efficiency improvements
- First step is a walk-through analysis to give payback estimate
- Second step is a detailed feasibility analysis – many consulting firms, energy service companies, or can be done by industry
- Many publications and analysis tools available
## HUDCO Sanctioned Bagasse-based Cogeneration Project Capital Costs in India
| Project/borrowing organization | Installed capacity/Surplus capacity (MW) | Total project cost of installed capacity (Rs/kW) | Total project cost of installed capacity ($/kW) |
| --- | --- | --- | --- |
| Ryatar Niyamit, Mudhol | 12.3/7.7 | 20,280 | 414 |
| Vasant Dada, Sangli | 12.5/6.9 | 32,040 | 654 |
| Mysore Sugars, Mandya | 28/19.2 | 27,270 | 556 |
| Jeypore Sugars, Chagallu | 16.3/9.4 | 16,610 | 339 |
| Kukkuwada, Karnataka | 24/15.1 | 33,990 | 694 |
| Bellad, Karnataka | 14/9.2 | 28,210 | 576 |
| Chikkodi, Karnataka | 20/14.8 | 27,800 | 567 |
- Assuming Rupees 49 = 1 US$
**Notes:**
Note how these capital costs are significantly less than costs shown earlier (comparing to reciprocating engine system costs)
Could be due to local manufacture and learning, labor costs
## Status of Industrial Cogeneration in India
| Industry | Potential (MW) |
| --- | --- |
| Sugar | 5,200 |
| Distilleries | 2,900 |
| Rice mills | 1,000 |
| Fertilizers | 1,000 |
| Pulp and paper | 850 |
| Others | 4,250 |
| Total | 15,000 |
| State | Sugarcane cogen capacity (MW) |
| --- | --- |
| Tamil Nadu | 98 |
| Karnataka | 61.6 |
| Andhra Pradesh | 36.2 |
| Uttar Pradesh | 46.5 |
| Others | 30.5 |
| Total | 272.8 |
**Notes:**
Note sugar industry has potential to install 5,200 MW, and has installed capacity of about 273 MW
## Problems Faced by CHP Projects in India
- Stand-alone plants are meeting emergency or captive requirements of industry
- Back-up supply from the utility is required in most cases
- Installed capacity is far below of estimated potential in India
- Significant work and experience has been obtained
- Problems with the State Electricity Boards
- Delay in construction of transmission lines
- Synchronization with grid
- Inconsistent State government policies pertaining to power purchase agreements
- Bagasse/biomass availability
## CHP Study - Bangladesh
- Based on 1998 BUET-AIT-UNDP study preliminary survey of CHP potential in Bangladesh – 1,000 MW potential in Bangladesh
- Some experience with technology meeting 10% of total electrical requirement – fertilizer, sugar, paper, textile spinning
- Potential sites in industrial sector: pharmaceutical, edible oil, refinery
- Potential sites in commercial sector: hotel, hospital, cinema hall,
- How much follow-on and project implementation work has been done since then?
- How much of the capacity is only stand-by emergency capacity and how much wheeling, banking and buy-back activities are being done between BPDB, REB and CHP sites?
**Notes:**
Other potential sites in industrial sector include: paper recycling, textile processing, textile spinning, jute, tobacco curing, food processing, tea, tannery, knitting and hosiery, soap and chemicals, cement, ceramics, distillery, and industrial estates
Other potential sites in commercial sector include: housing complex, shopping, office
## CHP Application in Textile Spinning Mill
- Largest spinning mill in Bangladesh, established July 92, 24 hours/day, 260 days/year operation
- 7 Waukesha gas generators (920 kW each) for total capacity of 6.4 MW
- Electrical energy for motors, fans, lights, heaters, other loads
- Space cooling using 2 waste heat boilers to generate 5 tons/hr steam at 6 bar (5.9 atm, 87 psia) to drive vapor absorption chillers
- Low pressure boilers compared to state-of-the-art boilers available in India
- Chilled water used to cool production section
## CHP Application in Sugar Mill I
- One mill, 3 water tube boilers, 16 tons steam/hr at 14.7 bar (213 psia, 14.5 atm) at 246 C
- Low pressure boilers compared to state-of-the-art boilers available in India
- Steam turbine used to generate electricity for motor drives, process steam
- 1 steam turbine during milling season to meet the entire electric demand, 1 standby diesel generator also available and run during emergency
- Cogeneration facilities operate only during season 150 days/year, can be operated off-season with balancing, modernization, rehabilitation, and expansion (BMRE)
## CHP Application in Sugar Mill II
- Most sugar industries operate low-pressure boilers (15 bar)
- High-pressure boilers needed to increase efficiency
- 2,500 tons crushed/day (TCD) plant can sell 10 MW of excess capacity to grid with high pressure 64 kg/cm2 (910 psi, 63 bar) boiler
- Sound technical management needed in sugar mills to maintain high-pressure boilers
- Existing low-pressure boilers not being maintained properly leading to outages
## CHP Application in Paper Mill
- Newsprint mill with steam turbine cogeneration facility
- Capacity 13.1 MW, purchases 2.5 MW from utility grid
- Furnace oil used in boilers for steam generation
- Steam at 42 bar (41 atm, 609 psia) 400 C, 3 boilers, 161 tons steam/hr used in 3 back pressure turbines to generate electricity, steam for paper machines, autoclaves
## CHP Application in Fertilizer Plant
- One of the largest in Bangladesh, 1.8 million tons of urea/year
- Most electricity self-generated with provision for buying from grid
- 2 boilers with capacities to produce 180 tons steam/hr and 171 tons steam/hr, 60 bar (59 atm, 871 psia), at 510 C
- Steam used in 2 back pressure steam turbines to generate up to 11 MW of electricity, and used for processing
## CHP Potential in Bangladesh I
| Industry | Number of sites | Avg. installation potential per site (kW) | Potential (MW) |
| --- | --- | --- | --- |
| Tea gardens | 180 | 900 | 162 |
| Sugar (surplus capacity) | 15 | 10,000 | 150 |
| Jute | 70 | 1,500 | 105 |
| Textile spinning | 50 | 2,000 | 100 |
| Hospital | 150 | 500 | 75 |
| Office complex | 150 | 500 | 75 |
| Textile processing | 50 | 1,000 | 50 |
| Paper recycling | 14 | 3,000 | 42 |
| Ceramics | 20 | 1,500 | 30 |
| Knitting and hosiery | 50 | 600 | 30 |
| Tannery | 50 | 600 | 30 |
| Export processing zone | 5 | 5,000 | 25 |
| Hotel | 50 | 500 | 25 |
| Industrial estate | 5 | 5,000 | 25 |
| Soap and chemicals | 20 | 800 | 16 |
| Food | 15 | 1,000 | 15 |
| Housing complex | 10 | 1,000 | 10 |
| Cement | 10 | 800 | 8 |
| Distillery | 10 | 600 | 6 |
| Total | | | 979 |
## Sugar mill average potential per site may be high since mills are not big in terms of TCD
2,500 TCD provide an excess of 10 MWe to grid with high pressure boiler according to Indian experience
Using this as a guide, potential for sugar industry surplus capacity may be about 80 MW
Sugar mills have to upgrade to high pressure boilers to realize the 80 MW potential
Sugar mills have to find alternative sources of biomass to augment sugarcane bagasse, extend operation of CHP system, increase profitability
Jute industry with closing of Adamjee may have lower potential than indicated in table
If jute is approximately halved from 105 to 50, sugar is reduced to 80, the total reduces to 860 MW CHP potential in Bangladesh
- 2,500 TCD provide an excess of 10 MWe to grid with high pressure boiler according to Indian experience
- Using this as a guide, potential for sugar industry surplus capacity may be about 80 MW
- Sugar mills have to upgrade to high pressure boilers to realize the 80 MW potential
- Sugar mills have to find alternative sources of biomass to augment sugarcane bagasse, extend operation of CHP system, increase profitability
- Jute industry with closing of Adamjee may have lower potential than indicated in table
- If jute is approximately halved from 105 to 50, sugar is reduced to 80, the total reduces to 860 MW CHP potential in Bangladesh
- CHP Potential in Bangladesh II
## Sugar Mills in Bangladesh, 1993-94
| Mill | Cane processing capacity (TCD) | Existing electricity capacity (MW) | Potential electricity capacity (MW)* | Operating season (days/year) |
| --- | --- | --- | --- | --- |
| Panchagar | 1,016 | 2.0 | 4.1 | 150 |
| Thakurgaon | 1,524 | 3.0 | 6.1 | 148 |
| Shetabganj | 1,250 | 4.0 | 5.0 | 114 |
| Shyampur | 1,016 | 2.0 | 4.1 | 138 |
| Rangpur | 1,321 | 2.6 | 5.3 | 131 |
| Joypurhat | 2,032 | 2.5 | 8.1 | 136 |
| Rajshahi | 2,000 | 3.5 | 8.0 | 162 |
| Natore | 1,500 | 4.0 | 6.0 | 167 |
| North Bengal | 1,500 | 2.0 | 6.0 | 166 |
| Kushtia | 1,524 | 3.0 | 6.1 | 130 |
| Carew | 1,150 | 3.0 | 4.6 | 175 |
| Mobarakganj | 1,500 | 2.0 | 6.0 | 156 |
| Faridpur | 1,016 | 2.0 | 4.1 | 160 |
| Zeal Bangla | 1,016 | 2.0 | 4.1 | 155 |
| Deshbandhu | 300 | 0.5 | 1.2 | 67 |
| Total | | | 78.8 | |
- Export potential to grid with installation or retrofit of high-pressure boilers
## Feasibility Study Revision Needed
- Feasibility analysis was conducted in 1998 with the following capital cost assumptions: steam turbine US$1,200/kWe, gas turbine US$1,000/kWe, reciprocating engines US$900/kW
- Taka exchange rate of 48 Taka/US$
- These need to be revised, steam turbine, gas turbine costs have come down, further reductions are possible with local manufacture, Indian examples show the potential for cost reductions
- Feasibility analysis was done for paper mill, vegetable oil refinery, textile spinning mill, textile processing mill, hospital, and hotel
- Revisions needed for these with updated costs and financial conditions
## Summary of Feasibility Study for Bangladesh
| Study site | Hypothetical installed capacity (MW) | Hypothetical initial investment (crore Takas) |
| --- | --- | --- |
| Recycled paper mill | 2.75 | 11.88 |
| Vegetable oil refinery | 0.52 | 2.2 |
| Textile spinning | 2.35 | 10.2 |
| Textile processing | 0.875 | 3.7 |
| Hospital | 0.8 | 3.56 |
| Hotel | 0.8 | 3.56 |
- All sites used reciprocating engine power match option
- Need to be revised
- Economics look good but depend on price of natural gas
## Wood Waste Fired Boiler in Indonesia
- Kurnia Musi Plywood Industried (KMPI) plywood manufacturer with 850 cubic meter of log input/day, Pulau Borang, Palembang, Sumatra, Indonesia
- Residues used for 3 boilers for steam generation for use as heat source in mills
- Boilers low pressure, inefficient, poor environmental performance
- Invested in new high pressure boiler coupled with existing turbo-generator
- New boiler fired with wood waste, producing superheated steam at 35 bar g (508 psig), 380 C, coupled to existing 3.2 MW fully condensing steam turbine
- Total cost US$1.6 million (US$500/kW), excluding civil works, expected payback over 1 year
- New 35 tonnes/hr boiler
- Wood complex at Palembang
## Rice Husk Fired Plant in Malaysia
- Ban Heng Bee rice mill in Pendang, near Alor Setar in Kedah, Malaysia
- Capacity of 10 tonnes paddy/hour produces 2 tonnes rice husk/hour
- CHP plant consists of: steam boiler with capacity of 8 tons/hour saturated steam at 32 bar g (464 psig), 450 kW back pressure turbine, 3 million kcal/hour (11.9 million Btu/hour) heat exchange system for paddy drying, multicyclone dust collector
- Provides power for milling operation, hot water for paddy drying
- Equipment costs US$1.15 million (excluding civil and structural works), additional income could come from sale of ash, payback expected to be 3 years
## Malaysia
- Palm Energy Sdn. Bhd. to build 9.8 MW biomass fueled cogeneration plant in Lahat Datu, Sabah, Malaysia
- Loan by Bank Industri and Teknologi Malaysia Bhd. of 20 million ringgit (~$5.2 million), 7 year
- Total plant cost 30 million ringgit (~$7.9 million, $806/kW), comparable to US costs
- Feedstock palm oil waste
- Power to be supplied to Kwantas Corp. Bhd., Palm Energy’s parent company
- Supplying energy to Kwantas Palm Oil refinery
- Kwantas also considering possibility of selling power to local customers
## Mauritius
- Latest state of the art CHP plant
- Belle Vue sugar mills, in operation since March 2000
- 2 x 140 tons/hour boilers operating at pressure of 82 bar (81 atm, 1,190 psia) and 525 C
- 2 x 35 extraction/condensing turbine generators
- Operation on bagasse during crushing season, operation on coal and bagasse during off-season
- In-season capacity on bagasse 54 MW
- No high pressure heater, only low pressure heaters, deaerator, boiler inlet feedwater temperature 125 C
## Paper Company in Thailand
- Paper company in Panom Sarakham, 130 km east of Bangkok
- 600 kW single stage back pressure turbine coupled with an existing locally-made rice husk-fired boiler producing steam at 20 bar (290 psi)
- System supplies 15 tonnes/hour of process steam at 6 bar and 600 kW of electricity
- Payback period claimed to be less than 4 months
- 600 kW back pressure turbo-generator
## Rice Mill in Thailand
- Chia Meng Co. Ltd., Chakkaraj, Nakorn Ratchasima, Thailand, milling capacity 500 tonnes paddy/day
- 2.5 MW cogeneration plant using rice husk as fuel commissioned in March, 1997, 100 tonnes/day of rice husk input
- System includes rice husk storage, conveying, and automatic boiler feed equipment
- Exporting power to grid, may reduce export in future due to mill expansion, earning revenue from ash sales to Europe
**Notes:**
Furnace/boiler producing 17 tonnes/hour of superheated steam at 35 bar (508 psi), with automatic ash removal
2.5 MW multistage, fully condensing, turbo-generator with condenser, heat exchangers using boiler flue gas and/or superheated steam to generate hot water for paddy dryers
## Thailand - Mitr Kalasin Sugar Plant I
- Northeast Thailand, 520 km from Bangkok, owned by Mitr Phol largest sugar producer in Thailand
- Sugarcane bagasse to power internal loads and supply power to nearby villages
- Buying other industrial wastes – wood chips, rice husk, bran to produce power for people in 50 km (30 mile) radius of plant
- One of several dozen small Thai factories that are part of official drive to use waste for electricity
- Other fuels being promoted by Thai authorities – rice husk, rice bran, paddy hay, wood chips
- For small power producers (<90 MW), government has pledged to buy unlimited power from waste
- Mitr Phol supplied 100 million kWh of electricity to EGAT in 2001
## Thailand - Mitr Kalasin Sugar Plant II
- Project began 9 years ago by using bagasse combustion to produce steam to heat water
- In 2001 revenues 300 million baht ($6.93 million) from power sales, equivalent to about 3% of its 10 billion baht revenue from sugar sales
- Over past 10 years, EGAT has purchased 261 MW from 24 biomass power plants – over half of them powered by bagasse
- National Energy Policy Office (NEPO) expects that figure to grow to over 700 MW in the next 10 years
## Thailand – Second Project by Mitr Phol
- 25 MW, in Dan Chang District, Suphan Bari
- Cost $43 million ($1,720/kW), high, planned to start up in 2004
- World Bank grant of $8 million in exchange for carbon credits based on Thai government ratification of the Kyoto Protocol
- Under Kyoto Protocol’s Clean Development Mechanism (CDM), the World Bank Prototype Fund is offering $3/tonne of greenhouse gas saved over a 10 year period
## Manufacturers
- Over 250 component manufacturers
- About 50 system integrators
- Most have presence on the web
- Many have local offices in South Asia
- Significant Indian experience with sugarcane bagasse cogeneration should be exploited by Bangladesh
- Experience with CHP in Thailand, Indonesia, Malaysia, is also valuable in designing projects for Bangladesh
## Conclusions
- Significant potential in Bangladesh
- The hurdles are: institutional structure, policies, energy pricing and tariff, investment and financing
- Strong institutional barriers
- Lack of awareness
- Study needs to be updated to assess cogeneration potential (energy demand patterns, plant size, power-to-heat ratio, access to natural gas)
- Discussions are necessary between PDB and energy users to explore the CHP option
## Recommendations for Follow-up Actions
- Regulatory measures needed for sale of electricity to grid or third party, backup power from grid
- Electricity and gas company partnerships with industries to invest, guarantee O&M, share costs
- Exploration of alternative financing such as third-party participation, leasing, soft loans
- Extension of financial incentives: faster depreciation, soft loans, tax benefits
- Demonstration projects
- Education and outreach
- Survey and pre-feasibility study on CHP
**Notes:**
Alternative financing includes bilateral and international funds targeted towards global environmental protection (clean development mechanism, GEF).
Financial incentives have to be selectively granted to projects that satisfy well-specified technical, economic, and environmental criteria.
Education and outreach includes: Courses, training programs, information exchange on renewable energy, cogeneration, site selection, equipment design, establishment of curricula in schools and colleges for development of long-term human resources | en |
all-txt-docs | 184312 | *Pages 1--1 from Microsoft Word - 19746.doc*
1
STATEMENT OF COMMISSIONER MICHAEL J. COPPS
Dissenting
RE: Lockheed Martin Global Telecommunications, Comsat Corporation, and Comsat General Corporation, Assignor, and Telenor Satellite Mobile Services, Inc., and
Telenor Satellite, Inc. Assignee, Order and Authorization, SES- ASG- 20010504 00896, et al.; Order on Reconsideration.
I dissented to the assignment of licenses from Comsat to Telenor last year. I did so because the transaction resulted in 79% indirect foreign government ownership of U. S.
licenses. This represented the highest level of government control of a U. S. license allowed by the Commission in its history.
I continue to believe that foreign government control represents a serious potential threat to competition. There is a fundamental difference between companies
that operate in a free market and state- run industries that may act counter to free market forces. The Commission must only allow transactions that are in the public interest. For
me, the benefits of a transaction with such high foreign government ownership must be significant enough to overcome the potential harm to competition for the transaction to be
in the public interest.
I find now, as I found last year, that such public interest benefits do not exist here. Telenors significant market power can be used to cross- subsidize competitive services
that their U. S. licensee will provide here. Such cross- subsidization could undermine competition here in the U. S. and present a direct threat to the public interest.
The Commissions unrelenting march toward allowing more and more foreign government control of US licensees runs counter to what should be the U. S. goal of
promoting global telecommunications industry privatization. Privatization brings choices for consumers, competition for providers, and incentives for technology development.
Because this transaction allows a government- owned telecommunications company to threaten the American free market in satellite services, I must again respectfully dissent.
1
| en |
converted_docs | 071045 | Background:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
The Office of AIDS Research requests the Contractor to issue a check for
\$58,704 to support the 26^th^ Annual Symposium for Nonhuman Primate
Models for AIDS to be held on December 9-12, 2008 in San Juan, Puerto
Rico. These funds will provide travel support for key conference
participants, registration subsidies, and travel scholarships for young
scientists participating in this conference. In addition, funds will
provide support for the satellite meeting on translational medicine to
bring together investigators working in the clinical networks with
investigators working in the NHP studies.
Description of Work:
1\. Issue a check for \$58,704.
Make check payable to: Research and Sponsored Programs
21 N. Park Street, Suite 6401
Madison, WI 53715
2\. Deliver check to: Karen Watts-Green
5635 Fishers Lane, Suite 4000
Rockville, Maryland 20892
\(301\) 435-7544
| en |
markdown | 043021 | # Presentation: 043021
- EAI Service Components in Relation to XML Registry Services, eGov, LOBs & FEA/TRM
## Agenda
- What is Integration Consortium
- Integration Definitions
- IC’s Global Integration Framework
- Components of Integration
- Applying this to eGov initiatives
- FEA TRM
- OMB LOBs
- Use of Registry
- Questions?
## The Integration Challenge
- A CEO once aptly described the current state of most corporate IT structures as modern cities connected by dirt roads.
- Organizational Overview
- Founded July 2001
- http://www.integrationconsortium.org
## Mission & Purpose
- The Integration Consortium is a non-profit, leading industry body responsible for influencing the direction of the integration industry. Its members champion Integration Acumen by establishing standards, guidelines, best practices, research and the articulation of strategic and measurable business benefits.
- The mission of the Consortium is to:
- (1) support the acceptance and implementation of Enterprise Application Integration and other integration technologies, applications and services, based on international standards,
- (2) support the interoperability, advancement and convergence of technologies that enhance enterprise integration markets.
## Integration Consortium
- Launched in 2001 as the EAI Industry Consortium
- Incorporated as a non-profit organization under the Alberta Societies Act on February 25, 2002
- Changed name to Integration Consortium on May 24, 2004 to reflect broader mandate
- Membership categories:
- Executive
- Associate
- Educational/Non-Profit
- End-User
- Professional Services
- Individual
- Student
- Partnership
- Notes:
- Full voting rights
- Non voting member
## Committees
- Adaptor Technology
- Enterprise Information Integration
- Business Process Integration
- SOA
- Web Services
- Wireless Technology
- Emerging Technologies
- Methodology
- Best Practices
- More
## Definitions
- Enterprise Application Integration
- Definition: ***The process of integrating multiple applications that were independently developed, may use incompatible technology, and remain independently managed.***
- By this definition, EAI would include:
- Business Process Integration
- Enterprise Information Integration
## Guiding Principles for Enterprise Integration
**Clear IT Strategy mapped to Business Strategy**
**Mapping of corporate process and data models**
**Plan ahead for EI - investment vs. cost justification**
**Formulate an EI architecture based on integration characteristics**
**Establish clear lines of ownership and accountability**
**Evaluate vendors on commercials, stability, references, strategy**
**Evaluate technologies - scalability, flexibility, customization, standards**
**Invest in the right skills - Solution & Integration Architects**
**Pilot the desired solution, but in a real environment**
**Ensure tools and processes in place for end-to-end service mgmt **
## Enterprise Integration Taxonomy
## Common Layers of EAI Solutions
- Business Intelligence
- Business Process
- Management
- Messaging
- Adapters
- Provides real-time and historical data on performance
- of processes and assists in making decisions.
- Manages and tracks business transactions that might
- span multiple systems and last minutes to days.
- Ensures the reliability of data delivery across the
- Enterprise or between systems.
- Provides “open” connectivity into data sources while
- allowing filtering and transformations of data.
## IC Integration Methodology
## Global Integration Framework (GIF)
- a universal lexicon of integration terminology
- a vendor-neutral reference architecture
- an integration methodology including prescriptive templates and standards
- a central registry of GIF-compliant interfaces
- a software framework (possibly open source) of integration services
- an integration data model and associated tools
- an education program
- a certification process to validate the skills and knowledge of individuals, the conformance of products, and the maturity of organizations
## Global Integration Framework (GIF)
*The Global Integration Framework brings together industry standards, integration best practices, formal modeling techniques, and other initiatives to create a ****prescriptive ****approach to systems integration.*
- GIF is similar to
- W3C’s Semantic Web Vision
- Model Driven Architecture from OMG
- Boundaryless Information Flow from The Open Group
**Notes:**
GIF combines the best of each of these into a holistic approach.
## Global Integration Framework (GIF)
- Defines:
- Business Architecture
- Data Architecture
- Application Architecture
- Technology Architecture
- Based on The Open Group Architecture Framework (TOGAF)
- This is similar to FEA Reference Models
## Integration Today
## Integration Requirements
- As boundaries in organizations are demolished and stovepipes eliminated, the challenge of managing and accessing information becomes critical to organization success
- Data / information available
- Access mechanisms
- Security
- Relationships of data across disparate sources
- Rules for sharing relevant information
- Proof
- Lineage
- Verification
## N-Tier Architecture
- Business
- Logic Tiers
- Presentation
- Logic Tiers
- Presentation
- Tier
- Data Access
- Logic Tiers
- Data Tier
- Adapters
- Web Services
- Message
- Middleware
- Filters
- Related
- Information
- Aggregation
- Rules
- Constraints
- Terminology
- Resolution
- Operational
- Security
- Data Tier
- Security
- Integration
- Templates
- Transformation
- Portal
- Interface
- RPC Interface
- Workflow
- Object Model
- Forms
- Terminology
- Resolution
- Formatting
- Objects
- Adapters
**Notes:**
This is a common N-tier architecture. Traditionally, we think of the presentation layer as being devices or applications where a user would view information. However, the presentation layer could be a database, an application, external EDI feeds, etc.
## Integration Approach Benefits
- Reuse of integration objects
- Modeling business information corresponds directly to business model
- End-user / SME driven changes
- Multiple presentations for single piece of information
- Lower cost of integration
- Initial
- Maintenance
## What’s Driving Change in Federal Government?
- Agency business rationalization
- Citizen-centric services
- ROI & ROA
- Need for real-time & integrated data
- Consolidation within and across agencies
- Legacy system limitations
- Shorter development lifecycles / reduced development costs
## Federal Enterprise Architecture
- FEA reference models create a comprehensive government-wide framework to guide agency IT investment activities; and identify opportunities to collaborate on and consolidate initiatives, and integrate government activities.
## E-Gov Initiatives
- Government should be
- citizen-centered
- results-oriented
- market-based
- “Effective implementation of E-Government is important in making Government more responsive and cost-effective.”
## OMB LOB’s
- The five Lines of Business and their agency team leads are:
**Financial Management (FM) **
- Department of Energy
- Department of Labor
**Human Resources Management (HR) **
- Office of Personnel Management
**Grants Management (GM) **
- Department of Education
- National Science Foundation
**Federal Health Architecture (FHA) **
- Health and Human Services
**Case Management (CM) **
- Department of Justice
## IC and e-Gov Initiatives
- Stove-piped, agency-centric open, citizen-centric
- Replacement too expensive
- Different “duplicate” data across agencies; data access and business logic tiers resolve this
- Need to model business information to produce citizen-centric services
- Separate presentation reuse business logic / function
## XML Registry Uses
- Data Access Logic Tier utilizes adapters and services that will be defined as XML and should be sharable across agencies
- Business Logic Tier could use XML-based information models, like RDF< OWL or XTM, and rules, like SWRL or RuleML. Reuse is imperative.
- Presentation Logic Tier will utilize XSL, XForms, and other XML markups.
## The Final Architecture
- Business
- Logic Tiers
- Presentation
- Logic Tiers
- Presentation
- Tier
- Data Access
- Logic Tiers
- Data Tier
- Adapters
- Web Services
- Message
- Middleware
- Filters
- Related
- Information
- Aggregation
- Rules
- Constraints
- Terminology
- Resolution
- Operational
- Security
- Data Tier
- Security
- Integration
- Templates
- Transformation
- Portal
- Interface
- RPC Interface
- Workflow
- Object Model
- Forms
- Terminology
- Resolution
- Formatting
- Objects
- Adapters
- Security Model, Encryption, Signature...Proof
- Registry
**Notes:**
This is a common N-tier architecture. Traditionally, we think of the presentation layer as being devices or applications where a user would view information. However, the presentation layer could be a database, an application, external EDI feeds, etc.
## Agenda
- What is Integration Consortium
- Integration Definitions
- IC’s Global Integration Framework
- Components of Integration
- Applying this to eGov initiatives
- FEA TRM
- OMB LOBs
- Use of Registry
- Questions? | en |
converted_docs | 224383 | # Status Report on
# Studies of Compensating Planar Dual Readout Calorimetry
G. Mavromanolakis, A. Para, N. Saoulidou, H. Wenzel, Shin-Shan Yu,
Fermilab
Tianchi Zhao, University of Washington
# Motivation
ILC will be a source of high precision measurements which will allow
determination of the nature and the detailed structure of the 'Physics
beyond the Standard Model'. It is expected that many heavy particles
will be found at the LHC with cascade decays down to the LSP. Jets and
W/Z bosons will play the role similar to gammas in the nuclear decays;
hence a precise jet energy measurement will have the same impact as the
high precision gamma spectroscopy in nuclear physics, or in the studies
of excited states of charmonium.
The need for the improvements of the jet energy resolution is evident;
the ways to improve the 'traditional' calorimetry are few. The principal
reason for the poor energy resolution of hadron calorimetry comes from
the fluctuations of the energy lost to nuclear breakup. It results in
the observable energy to be reduced by about the 30%. This overall
(energy dependent) calibration factor(function) can be calibrated-out
for single hadrons, but event-by-event fluctuations of this energy
deficit leads to a constant term in the energy resolution.
In case of hadronic jets, where the observed signals from different
particles are typically mixed up, the difference in response of a
calorimeter to charged and neutral pions introduces another, usually
dominant, term in the jet energy resolution. Another major contribution
to jet energy resolution arises in the usual case when 'electromagnetic'
and 'hadronic' sections of a calorimeter have different
response/calibration.
There are two principal methods for major improvement of jet energy
resolution proposed so far:
- Particle Flow Calorimetry, which reduces the above-mentioned
contributions to energy resolution by reducing the role of the
'hadron' calorimetry to that of measuring the relatively small
fraction of jet energy carried by neutrons and neutral kaons
- Compensating calorimetry, which attempts to correct the energy
deposited by hadrons for the nuclear-binding energy loss. To achieve
good resolution for single hadrons this compensation must be
performed on the event-by-event basis, to maintain good jet energy
resolution it must not affect the measurement of neutral pions
energy.
# Compensating Calorimetry
Observable signals produced in the calorimeter by mono-energetic hadrons
vary substantially from one shower to another, reflecting fluctuations
of a number of nucleons liberated from the nuclei of the medium.
Improvement of the energy resolution can be attained by making a
correction for the energy lost for overcoming the binding energy. This
correction must be done on the event-by-event basis and it must reflect
the number of the nuclei broken in a particular shower. There are two
experimental sources of such a correction:
- Number of slow neutrons in the shower is proportional to the number
of broken nuclei. By a judicious weight given to the signals created
by slow neutrons one can accomplish, on average, a correction to the
observed energy which will be compensated for the invisible energy.
Such a calorimeter can be realized in practice by a judicious choice
of the relative thicknesses of the absorber and scintillation
layers.
- Number of the broken nuclei is anti-correlated with the
electromagnetic fraction of a hadron shower. The latter can be
determined from the relative amount of scintillation and Cherenkov
light as the latter will reflect primarily the contribution of
electrons in the electromagnetic cascades. This method is known as
Dual Readout Calorimetry.
# Dual Readout Calorimetry
For an illustration of the principles of dual readout calorimetry let's
consider the energy deposited via ionization in a large homogeneous
block of lead glass by 10 GeV electrons and pions.
# {width="5.0in" height="3.38125in"}
Figure 1 Fraction of energy of the incoming particle deposited in the
homogeneous block of material (lead glass) for electrons and pions.
As it is well known, in the case of the electron-induced showers the
total ionization energy is, with high precision, equal to that of the
incoming particle. In the case of the pion-induced showers, even in this
total-absorption calorimeter case, some 30% of the incoming particle
energy remains undetected and the fluctuations are very large.
{width="5.0in" height="3.386111111111111in"}
Figure 2 Correlation between the total observed ionization energy and
the electromagnetic component of the shower, as measured by the
Cherenkov component. The calibration factor K is determined by the
requirement that K×E~Cherenkov~ = E~ionization~ for electrons.
Strong correlation between the fraction of the incoming particle energy
observed as the scintillation light and the amount of Cherenkov light is
illustrated in Fig. 2. If both, the scintillation and Cherenkov light
were recorded for the hadronic showers than this correlation can be used
to correct the observed scintillation light (compensate for the nuclear
binding energy losses) and the resulting energy resolution will be only
limited by the width of the correlation.
### Dual readout? Why Planar?
Principles of dual readout calorimetry have been experimentally
established by the DREAM collaboration with fiber-based geometry. This
design is also used by the 4-th concept ILC collaboration, hence the
obvious question arises, why should one purse an alternative calorimeter
design? Here are some reasons:
- Planar geometry of dual readout calorimeter is probing the
underlying phenomena in a different way, hence it will provide
additional cross-checks for the physics mechanism of compensation
- Planar implementation allows the calorimeter to have uniform
detector/absorber structure throughout the entire volume, hence
avoid the degradation of the resolution from combination of two
different devices
- Lead glass planar calorimeter offers excellent electron and photon
energy resolution
- Planar implementation admits fine segmentation of the front section
to meet or exceed requirements of the EM calorimeters. If this
segmentation is a sub-division of the 'hadronic' part of the
calorimeter it accomplished without compromising the above-mentioned
advantage
- It allows fine transverse segmentation if it required by some
physics requirement, but it is likely to require rather crude
segmentation by itself.
### Dual Readout? Why not PFA?
PFA is widely believed to be best (the only?) method to attain very high
energy resolution for hadronic jets. This may be even true, although no
convincing method of experimental demonstration of the PFA performance
has been proposed, yet. PFA energy resolution is dominated by the
confusion term, with the next contribution, that of the hadron
calorimeter being in practice negligible. The confusion term related to
the spatial extent of a hadronic shower being the figure of merit.
Ultimate spatial resolution is of no use, wheres making hadronic shower
nearly pencil-like can help a lot. This situation is very similar to
that of very forward jet calorimetry at the LHC and the solution may be
the similar: Cherenkov based calorimetry. If the only signals used are
those produced by electrons inside the EM component of the hadron shower
the visible shower size shrinks to a very small radial extent, dependent
on the effective Moliere radius at the expense of a very poor energy
resolution, of the order of .
It may well be, therefore, that the planar dual readout calorimeter
represents the optimal detector design for the PFA. This is a unique
situation for two reasons:
- Typical PFA-optimized calorimeters have mediocre-to-poor performance
as stand-alone calorimeters, thus requiring a commitment to the
detector design long before the performance can be experimentally
demonstrated (if ever). In case of a dual readout planar calorimeter
the fall-back position is a very comfortable one.
- Improvements in the PFA and dual readout calorimeters energy
resolution are probably weakly correlated. This opens up a
possibility of both methods used at once with even further
improvement in the jet energy resolution.
# Studies of Dual Readout Calorimetry: Outline of a Program
Dual readout calorimeter, as described before, offers a very attractive
possibility for the future experiments in general and for the ILC in
particular. We propose to undertake a systematic study of practical
implementations of such a calorimeter and to examine contributions to
the energy resolution from various sources including detector geometry,
sampling fluctuations, inevitable presence of structural materials etc.
We also propose to undertake studies to develop cost-effective
implementations of such detectors. It is important to point out that the
idea of the dual readout calorimetry is more than 20 years old. Its
practical implementation was made possible only recently by the advances
of integrated electronics circuitry and the advent of novel solid
state-based photodetectors: Geiger-mode Avalanche Photodiodes.
Our current research program consists of three components, described
below:
- Simulation studies of various detector configurations and
optimization of the detector design
- R&D efforts on development of cost-effective detecting medium
- Evaluation and characterization of the GM-APD's
We believe that the construction of a final detector with high jet
energy resolution requires experimental demonstration of the claimed
performance. This is a tall order, but an important one to satisfy. Test
beam demonstration of high resolution requires a large detector with the
design very close to the final one; small 'details' can make a
significant difference when the resolution is very good.
The purpose of this study is to optimize a design of such a detector and
to establish technologies necessary for its construction. As an
intermediate step we plan to construct and test in the beam a smaller
prototype aimed at the demonstration of the performance of this
jet-oriented calorimeter for photons and electrons, including the
pointing accuracy and spatial resolution. While the segmentation of this
small prototype will likely be driven by the EM-oriented requirements,
its materials and structure must be such that by appropriate grouping of
signals it will be identical to the main body of the calorimeter.
At some later stage, once the optimal detector configuration is
identified we envisage detailed engineering studies including
integration with the rest of the experiment.
## Detector optimization studies
Given the high precision of the target calorimeter we have divided the
optimization studies into several steps with increasing complexity. This
will help, hopefully, to understand sources of various contributions to
the energy resolution and their relative interplay. It is interesting to
note, that all stages considered correspond to build-able detectors and
that the choice of the final detector design may depend on
considerations other than the ultimate energy resolution.
We have concentrated on the calorimeters using lead glass as the primary
material. Its high density, approaching 6 g/cm^3^, allows for very
compact calorimeter design. Lead glass is a good Cherenkov radiator, it
can also be doped with organic or inorganic scintillators to provide the
second readout. While this was an obvious starting point, it is quite
possible that some other materials may be finally used.
### Step 1: Large Homogeneous Calorimeter
A calorimeter consists of a single large block of an active material
with separate readout of the scintillation and Cherenkov light
components. A possible realization of such a detector could be a lead
glass block doped with (relatively slow) scintillator and the timing of
the light signal serving as a discriminator of the two components.
Mechanism of dual readout-based compensation was illustrated in Fig. 2.
{width="5.041666666666667in" height="3.4375in"}
Figure 3 Observed energy, scaled by the beam energy, of 20 GeV pions in
a large total absorption calorimeter (black histogram). Read histograms
illustrate the effect of the correction using the correlation between
scintillation and Cherenkov light.
Fig. 3 illustrates the result of the measurement with a dual readout
calorimeter: the mean energy is equal to the beam energy (linearity!)
and the relative energy resolution is significantly improved. It is
worth noticing that the corrected response is much better described by a
Gaussian curve than the uncorrected one. It is important to notice that
the shape of the correlation is very weakly dependent on the pion energy
and in the following we will use a single correction function derived
for pions at 5 GeV.
{width="5.0in" height="3.392361111111111in"}
Figure 4 Scaled energy resolution  for pion-induced
showers as a function of pion energy. Black points are for the total
ionization measurement, red points are the measurements corrected using
the Cherenkov component.
Resulting corrected energy resolution for single charged pions scales
with the pion energy like  in contrast to the
uncorrected measurement which shows an early onset of the departure
related to a constant term in energy resolution.
The measurement of pion energy using the Cherenkov-corrected
scintillation light shows no significant non-linearity: the resulting
mean energy is equal to the primary particle energy and, at the same
time, it is same for the neutral and charged pions. This is of critical
importance for the jet energy measurement; it removes the dependence on
the jet fragmentation.
The results mentioned above are for single particles detected in a large
calorimeter. One might expect that the event-by-event correction will be
less effective when an ensemble of particles (jet) is measured at once.
{width="6.1097222222222225in"
height="4.097222222222222in"}
Figure 5 Scaled jet energy resolution for corrected and uncorrected
measurement as a function of jet energy. Jets are defined as ensembles
of particles, with 20% of them, on average, being neutral pions. 'Basic'
jets are constructed with a 'typical' fragmentation function, 'Low' jets
consist of 5 GeV particles, 'High' jets consist of 20 GeV particles
only.
Fig. 5 demonstrates that the Cherenkov-based correction works well even
in the jet environment. Jet energy is determined using the scintillation
and Cherenkov signals summed over the entire collection of particles,
yet the energy resolution remains better thanand it
depends very little on the actual jet fragmentation model. This is in
contrast with the uncorrected measurement, where the energy resolution
depends significantly on the jet composition.
{width="6.1097222222222225in"
height="4.143055555555556in"}
Figure 6: Jet energy resolution as a function of jet energy of corrected
and uncorrected measurement for 'typical' jets and the artificial
ensemble of jets consisting of charged hadrons only.
Fig. 6 shows that in the traditional calorimeters with e/π response
different from unity the jet energy resolution is dominated by the
fluctuations in the π^o^ component of the jet. In case of the dual
readout calorimetry the situation is quite different; in fact the
sizeable electromagnetic component of the jet tends to improve slightly
the energy resolution.
We conclude that a homogeneous calorimeter with dual readout would
provide a very attractive option for detector optimized for jet
spectroscopy. If built on the basis of lead glass doped with
scintillator it would be a relatively compact detector, as the density
of lead glass may approach 6 g/cm^3^. It is imortant to note that while
the requirements on the detector granularity are extremely weak in such
a case, very fine segmentation is not at all precluded, if desirable for
other reasons.
The principal challenges in the construction of such a detector will
likely involve:
- Identification of a suitable scintillating dopant, preferentially
with longer time constant of the order of tens of nanoseconds
- Efficient light collection
- Photodetectors capable of separation of the 'prompt' and the 'slow'
components of light
### Step 2: Longitudinally Segmented Calorimeter; Case I - Uniform Medium
In this step we investigate how the performance of the dual readout
degrades when the calorimeter is subdivided longitudinally into several
layers: Cherenkov detector, Scintillator and Absorber (structural
material). We expect several sources of additional fluctuations to
appear here, in comparison with the previous step:
- Observed signals (Cherenkov and scintillation) will reflect
additional (sampling) fluctuations. They are present even in the
absence of structural materials.
- The Cherenkov signals and the scintillation signals (one used to
'correct' the other) reflect physical signals in different locations
in the detector
It would be natural to use plastic scintillator to detect scintillation
light. This would, however, introduce another source of complexity
related to the fact that the majority of neutrons would be deposit their
energy in the scintillator. This configuration, will be studied in the
next step.
Investigations of the longitudinally segmented detector have just
commenced. The main questions we want to address are:
- What is the optimal geometry of the detector layers to achieve the
best energy resolution? What is the contribution of the sampling
fluctuations to the energy reaolution?
- What is the optimal procedure of combining the scintillation and
Cherenkov information? Segmented readout opens up possibility of
'local' rather than 'global' correction.
In the following we indicate some of the initial insights:
{width="5.0in" height="5.1in"}
Figure 7 Sampling fluctuations contribution to the energy resolution as
a function of the thickness of the active detector for different
thicknesses of the interleaved inactive (absorber).
We have simulated a detector consisting of 1 mm thick lead glass and
collected the ionization and Cherenkov energy loss in every layer. In
the subsequent analysis we group these thin layers into 'scintillation',
'Cherenkov' and 'passive' layers to study various detector geometries.
Fig. 7 shows the contribution of sampling fluctuations (for 10 GeV pion
showers) to the energy resolution as a function of the thickness of the
'scintillation' layer. When scintillator layer is 'thick enough' its
actual thickness is unimportant and the energy resolution scales
approximately like , where d is the thickness of
the inactive layer. We observe that the energy resolution is not only a
function of the sampling fraction, or the sampling frequency alone. In
particular we notice that fluctuations of energy depositions in a very
thin scintillation layer have a significant contribution to the energy
resolution.
The compensation algorithm in a segmented detector can be more
complicated, but as a first step we use the same one as used for the
homogeneous detector: correct the total amount of scintillation light
with the help of total amount of the Cherenkov light. It appears that
this compensation method works quite well, moreover it appears that the
compensating information is fully contained in a very thin layer of
Cherenkov radiator adjacent to the scintillator layer. As an example,
energy resolution of a detector consisting of alternating layers of 30
mm scintillator and 20 mm Cherenkov detector is nearly the same as the
detector consisting of 30 mm scintillator, 2 mm Cherenko0v and 18 mm
structural material.
{width="4.822916666666667in"
height="3.2395833333333335in"}
Figure 8 Jet energy resolution as a function of jet energy for a
calorimeter with 3 cm thick scintillator, 2 mm thick Cherenkov radiator
and 18 mm thick passive material
In a manner similar to the homogeneous detector case we have studied the
energy resolution for the ensembles of particles (a.k.a. jets). As shown
in Fig. 8 even in the presence of significant structural material the
'global' correction allows to attain the energy resolution of the order
of .
In a segmented detector there is more information available in a form of
individual scintillation and Cherenkov energy depositions. As the
compensation aims at correcting the 'hadronic' response to the level of
'electromagnetic' one may expect further improvement of the resolution
by a judicious use of depth-dependent information. As the first step we
tried to apply a 'correction' to the scintillation signals by defining
the total energy as:
where i denotes the layer number, E^sc^ and E^Ch^ are the observed
energy depositions and the correction function β is determined to
optimize the overall energy resolution.
Initial studies indicate that further improvement to the resolution can
be realized, as shown in Fig. 9
{width="3.6145833333333335in"
height="2.4895833333333335in"}
Figure 9 Energy resolution for single particles om a calorimeter with 3
mm scintillator and 2 mm cherenkov layers. Red curve is the scintillator
energy alone, blue curve is the dual readout-corrected with the total
amount of light, green line is for the dual readout and local correction
### Step 3: Longitudinally Segmented Calorimeter; Case II -- Plastic Scintillator
Shower development depends to a certain degree on the material. From the
calorimetric point of view the probably the most important material
difference is related to the hydrogen (or other light elements) content
of the material. The primary difference between the scintillating glass
discussed before and the plastic scintillator case lies in the fact that
most of slow neutrons are likely to deposit their kinetic energy in the
plastic, thus providing some degree of compensation. We expect to extend
the studies of local compensation to the plastic scintillator case and
to learn about possible advantages of combined compensation mechanism
involving neutrons and Cherenkov light.
### Step 4: Longitudinally and Transversally Segmented Calorimeter
Dual-readout compensation in a homogeneous calorimeter did not require
any segmentation. With segmented detector a global correction using dual
readout is clearly an attractive avenue. The power of such a correction
is reduced by the fact that two observed components: scintillation and
Cherenkov light do not necessarily correspond to the same physical
signals. In the case of longitudinally segmented calorimeter a 'local'
correction dependent on the local scintillation-to-Cherenkov ratio has
further improved the energy resolution, despite the fact that the light
collected in any given layer is, in general, a mixture of signals
produced by 'electromagnetic' and 'purely hadronic' shower components.
One may expect that extension of the weighting technique, but involving
a weighting function defined for a single cell, rather than an entire
plane, will lead to further improvement of the resolution.
## Hardware-oriented R&D
Detector performance and optimization studies are the primary focus of
our studies and this is primarily related to the scarcity of available
resources and manpower. It is very important to keep adequate connection
with reality, to make sure that the concepts under investigations
correspond the some realize-able detectors. Conversely, we utilize our
optimization studies to identify critical areas which need to be
addressed.
So far we have identified the following areas:
- Light collection and light yield.
- Development of scintillator-doped (lead) glass
- Production of cost-effective lead glass
- Photodetectors permitting seamless light read out of voxel-ized
detector
On the light yield front, we have started to build an infrastructure and
cosmic ray test stands to evaluate the number of collected photons, but
we do not have definite answers, so far. On the other hand we notice
that related measurements were performed as a part of the detector R&D
for TESLA. Thesis of Ralph Dollan reports that a minimium ionizing
particle traversing a 1×1×4 cm crystal of SF57 lead glass read out with
the waveshifting fiber produces 19±7 photons emerging from the fiber.
In a similar vein, we did not make any progress towards the production
of scintillating glass, but we notice that there are groups pursuing
this subject with new colliding beam detectors in mind. For example, a
group from Northwestern Polytechnical University, Xian has reported
interesting results of doping glass with organic activators p-TP and/or
POPOP.
Production in general, and cost effective production in particular, of
lead glass tiles presents a significant problem. Lead glass was a
workhorse of high energy physics for decades, but its relatively high
cost was one of the impeding factors. This cost is dominated by the cost
of cutting and polishing of the blocks to provide superb optical
quality. Already some 25 years ago a dedicated studies have demonstrated
that a cost-effective casting and/or extrusion production methods can be
utilized to produce lead glass with adequate quality for a possible use
in large colliding beam detectors. Environmental concerns have reduced
the spectrum of potential vendors, though. We have contacted several
potential lead glass manufacturers. The most advanced discussions have
been conducted with the Shanghai Xinhu Glass Co., LTD in Shanghai. The
preliminary discussions of our needs and the working of their production
line indicate that relatively inexpensive production of tiles of the
required dimensions. Cost estimates make little sense at the present
stage, though, before the adequacy of dimensional tolerances and optical
quality is demonstrated.
The greatest amount of effort we have dedicated to photodetectors. For a
magnetic environment of the expected detectors and for the purpose of
hermetic light read out inside the large volume there is the only one
possibility: Geiger-mode Avalanche Photodiodes. These novel
photodetectors are, in fact, an enabling technology for the planar dual
readout calorimetry. These detectors are still in their infancy, hence
their evaluation and characterization is of great importance. On one
hand we need to validate their applicability for our purposes, on the
other hand it is still possible to contribute to their evolution.
We have constructed a GM APD testing laboratory with a goal of
systematic evaluation and characterization of detectors produced by
different vendors. The testing facility is fully automated and run under
the control of LabView. At present we are conducting and analyzing
static tests to determine the breakdown characteristics of the diodes as
a function of the operating conditions.
{width="5.0in" height="3.8652777777777776in"}
Figure 10 I-V curves for different types of detectors as a function of
temperature. For each of the three detectors there are 8 curves taken at
temperatures ranging from 0 to 30 degrees C.
Fig. 10 illustrates the range of characteristics of the available
detectors. The operating voltages, gains, noise levels and the
temperature sensitivity vary considerably.
Static characteristic of the detector is used to establish the operating
point as a function of the temperature. This is the input to the dynamic
studies, which are conducted in two steps: with and without the external
light input.
The setup for the dynamical characterization of the detectors consists
of transconductance amplifier, digital scope, LabView data acquisition
and ROOT-based analysis program. We have established an automated system
for measurement of rates and gains of the detectors as a function of the
operating conditions. We have also commissioned a laser-based
variable-intensity light source and we are planning to develop a
complete characterization of the detector output as a function of rate
and amplitude of the light signal.
Dual readout calorimetry we may require separation of fast and slower
light components. On one had silicon-based photodetectors have excellent
timing resolution, on the other hand they do exhibit significant
afterpulsing, as shown in Fig. 11. Good understanding of the origin and
the scale of these phenomena is necessary to provide feedback to the
manufacturers to optimize the detector design on one hand and to
understand their implications for our application on the other hand.
{width="5.0in" height="3.8631944444444444in"}
Figure 11 Examples of single output waveforms produced by a silicon
photodetector in the absence of external light. Dark count rates are far
too low to account for the frequency of the multiple signals observed.
These signals are afterpulses induced by the trigger signal.
# Manpower and resources
The work presented here was conducted by a group of people and Fermilab
and University of Washington working on a part-time fashion. The total
efforts intgegrates to about 1.0 FTE. The hardware effort at the
University of Washington is supported by the LCRD grant of \$17K. At
Fermilab this effort benefits from a support by the Particle Physics
Division.
While we find these studies are quite interesting, it is quite clear
that the resources available are not adequate to bring the planar dual
readout calorimeters to a full maturity. We are very happy to notice,
however, that the interest in this approach to calorimetry is growing.
Our efforts have been joined lately but the INFN groups from Pisa and
Trieste and by University of Iowa. We are also aware of the dual readout
calorimetry collaboration *in statu nascendi* in Italy. The 4-th concept
collaboration pursues different implementation of a dual readout
calorimeter, but there is a considerable of overlap.
| en |
converted_docs | 994453 | Required Report - public distribution
**Date:** 12/20/2005
**GAIN Report Number:** AR5038
AR5038
**Argentina**
**Food Processing Ingredients Sector**
**2005**
**Approved by:**
Kari Rojas
U.S. Embassy
**Prepared by:**
Martha Melgarejo/ María Julia Balbi
**Report Highlights:**
The Argentine market of food ingredients of natural origin accounts for
\$120 million, of which imports are approximately 10 percent. Imported
food ingredients are usually those which are not manufactured locally.
There is a significant market for some U.S. food ingredients among local
producers of ingredients, who use them to manufacture high-value,
tailor-made food products.
Includes PSD Changes: No
Includes Trade Matrix: No
Unscheduled Report
Buenos Aires \[AR1\]
\[AR\]
Table of Contents
[INTRODUCTION 3](#introduction)
[SECTION I. MARKET SUMMARY 3](#section-i.-market-summary)
[SECTION II. ROAD MAP FOR MARKET ENTRY
6](#section-ii.-road-map-for-market-entry)
[A. Entry Strategy 6](#a.-entry-strategy)
[B. Market Structure 6](#b.-market-structure)
[C. Company Profiles (2004) 7](#c.-company-profiles-2004)
[D. Main Argentine F&B Companies by Product-Type
9](#d.-main-argentine-fb-companies-by-product-type)
[E. Sector Trends 14](#e.-sector-trends)
[SECTION III. COMPETITION 15](#section-iii.-competition)
[SECTION IV. BEST PRODUCT PROSPECTS
16](#section-iv.-best-product-prospects)
[SECTION V. USEFUL WEBSITES 16](#section-v.-useful-websites)
[SECTION VI. POST CONTACT AND ADDITIONAL INFORMATION
17](#section-vi.-post-contact-and-additional-information)
[ANNEX I. MAIN FOOD INGREDIENT IMPORTS 2004
18](#annex-i.-main-food-ingredient-imports-2004)
[ANNEX II. ORIGIN OF FOOD INGREDIENTS USED IN THE ARGENTINE MARKET
20](#annex-ii.-origin-of-food-ingredients-used-in-the-argentine-market)
# INTRODUCTION
During the past decade, the Argentine food and beverage industry (AF&BI)
underwent steep changes, which reflected the political and economic
development of the country. The most relevant changes were as follows:
- Until 1999, food production and exports grew significantly. The
economic indicators of 1999 were the most relevant during the period
between 1994 and the beginning of 2004.
- The convertibility plan, which pegged the Argentine peso to the
dollar, strongly reduced the local production of many food
ingredients, which were promptly substituted by imports. The
Purchasing and Development Divisions of local food companies
searched for domestic supply of inputs to minimize the impact in the
final cost of the products. This worked for basic ingredients but
other more complex ones, or those whose manufacturing was not
feasible due to the small volumes demanded by the market, had to be
imported.
- After the economic crisis, followed by devaluation, of early 2002,
the volume of imported food ingredients increased, fostered by a
remarkable growth in food exports as a result of the competitiveness
gained by Argentine companies. During the past few years, with a
more stable economy, some positive indicators showing good prospects
were:
- Launching of new products by food companies.
- Important investments in food processing machinery.
- Growing demand of technical staff for laboratories and
production areas.
# SECTION I. MARKET SUMMARY
Food ingredients used in the manufacturing of foods and beverages (F&B)
vary according to their complexity, and the percentage of each
ingredient used in the formulation of the product may differ with
respect to its functionality. The most simple and widely used
ingredients in the AF&BI are: corn starch, natural sweeteners (such as
fructose) which substitute for sacarose, powdered milk, egg albumin, soy
protein, casein, gelatin, and fruit concentrates. Wheat and potato
starches are also used but to a lesser extent. Spices and herbs, and
their extracts, have more specific uses. There is local supply of
powdered milk, fructose, egg albumin, gelatin, casein, fruit pulp,
glucose, citrus essential oils, among others.
The confectionery, baking, sweet and salty premix, and beverage
industries demand the largest volume of food ingredients. Pet food
manufacturers also use food ingredients.
According to private sources, the Argentine market of food ingredients
of natural origin (excluding artificial ingredients of chemical origin)
accounts for \$120 million, of which imports are approximately 10
percent. Imported food ingredients are usually those which are not
manufactured locally, such as: cocoa, pectins, protein concentrates and
isolates, some spices, some food supplements, ginseng, and modified
starches, among others.
The following table illustrates F&B imports destined to the food
manufacturing industry, including natural and artificial ingredients:
Million \$
-------------------------- --------------------------------------------
Calendar Year F&B imports for the food industry (incl.
natural and artificial ingredients)
2000 230
2001 187
2002 138
2003 203
2004 292
2005 350 (\*)
-------------------------- --------------------------------------------
Source: Dirección Nacional de Alimentos (National Food Division),
Secretaría de Agricultura, Ganadería, Pesca y Alimentación (Secretariat
of Agriculture, Livestock, Fisheries, and Food - SAGPyA, in Spanish)
(\*) Estimated.
The AF&BI comprises approximately 25,000 manufacturing plants and total
sales are estimated at about \$35 billion.
The following information shows the behavior of the AF&BI during the
past decade:
1. The Gross Domestic Product (GDP) of the AF&BI reached its highest
level in 1998, then dropped to a minimum in 2002, and finally
increased during 2004 to reach values very close to record levels.
In 2005, the maximum GDP was exceeded, which means that the economy
has not only recovered but is also expanding significantly.
2. The Monthly Industrial Estimate (MIE), created by the National
Institute of Statistics and the Census (INDEC, in Spanish), shows
the evolution of the food processing sector based on data from the
leading local companies. The AF&BI grew from 96 to 103, i.e. about
7.6 percent in 2004, compared to the previous year. In 2005, the
1998 record value of 103 was exceeded. (Base 1997=100)
> According to the MIE during January-August 2005, compared with the
> same period of 2004, interannual variation of some sectors of the
> AF&BI shows significant growth, primarily due to sustained economic
> recovery. The following are some examples:
Beef 2.7%
# Poultry and fish 25%
### Dairy products 16.5%
Oils and meals 15.6%
Beverages 5%
3. According to INDEC, during the first half of 2005, the average use
of the local installed capacity of the AF&BI was about 73 percent,
slightly below the 2004 value.
4. The growth of investment is another significant indicator of
confidence within the food processing sector. According to official
statistics, imports of food processing machinery in 2005 accounted
for \$80 million, similar to 2004.
> The investment of food processing machinery, during the first half of
> 2005, by product category is illustrated below:
>
> Fats and oils 35%
Fruit juices, wine and other alcoholic beverages 11.5%
### Cereals and vegetables 8.5%
Cocoa and chocolate 6%
5. Foreign Trade
1. During January-June 2005, AF&BI exports (\*) totaled about \$5.5
billion, and 16 million metric tons. The oilseed industry
accounted for 60 percent; the beef industry, 14 percent; the
fish industry, 8 percent; the dairy industry, 5 percent; and the
fruit and vegetable industry, 4 percent.
2. During the first half of 2005, F&B imports (\*) totaled about
\$294 million, up approximately 10 percent compared to the same
period of 2004, due to an increase in consumption and lower
prices of imported products. Contrary to exports, which are
concentrated in relatively few sectors, imports cover a wide
range of products, such as:
> Cocoa and cocoa preparations 14%
>
> Various food preparations 11%
>
> Coffee, tea, and spices 10.5%
>
> Meat products, especially pork meat 9.5%
Edible fruits 8%
Preparations of meat, fish, and seafood 7%
(Source: INDEC)
(\*) All items related to F&B products, including consumer-ready foods,
intermediate products, and food ingredients.
3. Origin of imports by value:
> Mercosur (Argentina, Brasil, Paraguay & Uruguay,
>
> with Chile, Bolivia, and Peru as associates) 59%
EU (European Union) 12%
ALADI (Latin American Integration Assn.) 11%
### NAFTA (North American Free Trade Agreement) 7%
ASEAN (Assn. of Southeast Asian Nations) 4%
Other 7%
> (Source: FAS estimate based on data from Dirección Nacional de
> Alimentos, SAGPyA)
6. Trends in the AF&BI
1. Modern technology in facilities, for the processing of both
commodities and high-value foods.
2. Implementation of updated food quality and safety systems, even
in small and medium-sized companies.
3. Very good storage, distribution, and logistical systems.
4. High share of the F&B sector in total Argentine exports.
5. High technical level in research and development, and quality
control areas.
6. Expansion of foreign markets for high-value F&B.
7. Opportunities and Challenges of U.S. Food Ingredients
----------------------------------- -----------------------------------
ADVANTAGES CHALLENGES
Wide variety of U.S. high-value High cost incidence of U.S. food
food ingredients and specific uses ingredients in formulated foods.
for each food application.
Higher competitiveness of U.S. food Strong competition of Brazilian
ingredients compared to EU products products, which have lower costs,
due to the high value of the euro primarily due to the zero import
vis-a-vis the dollar. tariff for most food products among
Mercosur member countries.
Expansion of Argentine exports of Domestic production of basic food
high-value foods (mainly bakery and ingredients at lower costs.
confectionery products), which will
demand higher volumes of food
ingredients.
U.S. supply of concentrated juices Competition from other markets,
and herb extracts for the beverage which are not tied to the euro,
industry, which is expanding in such as China.
Argentina.
----------------------------------- -----------------------------------
# SECTION II. ROAD MAP FOR MARKET ENTRY
## A. Entry Strategy
There are various ways to introduce food ingredients into the local
market depending on the profile of the company and the food ingredient
involved. The following are a few recommendations to consider:
- The presentation of the product to the food processing company may
be done directly or through a distributor and/or representative.
There are a few local and/or regional distributors who are very well
known in the AF&BI. Another option is through a joint-venture.
- It is necessary to identify the sector/s of the company where it is
more convenient to present the food ingredient offered. This is
extremely important for the product to be evaluated by the
appropriate professionals. Larger companies usually have a Research
and Development Division. Other smaller companies receive proposals
of new ingredients through their Purchasing Division. If the
ingredient is a novelty product, it is more convenient to present it
to the Marketing Division.
- Besides presenting the product to the industry, it can be
simultaneously promoted in specialized magazines (focused on food,
nutrition and health), at technical events (seminars, conferences,
etc.), and/or trade shows.
## B. Market Structure
There is a significant market for some U.S. food ingredients among local
producers of ingredients, who use them to manufacture high-value,
tailor-made food products through mixes, combinations of various
ingredients, etc. This system is very useful for both large and
medium/small-sized companies.
## C. Company Profiles (2004)
The following are some of the most important F&B companies in Argentina:
+------------------+-----------+----------+------------+--------------+
| Company | Sales | End-Use | Production | Procurement |
| | | Channels | Location | Channels |
| (Product Types) | (\$ | | | |
| | Thousand) | | | |
+------------------+-----------+----------+------------+--------------+
| Aceitera General | 1,220,000 | Retail | San Luis | Direct |
| Deheza (edible | | and HRI | (1) | |
| oils, | | | | Importers |
| mayonnaise, soy | | | Córdoba | |
| milk) | | | (3) | |
+------------------+-----------+----------+------------+--------------+
| Molinos Río de | 850,000 | Retail | Buenos | Direct |
| la Plata (edible | | and HRI | Aires (7) | |
| oils, rice, | | | | Importers |
| pasta, premixes, | | | San Luis | |
| breading, | | | (1) | |
| margarine, | | | | |
| frozen foods, | | | Santa Fe | |
| meats) | | | (2) | |
| | | | | |
| | | | Chaco (1) | |
+------------------+-----------+----------+------------+--------------+
| SanCor | 420,000 | Retail | 18 plants | Direct |
| | | and HRI | | |
| (milk, yoghurt, | | | | Importers |
| "dulce de | | | | |
| leche", butter, | | | | |
| cheese) | | | | |
+------------------+-----------+----------+------------+--------------+
| Mastellone | 400,000 | Retail | Buenos | Direct |
| (milk, "dulce de | | and HRI | Aires (4) | |
| leche", butter, | | | | Importers |
| yoghurt, cheese) | | | San Luis | |
| | | | (1) | |
| | | | | |
| | | | Córdoba | |
| | | | (1) | |
+------------------+-----------+----------+------------+--------------+
| Arcor | 400,000 | Retail | 31 plants | Direct |
| (confectionery | | and HRI | in | |
| pcts., baked | | | | Importers |
| goods, canned | | | Argentina | |
| vegetables, | | | | |
| jams, chocolate | | | Brasil | |
| pcts., premixes) | | | | |
| | | | Uruguay | |
+------------------+-----------+----------+------------+--------------+
| Química Estrella | 75,000 | Retail | | Direct |
| (rice, dried | | and HRI | | |
| foods) | | | | Importers |
+------------------+-----------+----------+------------+--------------+
| Quickfood | 170,000 | Retail | Buenos | Direct |
| (chilled cuts, | | and HRI | Aires (3) | |
| frozen cuts, | | | | Importers |
| beef patties, | | | Santa Fe | |
| frozen cooked | | | (1) | |
| beef) | | | | |
| | | | San Luis | |
| | | | (1) | |
| | | | | |
| | | | Uruguay | |
| | | | (1) | |
+------------------+-----------+----------+------------+--------------+
| Lagomarsino | 100,000 | Retail | 8 plants | Direct |
| (wheat flour, | | and HRI | | |
| bakery and | | | | Importers |
| premixes for | | | | |
| cakes and bread) | | | | |
+------------------+-----------+----------+------------+--------------+
| Molinos Fénix | 11,000 | Retail | 3 plants | Direct |
| (wheat flour) | | and HRI | | |
| | | | | Importers |
+------------------+-----------+----------+------------+--------------+
| Molinos Semino | 25,000 | Retail | 2 plants | Direct |
| (wheat flour, | | and HRI | | |
| gluten and | | | | Importers |
| starch) | | | | |
+------------------+-----------+----------+------------+--------------+
| Orieta (jams, | 11,000 | Retail | 2 plants | Direct |
| solid jams, | | and HRI | | |
| confectionery | | | | Importers |
| pcts., solid jam | | | | |
| milk, raisins) | | | | |
+------------------+-----------+----------+------------+--------------+
> Source: Comisión Nacional de Valores.
## D. Main Argentine F&B Companies by Product-Type
# DAIRY PRODUCTS
+---------------+-------------------------+---------------------------+
| COMPANY | Main activity | Location (Provinces) |
+---------------+-------------------------+---------------------------+
| SanCor Coop. | Butter, milk, powdered | Santa Fe, Córdoba, Buenos |
| Ltda. | milk, cheese, cream, | Aires |
| | | |
| | yogurt | |
+---------------+-------------------------+---------------------------+
| Mastellone | Butter, milk, powdered | Buenos Aires, San Luis |
| Hnos./ | milk, cheese, cream, | |
| | | |
| La Serenísima | yogurt, dessert | |
+---------------+-------------------------+---------------------------+
| Nestlé | Powdered milk, | Córdoba, Santa Fe, Buenos |
| Argentina | concentrated milk, | Aires |
| S.A. | infant formula, | |
| | fortified milk, ice | |
| | cream | |
+---------------+-------------------------+---------------------------+
| Molfino - La | Milk, cheese, cream | Córdoba, Santa Fe. |
| Paulina | | |
+---------------+-------------------------+---------------------------+
| La Salamandra | Dairy artisan products | Buenos Aires |
+---------------+-------------------------+---------------------------+
| Williner | Milk, cheese, butter | Santa Fe |
+---------------+-------------------------+---------------------------+
| Kasdorf | Baby food | Buenos Aires |
+---------------+-------------------------+---------------------------+
| Milkaut | Milk, butter, cheese, | Santa Fe, Buenos Aires, |
| | yogurt, whey protein, | San Luis, La Rioja |
| | milk protein | |
+---------------+-------------------------+---------------------------+
SNACK FOODS (FLAVORED AND SWEET SNACKS AND NUTS)
+----------------+-----------------------+----------------------------+
| Pepsico | Flavored snacks, oat | Buenos Aires |
| Elaboradora | flakes, cereal bars, | |
| Argentina de | flakes (potato, | |
| Cereales SRL | carrot), foie gras | |
+----------------+-----------------------+----------------------------+
| Georgalos | Candied peanuts**,** | |
| Hnos. | cereal bars, nougats, | |
| | and other | |
| | confectionery | |
| | products | |
+----------------+-----------------------+----------------------------+
| Golden Peanut | # | Córdoba |
| Argentina S.A. | Confectionery peanuts | |
+----------------+-----------------------+----------------------------+
| Olega | # | Córdoba |
| S.A.C.I.I.A. y | Confectionery peanuts | |
| F. | | |
+----------------+-----------------------+----------------------------+
| Cotagro Coop. | # | Córdoba |
| Agropecuaria | Confectionery peanuts | |
| Ltda. | | |
| | By-products | |
| | | |
| | Seeds | |
+----------------+-----------------------+----------------------------+
| Gastaldi Hnos. | # | Córdoba |
| | Confectionery peanuts | |
| | | |
| | Wheat mill products | |
| | and by-products | |
+----------------+-----------------------+----------------------------+
| Nutrasun | Sunflower seeds | Buenos Aires |
+----------------+-----------------------+----------------------------+
| La Delicia | Chocolates, cereals | Buenos Aires |
| Felipe Fort | and fruit bars | |
| S.A | | |
+----------------+-----------------------+----------------------------+
| Laso S.A. | Cereal bars, | Buenos Aires |
| | | |
| | granola bars, corn | Chubut |
| | flakes, frosted | |
| | flakes, puffed | |
| | cereals, chocolate, | |
| | fruits, cookies, | |
| | fried potatoes and | |
| | sweet potatoes | |
+----------------+-----------------------+----------------------------+
> PREPARED FRUITS AND VEGETABLES; OILSEED PRODUCTS; SAUCES; AND FROZEN,
> CANNED AND DRIED PRODUCTS
+----------------+-----------------------+----------------------------+
| # Farm Frites | Frozen fried potatos | Buenos Aires |
+----------------+-----------------------+----------------------------+
| Mc Cain | 170,000 MT/year | Buenos Aires |
| Argentina S.A. | Frozen potatoes | |
| | | |
| (67% market | | |
| share) | | |
+----------------+-----------------------+----------------------------+
| Molinos Río de | Frozen vegetables | Buenos Aires |
| la Plata | | |
+----------------+-----------------------+----------------------------+
| Benvenuto | Jams, fruit | Mendoza |
| S.A.C.I. | preserves, | |
| | marmalades, fresh | Buenos Aires |
| | fruits and | |
| | vegetables, pulses, | Río Negro |
| | | |
| | concentrated fruit | |
| | pulp, tomato paste, | |
| | sauces, preserved | |
| | fish | |
+----------------+-----------------------+----------------------------+
| # Molto | 1,500 MT/year of | Mendoza |
| | dried vegetables | |
| | | San Juan |
| | 400 MT/day of fresh | |
| | tomatoes | |
| | | |
| | 6 million units of | |
| | processed tomatoes, | |
| | 25 million units of | |
| | fruit cans (on an | |
| | annual basis) | |
| | | |
| | Dehydrated | |
| | vegetables, | |
| | concentrated fruit | |
| | pulp, canned fruits | |
| | and vegetables | |
+----------------+-----------------------+----------------------------+
| Canaille - | Canned fruits, | Mendoza |
| Redcap | tomatoes and other | |
| | vegetables, jams, | Buenos Aires |
| | marmalades | |
+----------------+-----------------------+----------------------------+
| Industrias | Canned fruits and | Catamarca |
| Alimenticias | vegetables | |
| Argentinas/ | | Mendoza |
| ALCO | | |
| | | Buenos Aires |
+----------------+-----------------------+----------------------------+
| Orieta/ | Annual sales: \$10 | |
| | million | |
| Goy Widmer y | | |
| Cía. S.A. | 4,500 MT/year of | |
| | confectionery | |
| | products | |
| | | |
| | Jams, solid jams, | |
| | "dulce de leche", | |
| | raisins | |
+----------------+-----------------------+----------------------------+
| Dánica S.A. | Margarine, | Buenos Aires |
| | mayonnaise, | |
| | | San Luis |
| | sauces, bakery | |
| | products | |
+----------------+-----------------------+----------------------------+
| Bestfoods/ | Ketchup, mayonnaise, | Buenos Aires |
| | sauces, mustard | |
| Unilever | | La Rioja |
+----------------+-----------------------+----------------------------+
CONFECTIONERY PRODUCTS
+----------------+-----------------------+----------------------------+
| # Arcor | Candy, chocolate | Buenos Aires |
| | products, *alfajores* | |
| | (traditional | Córdoba |
| | Argentine cookies) | |
| | | Brasil |
+----------------+-----------------------+----------------------------+
| Cadbury | Candy, chewing gum, | Buenos Aires |
| St | chocolate products, | |
| ani/Terrabusi/ | *alfajores*, cereal | |
| Adams | bars | |
+----------------+-----------------------+----------------------------+
| # Nestlé | Candy, *alfajores*, | Buenos Aires |
| | chocolate products | |
+----------------+-----------------------+----------------------------+
| Bonafide | Candy, chocolate | Buenos Aires |
| | products, chewing gum | |
+----------------+-----------------------+----------------------------+
| Bombonería | Chocolate products, | Buenos Aires |
| Elite S.A | candy | |
+----------------+-----------------------+----------------------------+
| Kraft Food | Chocolate products, | Buenos Aires |
| Argentina S.A | *alfajores*, candy | |
+----------------+-----------------------+----------------------------+
| La Delicia | Candy, cereal bars, | Buenos Aires |
| Felipe Fort | chocolate products | |
| S.A | | |
+----------------+-----------------------+----------------------------+
| Lheritier | Candy, nougats, | Buenos Aires |
| Argentina S.A | cereals bars | |
+----------------+-----------------------+----------------------------+
| Productos Lipo | Candy | Buenos Aires |
| S.A | | |
+----------------+-----------------------+----------------------------+
| Fortunato | Candy, chocolate | Buenos Aires |
| Arrufat | products**,** | |
| | nougats, *alfajores* | |
+----------------+-----------------------+----------------------------+
BAKED GOODS
+----------------+-----------------------+----------------------------+
| # Arcor/Bagley | Crakers, cookies | Buenos Aires |
| | | |
| | | Córdoba |
+----------------+-----------------------+----------------------------+
| Kraft Foods | Crackers, cookies | Buenos Aires |
+----------------+-----------------------+----------------------------+
| La Salteña | Bread, fresh dough | Buenos Aires |
+----------------+-----------------------+----------------------------+
| Bimbo | Bread, cakes | Buenos Aires |
| Argentina | | |
+----------------+-----------------------+----------------------------+
| Fargo | Bread, cakes | Buenos Aires |
+----------------+-----------------------+----------------------------+
BEVERAGES (INCLUDING ALCOHOL)
+----------------+-----------------------+----------------------------+
| # SAVA Gancia | Herbal beverages, | San Luis |
| | liquors | |
| | | Buenos Aires |
+----------------+-----------------------+----------------------------+
| Miscellaneous | Wine, sparkling wine | Mendoza |
| wineries | | |
| | | San Juan |
| | | |
| | | Salta |
| | | |
| | | Catamarca |
| | | |
| | | La Rioja |
| | | |
| | | Río Negro |
+----------------+-----------------------+----------------------------+
| Quilmes, | Beer | Buenos Aires |
| Budweiser, | | |
| Heineken | | Santa Fe |
| | | |
| | | Córdoba |
+----------------+-----------------------+----------------------------+
| Coca Cola | Soft drinks, | |
| | beverages with juices | |
+----------------+-----------------------+----------------------------+
| # Pepsi Cola | Soft drinks, | |
| | beverages with juices | |
+----------------+-----------------------+----------------------------+
| Danone | Mineral water, | Buenos Aires |
| | flavored water | |
| | | Mendoza |
+----------------+-----------------------+----------------------------+
DRIED FOODS AND CONDIMENTS (canned soups, dry mixes, pasta, pet food,
seasonings)
+----------------+-----------------------+----------------------------+
| # Kraft | Dry sweet mixes: | Buenos Aires |
| | cakes, gelatin, | |
| | pudding. | |
| | | |
| | Dry pasta | |
+----------------+-----------------------+----------------------------+
| Bestfood | Soup dry mixes. | Buenos Aires |
| (Unilever) | | |
| | Cube boullions. | |
| | | |
| | Seasoning powder | |
+----------------+-----------------------+----------------------------+
| Molinos Río de | Dry pasta | Buenos Aires |
| la Plata | | |
| | Dry mixes: cakes, | San Luis |
| | gelatin, puddings, | |
| | ice cream, ñoquis, | |
| | cheese bread, soy | |
| | patties. | |
+----------------+-----------------------+----------------------------+
| Nestlé | Pet foods | Buenos Aires |
| | | |
| | Canned soups, dry | |
| | mixes, pasta | |
+----------------+-----------------------+----------------------------+
| Masterfoods | Pet foods | Buenos Aires |
| Argentina Ltd | | |
+----------------+-----------------------+----------------------------+
| La Virginia | Spices, seasonings | Buenos Aires, Santa Fe |
+----------------+-----------------------+----------------------------+
| Alicante | Spices, seasonings | Buenos Aires |
+----------------+-----------------------+----------------------------+
PREPARED MEALS (\"ready to eat\" mixed ingredients; retail, and food
services meals and entrees)
+----------------+-----------------------+----------------------------+
| Industrias | Pizzas | Buenos Aires |
| Alimenticias | | |
| Argentinas | Production: 420,000 | |
| | pizzas/shift | |
| | | |
| | Storage capacity: | |
| | 150,000 units | |
+----------------+-----------------------+----------------------------+
| SAVA - Gancia | *Empanadas* | Buenos Aires |
| | (traditional | |
| | Argentine appetizer), | |
| | | |
| | dried filled pasta | |
+----------------+-----------------------+----------------------------+
| Molinos Río de | Frozen meals | Buenos Aires |
| la Plata | | |
+----------------+-----------------------+----------------------------+
| Bestfood | Soups | Buenos Aires |
| Unilever | | |
+----------------+-----------------------+----------------------------+
| Compañía de | Frozen precooked | Buenos Aires |
| Alimentos | bakery | |
| Fargo | | |
+----------------+-----------------------+----------------------------+
| Corporación | Risotto, tomato paste | Buenos Aires |
| General de | | |
| Alimentos S.A | | |
| | | |
| Grupo Estrella | | |
+----------------+-----------------------+----------------------------+
SPECIALIZED FOOD INGREDIENTS (additives, preservatives, thickeners,
sweeteners)
The following are local manufacturers of food ingredients who account
for the largest share of imported food ingredients in Argentina:
+----------------+----------------------+-----------------------------+
| Saporiti Hnos | Thickeners, | [www.saporiti.com.ar](h |
| | sweeteners, flavors, | ttp://www.saporiti.com.ar/) |
| | stabilizers, | |
| | emulsifiers, colors, | |
| | preservatives, | |
| | cacao, | |
| | | |
| | food ingredients | |
+----------------+----------------------+-----------------------------+
| Gelfix | Thickeners, | [www.gelfix.c |
| | sweeteners, flavors, | om](http://www.gelfix.com/) |
| | stabilizers, | |
| | emulsifiers, colors, | |
| | preservatives, | |
| | cacao, dried fruits, | |
+----------------+----------------------+-----------------------------+
| Granotec | Emulsifiers, | [www.granotec.com |
| Alimentos | antioxidants, | ](http://www.granotec.com/) |
| | stabilizers, | |
| | hydrocolloids, | |
| | preservatives, | |
| | sweeteners, | |
| | proteins, enzymes, | |
| | food ingredients. | |
+----------------+----------------------+-----------------------------+
| Farmesa | Stabilizers, | [www.farmesa.com.ar]( |
| | emulsifiers, | http://www.farmesa.com.ar/) |
| | flavors, salts for | |
| | meat products, soy | |
| | protein, food | |
| | ingredients, natural | |
| | colors, | |
+----------------+----------------------+-----------------------------+
| El Bahiense | Stabilizers, | [www.elbahiense.com]( |
| | emulsifiers, | http://www.elbahiense.com/) |
| | preservatives, | |
| | cacao, wheat gluten, | |
| | dextrins, food | |
| | ingredients. | |
+----------------+----------------------+-----------------------------+
| O.V specias | Functional | [www.ovespecias.com.ar](htt |
| | ingredients, | p://www.ovespecias.com.ar/) |
| | emulsifiers | |
+----------------+----------------------+-----------------------------+
| Adama Food | Citrates, citric | [www.adama. |
| Ingredients | acid, enzymes, | com](http://www.adama.com/) |
| | lactates, milk | |
| | proteins, whey | |
| | proteins, soy | |
| | proteins, food | |
| | ingredients. | |
+----------------+----------------------+-----------------------------+
| Cordis | Functional | [www.cordis.com.ar] |
| | ingredients, | (http://www.cordis.com.ar/) |
| | preservatives, | |
| | emulsifiers, | |
| | proteins, cacao, | |
| | stabilizers | |
+----------------+----------------------+-----------------------------+
| Alpha | Emulsifiers, ice | |
| emulsionantes | cream ingredients | |
+----------------+----------------------+-----------------------------+
| Duas Rodas | Ice cream additives; | [www.duasrodas.com] |
| Industrial | condiments, food | (http://www.duasrodas.com/) |
| | ingredients | |
+----------------+----------------------+-----------------------------+
| Alvarez Hnos | Spices, seasonings | <Al |
| | tailor made. | cala_general@ciudad.com.ar> |
+----------------+----------------------+-----------------------------+
| Siviar | Vegetal concentrates | [www.siviar.com.ar] |
| | for beverages and | (http://www.siviar.com.ar/) |
| | soft drink emulsions | |
+----------------+----------------------+-----------------------------+
| Taxonera | Food ingredients for | [www.taxonera.com |
| S.C.A. | bakery, ice cream | ](http://www.taxonera.com/) |
| | and pastry | |
+----------------+----------------------+-----------------------------+
## E. Sector Trends
Argentina is a primary food producing country. Its diverse geography and
various climates allow it to produce a wide variety of food products, of
which many are exported throughout the world.
## Basic Foods
Argentina produces the following foods with little or no processing:
- Of vegetable origin: grains and oilseeds in large volumes (large oil
processing capacity), and fruits, vegetables, aromatic herbs,
spices, olives, etc.
- Of animal origin: primarily, bovine, ovine, and caprine meat, and
poultry. In addition, some specialty products for which there is an
increasing international demand for gourmet markets, such as snail,
frog, iguana, and llama meat. The local dairy sector is large and
very competitive.
These two groups of food products follow the trends listed below:
- Specialized products (name of origin)
- Safe products, produced under traceability standards
- Organic products (olive oil, herbs, etc.)
- Regional products (Andean potatoes, amaranth, chia, etc.)
## Processed Foods
The following trends have been noticed in processed foods:
- Healthy products
- Sugar-free products, or with a low content of sugar
- Low-fat/calorie foods
- Consumer-ready foods
- Low-cost foods.
##
##
##
##
## General Trends in the Food and Beverage Industry
The growth of the Argentine food manufacturing industry has focused on
export competitive expansion and on the development of novelty products.
The following are the most important trends in this sector:
- Consolidation of medium and small-sized companies, which produce
regional specialty foods in smaller volumes but with a higher value,
such as: marmalades, preserves, dried fruits and nuts, olive oil,
pickles, specialty meats, etc. Many of these undertakings are
connected with tourism "roads", such as the "wine road", the "olive
road", among others, which tourists can visit. They can also
participate in the harvest process.
- Launching of functional foods, such as fiber, omega 3 and
phytosterol-added milk (all imported food ingredients). The recent
interest in these types of products follows a growing international
trend.
- Beverage diversification: flavored beverages, such as water with
herb extracts, have become very popular to the detriment of
conventional soft drinks. Demand for imported energy drinks has
increased considerably.
- Larger beer supply, with new microbrewery beers and increased
consumption of conventional beer.
- High-quality varietal and sparkling wines, which meet international
quality standards.
- Permanent launching of novelty dairy by-products, such as cheese and
yogurt, to supply both the domestic and export markets.
- Expansion of herb infusions as a healthy option. Raw materials for
their production are both local and imported.
- Increased production of commodities such as oils, grains, meat and
dairy products, as a consequence of export expansion.
- AF&BI´s focus on the industrialization of commodities as a means of
increasing income, which will demand food ingredients that are not
produced locally, either at the present time or in the near future,
because of limited volumes needed (artificial sweeteners, special
thickeners and stabilizers, nutritional ingredients).
- Expansion of facilities to other regions, primarily, South America
and, in some cases, to countries such as Ukraine and China, by some
multinational companies.
- Interest of the Argentine confectionery industry in markets in
Central America and the United States, among others.
- The baking industry is growing and developing novelty products.
# SECTION III. COMPETITION
- Food ingredients used in the AF&BI are primarily manufactured
locally. Those that are unavailable in the local market are
imported, such as cocoa from Brazil. Specialty food ingredients are
imported mainly from the United States, Europe, and China. Products
from Europe are less competitive due to the high-value of the euro
compared to the dollar.
#
#
# SECTION IV. BEST PRODUCT PROSPECTS
Best prospects for imported food ingredients are in the following food
industries:
- Bakery
- Confectionery
- Condiments, seasonings, and spices
- Dairy
- Non-alcoholic beverages
- Snack foods
- Dry/dehydrated products
- Consumer-ready foods
- Sauces
# SECTION V. USEFUL WEBSITES
[www.cipa.org.ar](http://www.cipa.org.ar/) Cámara de Industriales de
Productos Alimenticios
(Food Industry Chamber)
> Provides information on food processors.
[www.copal.com.ar](http://www.copal.com.ar/) Coordinadora de las
Industrias de Productos Alimenticios
(Food Industry Coordinating Agency)
> Provides information on F&B processors, and their chambers.
[www.alimentosargentinos.gov.ar](http://www.alimentosargentinos.gov.ar/)
Dirección Nacional de Alimentos, Secretaría de Agricultura, Ganadería,
Pesca y Alimentos
(National Food Division, Secretariat of Agriculture,
Livestock, Fisheries, and Food)
> Provides official F&B import, export, and production statistics, and
> regulations.
[www.cil.org.ar](http://www.cil.org.ar/) Centro de la Industria Lechera
(Dairy Industry Chamber)
Provides dairy statistics.
[www.cafgda.com.ar](http://www.cafgda.com.ar/) Cámara de Fructosa,
Almidones, Glucosas, Derivados y Afines
> (Chamber of Fructose, Starches, Glucose, and By-Products)
>
> Provides statistics and company contact information.
[www.anmat.gov.ar](http://www.anmat.gov.ar/) Administración Nacional de
Medicamentos, Alimentos y Tecnología Médica
> (National Administration of Drugs, Food, and Medical Technology)
>
> Regulates processed food products which are prepared for direct human
> consumption, health supplements, and both alcoholic and non-alcoholic
> beverages, with the exception of wine)
# SECTION VI. POST CONTACT AND ADDITIONAL INFORMATION
Office of Agricultural Affairs
U.S. Embassy, Buenos Aires
Avda. Colombia 4300
C1425GMN Buenos Aires, Argentina
Phone: 54-11-5777-4844
Fax: 54-11-5777-4216
E-mail: <agbuenosaires@usda.gov>
Homepage: [http://www.fas.usda.gov](http://www.fas.usda.gov/)
# ANNEX I. MAIN FOOD INGREDIENT IMPORTS 2004
-------- ---------------------------------- ----------- ------------ -----------
**HTS **Product Description** **MT** **Thousand **\$/MT**
Code** \$ FOB**
0201 Meat of bovine animals, fresh or 1,702.80 1,415.49 831.27
chilled
0203 Meat of swine, fresh, chilled or 11,724.67 19,341.38 1,649.63
frozen
0209 Pig fat, free of lean meat, and 4,820.97 2,631.82 545.91
poultry fat, not rendered
0401 Milk and cream, not concentrated 22,006.64 3,564.48 161.97
nor containing added sugar or
other sweetening
0713 Dried leguminous vegetables, split 4,790.51 2,158.16 450.51
1006 Rice 4,674.74 1,475.62 315.66
1108 Starches; inulin 3,067.28 1,491.13 486.14
1502 Fats of bovine animals, sheep or 12,003.77 4,460.02 371.55
goats
1513 Coconut, palm kernel, and almond 2,606.32 2,027.88 778.06
oil, and fractions
1516 Vegetable fats and oils and their 3,540.35 3,632.93 1,026.15
fractions, partly or wholly
hydrogenated
1517 Margarine, edible mixtures or 1,908.90 2,657.42 1,392.12
preparations of animal or
vegetable fats or oils
1604 Prepared or preserved fish; caviar 5,466.43 7,131.73 1,304.64
and caviar substitutes prepared
from fish eggs
1701 Cane or beet sugar and chemically 4,935.41 944.46 191.36
pure sucrose, in solid form
1702 Other sugars, including chemically 1,688.18 1,611.92 954.83
pure in solid form; sugar syrup
not containing flavorings or
colors
1704 Sugar confectionery, not 4,475.30 6,758.04 1,510.07
containing cocoa
1803 Cocoa paste, whether or not 4,244.51 9,237.34 2,176.31
defatted
1804 Cocoa butter, fat, and oil 3,640.54 11,181.23 3,071.31
1805 Cocoa powder, not containing added 4,409.26 7,659.92 1,737.23
sugar or other sweetening matter
1806 Chocolate and other food 3,315.16 7,964.04 2,402.31
preparations containing cocoa
1905 Bread, pastry, cakes, biscuits, 2,133.69 2,538.88 1,189.90
and other bakers´ wares, whether
or not containing cocoa
2002 Tomatoes, prepared or preserved 2,736.67 1,471.99 537.88
2005 Other vegetables and leguminous 2,551.37 1,639.90 642.75
vegetables, prepared or preserved,
not frozen
2008 Fruit that have been prepared of 7,209.21 7,647.79 1,060.84
preserved by freezing, by packing
(including containing added sugar,
other sweetening, or alcohol)
2009 Fruit juice not fermented, and not 3,350.74 2,563.93 765.18
containing alcohol, with added
sugar or other sweetening
2101 Extracts, essences and 2,054.73 6,345.72 3,088.35
concentrates of coffee, tea or
mate, and preparations with these
products
2102 Yeasts, prepared baking powders 1,849.17 2,815.51 1,522.58
2106 Food preparations not elsewhere 3,869.88 14,732.67 3,807.01
specified or included
2202 Waters, including mineral waters, 2,903.20 1,505.40 518.53
aerated waters, flavored waters,
and other non-alcoholic beverages,
containing added sugar or other
sweetening
2208 Undenatured ethyl alcohol of an 2,601.16 5,637.11 2,167.16
alcoholic strengh by volume of
less than 80%, brandy, liquor, and
other spirits
2302 Residues of cereals and leguminous 7,637.36 227.52 29.79
plants
-------- ---------------------------------- ----------- ------------ -----------
Source: Dirección Nacional de Alimentos (National Food Division), SAGPyA
# ANNEX II. ORIGIN OF FOOD INGREDIENTS USED IN THE ARGENTINE MARKET
--------------- ---------------------------- ---------------- --------------
**Product **Product name** **Manufactured **Imported**
category** locally**
Acids Oleic acid X
Steric acid X
Albumins Albuminal substances X X
Egg albumin X
Extracts Coffee extract X
Fish extract X
Meat extract X X
Tea extract X
Herb extracts X
Starches Corn starch X X
Potato starch X
Wheat starch X
Fruits Dehydrated fruits X
Dried fruits X
Nuts X X
Miscellaneous Casein X
Chocolate X
Cocoa powder X
Condiments X X
Dextrins X X
Essential oils X X
Food supplements X X
Fructose X X
Fruit pulp X
Gelatin X
Ginseng X
Glucose X X
Glues X
Herbs X X
Lactose X
Milk powder X
Milk substitutes X
Pectic substances X
Potato flakes X X
Protein concentrates X X
Protein isolates X X
Spices X X
Sugar substitutes X
(sweeteners)
Vanilla X X
Wheat gluten X
Whey X X
Yeast X X
--------------- ---------------------------- ---------------- --------------
Source: Data provided by private sources.
| en |
converted_docs | 124200 | **Discussion forum for strategies of simulation data.**
Discusssion about representativeness error in November and presentation
by Ron Errico and other materials are posted at
<http://www.emc.ncep.noaa.gov/research/osse/NR/RepE/>
Summary of discussion forum
<http://www.emc.ncep.noaa.gov/research/osse/NR/RepE/RepE.Jun06-061116.doc>
Note by Ad Stoffelen and Gert-Jan
<http://www.emc.ncep.noaa.gov/research/osse/NR/RepE/Stoffelen.representation3.061116.pdf>
Presentation by Ron Errico
<http://www.emc.ncep.noaa.gov/research/osse/NR/RepE/Errico.reperror.061116.ppt>
Paper by Andrew Lorenc
<http://www.emc.ncep.noaa.gov/research/osse/NR/RepE/Lorenc.1992.TIDCCR4129.pdf>
References
<http://www.emc.ncep.noaa.gov/research/JointOSSEs/references/references.html>
Presentation by Ron Errico about simulation of Radiance
<http://www.emc.ncep.noaa.gov/research/osse/NR/Jun07/RADIATION/Errico_cloudtalk_fnl_070622.x.ppt>
Discussion forum is updated at
<http://www.emc.ncep.noaa.gov/research/JointOSSEs/forums/index.forums.html>
**\[On 2/21/07 Ad Stoffelen wrote\]**
I note your forthcoming discussion on simulating clouds for DWLs and
wonder how this relates to earlier work. For simulating ADM-Aeolus DWL
data in LIPAS we used ECMWF cloud properties and the ECMWF cloud overlap
model to simulate the probability that a laser shot hits a cloud at any
level. The simulated cloud hit probabilities are verified to be 1similar
to space lidar cloud hit rates. See the LIPAS publication in the QJRMS.
The approach may be used for other DWLs and sounders as well with some
care. We would use it again in our forthcoming DWL simulations. We would
be happy to be informed further and contribute to the discussion on this
topic.
Best regards,
Ad
**\[Dave Emmitt responded 2/21/07\]**
Steve and I have just finished looking at 7 days of the 1 x 1 degree
Nature Run. The average total cloud coverage (using ECMWF\'s overlap
functions) appears to be \~ 70%. This is less than the \~75 -80% we see
with GLAS based upon 1.25 km line integrations. We expect that the
difference is primarily in the cirrus\...particularly the Tropics. More
on that later. Last month we simulated GLAS observations using the T213
nature run (with adjusted clouds) and found results that would produce
significant understatements of coherent shots getting into the boundary
layer and overstatements of cloud free integration intervals for the
direct detection. We are getting ready (all without funding of course)
to simulate CALIPSO in the New Nature Run. Since we are using the 1 x 1
degree set, we will avoid any conclusions until we repeat the experiment
with the full resolution NR.
Lars Peter, Oreste Reales, Joe Terry, Steve Greco and I had a meeting at
GSFC on February 1 and began making plans for assessing the new Nature
Run Clouds. For the lidars we must feel comfortable with the subgrid
scale representation of penetrability. The fact that AIRS found only 4%
cloud free scenes is also noteworthy. I am focusing upon the Tropics so
if anyone wants to focus upon the extratropics and the poles, please let
me (us) know. It\'s a lot of work.
**\[Steve Greco produced the initial summary 2/22/07\]**
Partial summary of cloud statistics\* from 7 days (June 1 -- 7) of NR (1
X 1)
------------ ----------- ------------ ----------- ---------- -----------
Region Low Middle High Total Cloud Free
Global 40 31 33 78 4
Tropics 60 12 38 52 6
NML 37 28 36 64 7
SML 53 39 33 79 1
------------ ----------- ------------ ----------- ---------- -----------
\* Using ECMWF satellite view overlap algorithm
A diagram for distribution of cloud cover is posted at
http://www.emc.ncep.noaa.gov/research/osse/NR/Feb07/SWA_T511_cloud.ppt
**\[Michiko posted Cloud data 2/21/07\]**
Ken Campana has RTN cloud reported every hour at 1 degx1deg (64bits
real) for HCC, MCC, LCC, TCC, BCC. He has CLAVRX data reported every 6
hours at 0.5 deg x 0.5deg in grib code for TCC, HCC, MCC, LCC.
Posted at
<ftp://ftp.emc.ncep.noaa.gov/exper/mmasutani/cloud/RTN>
size 150MB per month
Jun 05 is missing.
CLAVRX data for 6 hourly 0.5 degx0.5deg grib code
TCC,HCC,MCC,LCC
Posted at
<ftp://ftp.emc.ncep.noaa.gov/exper/mmasutani/cloud/CLAVRX>
**\[Some questions after meeting on Feb 22^nd^\]**
**Gert-Jan Marseille**
If T799 nature run is produced for every 1 hour no time interpolation
between archived fields is required and observations may be simulated at
1-hour resolution.\
Is this the strategy shared by the whole observation simulation group ?
**Jack Woollen**
We could adjust observational error so that we can use existing back
ground error covariance.
Michiko suggested that we should use same RTM for simulation and
assimilation to start and make sure all other problem such as cloud
problems are cleared.
In the meeting at NCEP with Jack, Yucheng, Yuanfu and Michiko discussed
that identical (fraternal) twin OSSE may be useful identify the real
problems. There are so many negative impact for very good data.
**\[Ad Stoffelen wrote on 3/6/07\]**
To those concerned,
Gert-Jan Marseille pointed me to some issues on spatial
representativeness in the document provided by Tom Schlatter.
1\) The issues of simulation of observations from the nature run and
assimilation of the simulated observations appear not clearly separated.
This is, why is x introduced in section 2.3? x_t is the nature run and
is needed to simulate the observations. x is another NWP model\'s
representation of x_t (x_t remains the reference state), but only
relevant at the stage of assimilation of simulated observations, which
stage is documented later on.
2\) Under the heading \"Application to OSSEs\" it reads \"After the
forward model is applied to the gridpoint values of the nature run, we
have an \'observation\' that contains representativeness error
(precisely as defined above) but no instrument error.\". Ealier it reads
H(x_t) = y_t + e_r which I would put rather as y_t = H(x_t)+ e_r . So,
\"after the forward model is applied to the gridpoint values of the
nature run, i.e. H(x_t), we have an \'observation\' y_t that still lacks
representativeness error e_r\". The representativeness error e_r is the
true atmospheric variance not present in x_t (since truncated) and
therefore lacking in the projection to y_t. After this variance has been
added as a random contribution to the forward model, an observation with
realistic variance appears.
In summary, both x_t and y_t are drawn from an assumed truth. Where x_t
and y_t collocate, the truncated x_t can be extended by assuming some
random local variance resolved by y_t but not by x_t. The same mechanism
may be applied when y_t is sensitive to variables not available in x_t:
the expected variance in y_t due to these variables should be added to
H(x).
3\) Grid cell volume or spectral truncation is explicitly mentioned as
the reference atmospheric cell size. In practise, as is documented in
our note on spatial representativeness, NWP models do not describe
atmospheric variance down to these scales realistically. The
determination of the truncated spatial variance spectrum in the nature
run for the relevant meteo variables should be well established for a
realistic simulation of representativeness errors.
We hope these points can be clarified.
Best regards,
***[\[Andrew Heidinger 070411\]]{.underline}***
I am sorry but I am at an NPOESS meeting on April 12. Thanks for
including me in this group and I am happy to participate in future
discussions.\
\
In addition to the data that Ken Campana hosts, we also have hdf data
and images available at
[[http://cimss.ssec.wisc.edu/clavr]{.underline}](http://cimss.ssec.wisc.edu/clavr)\
\
We are also happy to provide reprocessed results as well for any
specific time since 1982. Lastly, the GEWEX cloud climatology
assessment workshop report is being finished and that report contains
analysis of several cloud climatologies that might be of interest. I
can provide that report if there is interest. It provides a nice sense
of the relative differences and similarities between the different data
sets.\
\
thanks,\
\
Andy Heidinger
***[Michiko Masutani 070424]{.underline}***
Initial Condition for OSSE
Jack has simulated conventional data and we are working on assimilating
data. One of the problems is to get appropriate initial condition.
Another one is constant fields.
1\) Start data assimilation from 12Z May 1st.
We agreed to start working on August 2005, however, making initial
condition for August is not a trivial matter. We could make initial
condition from NR but that will be a significant project itself.
For the nature run 12Z May 1st is analysis fields which can be compared
to any other analysis fields and real observation. Simulated observation
at 12Z May 1st can be verified against real observation to check the
simulation procedure. Simulated observation at 12Z May 1st should be
able to be assimilated with initial condition taken from operational
archive.
Jack is simulating conventional observation for May, June, July as well
as August 2005. So we can start data assimilation from 12Z May 1st to
reach August 2005. In August 2005 we can add other simulated data.
2\) SST, and ICE
Daily SST and ICE processed by NCEP is used for the Nature run. I need
confirmation from Erik. So in our data assimilation we can use NCEP SST
and ICE.
3\) Other constant fields
I wonder there are more constant fields required to simulate
observation. ECMWF agreed to provide any data required. There must be
some climatology fields used to generate nature run.
***[Yuanfu Xie 070524]{.underline}***
<http://www.emc.ncep.noaa.gov/research/osse/NR/May07/YXie.OSSErun.yy.ppt>
Yuanfu Xie summarized an experiment that assimilated perfect
\"conventional\" data\
extracted from the ECMWF T511 Nature Run into a low-resolution version
of the GFS\
using the GSI analysis package. The simulation experiment ran for one
week beginning\
on 1 May 2005. The analyses indicate that the simulated conventional
obs are behaving\
as expected in the assimialtion cycle.
We notice wind fields are much closer to NR than temperature. Jack said
SATWIND is included in his data. This include SSMI wind and Quick scat
wind.
***[Jack Woollen and Daryl Kleist 070524]{.underline}***
**\[Temperature in prepbufr \]** (Jack and Daryl)
Jack and Daryl explained the historical reason for using virtual
temperature as input for the DA program. In prepbufr dry (sensible)
temperature is saved. However, GSI expects virtual temperature for RAOB
data, but the simulated data for OSSE will keep dry temperature as an
input to GSI. There is a flag TPC to indicate if the temperature is
virtual (TPC=0) or sensible (TPC=1).
The DA program was not handling dry temperature in RAOB correctly, Daryl
and Jack fixed the program and made it more flexible. The new
read_prepbufr.f90 is posted at
<http://www.emc.ncep.noaa.gov/research/JointOSSEs/NR/May07/read_prepbufr.f90>
***[Yoshiaki Sato 070525]{.underline}***
I think it needs to define what is the conventional data, especially for
AMV. AMV is very classic data and many people mention it is
\"conventional data\". Satellite retrieved wind data shares the
characteristics with the other satellite data: \# data distribution,
spatial error correlation, etc. Therefore, satellite data (i.e., SSMI
winds & Scatterometer winds) must not be included in conventional data.\
\
And this is my request: when we talk about MODIS data, please call it
\"MODIS-winds\".\
Because MODIS is sensor name and there are many products from the MODIS
sensor.
***[Michiko Masutani 070525]{.underline}***
In the meeting \"Conventional data\" was used for data simulated by Jack
which is used for the initial test. We should use another name like
\"prepbufr\" for ADPUPA ADPSFC SATWIND AIRCAR AIRCFT SFCSHP
Which data to be included in initial test is another issue. The
presentation by Yuanfu shows there is some unbalance between temperature
data and wind data. SATWIND must be reprocessed using NR cloud.
***[\[ Ron Errico \]]{.underline}*** 6/4/07
Regarding validation of clouds in the nature run.\
\
One of the issues regarding clouds in the nature run concerns how
cloud-affected, satellite observation locations are to be specified.
Since we must settle on this before we can create such observations and
proceed with a control (current obs suite) assimilation, it is important
that we appropriately examine the model NR clouds.\
\
In the previous NCEP OSSE using an earlier T213L31 ECMWF model for the
NR, the locations of cloud cleared radiances were defined as the
locations of cloud cleared radiances obtained for a corresponding real
assimilation. So, some (likely many) cloud cleared radiances were
simulated at locations that were actually cloud covered in the NR.
Similarly, cloud track winds were simulated in regions where the NR was
cloud free. In this way, the observation locations were very easy to
specify and the numbers of cloud cleared and QC accepted observations
were identical in the OSSE and corresponding real analysis. Also, the
clouds in this old NR were presumably much less realistic than those
produced now.\
\
The above technique may introduce unrealism if the impacts of
observations in cloud free and cloudy regions are significantly
different. For example, clouds tend to occur in dynamically active
regions where \"things are happening\" and where magnitudes of model
errors (e.g., due to imperfect modeling of diabatic heating/cooling
associated with precipitation or turbulence) are likely large. If in
real assimilation systems some instruments observe these active and
error-prone regions more poorly, then it may be important that the OSSE
observations simulate the same selectivity. The questions then are:\
\
(1) For each observation type, what characteristics of the clouds are
important for defining whether a simulated observation should be
specified as being useful at each location?\
\
(2) How can the critical characteristics determined for (1) be specified
from the cloud field data provided by the NR?\
\
(3) Are these characteristics sufficiently well simulated by the NR that
we can specify the locations of useful (e.g., cloud-cleared)
observations using the NR data and, for each data type, obtain both
distributions and counts of usable observations that are realistic.\
\
For the purpose of deciding how (i.e., where) to simulate satellite
observations of wind or radiances it is neither sufficient nor necessary
to validate monthly mean cloud fields produced in the NR (although such
statistics may be relevant for other interests). Instead, the specific
application must be considered, principally by first answering (1) and
(2). At this stage, although (1) should be answered fairly completely,
the answers to (2) likely must be simplistic. Our goal should be to be
significantly more realistic than in the previous OSSE, although we may
need to be satisfied with much less sophisticated techniques than we
could develop over a much longer time period. Perhaps the earlier
technique for defining locations will prove best (I hope not!), but we
should not abandon serching for a better technique too quickly.\
\
Who has the experitse and commitment to perform this investigation?\
With whom will they be consulting?
***[\[Michiko\]]{.underline}*** 6/5/07
Please find attached comments from Ron Errico regarding NR cloud. Please
note T799 NR is not a cloud resolving model, yet. Global cloud resolving
model is yet to come. We should discuss what we can do with NR we have.
Then later on we will discuss requirement for the next NR possibly a
global cloud resolving model.
***Dave Parsons 6/5/07***
Ron raises a good point about how using the model cloud fields in the
OSSEs due to the potential displacement of both sensitive areas and
cloud fields between the atmospheric measurements and the model. Some
comments on points (1) -- (3).
1. The important characteristic of the cloud field for lidar sampling
from space would be its optical depth.
2. First one would need to convert the model mixing ratios, particle
types etc to optical depth or cloud extinction. Taking the model
hydrometer fields and determining whether you can get good lidar
data at and below this level should be fairly straight forward in
optically thick clouds and clear air. You will need to assume some
threshold that would reject these thick clouds and allow high
quality data in those thin cirrus and other optically thin cases.
What you really need is a lidar sampling model and some assumptions
about the pulse energy, frequency, pulse repetition rate and other
lidar characterisitics (e.g., direct detection or heterodyne). I
think that these issues will impact the quality and resolution of
the data as a function of height even in clear air. Lidar instrument
designers spend a lot of time on such models to determine the
interplay between lidar design and the resulting data quality,
vertical and horizontal resolution and vertical coverage. These
lidar models are often publishable work in themselves. One example
of the detail necessary is the Marseille and Stoffelen QJR 2003
article. Much of what you are asking about is in the cloud
extinction equations 5 and 6 in that article.
3. I am not the best person to answer that question, but the Marseille
and Stoffelen paper goes part way to addressing that issue.
On the question of who and how this would be done, I would try to push
you towards an established lidar model such as was used for ADM-AEOLUS
or the lidar work at NASA and NOAA. If you are interested in working
within NOAA, Mike Hardesty would be a good start. Lars in on the email
list so he would be a better person to give you the NASA contacts.
**\[ David Emmitt\] 6/5/07**
Appreciate the discussion prior to the meeting on Thursday. We will post
our ppt tomorrow via Michiko. Our main concern, from the lidar
simulation perspective, is to insure that the model clouds have
reasonable global statistics and are properly collocated with the
atmospheric dynamics. The clouds offer both wind observation
opportunities (lidars and CMVs) as well as obscuration of the total
column. A second concern is that the simulations of passive imagers and
sounders are affected by the same clouds affecting the active optical
sensors.
In the meantime, for the question regarding simulation of space-based
lidar observations from Nature Runs I refer you to the following web
site:
[[http://www.swa.com/laser/index.html]{.underline}](http://www.swa.com/laser/index.html).
As the main page states:
Since 1983, NASA, NOAA, U.S. DoD, CNRS, Lockheed, General Electric, and
Northrop Grumman have funded the development and application of the DLSM
(Doppler Lidar Simulation Model) for space-based and airborne Doppler
lidar wind measuring systems. The DLSM has been used extensively with
the T106, T213 and the NASA FVM Nature Runs.
A list of papers and presentations regarding the DLSM and OSSEs is
available.
Dave
G. D.
**\[ Tom Schlatter \] 6/5/07**
I think Ron\'s comments are right on the mark about how we
should treat clouds, I think his questions 1 thru 3 are the right
questions
to ask..
**\[Erik Andersson\] 6/6/07**
The discussion is about simulation of the yield and accuracy of lidar
doppler-wind-lidar data. Dave Parsons suggested the lidar model of
Marseille and Stoffelen QJR 2003 as a reference.\
\
In the paper by Tan and Andersson 2003 QJR we used the Marseille and
Stoffelen lidar model and ECMWF clouds to assess the yield and accuracy
of future ADM-Aeolus winds. We showed expected accuracy of the profile
wind data in different regions of the world and globally, as a function
of cloud conditions (assuming climatological aerosol profile).\
\
This may or may not be satisfactory for the OSSE simulations. At least
it is an example of what can be done, and what is involved.\
\
The full reference is:\
\
Tan D.G.H. and E. Andersson, 2005: Simulation of the yield and accuracy
of wind profile measurements from the Atmospheric Dynamics Mission
(ADM-Aeolus). QJRMS, 131, 1737-1757.\
\
Also available from
[[www.ecmwf.int/publications/library]{.underline}](http://www.ecmwf.int/publications/library)
as Technical Memorandum 431.\
\
Regards, Erik
<http://www.ecmwf.int/publications/library/ecpublications/_pdf/tm/401-500/tm431.pdf>
**\[Ad Stoffelen\]**6/7/07
Gert-Jan and me will not be in the opportunity to join you this
afternoon (morning for you), but I could provide some more information
on our cloud model in LIPAS. If similar cloud modelling will be
attempted for other observation types I am happy to review the
suggestions and provide constructive comments. Some first thoughts
below.
In LIPAS we treat NR cloud cover and cloud ice water as statistical
parameters valid for \~100-km boxes in the ECMWF model. Realism of ECMWF
statistical clouds has been studied in several ways:
1\) By ECMWF in \'94
2\) By you
3\) By Beljaars et al comparing with LITE accumulated equivalent
statistical parameters.
4\) By comparing AVHRR and MeteoSat clouds with ECMWF clouds (I can dig
up a reference if you want).
Conclusion is that clouds appear in places coherent with the dynamics
and in about the right amount generally. Some problem areas are noted:
in some tropical regions, over subtropical ocean (PBL). Perhaps in
arctic regions, but here satellite data are not reliable to distinguish
low cloud from snow. We noted these problems, but did not consider them
limiting for a DWL OSSE.
Given mean cloud cover and ice content on all vertical layers in a 50-km
Aeolus observation, we use cloud cover at each layer as a probability of
cloud and draw a cloud profile for each laser shot. We take into account
the assumption of maximum cloud overlap, i.e., clouds on a next lower
level first occur below clouds on a higher level and, second, randonly
in other places. We do not assume any horizontal structure, but this
really not necessary, i.e., we can in principle rearrange the individual
shot profiles into any horizontal structure without changing the
simulated information concent in a 50-km observation. LIPAS statistics
of cloud obstruction on different levels, cloud opacity and ground
visibility compare statistically well with results from LITE and more
recently CALYPSO. Dave Emmit was the first to statistically evaluate
atmospheric lidar returns in cloudy atmospheres.
In particular cases clouds do generally compare less well, since the
correlation radius of a cloud is generally only a few 100m. In the OSSE
we are not concerned with this, but mainly with the statistical
representation and realistic co-occurence of clouds and dynamical
structures. In this light Gert-Jan and me investigated the observability
of strong wind shear with LIPAS. We found no tendency with the ocurrence
of clouds or not, in line with a series of real case studies by Lorenc,
Graham et al in \'92. Such issue could now be further studied by CALYPSO
data collocated with NWP (if you believe this is important).
If a similar method needs to be applied for (subgrid) radiance
measurements, which I recommend and appears feasible to me in principle,
I note the following
\- cloud cover depends strongly on whether you look straight up or just
over the horizon, with straight up the least cloud. In communication
this has been studied extensively. Depending on general cloud cover, the
effective increase in cloud cover for ADM-Aeolus (38 degrees incidence
angle) is up to 10-15% if I recall well (we neglected this). However,
for medium cloud cover, this goes up really fast for higher incidences
(as used by radiometers). Such issue could now be studied by CALYPSO
data (along track), and perhaps, more practically, by analysing angle
dependency of cloud masking for radiometers. I\'m not sure the latter
has been done?
\- irradiance is not isotropic in a broken cloud atmosphere, certainly
not if sun lit. I\'m not sure about bias or other error effects or how
this should be estimated from existing (ir)radiance measurements?
There are undoubtedly aspects I do not mention above that may need
further consideration. There will be a compromise between available
resources and sophistication of simulation, so I recommend a careful
planning here.
Comments or elaborations on the above are most welcome. I hope you will
have a fruitful teleconference.
Best regards,
Ad
**\[ Ronald Errico \]\
**My points are about the current suite of satellite radiance
simulations. My concern is first that we get a good control OSSE. I
was not thinking of future instruments at all.
**\[Erik Andersson \]**
OK, I fully agree with your comments. The spin-off discussion became
rather lidar-specific\...\
The radiance data should (also) be simulated with respect to the NR
clouds. The OSSE must not pour clear-sky radiances into the cyclone
centres. That would exaggerate their apparent impact.\
\
Erik
***[Ron Errico 070606]{.underline}***
My concern is about the simulation of the current observations, not
about future observations. We first need a control OSSE and that is what
we can validate. We all need the control.
**\[ Tom Schlatter \] 070607**
In recent years sophisticated sensors indicate that there may be more
thin cirrus clouds (some of them hardly perceptible to the eye) at high
altitudes than has previously been supposed. It is probable that our
best global models do not predict these thin, high clouds.
When we simulate various observing systems, it is appropriate to ask
whether the measurements they take are sensitive to the presence of thin
cirrus. For observing systems supplying data to current assimilation
and prediction systems, we can compare the observed and background
values, the latter arising from the application of a forward model. If
these two values match well, and if the model doesn\'t predict the high
thin clouds nor does the observing system sense them, then we can be
confident that the forward model is adequate. In other words, there
is no problem. We should confirm with observing system specialists when
this is the case.\
\
On the other hand, if the obs-minus-background differences are
alarmingly large, we suspect either that the observing system is
sensing something outside the \"purview\" of the assimilating model or
that the forward model is faulty. One or the other has to be fixed
before this type of observation can be effectively assimilated.\
\
In dealing with a FUTURE observing system, lab experiments and
instrument engineers need to tell us whether the system will be
sensitive to thin cirrus clouds. If a Doppler Wind Lidar IS sensitive
to thin cirrus (in the sense that it will not be able to extract
line-of-sight winds from as deep in the atmosphere as would be possible
if there were no high clouds), then we need to alter the forward model
accordingly. I agree with Dave Emmitt that we should not alter the
nature run output but rather should perform a post-processing step that
infers thin high clouds\
from the information already present in the nature run.\
\
Tom
***[Ron Errico 070607]{.underline}***
The very first thing that we must do is talk with the people who know
how each of the sat radiance instruments is used in terms of data
selection criteria. For example, if cloud problems are detected for
some sounding, are channels weighting about the detectd clouds still
used, or are all the channels discarded. Knowing things like this an
help us focus.\
\
I would like to get a list of these criteria for each instrument before
the meeting so that I have time to think about the implications. At the
meeting it is important that we begin by reviewing why this may be
critical (We are still not in agreement on this, and that makes
discussion difficult.), what the questions are and how they can be
answered. Also, a collection of straw man techniques should be
described. Also, a talk about the GSI obs selection criteria should be
presented.
***[Ron Errico 070608]{.underline}***
These multiple-people email \"discussions\" are a problem. For example,
earlier in the week i wrote my short piece explaining the cloud
validation required for the nature run. Then all these people whom i did
not know were even part of our group added items about DWL. Next I get
an email from Erik saying something about my item, interpreting it as
regarding DWL, which it was not. So, I sent him a note telling him my
concern about the current IR instruments, and then he understood. So, it
is easy for things to get confused.
***[Ron Errico 070608]{.underline}***
I looked at our validation of your high-resol OSSE with no sat
radiances, and the rms analysis increments match very well with the real
assim, a much better match than when you included sat rads. So, I think
that is good reason to at least try to do better this time. I still
have hopes that an acceptable improvement will be easy to impliment.
***[Presnetation by Ron Errico on Radiation and Cloud subgroup meeting
on 6/22/07]{.underline}***
<http://www.emc.ncep.noaa.gov/research/osse/NR/Jun07/RADIATION/Errico_cloudtalk_fnl_070622.ppt>
Excerpt from presentation
Out line
1. Lessons from previous OSSEs
2. What are the important issues?
3. Simulation of cloud cleared locations
4. Simulation of errors remaining after QC
**Decide what characteristics of observations and their errors**
**are critical to duplicate (and by how close an approximation)**
The above decision depends on:
1. How well the OSSE validation test criteria are to be satisfied
2. How much development time is to be invested
**My suggestion:**
Let's not aim for perfection for the new control simulations
(i.e., the ones using current operational observation data types),
but let's strive to do significantly better than for previous OSSEs
Decide what characteristics of observations and their errors
are critical to duplicate (and by how close an approximation)
**Validation of simulated locations**
Ideally, the simulation of locations is validated, if global maps of
simulated observation locations for individual observing periods are
indistinguishable from random maps of real observation locations for
equivalent periods.
**Cloud Related Nature Run Fields**
> 2-D:
>
> Low cloud fractional coverage
>
> Medium cloud fractional coverage
>
> High cloud fractional coverage
>
> Total cloud cover
>
> Convective precipitation
>
> Stratiform precipitation
>
> 3-D
>
> Cloud liquid water content
>
> Cloud ice water content
>
> Cloud Cover
Our modest goal need not be to simulate the radiances from cloudy
regions, but more simply to get the geographical distribution and
selected innovation statistics "realistic."
This is simpler because most details regarding the clouds are
irrelevant.
Algorithm for determining cloud-cleared observation locations
For each grid box where a satellite observation is given, use the cloud
fraction to specify probability that it is a clear spot. Then use random
number to specify whether pixel is clear. Use a functional relationship
between probability and cloud fraction that we can tune to get a
reasonable distribution.
Sample functions for probability P=P(cloud fraction)
{width="4.125in" height="3.3in"}
Strawman procedure for simulating observations
1\. For each observation location ......
2\. Bilinearly interpolate cloud fractions from NR grid to location
3\. Compute P (f, tuning parameter)
4\. Select random number x from uniform distribution (0,1)
5\. If x\>P then consider cloud free for this height of cloud, otherwise
cloud covered point
6\. If cloud free, then bilinearly interpolate q,T to location and
compute radiances for these unaffected channels
7\. If cloudy region, set radiance to very small value such that QC will
detect and discard.
8\. Repeat this process with various tuning parameters for P until the
observation count and distribution look reasonable. Then use this
parameter for all further experiments.
Information required from nature run:
T, q, Ps, Ts
Surface information that affects emmisivity
**Instrument Plus Representativeness Error**
1. Since we have no real instrument, its errors must be entirely
simulated.
```{=html}
<!-- -->
```
2. If different radiative transfer models (more generally called
"forward
models" or "observation operators") are used for simulation and
assimilation, then a portion of representativness error has already been
added.
3. The assimilation uses an interpolation algorithm (another form of
forward
model) for interpolating from fields defined at analysis grid points to
values
specified at observation locations. Similar models are also applied to
the nature
run for simulated observation locations. Since the assimilation and N.R.
grids
differ in resolution, there is another source for differing
relationships between
grid point values. For these reasons, another portion of
representativness error
has already been added when the simulated observations were created.
**Instrument Plus Representativeness Error**
1. Obtain an estimate of the statistics of representativeness error
due to using 2 different RT models (biases and variances)
2. Obtain an estimate of the statistics of representativeness error
due to differing grid resolutions and bilinear interpolation
3. Generate errors to be added to each observation by drawing
random numbers from a N(R',0) distribution. Ignore biases
since any large bias will be removed by the assimilation anyway.
Use R'\<R, R being the error value specified in the DAS.
4. Run the assimilation for a short time and note the variance of
the innovations. Re-adjust R' so that this variance better matches
the corresponding variance computed for the real assimilation.
5. After 1 or 2 iterations of this, use the final R' in any further
experiments.
Note: 1 and 2 are not strictly necessary for this purpose since they
only
help in defining an initial iterate for R'. For interpreting results,
however,
they should be very helpful. Otherwise a starting value for R' can be,
e.g.,
R'=2R/3.
***[\[ Comments from Ad Stoffellen \]]{.underline}* 070622**
Dear Ron,\
\
I read your presentation with interest and the procedure you line out is
pretty much what I would do. It is not entirely clear to me whether you
intend to evaluate cloud cover versus radiance acceptance fraction for a
real data assimilation experiment. This would provide a good proxy for
cloud cover version radiance cloud contamination probability. A second
point, when you realistically simulate \"cloudy\" radiances in case of a
random number exceeding some fraction threshold (is this your
suggestion?), are you sure that the data assimilation system will always
detect this? If it does not in some cases, you will systematically
influence the simulated radiance and create a bias. (This effect is
realistic by the way.) So, I suggest this point to be avoided, clarified
or checked in the experiments.\
\
Cheers,\
\
Ad
***[\[Jack Woollen \] 070625]{.underline}***
Ron,\
\
First, thanks for your presentation on locating NR clouds for simulating
radiance data. I hope we can get something going along those lines.\
Questions I have. Your procedure will work for AMSU, IASI, GOES
sounder/imager as well as HIRS/AIRS data?\
Did Mitch say he will develop lookup tables for cloud impact on various
representative wavebands? That would be nice to have.\
\
The paper is very good I think. I have just one small comment.\
\
1) On page three, the statement that representative error is potentially
been added \"twice\" because we add random errors as well as using high
resolution NR background,\
is somewhat misleading. It would be clearer to say that although some
representative error is introduced in the simulated observations due to
interpolation from the NR,\
additional errors must be added to the interpolated values to accurately
reflect the total error levels (instrument plus representative) found in
actual observations.\
\
Jack
***[Michiko Masutani]{.underline}* 070625**
For real data each radiance data is marked with cloud mask. So we can
produce function P(f) between probability of cloud clear (P) and total
cloud cover (f). Since there are more than one estimate of f, we will
get more than one function P. P(f) must be created for each channel.
CRTM has facility to handle six types of cloud however, when CRTM is
called from GSI, information about clouds are not used. Only
temperature, moisture, pressure, ozone seems to be used. Ron is
suggesting use CRTM without cloud liquid water content (CLWchbl) , cloud
ice water content (CIWchbl), cloud cover (CChbl). When Haibing simulated
AIRS data for T213 NR, he used cloud information. He estimated particle
sizes based on CLWchbl CIWchbl and CChbl and compute optical depth etc.
Probably he could generate AIRS data without using cloud information.
That will generate very optimistic data and may be a good start.
**\[Walter Wolf 070625\]\
**I am not sure who puts the cloud mask with HIRS, MSU and AMSU. The
cloud mask that goes with AIRS is from the MODIS near real-time
processing system. The developers of this cloud mask is CIMSS.\
\
Take it easy,\
\
Walter
**\[Ron Errico 070627\]**
I am not sure what a \"cloud mask\" precisely is. The simulation of IR
radiances from the NR by simply throwing possibly cloudy profiles, based
on cloud liquid and ice values into a version of the CRTM may or may not
be a problem. It depends on the distribution (histogram of cloud
fractions), on the realism of details of the liquid and ice profiles, on
the behavior of the cloudy CRTM, and especially on the effects of thin
clouds. This to me seems (1) unnecessary since most cloudy profiles will
be discarded and random errors added to partial account for the effects
of undetected thin clouds; (2) cloud fraction may have to be treated as
I suggest in any case, depending on the character of the histogram; (3)
if the resulting geographical distribution and/or innovations are
significantly unrealistic, you must ask where the flexibility is to
retune the simulations. My worry, just as in the case of almost everyone
misunderstanding the origins of representativeness error, some people
are thinking simplistically that just because they have a tool (CRTM)
that can produce some degree of cloudy radiances, all you need do is
throw profiles in without thinking more fully about the fundamental
issues concerning the application.
**\[Michiko Masutani 070627\]**
This is the way I understand. Please correct me if any this is wrong.
NCEP (any data assimilation) receive radiance data with cloud mask but
CRTM has a simple could scheme. Current GSI do not use the radiance data
with cloud mask and treat all radiance as clear radiance. Someone in
CIMSS in Wisconsin put all these cloud mask but we have to find out how
cloud mask is generated.
I thought what Ron suggested was to simulate and assimilate clear sky
radiance only.
Haibing came up with his own cloud scheme when he simulated AIRS data.
Based on his radiance he set cloud mask to radience data. He knew some
algoriths for AIRS cloud mask, I suppose.
There are a few cloud schemes in radiation and CRTM and development of
cloud scheme is one of the major subject in GSI. There seems to be
various cloud clear and QC algorithm. Simulating radiance without cloud
using Ron Errico strategies will be a good start.
Steve Lord suggested that simulating and assimilating using different
cloud scheme to assess simulation cloudy radiance will be one of the
interesting subject for OSSE.
**\[Michiko Masutani 070627\]**
Full OSSEs
I found there are serious confusion in definition of OSSEs. OSSEs using
real data and simulating future observation from analysis is widely
conducted. The OSSE using long nature run and simulating all observation
from NR should be called differently. I wold like to suggest using
\"full OSSEs\" which is used before in this discussion forum.
\[Erik Andersson 070628\]
Michiko,\
\
A few minutes ago I sent you a grib file at T511 containing the constant
surface fields that define the vegetation. There are four of them,
labelled param=27,28,29,30\
They are\
amount of low and high vegetation\
type of low and high vegetation\
\
Our model is a bit primitive in this regard. These fields are fix, and
don\'t even change with season. (It is planned that we will use monthly
vegetation climatology within the next year or so.)\
\
The surface type is same everywhere. The only variation is land/sea. No
surface soil type variations.\
\
The model longwave emissivity is defined as follows\
Window range is 800 to 1200 cm-1\
Outside this window emis=0.99\
Inside window region it is\
REMISD = 0.93_JPRB (dry land)\
REMISL = 0.96_JPRB (wet land)\
REMISN = 0.98_JPRB (snow)\
REMISS = 0.99_JPRB (sea)\
There is a linear increase in emis between dry and wet value over land
depending on the model\'s soil moisture (top soil level)\
\
There is no notion of a cloud emissivity. The radiation from clouds
depends on the cloud optical properties via the assumptions of the RRTM
radiation scheme. This cannot be reproduced from the archived
cloud-liquid water.\
\
Erik
\[Michiko 070628\]
Erik:\
Thank you very much.\
This is very important. Without these data NESDIS would use whatever
data they have and most likely very different from what used for NR.
For T213 NR we could not get good results from AIRS OSSEs. I think lack
of these information was one of the reason.\
\
I was told according to the references ECMWF use A. Slingo scheme as
well as NCEP to estimate particle size and cloud emissivity.\
\
May I post this climatology data and these information to web site,\
[ftp://ftp.emc.ncep.noaa.gov/exper/mmasutani/NR2006/clim](ftp://ftp.emc.ncep.noaa.gov/exper/mmasutani/NR2006/clim )\
This web site is indexed out and only available to people who know how
to access. When SIVO portal become available, it will be password
protected. Still these data will be available to large number of
people.\
\
Alternatively I can keep these data to only people who are involved in
simulation and announce people that information is available.\
\
Michiko
***[Erik 070629]{.underline}***
Michiko,\
\
Please go ahead and post these constant fields on the web site. No
problem.\
\
Erik
***[Michiko 070629]{.underline}***
We have received the file contains vegetation cover etc which require in
simulation of radiance data. Erik also provided information about
emissivity.\
\
The file is posted at\
[[ftp://ftp.emc.ncep.noaa.gov/exper/mmasutani/NR2006/clim]{.underline}](ftp://ftp.emc.ncep.noaa.gov/exper/mmasutani/NR2006/clim)\
\
I think we have to use this vegetation tom simulate radiance data.
Otherwise we\
will have noise due to inconsistency. When we assimilate data we use our
data\
used for CTRM and our model.\
\
In ctl file generated by grib2ctl.pl depicted:\
\
ANORsfc 0 162,1,0 \*\* surface Angle of sub-gridscale orography
\[rad\]\
CVHsfc 0 28,1,0 \*\* surface High vegetation cover \[(0-1)\]\
CVLsfc 0 27,1,0 \*\* surface Low vegetation cover \[(0-1)\]\
ISORsfc 0 161,1,0 \*\* surface Anisotropy of sub-gridscale orography\
LSRHsfc 0 234,1,0 \*\* surface Logarithm of surface roughness length
for heat\
SDORsfc 0 160,1,0 \*\* surface Standard deviation of orography\
SLORsfc 0 163,1,0 \*\* surface Slope of sub-gridscale orography\
SRsfc 0 173,1,0 \*\* surface Surface roughness \[m\]\
TVHsfc 0 30,1,0 \*\* surface Type of high vegetation\
TVLsfc 0 29,1,0 \*\* surface Type of low vegetation\
\
\
Note from Erik Andersson 070628:\
\
The grib file at T511 containing the constant surface fields that define
the vegetation. There are four of them, labelled param=27,28,29,30\
They are\
\
amount of low and high vegetation\
type of low and high vegetation\
\
Our model is a bit primitive in this regard. These fields are fix, and\
don\'t even change with season. (It is planned that we will use monthly\
vegetation climatology within the next year or so.)\
\
The surface type is same everywhere. The only variation is land/sea. No\
surface soil type variations.\
\
The model longwave emissivity is defined as follows\
Window range is 800 to 1200 cm-1\
Outside this window emis=0.99\
Inside window region it is\
REMISD = 0.93_JPRB (dry land)\
REMISL = 0.96_JPRB (wet land)\
REMISN = 0.98_JPRB (snow)\
REMISS = 0.99_JPRB (sea)\
There is a linear increase in emis between dry and wet value over land\
depending on the model\'s soil moisture (top soil level)\
\
There is no notion of a cloud emissivity. The radiation from clouds\
depends on the cloud optical properties via the assumptions of the RRTM\
radiation scheme. This cannot be reproduced from the archived\
cloud-liquid water.\
\
Erik
***[Ron Errico 070629]{.underline}***
This simply adds another source of rep. error, with as yet unconsidered
consequences since the NR sim. and data assim system presumably use
diff. data sets. It is not necessary to use different datasets since for
these simulations there is no consistency issue that I recognize.\
\
Ron
***[Michiko 070629]{.underline}***
Ron:\
So do you think we can use same vegetation from ECMWF for assimilation.\
This may be better. NCEP vegetation has seasonal cycle, I believe. The
difference between ECMWF vegetation and NCEP vegetation may be too
much.\
Michiko
***[Ron 070629]{.underline}***
Michiko: The answer to your question goes back to the issue of
representativeness error that i brought up in March. Simply put, any
difference between how you simulate an obs from the nature run and how
the GSi simulates an obs from the NCEP background becomes a
representiativeness error in the OSSE. You also generally add some
portion rep. error artifically using some random number generator. A big
difference between the 2 ways these rep errors are therbey introduced is
that:\
(1) In the former way, you don\'t know the the resulting error
characteristics (biases, variances, correlations, \"flow dependence\"
etc.) until you do some study. It is not necessary that you know these
statistics, since your concern should be the stats of the end result
(i.e., the innovation statistics), but you should be aware that these
errors are there, having a likely complex (in this case) but unknown
characterization.\
(2) in the latter way, generally you keep rather simple; e.g., use
random numbers from a Gaussian or similar distribution with generally 0
mean and some specified variance. In this case, you know the error
characteristics more completely and it is fairly simple to retune the
parameters to better match real innovation variances. A drawback is
that the error stats are likely oversimplified (e.g., no correlations).\
Since you also likely add a random error even if you use approach 1, you
still have a portion of the tuning capability this provides.\
\
In the present case, you can easily experiment a bit to see what rep.
error charactersitics are introduced by using the first approach. But
whoever does this investigation must first understand what he is doing
(e.g., what rep. error is, how you measure it, and which stats are
important).\
\
Ron
***[Michiko 070629]{.underline}***
I suggest using ECMWF vegetation for simulation and NCEP vegetation for
assimilation. We could use both same vegetation.\
\
Before I forward to all, may I have comments from experts.\
Michiko
***[Ron 070629]{.underline}***
The only show-stopper that I know at this point occurs whenever the
variance of the repr. error caused by using different simulation and
assimilation models or parameters (such as vegetation) creates
innovation variances that are larger than computed for the real assim.
In this case, it seems to me that the stats cannot be corrected by
simply tuning an additive random error. In other words, if a simulation
approach implicitly creates too much error variance before any random
error is explicitly added, you must first modify the simulation approach
to reduce the implicit error variance. My guess is that this show
stopper will be uncommon.\
\
Ron
***[Michiko 070629 12:45pm]{.underline}***
We have to clarify how vegetation index is used in model and CRTM. It
seems we need vegetation for simulating surface albedo but not for
assimilation. We need to simulate and assimilate surface albedo for
MODIS.\
When we assimilate surface albedo from MODIS, do we use vegetation?\
\
Michiko
***[Tong 070629]{.underline}***
Does anyone know if the Surface Type is already in the old surface data
or the new vegetation data?\
\
Thanks\
\
Tong
***[Quanhua 070629 2:17]{.underline}***
Hi,\
\
I would use this opportunity to explain the surface model in CRTM. For
infrared sensor, we use surface emissivity. The surface emissivity is
determined\
by user inputs: surface type, sensor info (central wavelength of the
sensor channel). Vegetation type (rather than vegetation index) is
used.\
\
For microwave sensor, the surface emissivity in CRTM is computed either
using a physical model or derived from the microwave window channels.\
For a vegetable land, the physical model is applied for the channel
frequency \< 80 GHz. Vegetation fraction and soil moisture are needed
for the microwave\
land emissivity calculation.\
\
The surface albedo is normally used for visible channel and shortwave
radiation calculation. The vegetation index may be derived from\
the visible and near-IR channels. The operational version of the CRTM
doesn\'t include\
the visible part.\
\
Thanks,
***[Yuta- Hou 070629 3:54\
]{.underline}***Quanhua
In GFS model, there are two different sets of vegetation climatology
data currently parallel running on the operational model, due to legacy
of two separate developments. This discrepancy will be addressed in the
near future with an unified land surface model.\
\
One of the data set is used in the land model that was developed and
implemented a few years ago by Ken Mitchell and others. The data set
contains a global climatological vegetation type distribution and
vegetation cover to compute surface heat transport, etc. The vegetation
type classification was originally developed by Dorman and Sellers
(1989) that consists of 13 distinct surface vegetation types.\
\
The other one is used by radiation related calculations to obtain
surface albedo for shortwave radiation and surface emissivity for long
wave radiation. This part of codes was developed by me started in early
90\'s. The surface vegetation type, a fixed climatology also with 13
different classifications (Matthews, 1983; Briegleb, 1992), was used
implicitly (e.g. used in the off-line calculations to establish albedo
tables). For model\'s surface emissivity in the IR spectrum, the same
vegetation type data is used but is further reduced into only eight
distinct types. By the way, in the current operational model, surface
emissivity is still using a default value of one.\
\
Yu-Tai
***[Ronald Errico wrote:\
]{.underline}***
Are the forecast model vegetation data sets or emmisivities derived from
them also used for the CRTM calculations within GSI? In general, the
radiation paramaterization used by the forecast model is not the same as
that used by the radiance assimilation algorithm (the CRTm in this
case). Since in the OSSE context it is only the latter that concerns us,
please do not refer to the former (unless in the NCEP case they are
actually germane for some reason) since otherwise it will likely confuse
our discussion. Generally radiation parameterizations in a forecast
model are designed to model (parameterize) radiation flux divergence,
since it is the radiative heating implied by that divergence that is
critical, whereas in the direct assimilation of radiances our concern is
with parameterizing channel transmittence through the atmosphere to
mimick what a particular instrument sees. I am not an expert in this by
no means, but it is just what I was told once. Let me know if I am
wrong.\
\
\
Ron
***[Yu-Tai 070702 10:03]{.underline}***
Ron,\
\
You are right that the forecast model radiation and CRTM used in GSI are
two different types of calculations. In a forecast model, the radiation
computes the total radiative energy over the entire solar and thermal
spectrum. Thus, radiances have to be integrated over all angles of a
hemisphere and then be integrated over all spectral bands to get
upward/downward fluxes. From there surface and top fluxes and
atmospheric heating rates (divergence of fluxes) are obtained for
forecast model usage. On the other hand, in a forward radiance model,
such as CRTM, specific and and limited number of very narrow spectral
bands are needed to be considered in the computation. Those bands are
usually directly related to the satellite sensors specifications.\
\
Unlike in a GCM\'s radiation, where two-way whole spectral computations
are required, the forward radiance model usually needs to focus only one
direction that correlated to satellite position, and few absorption
gases. As a result, although the two types of radiations are started
from the very same radiative transfer equations, they are diverted
considerably in their computation methods as well as the consideration
of optical properties of absorbers (gases, clouds, aerosols, etc.) and
surface radiative characteristics (albedo, emissivity).\
\
Due to the large differences between the two, I was hesitate at the
beginning to be involved with you guys work. The email I sent out
earlier was intended for information only to respond the inquires posted
by Michiko and others. You may ignore my part if it is not any use for
your work, and i am sorry for any confusion it may cause to anybody.\
\
Yu-Tai
***[Michiko 070702 12:27]{.underline}***
In 892 of July 2006 BAMS article by John LeMarshall. AVHRR vegetation
cover is listed as data used by GFS. There are vegfrac and vegtype in
fixed file, which Yu-tai told me he does not use. I suspect if ECMWF
does not use vegetation cover Erik sent us in operational forecasting,
but for they may used for nature run. Then how can we make simulation
consistent?\
\
I need help in putting together intelligent questions to ask to ECMWF.\
\
\
Michiko
***[Ron Errico 070702 2:28pm]{.underline}***
Michiko: I first ask \"consistent with what?\" The nature run does not
include sat obs as part of its run. The sat obs are the only radiance
issue that concerns us for the OSSE at this time (maybe later we can
concern ouselves with the nature of model error (difference) in the NCEP
vs ECMWF NWP models). The issue is exactly what I stated back in March
about representativeness error and what i have tried to explain several
times since then. Is it better to have a source of rep. error that is
implicitly drawn from a non-random distribution with rather complex
relationships that may be qualitatively but not quantitatively
charactertistic of the real observing system, or better to draw from an
over simplified random distribution tuned to the correct variance?\
I don\'t know the answer. It should be relatively easy to perform some
simple exps. to compare the two approaches before actually performing
the OSSE.
***[Michiko 070702 3:21]{.underline}***
Ron:\
What kind of two approach are you thinking about?\
I will put together all your E-mails and read though all.\
Michiko
***[Ron Errico 070707]{.underline}***
About the 2 methods of creating rep error:\
One is to add values drawn from a random number generator.\
The other is to use different forward models(interpolation and radiative
transfer). The first you can totally control but is more difficult to
design to be totally realistic. The second is hard to adjust (since it
yields the error determined by an algorithm less adjustable) but may be
more realistic (e.g., it will create biases and correlations, although
it is unclear hw they may be related to those of the real errors). Even
if you use the second method, you will still have to use the first to at
least simulate the instrument error. If that addition does not
necessary to yield the correct 0-B stats, then the rep. error you
already have is not realistic.\
\
There is a way to do this testing off line.
***[Michiko 070711]{.underline}***
That what I understand for vegetation. Please let me know how if I
understand correctly.
= = = = = = = =
At NCEP monthly climatology vegetation(cover and type) and surface type
are used for GSI, fcst model and Land model. Land model read from fixed
file and does horizontal and time interpolation to model grid save to
sfc file. GSI and forecast model uses what ever in sfc file.
There is a confusion in language. Radiation scheme in fcst model does
not use vegetation but uses surface emissivity based on vegetation and
surface type. Forecast model uses table based on Matthews scheme to get
emissivity and Land model uses other table based on MODIS data. CRTM has
model to evaluate surface emissivity. CRTM handle much narrower wave
band but it gives more detail and uses more than vegetation and surface
type.
Erik said sfc long wave emissivity is defined, in ECMWF model
Window range is 800 to 1200 cm-1
Outside this window emis=0.99
Inside window region it is
REMISD = 0.93_JPRB (dry land)
REMISL = 0.96_JPRB (wet land)
REMISN = 0.98_JPRB (snow)
REMISS = 0.99_JPRB (sea)
There is a linear increase in emis between dry and wet value over land
depending on the model\'s soil moisture (top soil level)
When we simulate radiation data we have to discuss if we use ECMWF
scheme or CRTM.
ECMWF uses annual mean vegetation and surface type. I think we should
use ECMWF surface to simulate data and use NCEP monthly climatology to
assimilate. Yutai told me model may not be so sensitive to monthly
varying vegetation and surface type.
**Summary if the meeting on august 20 and 23rd.**
**\[Summary of meetings and discussion\]**
***[- Talk by Chris Barnet and other information]{.underline}***
He talked about how AIRS data are simulated and how to estimate
observational errors.
There are products for estimated clear sky radiance data using
extrapolation. There is a effort to assimilate retrieval data in Univ
MD. There are nine versions of SARTA based on various stages of AIRS.
There were two major warm up episodes.
Comments from Jim Jung:
JCSDA has made up its mind not to use retrieval and clear sky radiance
from NESDIS. However, it may be worthwhile to look into these products
to evaluate the performance of GSI and CRTM.
Comments from Paul:
When we do simulations the data response function used for simulation
and coefficient used for assimilation must match. For example, the AIRS
response function has not been changed from version 5 and the matching
coefficient for CRTM is version 4. This mismatch will not be corrected
by bias correction.
***[-Calibration for OSSE with T213 NR]{.underline}***
Michiko went over various problems encountered in the OSSE with T213 NR.
1\. General agreement in data impact test and detailed differences.
Trouble in the tropics.
2\. Problems caused by constant SST.
3\. How to handle surface topography and surface data.
4\. Systematic error using obs-anl.
***[- Procedure of simulation of Radiance for existing
instruments-]{.underline}***
This proposed procedure is based on the summary from the meeting on 8/20
and follow up discussions. Initially, we would produce files for HIRS,
AMSU, AIRS, and GOES channels.
We will work on two streams, A and B, in parallel:
A. Development of codes and scripts from NR grib code to BUFR formatted
radiance data.
1\) Retrieve the information about radiance data from the archive.
(RADINFO)\
2) Generate soundings as a necessary first step, separate from any cloud
masking or error assignments. We would use the orbital data patterns
from BUFR dump files. (DB91L). DB91L can be saved either 6 hourly or
every 6 min depending on the amount of data.
3\) DB91L using RTN simulated radiance data to produce BUFR files
containing the simulate the clear sky radiances. (SIMRAD) First we will
use ad hoc sampling strategies. If TCC is less than a certain amount
(for example, 10%) simulate clear sky radiance.
B. Development of sampling strategies and study of error characteristics
presented by Ron Errico.
1\) How big are differences between radiances produced by different RT
algorithms for identical input profiles. I have asked her to use 2
different RTMs that I think are options in the CRTM. This is to check
whether we can in fact use a different RTM to simulate radiances fro the
NR than used in the GSI-DAS.\
2) What is the distribution of relevant cloud parameters in the NR that
we hope to use to determine whether clouds are affecting radiances at
observation locations. She is starting by looking at the distribution of
cloud fractions for H,M and L clouds at a single time. What this
distribution looks like will inform us of our options for proceeding.\
\
\
**\[Proposed task for next few months\]**
Simulation of radiance for existing instruments:
Jack Woollen
He offered to work on A1-A2. DB91L for task A is in BUFR format and
contains only basic data.
Haibing and Tong Zhu will work on task A3.
Read DB91L and generate SIMRAD using adhoc sampling and error
assignment.
Haibing will work on AIRS AMSU and HIRS data and Tong Zhu will work on
GOES data.
Tong Zhu may continue to GOESR project by generating DB91L for GOESR
himself
Yuanfu and Michiko will provide help for Haibing.
Runhua , Ron Errico, and Emily will work on task B.
For task (B), Jack will generate DB91L for October 1, 2005 for T511NR
containing all model and surface variables in binary format, not BUFR.
GMAO work on one day data and select the list of variables. For the
selected variables DB91L will be generated for the first two or three
weeks of October 2005 from T511NR.
| en |
all-txt-docs | 092807 | Appendix B:
Examples of Various States' Building Code
Practices
44
Appendix B
Examples of Various States' Building Code
Practices
In addition, the examples below
describe the variety of practices
used in administering codes and
enforcement. Even though some
states have building codes, their
mechanisms for enforcement are
poor. This is often the case in smaller
communities that do not have an
inspection staff and in states that
have just adopted statewide codes.
Each state varies, and what works
United States
in one state may not work in an-
other. The purpose of these ex-
amples is to give you ideas on what
has been tried and how such a
system might work in your state.
The adoption of a statewide build-
ing code with seismic provision will
save lives when an earthquake or
disaster occurs.
FIGURE B.1 This appendix describes Code administration varies by state.
the building code practices of Arkansas, As noted in chapter 4, some states The case study information was
California,Kentucky, Massachusetts, require local code adoption, some collected from the National Confer-
South Carolina, and Utah. have mandatory state codes, and ence of States on Building Codes
others have no requirement at all. and Standards, Inc.,' augmented
Typically where there is no compre- through a series of interviews. A list
hensive statewide building code the of interviewees is included at the
state regulates through individual end of this appendix.
standards some of the following: fire
safety, building accessibility, manu-
Arkansas
factured housing, health facilities,
swimming pools, schools, and
Adoption and Revision
plumbing.
Arkansas' first building code, the
The case examples given below
Arkansas Fire Protection Code,
demonstrate the wide range of
adopted in 1955, applies to all
practices used. States such as South
buildings in Arkansas. The state fire
Carolina and California have had
marshal is part of the state police
building codes with seismic provi-
department, and is charged with
sions for some time. Other states
enforcing the Arkansas Fire Preven-
have recently adopted a statewide
tion Code as well as other functions.
building code with seismic provi-
Because of the code, the state must
sions. Usually, the move to adopt a
adopt the most recent fire and
statewide building code is in
building codes from SBCCI.
response to a natural disaster or
serious fire. This illustrates the point The state fire marshal delegates
that the best time to act is right after plan review to local fire marshals as
a disaster occurs. Awareness of the is permitted by the code. Local
need for building codes is highest at municipalities having building code
this time. departments can pass building
Examples ofVarious States' Building Code Practices 45
codes at least as stringent as the engineer. The act does not apply to
residential structures of four units
state's. It
* 4 4 4
or less, nor to agricultural struc-
Code updates are determined
tures. Another key element of the As mentioned in Chapter 4,
administratively. New versions of
adt is that it specifies a penalty of seismic advisory councils can help
the SBCCI codes are reviewed by the
$1,000 per day of violation. reduce earthquake hazards in
state fire marshal and a committee
many different ways. The Arkan-
of design professionals, fire fighters, Although the state already has a
sas example proves that point.
building code, Act 1100 legisla-
and others. The fire marshal's office
Established in December 1984,
makes appropriate amendments and tively underscores that the state
vith 17 members, the Earthquake
sends the proposed code out for requires seismic design, estab-
Advisory Council consists of
lishes zones more specific than
public comments. The recom- representatives from state agen-
mended code is then approved by those in the SBC, is self-updating cies, utilities, universities, hospi-
the state legislative council and sent by the most recent published SBC, tals, local agencies, and other
to the secretary of state. There is no and sets forth penalties for non- interested parties. The Council is
compliance.
prescribed schedule for code update: open to additional, members, if
The fire marshal determines when they can carry the Council's
the code should be updated. Arkan- Enforcement message to an important constitu-
sas, generally, tries to update its ency!
Some larger towins (such as West
code every time a new edition of the
Memphis, Blytheville, and The Council has been very
Standard Building Code (SBC) is
Jonesboro) have building depart- successful in providing a forum
published.
ments and are well equipped to for most of the major constituen-
cies to get together and exchange
enforce seismic design and con-
Seismic Requirements ideas and alert one another to the
struction requirements. However,
latest news in the field. Without
In March 1991 the Arkansas General enforcement can be a problem in
the Arkansas Advisory Council,
Assembly chose to emphasize the smaller communities that do not
Act 1100 would never have
have inspection staff. Under Act
importance of seismic design by
happened. The Council devel-
enacting Act 1100, "An Act to 1100 enforcement mechanisms
oped the idea several years before
Safeguard Life, Health, and Property probably will continue to be poor.
the bill wtlas passed, drafted the
Still, the new Act puts much of the
by Requiring Earthquake-Resistant
bill, argued for seismic codes
Design for all Public Structures to be responsibility on professional
whenever members gave public
engineers, who enforce the Act by
Constructed Or Remodeled within
presentations, and routed it
the Boundaries of this State Begin- their signatures on plans.
through the legislature. Their
ning September 1, 1991." Introduc-
strategy was to create both public
For some types of buildings
tion of Act 1100 in the legislature
and professional support.
(hospitals, schools, dormitories,
coincided with the aftermath of the
places of assembly, department The bill had been a high
Loma Prieta, California, disaster;
stores, etc.), the state reviews the priority of the Council since its
and the bill passed\ with no opposi-
plans if there is no local building inception. Refined drafts of the
tion votes. It was signed by the
official. All state buildings or state- bill had been in progress for about
governor on April 9,1991.
funded buildings must be re- three years, and it was almost
The act requires that all "public vdiewed by State Building Services ready to be introduced. The
structures" (buildings open to the (the state architect's office). This timing of the bill coincided waith
public as well as all public works) be requirement has only been in the post-Loma Prieta disaster, and
designed to resist seismic forces, in existence for the past ten years. A in November 1990 the bill 'as
accordance with the minimum memo of understanding has been introduced to the legislature. The
bill passed with no opposition
requirements of the 1993 revision to established between the Health
votes.
Department and the Department
the 1991 SBC or the latest edition
with revisions. of Human Services regarding
regulations for hospitals and long-
The act specifies the standard
term ambulatory care facilities.
building code seismic zones to be
used for each county, interpreted Code enforcement and plan
from Algermissen and Hopper's review is relatively new in Arkan-
1984 U.S. Geological Survey map.2 sas. Prior to the 1970s, most
enforcement and review was
The structural design must be
signed and sealed by a professional voluntary and conducted by
46 Appendix B
private architects and engineers. The houses within cities in order to
number of staff plan reviewers and ensure the health and safety of the
inspectors depends on the size of the occupants of substandard housing.
municipality, its location within the A combination code in 1923 encom-
state, and its funding sources. passed tenement houses, hotels, and
A small city may have two to three dwellings. Amendments in 1951
inspectors, while a city the size of repealed many restrictive require-
Little Rock has fifteen to twenty ments and substituted more modern
inspectors and six to eight review- concepts and material ratings.
ers. Localities most commonly
California has enacted statewide
charge for permits, plan reviews,
standards for housing, mobile home
and inspections and are thus capable
parks, employee housing, manufac-
of supporting a sufficient enforce-
tured housing, energy conservation,
ment system.
fire safety, and handicapped access.
There are additional standards for
state-owned and -regulated facilities.
Seventeen state agencies adopting or
proposing building standards have
specific authority to regulate con-
struction.
Codes are mandated by state law.
I-
The legislature mandates, through the
Health and Safety Code, certain
uniform model codes that are appli-
cable throughout the state. Local
jurisdictions enforce the same edition
of the model building codes as the
state. California uses the Uniform
Building Code (UBC) with amend-
ments for general building and
seismic codes.
The adoption of updates occurs
i only with the publishing of a new
model building code, which occurs
FIGURE B.2 This scliool biiildiizg An appeals system is set up every three years. Proposed revisions
siistnirzed s a w e dnmag in thc 1933 Lory within the state's code. If building are prepared and documented by the
Bmcli, Califomin,qiinke. (Photo: U.S. pcrmits are denied the builder may adopting state agency. Revisions then
Dcpt. of Conziizerce, NORA) make an appeal to the commander go through the state administrative
of the fire marshal section of the procedures process of publication,
Arkansas State Police, then to the public comments, and hearings.
appointed state fire marshal, and the
head of the Arkansas State Police. If Seismic Requirements
a municipality has a building
State and local officials in California
department, it has the authority to
have years of experience with seismic
establish a local board of appeals.
provisions. California has had seismic
provisions since the 1933 Long Beach
California
earthquake. The original regulations,
known as the Field Act, covered
Adoption and Revision public schools only. The UBC seismic
provisions originated in the work of
The first California building laws,
the Structural Engineers Association
enacted by the legislature in 1909,
of California, and have been refined
established standards for construc-
over the years primarily in response
tion and maintenance of tenement
to California practice and experience.
Examples ofVarious States' Buirding Code Practices 47
In addition, California requires Department of Housing, Buildings
mitigation of earthquake hazards in and Construction, which was
legislatively created in 1978 as a
unreinforced masonry (brick)
buildings. SBI 547, enacted in 1986, response to the Beverly Hills Supper
Club fire (this occurred in May 1977,
requires local governments to
killing 160 and injuring 130). The
inventory unreinforced masonry
buildings and to establish earth- department combines all functions
quake hazard mitigation programs, involved in construction of build-
ings. The Kentucky Building Code
such as retrofit requirements,
also includes the Kentucky Plumb-
notification of building owners, and
ing Code, Kentucky handicapped
programs to reduce the number of
accessibility requirements, and
occupants of unsafe buildings.
Kentucky boiler rules. The depart-
ment includes the Division of
Enforcement
Building Codes Enforcement, the
Local building departments are the
State Fire Marshal's Office, and the
primary enforcement agencies in
Division of Plumbing Having these
California. The requirements
programs under one department has
charging local building departments
simplified coordination of the
with the administration of codes are
various codes.
stated in the California Health and
The Board of Housing, Buildings
Safety Code, which is enacted by the
state legislature. Fifty-eight counties and Construction is responsible for
and 490 cities in the state have their adopting and amending the code.
own building departments, with The tbv entv-member board is
appointed by the governor to
plan review and inspection staff
represent the spectrum of interests
ranging from 1 to 350 people. The
related to the building industry.
quality of enforcement varies. The
State Department of Housing and
The Kentucky Building Code is
Community Development may
updated every three years, follow-
assume the responsibility of enforce-
ing the publication cycle of BOCA.
ment if local action is inadequate.
Once the new edition of BOCA is
Although the quality of local
published, the Department of
enforcement varies, for over twenty
Housing, Buildings and Construc-
years the state has not had to
tion analyzes the changes and takes
exercise this option.
administrative steps to incorporate
BOCA into law within a few
Local appeal procedures exist,
usually involving a local housing months.
appeals board. The local building
Kentucky code requirements are
official normally sits on the board. IF
mandatory throughout the state.
the board upholds the decision of
Local jurisdictions may amend only
the building official, the appeal may
the fire code, and only to make its
continue to the next level of author-
requirements more stringent.
ity, such as the city council or county
board of supervisors, and then, if
Seismic Requirements
appropriate, to litigation.
Kentucky has always incorporated
the latest seismic provisions of the
Kentucky
BOCA code. With the 1992 BOCA
code, Kentucky's code is now
Adoption and Revision consistent with the NEHRP Provi-
sions. As with other states in the
Since October 1979 Kentucky has
had a state building code, the eastern half of the country, enforce-
Kenttck-y Building Code, rhich is ment and local awareness of seismic
based on the BOCA NBC. It is requirements still need improve-
administered by the Kentucky ment. Professional training pro-
48 Appendix B
grams and workshops may be Massachusetts
necessary until adequate standards
are attained.
Adoption and Revision
In the late 1800s the Massachusetts
Enforcement
State Police was empowered to
Generally speaking, the state is
enforce various laws related to
responsible for larger buildings. The
building safety. By the early 1900s
state reviews plans, issues permits,
many local municipalities had
and provides inspection for these.
promulgated their own building
The state employs twelve inspectors
regulations. As a result of the
and nine plan reviewers. Smaller
Coconut Grove fire in 1942 (490
buildings and single-family homes
dead), a committee appointed by
are handled by local agencies.
the governor recommended the
Kentucky has a Building Inspectors
implementation of a mandatory
Certification Program, mandated by
state building code, but no action
the 1982 General Assembly, under
was taken. In 1945 a commission
which inspectors must pass appro-
again recommended a state uniform
priate examinations to become
building code. Instead, a State Board
certified.
of Standards was established in the
Department of Public Safety with
Communities with qualified
authority to prepare and propose
personnel can petition to manage all
building regulations for adoption by
building permit functions them-
local municipalities.
selves. Six of the larger cities and
counties (including Louisville,
In 1971 the board of standards
Lexington, and Jefferson County)
adopted and promulgated the State
0
have done so.
Board of Standards Building Code,
which was the 1970 BOCA Basic
The state depends on design
Building Code with certain amend-
professionals to sign and take
ments. In 1972 the legislature
responsibility for their plans. The
established a State Building Code
department does not have a struc-
Commission with authority to
tural engineer reviewing plans, so it
develop and implement a statewide
is particularly important for seismic
uniform building code. The first
design that a structural engineer
state building code was legislatively
sign the plans. The code's imple-
adopted in 1975 to consolidate the
mentation depends on having
351 different codes that existed
architects and engineers accept
throughout the state.
responsibility for their designs. This
code creates a common standard for
The Massachusetts State Building
building professionals across the
Code is administered by the State
state, an aspect very important to a
Board of Building Regulations. The
rural state in order to ensure compli-
state uses the BOCA National
ance by smaller communities.
Building Code with many amend-
ments.
Permit applicants may appeal
decisions for any reason, and all
Law requires the code to be
appeals receive a hearing from a
updated at least every five years, but
panel selected from among the
typically it is updated every two
twenty-member board. This system
years. Changes to the code are based
has been effective in ensuring a fair
on local needs rather than BOCA's
process.
publication schedule. Every May
and November public hearings are
held and administered by members
of the State Board of Building
Regulations. Anyone within or
Examples ofVarious States' Building Code Practices 49'
any existing building that experiences
outside the state can propose
changes. a change in use, a change in the
occupancy numbers, or is substan-
tially remodeled. The code then
Seismic Requirements
provides for the level of seismic
Seismic provisions have been
upgrading required. This amendment
adopted and enforced since the first
was made effective in February 1997.
edition of the state building code in
January 1975. just as with other code
Enforcement
provisions, the State Board of
Building Regulations votes to adopt Every municipality is required by law
seismic provisions and local munici- to appoint a building commissioner to
palities enforce them. Howrever, the administer and enforce the state code.
responsibility for design is placed on Very small towns are permitted to
registered professionals. Any regionalize under legislative provi-
building 35,000 cubic feet or larger sions, but they must still be overseen
must be designed by a qualified by a building commissioner. There are
registered professional engmieer or 351 building commissioners within
architect, and reviewers generally the state.
defer to them. Massachusetts also
Since November 1992 Massachu-
has a structural engineering peer
setts law has required the certification
review requirement for certain
of building officials. Certification
structures.
requires an exam and forty-fiv e hours
The State Board of Building of continuing education every three
Regulations has several advisory years. Because the system grandfa-
commuittees, including one for thers current officials, it wT il take
seismic issues. The seismic advisory approximately ten years for the effects
committee consists of ten structural to become apparent in local practice.
engineers who volunteer their
The law places enforcement
knowlTedge and time to adapt
responsibility with local building
BOCA's code to the state of lassa-
departments, except for state-owned
chusetts. The board updated their
buildings. Administration of building
building codes in February 1997
codes and enforcement for such
based on the 1993 BOCA National
buildings are conducted by district
Building Code and the 1992 N\lEHNRP
state inspectors with the Department
Provisions.
of Public Safety. There are twelve
The Massachusetts Emergency inspectors throughout the state, each
being responsible for thirty to thirty-
Management Agency and the Board
of Building Regulations and Stan- two cities within their specified
dards have conducted professional jurisdictions. These inspectors also
development workshops for build- assist local building commissioners
ing officials on seismic construction. and inspectors wvhen necessary.
Approximately 500 building officials
Massachusetts has more than 600
have received ATC-20 training for
building officials throughout the
post-earthquake evaluation of
state. The actual number of plan
buildings.
reviewers and inspectors for each city
Massachusetts recently enacted depends on the size of municipalities;
an amendment regarding seismic for example, Boston has twenty-five
safety in existing buildings. Massa- building officials.
chusetts has numerous unreinforced
The State Building Code Appeals
masonry buildings that not only
Board, a three-member board consist-
existed prior to the adoption of a
ing of members -ofthe State Board of
statewide code but are historical in
Building Regulations staff, holds
nature. The amendment requires a
appeals hearings twice a month. Local
seismic study to be conducted on
appeal boards are permitted by law,
Appendix B
50
for the city of Charleston in 1907. The
city of Columbia followed with its
own local building code in 1916. By
the mid-1960s a variety of building
codes were in use throughout the
state with little consistency in
construction requirements, causing
great confusion among architects,
engineers, contractors, and others.
By act of the South Carolina
General Assembly on June 21,1972,
the state authorized the SBC as its
first state-approved construction
document. This legislation allowed
voluntary adoption of this uniform
code. When local jurisdictions adopt
a code, it must be the SBC. Thus, this
requirement has gradually phased
out all other codes in the state. When
adopting the SBC, local jurisdictions
but only three or four exist. Most
FIGURE B.3 Tlzefirst Duildiizg code in
appellants take their appeals to the must adopt the latest code in print.
South Carolirin was n doczrnzeizf iiczdoped
state. The appeals board hears
by and for Ckarlestoiz in 1907. (Photo: The
The legislation prohibits local
approximately six to eight cases per
Clinrleston Area Coizucizfionnnd Visitors
amendments to the adopted building
Btireazd hearing. Written decisions are
code without approval of the South
administered within thirty days
Carolina Building Codes Council.
after the hearing.
This unique system was intended to
develop consistency in construction
South Carolina practices as well as provide design
professionals with a single set of
methods that would be acceptable to
Adoption and Revision
all jurisdictions in the state. Approxi-
South Carolina has no required
mately half of the local jurisdictions
statewide code. Rather, it permits
in the state have adopted the SBC.
local use of the Standard Building
Codes must be updated within a year
Code (SBC).The first building code
of the SBCCI's publication of the
within the state of South Carolina
revised SBC, which occurs every
was a document developed by and
three years.
Table B. I South Carolina Code Enforcement
Avg. No. of
Avg. Population Per
Code Enforcement
Officers One Code Enforcement
Jurisdiction Population Per Jurisdiction Officer
1 485
c 1,000
1.38 3,645
1,000-10,000
2 7,472
10,000-25,000
4.8 7,363
25,000-50,000
7.81 9,302
50,000-100,000
10.86 13,547
> 100,000
Examples ofVarious States' Building Code Practices So
by the Office of School Planning, a
Seismic Requirements
branch of the Department of Educa-
Local governments adopt and
tion. Staff members are licensed or
enforce the seismic requirements of
registered architects or engineers and
the most recent SEC. Many building
are required to pass the Standard
inspectors and plan reviewrers,
Building Code Test.
however, still are not familiar with
the seismic provisions. They often
Utah
leave compliance to the design
engineer who signs and seals the
plans. Most municipalities in South Adoption and Revision
Carolina simply have the engineer
Utah adopted the Uwlfornz Building
sign an affid'avit or require him or
Code (UBC) in 1988. Prior to this date
her to take full resp onsibility for
each municipality adopted their own
seismic compliance. The code
code (usually some version of the
permits this policy
UBC), and there was inconsistency
among jurisdictions.
Larger municipalities have more
knowledgeable building code staff.
The code is mandated by state law~T
They also have more money to
and administered by the Department
spend on plan reviewes. Charleston,
of Business Regulation. The state
for example, pays more attention to
legislature established a Uniform
seismic provisions than do local
Building Code Commission under
governments elsewhere in the state.
the Department of Business Regula-
tion to conduct code updates admin-
Enforcement istratively. The Uniform Building
Code Commission meets monthly to
The administration of codes is
consider requests for code amend-
entirely at the local level. Smaller
municipalities sometimes contract ments. Amendments are published
on March 1 and September 1 of each
buil ding code enforcement to a
year for changes enacted during the
larger county jurisdiction. South
Carolina has a total of 327 code preceding six-month period. Code
enforcement officers, including both up dates usually occur the year
following ICBO's publishing of a
plan reviewers and code inspectors.
Of that number, 228 are certified newr, UBC. For example, the 1991
professionals. Local jurisdictions UBC was adopted in January 1992
determine the necessary number of and the 1994 UB'C wvas adopted in
code enforcement officers based on 1995.
intensity of local construction
Local jurisdictions require state
activity.
approval to amend the code. The
Uniform Building Code Commission
The director of South Carolina's
Building Codes and Related Services determines if proposed local amend-
provided some recent data on ments will be adopted or rejected
distribution of code enforcement and, if adopted, whether such
personnel, shown in Table B.l. amendments will be statewide or
enforced only by the local jurisdic-
All appeals go to the local board
tion.
of appeals, and there is no recourse
to the state. If the owner still is
Seismic Requirements
unsatisfied, he or she can proceed
Seismic provisions have been
with legal action against the city or
county adopted and enforced statewide
since 1988, when the UBC was
Public building construction is
adopted. Prior to that some cities
administered by the State Engineers
had no code, while others had
Office, except for public school
already adopted the UBC and thus
construction, which is administered
52 Appendix B
had seismic provisions. The UBC INTERVIEWS
seismic requirements have been
Arkansas:
widely used in Utah since the mid-
Parks Hamon, State Building Services,
1970s.
Little Rock (Spring 1994); Dr. James
Seismic regulations are adopted Blacklock, Department of Engineering
by the state, but they are enforced Technology, University of Arkansas, Little
Rock (June 4, 1991); Lt. Ray Carnahan,
locally. Larger cities, such as Salt
Lake City, have adequate knowledge Commander, Fire Marshal Section,
of seismic provisions. However, Arkansas State Police, Little Rock (June 3,
1991); Dan Cicirello, Office of Emergency
some smaller municipalities do not
adequately enforce the code or do Services, Conway (June 3, 1991); John
David McFarland, Chair of Governor's
not have qualified personnel. The
lack of state oversight is sometimes Earthquake Advisory Council and Senior
a problem. Cities and counties do Geologist, Arkansas Geological Commis-
not enforce requirements for school sion, Little Rock (June 4, 1991); and Owen
district buildings. Rather, the school Miller, State Legislator, Marked Tree (May
districts themselves are expected to 22, 1991)
meet the requirements of the UBC,
California:
which not all are prepared to do.
Ed King, Chief of Housing Standards,
Division of Codes and Standards, Depart-
Enforcement ment of Housing and Community
Development, Sacramento (Spring 1994)
Local municipalities are fully
responsible for the administration of
Kentucky:
building codes. While the state has
Jack M. Rhody, Director, Division of
no plan reviewers and no building Building Code Enforcement Department
inspectors, everyone who inspects
of Housing, Buildings and Construction,
construction projects must be Frankfort (Spring 1994); Mike Lynch,
licensed by the state, which ensures
Division of Disaster and Emergency
a certain level of competency from Services, Department of Military Affairs,
building code enforcers. Frankfort (May 2, 1991); Charles Cotton,
Commissioner, Department of Housing,
The state board of appeals gets
Buildings and Construction, Frankfort
involved with appeals in jurisdic-
(May 2, 1991); and Professor Mike Cassaro,
tions with no local building code of
School of Engineering, University of
appeals. Most local municipalities,
Louisville (May 3, 1991).
however, have their own building
boards of appeals. Massachusetts:
Brian Gore, State Building Code Regula-
NOTES tion, Boston (Spring 1994)
1 Mclntrye, Marle, ed., Directory of State
South Carolina:
Building Codes and Regulations, 4th ed.,
Gary Wiggins, Director, South Carolina
National Conference of States on
Building Codes and Regulatory Services,
Building Codes and Standards
Columbia (Spring 1994)
(Herndon, VA), May 1987; and National
Conference of States on Building Codes Utah:
and Standards, Directory of Building Lawrence Reavely, Department of Civil
Codes and Regulations, State Directory, Engineering, University of Utah (Spring
1994); and Roger Evans, City of Salt Lake
NCSBCS (Herndon, VA), 1994.
City, Building Permits (Spring 1994)
2 See the maps by Algermissen and
Hopper in Estimation of Earthquake
Effects Associated with Large Earthquakes
in the New Madrid Seismic Zone, Hopper,
M.G., ed., U.S. Geological Survey Open-
File Report 85-457, 1984, 42-51.
53
Appendix B:
Sample EnablingActs:
Arkansas
Kentucky
South Carolina
Utah
Appendix B
Appendix B
54
54
Arkansas
Arkansas Act 1100 (1991)-RequiringEarthquake Resistant Design
As Engrossed: 3/15/91 3/26/91
State of Arkansas
78th General Assembly
HOUSE BILL 1577
Regular Session, 1991
By: Representative 0. Miller
For An Act To Be Entitled
"AN ACT TO SAFEGUARD LIFE, HEALTH AND PROPERTY BY REQUIRING EARTHQUAKE
RESISTANT DESIGN FOR ALL PUBLIC STRUCTURES TO BE CONSTRUCTED OR REMODELED
WITHIN THE BOUNDARIES OF THIS STATE BEGINNING SEPTEMBER 1,1991."
BE IT ENACTED BY THE GENERAL ASSEMBLY OF THE STATE OF ARKANSAS:
SECTION 1. It is the purpose of this act to protect the public by requiring that all public
structures be designed and constructed to resist destructive forces when an earthquake occurs in
the New Madrid Seismic Zone.
SECTION 2. Definitions. Whenever used in this act, unless a different meaning clearly
appears from the context:
(a) "Owner" shall mean any agency of the state, county, city, township, town, village, or
private entity, partnership, business or corporation.
(b) "Public Structure" means any building intended, or adaptable, for public employment,
assembly, or any other use if it will be open to the public. Also included in this definition are
certain building types as defined under the term "Public Works" projects.
(c) "Public Works" means works, whether of construction or adaptation, undertaken and
carried out by the national, state, county, school district, or municipal authorities, and designed to
serve some purpose of public necessity, use, or convenience; such as public buildings, road,
aqueducts, parks, and all other fixed works constructed for public use. The term relates to the
construction of public improvements and not to their maintenance or operation.
(d) "Add to" shall mean adding to existing buildings or structures more than four
thousand (4000) square feet in gross floor area and all areas of increased building height.
(e) "Alter", "retrofit", and "remodel" means any alteration or repair of a building which
when completed will increase the market value of the building by one hundred percent (100%) or
more.
(f) "Seal" means the Arkansas seal issued to signify certification of registration to practice
architecture or engineering.
(g) "Seismic" means pertaining to an earthquake or earth tremor (vibrations).
(h) "Structural Elements" shall mean all structural load carrying members of a building or
structure required to transmit loads (forces) within the building or between the building and the
ground.
Ss
Sample EnablingActs
HB 1577
As Engrossed. 3115191 3/26/91
SECTION 3. Seismic Zones Established. Areas within the boundaries of this State shall
be divided into zones of anticipated damage that wvill occur in various locations with respect to the
New Madrid Seismic Zone.
(a) Zone 3. Area of greatest anticipated seismic damage shall include the following
counties: Clay, Greene, Craighead, Mississippi, Poinsett, Cross, Crittenden, St. Francis, Randolph,
Lawrence, Jackson, AWtoodruff, and Lee.
(b) Zone 2. Area of moderate anticipated seismic damage shall include the following
counties: Sharp, Independence, White, Lonoke, Prairie, Arkansas, Monroe, Phillips, Fiulton, Izard,
Stone, and Cleburne.
(c) Zone 1. Area of low0v anticipated seismic damage shall include all remaining counties
within the boundaries of this State.
SECTION 4. Design Requirements. Hereafter, neither the state, any county, city,
to vnship, vSillage or private entity shall construct, add to, alter, retrofit, or remodel any public
structure unless the structural elements are designed to resist the anticipated forces of the
designated seismic zone in WI-hich the structure is located. Design loads and seismic design
requirements shall be, as a minimum, those listed in the chapter of Minimum Design Loads and
Referenced Chapters from the Standard Building Code, 1988 or latest edition with revisions.
All construction plans for public buildings and structures shall comply with Arkansas
Code 17-14-101 through 17-14-311. The design of structural elements of public buildings and
structures shall be performed by a professional engineer registered in the State of Arkansas who is
competent in seismic structural design according to current standards -oftechnical competence.
The structural plans of each public building or structure shall bear the Engineer's Arkansas seal
and signature and a statement of reference to what Seismic Zone the structure is designed to
satisfy.
SECTION 5. Exemptions. Certain building types such as single family residential,
duplexes, triplexes, fourplexes, and agricultural structures shall not be included in the
requirements of act.
SECTION 6. Violations and Penalties. Any owner knowingly constructing a public
building with this State after September 1, 1991, without complying with the provisions of this act
shall be gnilty of a Class A misdemeanor and shall upon conviction, be sentenced to pay a fine of
not less than one thousand dollars ($1,000). Each day of such unlawful construction practice shall
constitute a distinct and separate offense.
SECTION 7. All provisions of this act of a general and permanent nature are amendatory
to the Arkansas Code of 1987 Annotated and the Arkansas Code Revision Commission shall
incorporate the same in the Code.
SECTION 8. If any provision of this act or the application thereof to any person or
circumstance is held invalid, such invalidity shall not affect other provisions or applications of the
act which can be given effect without the invalid provision of application, and to this end the
pronisions of this act are declared to be severable.
SECTION 9. All laws and parts of lawes in conflict with this act are hereby repealed.
Approved by Governor Bill Clinton, April 9, 1991.
56 Appendix B
Kentucky
Kentucky Revised Statutes
CHAPTER 198B
HOUSING, BUILDINGS AND CONSTRUCTION-BUILDING CODE
SECTION 1988.560 Fire protection sprinkler contractor's license required
1988.010 Definitions. - Exemptions.
Board of housing, buildings and construction.
1988.020 1988.565 Preparation of designs of system.
Department of housing, buildings and construction.
198B.030 1988.570 Examination of applicant.
1988.035 Transfer of other agency functions to department. 1988.575 Affidavits in lieu of examination.
General powers and duties of the board.
1988.040 198B.580 Prerequisites to becoming licensed fire protection
1988.050 Uniform state building code. sprinkler contractor.
Local enforcement of Uniform Building Code-Workers'
198B.060 198B.585 Seal of certificate holder.
compensation coverage requirement. 198B.590 Signature on license and certificate.
198B.070 Appeals. 1988.595 Proof of liability insurance coverage.
1988.080 Amendments to the uniform state building code. 1988.600 Certificate holder permitted to obtain only one
198B.090 Certification of professional classifications-Training contractor's license at a time.
program for building code administration and 1988.605 Annual renewal of certificates and licenses.
enforcement. 1988.610 License as proof of competency - Power of local
198B.100 Mobile home exemption. officials regarding regulation.
198B.110 Effective dates for uniform building code-Exemptions. 198B.615 Disposition of fees collected by commissioner.
198B.120 Injunctions to enforce building code compliance. 1988.620 Refusal to renew license-Revocation or suspension of
198B.130 Private action for damages. license - Administrative fine - Appeal
198B.140 Hindrance of building inspectors prohibited. 1988.625 Inspection-Cease and desist order.
198B.250 Architectural barriers advisory committee. 198B.630 Application of KRS 198B.550 to 1988630.
198B.260 Regulations to make buildings accessible to physically
handicapped persons-Compliance required. PENALTIES
198B.270 Present requirements in effect until new regulations filed. 198B.990 Penalties.
198B.280 Exemption for temporary change. 198B.991 Penalty.
SAFETY GLAZING IN HAZARDOUS LOCATIONS
198B.300 Definitions for KRS 198B.310 to 1988.330.
198B.010. Definitions. -As used in this
198B.310 Labelling requirements.
198B.320 Prohibitions. chapter, unless otherwise provided:
198B.330 Workers exempt from liability.
(1) "Assembly occupancy" means the occupancy
ELEVATOR INSPECTIONS
or use of a building or structure or any portion thereof
198B.400 Definitions.
by a gathering of persons for civic, political, travel,
198B.410 Inspectors-Certificates of competency -Application -
Examination - Issuance - Reexamination. religious, social or recreational purposes, including
198B.420 State elevator inspection program - Qualifications of among others:
director - Appointment of general inspectors.
(a) Armories;
198B.430 Employment of special inspectors.
(b) Assembly halls;
198B.440 Suspension or revocation of certificates.
(c) Auditoriums;
198B.450 Lost or destroyed certificates.
1988.460 Registration of elevators. (d) Bowling alleys;
1988.470 Annual inspection. (e) Broadcasting studios;
1988.480 Report of inspection-Hearing on construction plans and
(f) Chapels;
specifications - Findings and orders of department.
(g) Churches;
1988.490 Rules and regulations.
(h) Clubrooms;
198B.500 Safety equipment.
198B.510 Certificates of operation-Renewal. (i) Community buildings;
198B.520 Permits for erection or repairs. (j) Courthouses;
198B.530 Prohibition.
(k) Dance halls;
198B.540 Enforcement-Notice of defective machinery.
(1) Exhibition rooms;
(m) Gymnasiums;
FIRE PROTECTION SPRINKLER CONTRACTORS
198B.550 Definitions. (n) Hotels;
198B.555 Administration of KRS 1988.550 to 198B.630 Duties of
-
(o) Lecture rooms;
commissioner.
(p) Lodge rooms;
(q) Motels;
57
Sample EnablingActs
selling or buying of goods, wares, or merchandise,
(r) Motion picture theaters;
or the housing of vehicles of transportation, except
(s) Museums;
w~%There occupancy is of high hazard, including
(t) Night clubs;
among others:
(u) Opera houses;
(a) Banks;
(v) Passenger stations;
6w) (b) Barber shops;
Pool rooms;
(c) Beauty parlors;
(x) Recreation areas;
(d) Department stores;
(v) Restaurants;
(e) Garages;
(z) Skating rinks;
(f) Markets;
(aa) Television studios;
(g) Service stations;
(bb) Theaters.
(h) Offices;
(2) "Attic' means the space between the ceiling
(i) Stores;
beams of the top habitable story and the roof rafters.
(j) Radio stations;
(3) "Basement" means that portion of a building
(k) Telephone exchanges;
the average height of which is at least half below
(1)Television stations.
grade, which is ordinarily used for purposes such as
(8) "Certified building inspector" means a
storage, laundry facilities, household tools shops, and
person who has been certified by the department as
installation and operation of heating, cooling and
having successfully completed the test requirements
ventilating facilities, but which is not ordinarily used
provided by KRES 198B.090 to practice as a city,
for purposes of general household habitation.
county. or state building inspector wiffinin,the
(4) "Building" means any combination of
Comnmonwealth.
materials, whether portable or fixed, which comprises
(9) 'Certified plans and specifications inspector"
a structure or non-mine underground area affording
means a person who has been certified by the
facilities or shelter for any human occupancy. whether
department as having successfully completed the
infrequent or regular. The word "building" shall be
test requi-remene ts provided by KRS 198Bf090 to
construed wherever used herein as if followed by the
practice as a city, county, or state plans and
words "or part or parts thereof and all equipment
specifications inspector within the Common; ealth.
therein" unless the context clearly requires a different
(10) "Certified plumbing inspector" means a
mearning. "Building" shall also mean swimming pools
person who has been certified by the department
constructed below grade on site, but not swimming
as having successfully completed the test
pools assembled above grade on site. "Building" shall
requirements provided by KRS 198B.A90 and
not mean a mobile home, or a farm dwelling or other
318.140, or 318.090 to practice as a city, county, or
farm buildings and structures incident to the
state plumbing inspector within the
operation and maintenance of the farm if such farm
Commonwealth.
structures are located outside the boundary of a
municipality and are not used in the business of retail
(11) "Commissioner" means the commissioner
trade or used as a place of regular employment for ten
of housing, buildings and construction.
(10) or more people or structures used in the storage
(12) 'Construction" means the erection,
or processing of timber products. This chapter shall
fabrication, reconstruction, substantial alteration or
not apply to any single family diweaing except those
conversion of a building, or the installation of
sold or constructed under a trade or brand name.
equipment therein, but shall not include the
(5) Any city, county or urban-county government
ordinary repair of a building or structure.
of the Commonwealth may extend, by ordinance, the
(13) "Department" means the department of
application of this chapter to those single family
housing, buildings and construction.
dciellings exempted under subsection (4) of this
(14) "Educational occupancy" means the
section, but may not enforce any building code other
occupancy or use of a building or structure or any
than the uniform state building code on such
portion thereof by persons assembled for the
dwellings.
purpose of learning or of receiving education
(6) Nothing in this chapter shall be construed to
instruction, including among others:
exempt single family dwellings from those provisions
(a) Academies;
of the uniform state building code that relate to the
(b) Care centers;
national electric code and the state plumbing code.
(c) Colleges;
(7) "Business occupancy" means the occupancy or
(d) Kindergartens;
use of a building or structure or any portion thereof
(e) Libraries;
for the transaction of business, the rendering or
(f) Pre-schools;
receiving of professional services, or the displaying,
Appendix B
58
Kentucky
manufacturing facility for installation or assembly on a
(g) Relocatable classroom units;
permanent foundation at the building site.
(h) Schools;
(19) "Institutional occupancy" means the
(i) Seminaries;
occupancy or use of a building or structure or any
(j) Universities.
portion thereof by persons harbored or detained to
(15) "Equipment" means facilities or
receive medical, charitable or other care or treatment,
installations, including but not limited to, heating,
or by persons involuntarily detained, including among
electrical, ventilating, air conditioning, and
others:
refrigerating facilities or installations.
(16) "High hazard occupancy" means the (a) Asylums;
(b) Homes for the aged;
occupancy or use of a building or structure or any
portion thereof that involves highly combustible, (c) Hospitals;
(d) Houses of correction;
highly flammable or explosive materials or which
(e) Infirmaries;
has inherent characteristics that constitute a special
(f) Jails;
fire hazard, including among others:
(g) Nursing homes;
(a) Aluminum powder factories;
(h) Orphanages;
(b) Charging or filling stations;
(i) Penal institutions;
(c) Distilleries;
(j) Reformatories;
(d) Dry cleaning plants;
(k) Sanitariums;
(e) Dry dyeing plants;
(1)Nurseries.
(f) Explosive-manufacture, sale or storage;
(20) "Mobile home" means the mobile home as
(g) Flour and feed mills;
defined in KRS 227.550(9).
(h) Gasoline bulk plants;
(21) "Ordinary repair" means any nonstructural
(i) Grain elevators;
(j) Lacquer factories; reconstruction or renewal of any part of an existing
building for the purpose of its maintenance, or
(k) Liquefied petroleum gas;
decoration, and shall include, but not be limited to, the
(1)Mattress factories;
replacement or installation of nonstructural
(m) Paint factories;
components of the building such as roofing, siding,
(n) Pyroxylin-factories, or warehouses;
windows, storm windows, insulation, drywall or lath
(o) Rubber factories.
and plaster, or any other replacement, in kind, that
(17) "Industrial occupancy" means the
does not alter the structural integrity, alter the
occupancy or use of a building structure or any
occupancy or use of the building, or affect, by
portion thereof for assembling, fabricating,
rearrangement, exitways and means of egress; but
finishing, manufacturing, packaging or processing
shall not include additions to, or alteration of, or
operations, except for occupancies of high hazard,
relocation of any standpipe, water supply, sewer,
including among others:
drainage, gas, soil, waste, vent or similar piping,
(a) Assembly plants;
electric wiring or mechanical equipment, including
(b) Creameries;
furnaces and hot water heaters or other work affecting
(c) Electrical substations
public health or safety.
(d) Factories;
(22) "Story" means that part of a building
(e) Ice plants;
comprised between a floor and the floor or roof next
(f) Laboratories;
above which is not a basement or an attic.
(g) Laundries;
(23) "Physically handicapped person" means a
(h) Manufacturing plants;
person confined to a wheelchair; a person who uses
(i) Mills;
braces or crutches; a person who because of the loss of
(j) Power plants;
a foot or leg or because of an arthritic, spastic,
(k) Processing plants;
pulmonary or cardiac condition, walks with difficulty
(1) Pumping stations;
or insecurity; a person who suffers from a faulty
(m) Repair garages;
coordination or palsy; a person who is blind or whose
(n) Smokehouses;
sight is so impaired that, functioning in a public area,
(o) Workshops.
he is insecure or exposed to danger; a person whose
(18) "Industrialized building system" means
hearing is so impaired that he is unable to hear
any structure or component thereof which is wholly
warning signals; and a person whose mobility,
or in substantial part fabricated in an off-site
59
59
Sample EnablingActs
Sam~ple EnablingActs
selected by the governor from a list of three (3)
flexibility coordination and perceptiveness are
submitted by the Kentucky retail federation.
significantly reduced by aging.
(2) Except for the commissioner of the
(24) 'Facility for physically handicapped person"
department, the commissioner of the department of
means any converience or device which facilitates the
health services, the executive director of the
health, safety or comfort of a handicapped person,
Kentucky housing corporation and the attorney
including, but not limited to, ramps, handrails,
general or his designee who shall serve on the board
elevators, and doors. (Enact. Acts 1978, ch. 117, sec. 1,
during the term of their existing office and shall be
effective June 17, 1978; 1980, ch. 361, sec. 1, effective
voting members, board members shall be appointed
July 15, 1980; 1982, ch. 189, sec. 1, effective July 15,
for four (4) year terms, except that initially four (4)
1982; 1982, ch. 308, sec. 1, effective July 15, 1982.)
shall be appointed for two (2) year terms, four (4)
shall be appointed for three (3) year terms, and six
198B.020'. Board of housing, buildings and
(6) shall be appointed for four (4) year terms. No
construction. - (1) There is hereby created the
board member shall be appointed for more than one
Kentucky board of housing, buildings and
(1) successive term except as provided in subsection
construction within the Kentucky department of
*(3) of this section. The governor shall, within the
housing buildings and construction comprised of
limitations of this subsection, set the length of term
twventy (20) members to indude: the commissioner of
of each of the initial appointees to the board.
the department/ one (1) local government fire chief
(3) Vacancies occurring on the board among
selected by the governor from a list of three (3)
those members appointed by the governor shall be
submitted by the Kentucky firemen's association; the
filled by seeking nominations as in subsection (1) of
executive director of the Kentucky housing
this section from the organization which originally
corporation; the commissioner of the department of
nominated the member who is to be replaced. A
health services, cabinet for human resources; the
replacement for a board member shall be appointed
attorney general or any assistant attorney general he
immediately upon the expiration of the departing
may designate to represent the interests of consumers;
board member's term of service. Should a board
one (1) professional homebuilder selected by the
member vacate his position on the board prior to the
governor from a list of three (3) submitted by the
expiration of his tern, his replacement shall be
home builders association of Kentucky; one (1)
appointed for the period of the unexpired term.
registered architect selected by the governor from a
Should the unexpired term be less than two (2)
list of three (3) submitted by the Kentucky society of
years, the person selected to fill the unexpired term
architects; one (1) registered structural engineer
may subsequently be appointed to one (1) successive
selected by the governor from a list of three (3)
four (4) year term.
submitted by the Kentucky society of professional
(4) Members may be removed from the board by
engineers; one (1) registered electrical engineer
the governor for unethical conduct or for failure to
selected by the governor from a list of three (3)
attend three (3) or more successive meetings of the
submitted by the Kentucky society of professional
board V\ ithout reasonable cause.
engineers; one (1) citizen member selected by the
(5) The board shall meet at least quarterly and
governor to represent the interests of low and
the first meeting shall occur no later than August 31,
moderate income housing consumers within the
1978. Before assuming their duties, members of the
Commonwealth of Kentucky; one (1) citizen member
board shall: take an oath as specified in section 228 of
at large; one (1) practicing gener-al contractor selected
the Constitution of Kentucky.
by the governor from a list of three (3) submitted by
(6) The commissioner of the department shall
the Kentucky association of general contractors; one
serve as chairman of the board. The board may elect
(1) practicing code administrator selected by the
from its members other officers as are required to
governor from a list of three (3) submitted by codes
conduct its business, except that neither the
administrators association of Kentucky; one (1) realtor
commissioner of the department for health services,
selected by the governor from a list of three (3)
the executive director of the Kentucky housing
submitted by the Kentucky association of realtors; one
corporation nor the attorney general or his designee
(1) member selected by the governor from a list of
shall be elected to office on the board.
three (3) submitted by the Kentucky state building
(7) The board may adopt such rules, regulations
trades council; one (1) member selected by the
and bylaws as are necessary to conduct its internal
governor from a list of three (3) submitted by the
business.
mechanical contractors association; one (1) electrical
(8) No member of the board may vote on any
contractor member selected by the governor from a
matter which will result in his direct or indirect
list of three (3) submitted by the national electrical
financial gain.
contractors association; and one (1) retailer member
Appendix B
60
Kentucky
(9) Those members of the board who are not each condition and execute such agreements as may be
necessary, convenient, or desirable.
salaried governmental employees shall be
(6) Nothing in this chapter shall preclude any
compensated for their time when attending board
other agency, board, or officer of the state from being
meetings or attending to official duties as directed
designated as the directing or allocating agency, board,
by the board at the rate of fifty ($50) per day. All
or officer for the distribution of federal grants and aid,
board members shall be compensated for expenses
incurred in the conduct of board business. (Enact. or their performance of other duties to the extent
Acts 1978, ch. 117, sec. 2, effective June 17, 1978; necessary to qualify for and to receive grants and aid
1980, ch. 82, sec. 1, effective July 15, 1980; 1982, ch. for programs under the administration of the
270, sec. 1, effective July 15, 1982; 1986, ch. 331, sec. department.
32, effective July 15, 1986.) (7) The commissioner is authorized to receive,
for and on behalf of the state, the department, and
198B.030. Department of housing, buildings the board of housing, buildings and construction,
and construction. - (1) There is hereby created the from the United States and agencies thereof, and
from any and all other sources, grants and aid and
Kentucky department of housing, buildings and
construction within the cabinet for public protection gifts made for the purpose of providing, or to assist
and regulation. The governor shall appoint a in providing, any of the programs authorized by this
chapter, including expenses of administration. Al
commissioner to head the department by July 1,
1978. The commissioner shall receive for his services such funds shall be paid into the state treasury and
such compensation as the governor shall determine. credited to a trust and agency fund to be used by the
(2) The commissioner may employ sufficient department in carrying out the provisions of this
staff to carry out the functions of his office. Neither chapter. No part of this fund shall revert to the
general fund of the Commonwealth. (Enact. Acts
the commissioner nor any member of his staff shall
be employed, either directly or indirectly, in any 1978, ch. 117, sec. 3, effective June 17, 1978.)
aspect of the building industry as regulated by this
198B.035. Transfer of other agency functions to
chapter while employed by the department of
department. - There are hereby transferred and
housing, buildings and construction.
vested in the Department of Housing, Buildings and
(3) The department shall serve as staff for the
board of housing, buildings and construction as Construction, office of the Fire Marshal or its successor
agency, all functions, powers and duties, funds,
established by this chapter, and shall perform all
budgeting, procurement, and other administrative personnel, equipment and supplies now vested in the
activities necessary to the functioning of this body. Commission on Fire Protection Personnel Standards
The board shall prescribe the duties of the and Education (KRS Chapter 95A), and in the
Department of Public Safety as follows:
commissioner in addition to those duties otherwise
delegated to it by the governor or prescribed for him Fire department aid (KRS 17.210 to 17.270); safety
glazing (KRS 17.410 to 17.440 and 17.990); boiler safety
by law.
(KRS Chapter 236); dry cleaning and dyeing (KRS
(4) The department may enter into contracts
Chapter 228); fire prevention and protection (KRS
with the federal government, other agencies of state
government or with its subdivisions, or with private 227.200 to 227.410); and transportation of hazardous
substances (KRS Chapter 234). (Enact. Acts 1974, ch.
profit or nonprofit organizations in order to effect
the purposes of this chapter. 74, Art. V, sec. 20; 1980, ch. 188, sec. 243, effective July
(5) Subject to the direction of the board of 15, 1980.)
housing, buildings and construction, the
commissioner shall cooperate with the agencies of 198B.040. General powers and duties of the
the United States and with the governing bodies and board. -The Kentucky board of housing, buildings
and construction shall have the following general
housing authorities of counties, cities, and with
powers and duties:
nonprofit organizations and area development
districts in relation to matters set forth in this (1) To conduct or cause to be conducted studies to
determine the needs of the building industry of
chapter, and in any reasonable manner that may be
necessary for the state to qualify for, and to receive Kentucky;
(2) To conduct or cause to be conducted or
grants or aid from such agencies. To these ends and
subject to the direction of the board, the participate in studies of the costs of the various factors
of building construction and uses of buildings; and to
commissioner shall have the power to comply with
6
611
Sample EnablingActs
Sample EnablingActs
to build public water purification plants will be
recommend programs and procedures which will
submitted by the department to the natural
mmnimize the cost of buildings, including the use of
resources and environmental protection cabinet for
energy, while maintaining safety, durability and
that cabinet's comments. Any such regulations shall
comfort;
require the natural resources and environmental
(3) To administer regulatory legislation relating to
protection cabinet's comments to be completed and
buildings and construction;
submitted to the department Tvlithin sixty (60) days;
(4) To assume administrative coordination of the
(9) To issue regulations providming for the proper
various state construction review programs and to
construction of sewage treatment plants, other than
cooperate with various federal, state and local
the seivage treatment equipment and systems in
agencies in the programs as they relate to buildings
such plants, provided, how ever. that any such
and construction;
regulations must require that applications for
(5) To assume administration and coordination of
permits to build sewage treatment plants will be
various state housing programs to include:
submitted by the department to the natural
(a) Devising and implementing procedures, in
resources and environmental protection cabinet for
conjunction with the department of local government,
that cabinet's comments. Any such regulations shall
for attaining and maintaining an accurate count of the
require the natural resources and environmental
housing inventory in Kentucky; including information
protection cabinet's comments to be completed and
on the age, physical condition, size, facilities and
submitted to the department within sixty (60) days;
amenities of such housing, and housing constructed
and
and demolished each year;
(10) To issue regulations for the safe installation
(b) Designing programs coordinating the elements
and operation of plumbing and plumbing fixtures.
of housing finance, production, maintenance and
(Enact. Acts 1978, ch. 117, sec. 4, effective June 17,
rehabilitation for the purpose of assuring the
1978.)
availability of safe, adequate housing in a healthful
environment for all Kentucky citizens;
198B.050. Uniform state building code. - (1)
(c) Establishing or causing to be established public
Within one (1) year from its initial meeting, after
information and educational programs relating to
adequate notice in accordance with KRS Chapter
housing, to include informing Kentucky citizens about
13A, the board shall adopt and promulgate a
housing and housing related programs that are
mandatory uniform state building code which shall
available on all levels of government;
establish standards for the construction of all
(d) Designing and administering, or participating
buildings, as defined in KRS 198EB.010, in the state.
in the design and administration of educational
The code shall provide that the review and
programs to prepare low income families for home
approvall, as necessary, of building plans for
ownership, and counseling them during their early
conformance with the uniform state building code
years as home-owners;
prior to construction approval shall be conducted
(e) Promoting educational programs to assist
only by the department of a local government or
sponsors in the development and management of low
governments delegated such responsibilities by this
and moderate income housing for sale or rental;
chapter, and any exceptions to -thispolicy shall be
(f) Cooperating with various federal, state and
explicitly stated in the code.
local agencies in their programs as they relate to
(2) The code shall be comprehensive and shall
housing;
include but not be limited to provisions for general
(g) Conducting or causing to be conducted studies
construction; structural quality; mechanical systems
to determine the housing preferences of Kentucky
to include heating, cooling, and ventilation;
citizens and the present and future housing
electrical systems; and life safety from hazards of
requirements of the state;
fire, explosion, and other disasters, whether caused
(6) To recommend state building industry policies
by acts of nature or man. The code shall encompass
and goals to the Kentucky general assembly;
the Kentucky State Plumbing Code promulgated
(7) To adopt and promulgate a mandatory uniform
pursuant to KRS 318.130, boiler rules and
state building code, and parts thereof, which shall
regulations issued pursuant to KRS 236.030, and the
establish standards for the construction of all
national electrical code.
buildings, as defined in KRS 198B.010, in the state;
(3) This code shall be designed after ancd may be
(8) To issue regulations providing for the proper
selected from the models offered by such model
construction of public w,ater purification plants, other
code agencies as the Building Officials and Code
than the water treatment equipment and systems in
Administrators, International, Inc.; the International
such plants, provided, however, that any such
Conference of Building Officials; the Southern
regulations must require that applications for permits
Appendix B
62
Kentucky
necessary to implement the uniform state building
Building Code Congress; and other nationally
code or to carry out any other responsibility assigned
recognized organizations which may include
to said board by this chapter.
governmental agencies. The code shall:
(6) The board shall monitor the effectiveness of
(a) Provide uniform standards and requirements
agencies designated by local governments to enforce
for construction and construction materials;
the provisions of the uniform state building code.
(b) To the extent practicable, set forth standards,
(7) If the board determines that any agency is not
specifications and requirements in terms of
enforcing the provisions of the uniform state building
performance objectives, so as to facilitate the use of
code, it shall direct the department to determine
new technologies, techniques, and materials. The
where deficiencies exist. The department shall require
code shall not discriminate in favor of particular
the local government to correct the deficiencies within
suppliers' materials, techniques, or technologies;
sixty (60) days and report to the department its
(c) Protect the public health, safety, and welfare
method of correcting the deficiencies.
within the state.
(8) If the local government fails to correct the
(4) Adoption of a code shall include provisions
deficiencies, the department shall recommend to the
for the continuing review of, and the board shall
board that the department be permitted to preempt
adopt when deemed justified to fulfill the purposes
the local program as provided for in KRS 198B.060(4).
of this chapter, new materials, technologies, and
techniques in the building industry. The board may
198B.060. Economic security and public welfare.
adopt a model code promulgated by a model code
(9) The board shall provide for the supply,
agency only if that agency provides a method for -
including amendments and revisions thereto, of
democratic participation by the board and any local
sufficient copies of the uniform state building code for
governments which may enforce the code, in a
all interested parties. (Enact. Acts 1978, ch. 117, sec. 5,
continuing review and possible adoption of new
effective June 17, 1978; 1982, ch. 308, sec. 2, effective
materials, technologies, and techniques in the
July 15, 1982.)
building industry.
(5) The board shall issue regulations, after notice
in accordance with KRS Chapter 13A, which are
63
Sample EnablingActs
. South Carolina
An act to amend Chapter 9, Title 6, Code of Laws of South Carolina, 1976, relating to building
codes, so as to revise the requirements and methods of adoption, the application, scope, and
exceptions, and for the enforcement of these codes; to provide for appointment of building officials
and establishment of building programs; to provide for adoption of building codes and standards
by state agencies, and the application of local ordinances, regulations, and standards to certain
state and school district construction projects, and to farm structures; to provide for the
membership and duties of the South Carolina Building Codes Council and for the duties of the
State Fire -Marshaland State E ngineer in connection with certain projects; to amend the 1976 Code
by adding Chapter 8 to Title 6 so as to provide for building codes enforcement officers and for their
functions, duties, and registration; by adding Section 38-7-35 so as to provide that the first one
hundred fifty thousand dollars of revenue collected pursuant to Section 38-7-30 must be used for
the purpose of implementing the training, certification, and continuing education program for
building codes enforcement officers; to amend Chapter 75 of Title 38 by adding Article so as to
provide for the Advisory Conmmuittee to the Director and the South Carolina Building Codes
Council and Loss Mitigation Grant Program; to provide that Chapter 10 of Title 6 is not applicable
in counties or municipalities that fully have implemented building codes required by Section
6-9-10; and to declare the public policy of South Carolina pertaining to maintaining reasonable
standards of construction in this state.
BE IT ENACTED BY THE GENERAL ASSEMBLY OF THE STATE OF SOUTH CAROLINA:
Building codes revised
SECTION 1. Chapter 9, Title 6 of the 1976 Code is amended to read:
CHAPTER 9
Building Codes
S ection 6-9-10'. All municipalities, as defined by Section 5-1-20, and counties in this State shall
adopt building, energy, electrical, plumbing, mechanical, gas, and fire codes, referred to as building
codes in this chapter, relating to the construction, livability, sanitation, erection, energy efficiency,
installation of equipment, alteration, repair, occupancy, or removal of structures located within
their jurisdictions and promulgate regulations to implement their enforcement. The municipality
or county may adopt only the national, regional, or model codes provided in Section 6-9-50.
-Withthe exception of structures used primarily for offices, storage, warehouses shop areas, or
residential housing, nothing in the building codes or regulations applies to electric cooperatives,
the Public Service Authority, or to a public utility corporation subject to regulation by the
authorities of the South Carolina Public Service Comm-lission or the Liquefied Petroleum Gas
Board.
To the extent that federal regulations preempt state and local la vs, nothing in this chapter shall
conflict with the federal Department of Housing and Urban Development regulations regarding
manufactured housing construction and installation.
Appendix B
64
South Carolina
Section 6-9-20. Municipalities and counties may establish agreements with other governmental
entities of the State to issue permits and enforce building codes in order to provide the services
required by this chapter. The South Carolina Building Codes Council may assist in arranging for
municipalities, counties, or consultants to provide the services required by this chapter to other
municipalities or counties if a written request from the governing body of the municipality or
county is submitted to the council. If a municipality or county determines that it is unable to arrange
for services for any annual period at costs totally within the schedule of fees recommended in the
appendixes to the building codes referred to in Section 6-9-50, the municipality or county shall
submit an affidavit to the council to be exempt from the requirements of this chapter. If such an
affidavit is submitted, the municipality or county is exempt from the requirements of this chapter,
which exemption is effective until such time as it becomes financially feasible for a county or
municipality to provide the services, or five years, whichever is less. A county or municipality may
renew its affidavit at the end of five years and at each five-year interval thereafter if it makes
another determination that it cannot arrange for services at costs totally within the schedule of fees
recommended in the building codes referred to in Section 6-9-50.
Section 6-9-30. Each county shall appoint a building official or contract with other political
subdivisions as authorized in Section 6-9-20 so that the unincorporated area of the county is under
the jurisdiction of a building official. Each municipality shall appoint a building official or contract
for a building official within the municipal limits. Based on the needs established by each
municipality or county, the building official or appointing authority may appoint and employ other
personnel and assistants necessary to perform the required inspections and duties and may
prescribe fees for construction permits and inspections. The appointment of a building official and
the establishment of a building inspection program for all municipalities and counties must be
accomplished according to the following dates and populations based on the population figures of
the latest official United States Census:
(1) municipalities and counties with a population above 70,000: one year after the effective date of
this provision;
(2) municipalities and counties with a population of 35,000 to 70,000: two years after the effective
date of this provision;
(3) municipalities and counties with a population under 35,000: three years after the effective date of
this provision.
Section 6-9-40. The building codes and standards referenced in Section 6-9-50 must be adopted
within six months after the establishment of a building inspection department. State agency
adoption of a building code or regulation permitted by this chapter must be accomplished in
accordance with the Administrative Procedures Act.
Section 6-9-50. (A) Municipalities and counties shall adopt by reference only those provisions of the
latest editions of the following nationally known codes and the standards referenced in the codes for
regulation of construction which directly relate to building and safety standards within their
respective jurisdictions: Standard Building Code, Standard Gas Code, Standard Plumbing Code,
Standard Mechanical Code, the Standard Fire Prevention Code, as published by the Southern
Building Code Congress International, Inc., the Model Energy Code, as published by the Council of
American Building Officials, and the National Electrical Code, as published by the National Fire
Protection Association. The appendixes of the codes provided in this section may be adopted as
needed by a municipality or county, but this fact must be referenced by name or letter designation in
the adoption ordinance. However, the provisions of the codes referenced in this section which
concern the qualification, removal, dismissal, duties, responsibilities of, and administrative
Sanmple EnablingActs 65
procedures for all building officials, deputy building officials, chief inspectors, other inspectors, and
assistants do not apply unless they have been adopted by the municipal or county governing body,
(B.) The governing body of a county may not enforce that portion of a nationally recognized fire
prevrention code it has adopted vishinci may regulate outdoor burning for forestry, vildlife, .and
agricultural purposes as regulated by the South Carolina Forestry Commission.
(C) A residential buildiing is considered in compliance with the Building Envelope Requiremnts of
the Model Energy Code if:
(1) it is built in compliance w ith prescriptive standards issued by the South Carolina Residential
Builders Commission, in consultation with the State Energy Office, based on computer models
of the Model Energy Code including, but not limited to, options developed by Pacific
Northwest National Laboratories for South Carolina's climatic zones, or
(2) if double pane or single pane with storm windows are used for window glass and in the
case of ceilings, exterior walls, floors wvith crawl space, and heating and air conditioning duct
work, the determination of the minimum thermal resistance ratings (R-value) is:
(a) R-30 for ceilings, except for ceiling/roof com,
binationls, which must be at least R-19;
(b) R-13 for exterior walls;
(c) R-19 for floors with crawl space;
(d) R-6, or the installed equivalent, for heating and air conditioning duct work not located
in conditioned space.
Section 6-9-60. (A) Municipalities and counties may adopt by reference only those provisions of the
latest editions of the following nationally known codes and the standards referenced in the codes
for regulation of construction which directly relate to building and safety standards vithin their
respective jurisdiction s: Standard Housing Code, Standard Existing Building Code, Standard
Swinmirg Pool Code, the Standard Excavation and Grading Code, as published by the Southern
Building Code Congress International, Inc., and the One and Two Family Dwelling Code, as
published by the Council of American Building Officials. The appendixes of the codes provided in
this section may be adopted as needed by a municipality or county, but this fact must be referenced
by name or letter designation in the adopting ordinance. However, the provisions of the codes
referenced in this section which concern the qualification, removal, dismissal, duties,
responsibilities of, and administrative procedures for all building officials, deputy building officials,
chief inspectors, other inspectors, and assistants do not apply unless they have been adopted by the
municipal or county governing body If a county or municipality adopts the One and Tv-o Family
DIelling Code, the One and TIXo Family Di 'elling Code shall take precedence over the Standard
Building Code for dwe gs as defined in the Standard Building Code. If a municipality or county
contends that the codes authorized by this chapter do not meet its needs due to local physical or
climatological conditions, the variations and modifications must be submitted for approval to the
South Carolina Building Codes Council of fifteen members which is established in this section.
(B) Members of the council must be appointed by the Governor for terms of four years each and
until a successor is appointed and qualifies. The council shall consist of (1) an architect registered in
South Carolina, (2) a municipal administrator, manager, or elected official, (3) a county
administrator, manager, or elected official, (4) a representative of the electrical industry who is
either an engineer or master electrician registered in South Carolina, (5) a general contractor
licensed in South Carolina, (6) a residential home builder licensed in South Carolina, (7) a disabled
person, (8) a representative of the mechanical and gas industries who is either an engineer
registered in South Carolina or a master mechanic, (9) a representative of the plumbing industry
who is either an engineer registered in South Carolina or a master plumber, ('l0) a representative
Appendix B
66
South Carolina
designated by the State Engineer of the Budget and Control Board, (11) a structural engineer
registered in South Carolina, (12) a representative of the general public who is not in the practice of
home or safety inspection, construction, or building, who does not have any financial interest in
these professions, and who does not have any immediate family member in these professions, (13)
a representative designated by the State Fire Marshal, (14) a representative from the Manufactured
Housing Institute of South Carolina who shall serve as a nonvoting member, and (15) a
representative designated by the Director of the State Energy Office of the Budget and Control
Board who shall serve as a nonvoting member. A vacancy must be filled in the manner of the
original appointment for the unexpired portion of the term. The primary function of the council is
to decide to what extent a jurisdiction may vary from the series of codes listed in this chapter in the
establishment of construction standards. The council shall monitor the adoption of building codes
by municipalities and counties to ensure compliance with this chapter. Members of the council shall
receive mileage, subsistence, and per diem as provided for other state boards, committees, or
commissions for attendance at board meetings called by the chairman. The council shall elect from
its members a chairman, vice-chairman, and secretary. The council shall adopt regulations
consistent with this chapter. Meetings may be called by the chairman on his own initiative and
must be called by him at the request of three or more members of the council. All members must be
notified by the chairman in writing of the time and place of meeting at least seven days in advance
of the meeting. Seven members constitute a quorum. All meetings are open to the public. At least
two-thirds vote of those members in attendance at the meeting constitutes an official decision of the
council.
Section 6-9-65. (A) For purposes of this section, 'farm structure' means a structure which is
constructed on a farm, other than a residence or a structure attached to it, for use on the farm
including, but not limited to, barns, sheds, and poultry houses, but not public livestock areas. For
purposes of this section, 'farm structure' does not include a structure originally qualifying as a
'farm structure' but later converted to another use.
(B) The governing body of a county or municipality may not enforce that portion of a nationally
recognized building code it has adopted which regulates the construction or improvement of a
farm structure. The standards published by the Federal Emergency Management Agency for the
National Flood Insurance Program shall apply.
(C) The provisions of this section do not apply unless before constructing a farm structure the
person owning the property on which the structure is to be constructed files an affidavit with the
county or municipal official responsible for enforcing the building code stating that the structure is
being constructed as a farm structure. The affidavit must include a statement of purpose or
intended use of the proposed structure or addition.
(D) This section does not affect the authority of the governing body of a county or municipality to
issue building permits before the construction or improvement of a farm structure.
Section 6-9-70. (A) A person found to be in violation of the building codes or regulations adopted
pursuant to the provisions of this chapter must be fined, by civil fine, in an amount not more than
two hundred dollars. Each day the violation continues is a separate offense. However, this
provision does not prevent a county or municipality from exercising its authority to impose by
ordinance criminal sanctions of a fine of not more than two hundred dollars or imprisonment for
not more than thirty days in lieu of the civil penalties required by this provision.
(B) However, before being charged with a second violation, an individual must be given seven
calendar days to remedy the violation if in the opinion of the inspector or official it does not place
the public in imminent danger or create an emergency situation. Each day a violation continues is a
separate offense if the inspector or official determines the situation places the public in imminent
Sample EnablingActs 6:7
danger or creates an emergency situation. In a situation wvhich does not place the public in
imminent danger or create an emergency situation, if in the opinion of the inspector or official no
substantial progress is made toward correcting the violation by the end of the seventh calendar day,
each day the violation continues thereafter is considered a separate offense.
Section 6-9-80. For a violation of the building codes or regulations adopted pursuant to this.
chapter, the local building officials, mumicipal or county attorneys, or other appropriate authorities
of a political subdivision, or an adjacent or neighboring property owner who would be damaged by
the violation, in addition to other remedies, may apply for injunctive relief, mandamus, or other
appropriate proceeding.
Section 6-9-90. Notw~ithstanding any other provision of law, the governing body of a county or
municipality may impose fees necessary to implement and continue the programs required by this
chapter upon a vote of a simple majority of the governing body unless (1) a super majority vote is
required by local ordinance, or (2) prior to December 1, 1998, the General Assembly specifically
amends, repeals, or otherwise affects this law by direct reference to this section or (3) after
November 30, 1998, the General Assembly provides otherwise by law.
Section 6-9-100. The provisions of this chapter are cumulative to other local ordinances and do not
limit the authority of counties or municipalities.
Section 6-9-110. (A) A county, municipal, or other local ordinance or regulation which requires the
purchase or acquisition of a permit, license, or other device utilized to enforce any building
standard does not apply to a:
(1) state department, institution, or agency permanent improvement project, construction
project, renovation project or property; or
(2) school district facility, permanent improvement project construction project, renovation
project, or property -owinch is reviewed and approved by the State Department of Education;
except that the State Department of Education or a local school district may direct that the local
ordinance or regulation apply to a particular facility, project, or property.
(B) After successful completion of all requirements, the State Fire Marshal shall certify personnel of
the State Engineer's Office of the Budget and Control Board designated by the State Engineer. The
certified personnel and deputy state fire marshals, including resident state fire marshals, have
exclusive jurisdiction over state buildings, including schools, in the exercise of the powers and
jurisdictional authority of the State Fire Marshal under Sections. 23-9-30, 23-940, and 23-9-50.
S ection 6-9-1290. Nothing in this chapter affects vater or sews er systems in this State.
Section 6-9-130. Buildings must be inspected according to the codes in effect for the locality on the
date of the issuance of the building permit.
Building Codes Council membership, terms
SECTION 2. Members of the South Carolina Building Codes Council serving in office on the
effective date of this act w'hoom the Governor determines possess those qualifications required by
Section 6-9-60 and, if applicable, represent an entity required to be represented by Section 6-9-60
shall continue to serve until their current terms of office expire. The terms of all other members
shall expire on the 'effective date of this act at which time, their successors shall be appointed by the
Governor in the manner provided by Section 6-9-60.
Building Codes Enforcement Officers
68 Appendix B
South Carolina
SECTION 3. Title 6 of the 1976 Code is amended by adding:
CHAPTER 8
Building Codes Enforcement Officers
Section 6-8-10. When used in this chapter 'building codes enforcement officer' means a person
employed by a public entity who is primarily responsible for the overall inspection or
enforcement of applicable building code requirements within the jurisdiction of the employer.
Section 6-8-20. (A) The South Carolina Building Codes Council is responsible for the
registration of building codes enforcement officers pursuant to this chapter. The council or its
designated representatives may conduct hearings and proceedings required by law or
considered necessary by the council. The Department of Labor, Licensing and Regulation shall
employ and supervise personnel necessary for the administration of this chapter. The council
may promulgate regulations for the proper enforcement of this chapter.
(B) The council shall keep a record of its hearings and proceedings and a register of applications
for the certificates of registration showing the date of application, name, qualifications, and
addresses of the business and residence of the applicant and whether the certificate is approved
or denied. The council shall publish biannually during odd-numbered years the applications in
the register which are approved. Applicants and registrants shall notify the council of changes
in required information within ten days of a change.
Section 6-8-30. (A) Certificates of registration may be issued without examination to building
codes enforcement officers employed in codes enforcement on the effective date of this chapter
only for the position and locality held at the time of registration pursuant to this section. This
registration is valid for two years and may be renewed.
(B) Upon initial employment by a political subdivision, an individual must be granted a
provisional certificate of registration without examination which is valid for one year from the
date of issuance. The provisional certificate of registration may not be renewed.
Section 6-8-40. No person may practice as a codes enforcement officer in this State unless
registered as provided in this chapter. A person violating the provisions of this chapter is guilty
of a misdemeanor and, upon conviction, must be fined not more than two hundred dollars or
imprisoned not more than thirty days. Each day the violation continues is a separate offense.
Section 6-8-50. If the council has reason to believe that a person is violating or intends to violate
a provision of this chapter, in addition to other remedies, it may order the person immediately
to refrain from the conduct. The council may apply to the court of common pleas for an
injunction restraining the person from the conduct. The court may issue a temporary injunction
ex parte not to exceed ten days and upon notice and full hearing may issue other orders in the
matter it considers proper. No bond is required of the council by the court as a condition to the
issuance of an injunction or order pursuant to this section.
Section 6-8-60. (A) A person desiring to be registered as a building codes enforcement officer as
required by this chapter shall apply upon a form prescribed by the council.
(B) An applicant shall furnish satisfactory proof to the council of valid certification by a
recognized code organization or testing agency in the general or special capacity in which he
desires to be registered. Special certificates of registration authorize the registrant to practice in
the named specialty only. General certificates of registration are not restricted. The council or its
designated representatives shall review the guidelines employed by the organization or agency
Sample EnablingActs 69'
in order to determine their continued compatibility with the requirements considered by the
council to be consistent with this chapter.
(C) A local jurisdiction may impose additional requirements upon a person employed as a building
codes enforcement officer in its jurisdiction.
Section 6-8-70. (A) A certificate of registration is valid for two years and expires on July first of each
odd-numbered year unless renewed before that date. Renewal of all registrations must be based
upon a determination by council of the applicant's participation in approved continuing education
programs. The council must promulgate regulations setting forth the continuing education
requirements for building codes enforcement officers. A person failing to make timely renewal of
his certificate is not registered unless qualified in the manner provided for new registrants and may
not practice until registered in accordance with this chapter.
(B) Funding for the certification, training, and continuing education of building code 'enforcement
officers must be appropriated to the Department of Labor, Licensing and Regulation in the manner
provided in Section 38-7-35.
Building 'Codes Enforcement Officers' training
SECTION 4. The 1976 Code is amended by adding:
Section 38-7-35. (A) The first one hundred and seventy-five thousand dollars of the revenue
collected annually pursuant to Section 38-7-30 must be transferred to the Department of Labor,
Licensing and Regulation for the purpose of implementing the training, certification, and
continuing education program for building codes enforcement officers as provided in Section 6-8-70
and by lace
(B) The Department of Labor, Licensing and Regulation shall report annually to the Chairman of
the Senate Finance Committee and the Chairman of the House Ways and Means Committee
detailing actual program expenditures including, but not limited to, the number of instructors
employed, the number of training sessions conducted, and the number of certifications issued. This
report must be submitted to the respective chairmen no later than January fifteenth of each year.
(C) One hundred thousand dollars of the revenue collected annually pursuant to Section 38-7-30
must be transferred to the Department of Insurance for the purpose of implementing the program
as provided in Section 38-75480.
(D) Subsection (C) of this section ceases to be of any force or effect after June 30, 2002.
Advisory committee to Building Codes Council
SECTION 5. Chapter 75 of Title 38 of the 1976 Code is amended by adding:
ARTICLE 8
Advisory 'Committee to the Director and the South Carolina
Building Codes Council and Loss Mitigation Grant Program
Section 38-75-47'0. The Director of Insurance shall appoint an advisory committee to the director
and the South Carolina Building Codes Council to study issues associated with the development of
strategies for reducing loss of life and mitigating property losses due to hurricane, earthquake, and
fire. The advisory committee also must consider the costs associated with these strategies to
individual property owners. The advisory 'committee must include:
(1) one representative from Clemson UnivTersity involved with rwind engineering;
Appendix B
70
South Carolina
(2) one representative from an academic institution involved with the study of earthquakes;
(3) one representative from the Department of Insurance;
(4) one representative from an insurer writing property insurance in South Carolina;
(5) one representative from the Department of Commerce;
(6) one representative from the Federal Emergency Management Association;
(7) one representative from the Homebuilders Association;
(8) one representative from the Manufactured Housing Institute of South Carolina;
(9) one representative from the State Fire Marshal's office;
(10) two at-large members appointed by the director; and
(11) two at-large members appointed by the Governor.
Members shall serve for terms of two years and shall receive no per diem, mileage, or subsistence.
Vacancies must be filled in the same manner as the original appointment.
Within thirty days after its appointment, the advisory committee shall meet at the call of the
Director of Insurance. The advisory committee shall elect from its members a chairman and a
secretary and shall adopt rules not inconsistent with this chapter. Meetings may be called by the
chairman on his own initiative and must be called at the request of three or more members of the
advisory committee. All members shall be notified by the chairman of the time and place of the
meeting at least seven days in advance of the meeting. All meetings must be open to the public. At
least two-thirds vote of those members in attendance at the meeting shall constitute an official
decision of the advisory committee.
Section 38-75-480. (A) There is established within the Department of Insurance a loss mitigation
grant program. Funds may be appropriated to the grant program, and any funds so appropriated
shall be used for the purpose of making grants to local governments or for the study and
development of strategies for reducing loss of life and mitigating property losses due to hurricane,
earthquake, and fire. Grants to local governments shall be for the following purposes:
(1) implementation of building code enforcement programs including preliminary training of
inspectors; and
(2) conducting assessments to determine need for and desirability of making agreements to
provide enforcement services pursuant to Section 6-9-60.
Funds may be appropriated for a particular grant only after a majority affirmative vote on each
grant by the advisory committee.
(B) The Department of Insurance may make application and enter into contracts for and accept
grants in aid from federal and state government and private sources for the purposes of:
(1) implementation of building code enforcement programs including preliminary training of
inspectors;
(2) conducting assessments to determine need for and desirability of making agreements to
provide enforcement services pursuant to Section 6-9-60; and
(3) study and development of strategies for reducing loss of life and mitigating property losses
due to hurricane, earthquake, and fire.
71
Sample EnablingActs
Exemptions to building codes requirements
SECTION 6. Chapter 10 of Title 6 of the 1976 Code is not applicable in counties or municipalities
which have fully implemented building codes as required in Section 6-9-10, as amended by this act.
Public policy as to building codes
SECTION 7. The public policy of South Carolmia is to maintain reasonable standards of construction
in buildings and other structures in the State consistent with the public health, safety, and welfare
of its citizens. To secure these purposes, a person performing building codes enforcement must be
certified by the South Carolina Building Codes Council, and this act is necessary to provide for
certification.
To clarify the intent of the General Assembly and address questions which might arise or have
arisen with respect to provisions of the nationally known codes which have been or are in place,
only those portions or provisions of the nationally known building and safety codes which relate to
building standards and safety are binding upon any state or local governmental entity or agency
which adopts the building and safety codes authorized or required by Chapter 9 of Title 6 of the
South Carolina Code of Laws.
Time effective
SECTION 8. This act takes effect upon approval by the Governor.
Approved the 13th day of June, 1997.
LegislativePrinting-LPITR @http://vwzv.pitr.state.sc.is
Appendix B
72
South Carolina
CODE OF LAWS OF SOUTH CAROLINA 1976 ANNOTATED
CHAPTER 9.
BUILDING, HOUSING, ELECTRICAL, PLUMBING AND GAS CODES
6-9-10. Authorization for and scope of codes and regulations.
The governing body of any incorporated municipality or county in this State is authorized to adopt
building, housing, electrical, plumbing, and gas codes relating to the construction, livability,
sanitation, erection, equipment, alteration, repair, occupancy, or removal of buildings and structures
located within its jurisdiction and promulgate regulations to implement the codes.
The codes and the implementing regulations may embrace matters such as the preparation and
submission of plans and specifications; the issuance of permits; standards governing the kind,
quality, and performance of materials, equipment, and workmanship; the establishment of fire
zones; fireproofing; means of egress and ingress; floor-area-per-occupant requirements; sanitary
facilities and proceedings for the correction of unsafe, unsanitary, or inadequate structures.
The codes and regulations may only be adopted by reference to national, regional, or model
codes listed in 6-9-60 and to certain special provisions approved by the South Carolina Building
Code Council. Nothing in these codes or regulations may extend to or be construed as being
applicable to the regulation of the design, construction, location, installation, or operation of
equipment or facilities used in the generation, transmission, distribution, or communication of a
public or private utility or electric or telephone membership cooperatives, other than buildings
used primarily for offices or residential housing nor to equipment or facilities already subject to
regulation by the Liquefied Petroleum Gas Board.
HISTORY: 1977 Act No. 173 1; 1984 Act No. 481, 2, eff June 20, 1984.
EFFECT OF AMENDMENT
The 1977 amendment inserted the words "lightning protection systems design and installation," in the first paragraph of this
section.
The 1984 amendment made grammatical changes in this section and deleted "lightning protection systems design and
installation" codes from the list of codes in the first paragraph.
6-9-20. Regional agreements.
County and municipal bodies are authorized to establish regional agreements with other political
subdivisions of the State to issue building permits and enforce building, electrical, plumbing, gas,
housing, and other codes in order to more effectively carry out the provisions of this chapter.
HISTORY: 1984 Act No. 481, 2, eff June 20, 1984.
EDITOR'S NOTE
Section 2, Act 481 of 1984 purported to amend this section. It is, however, identical with the contents appearing in the bound
volume.
6-9-30. Employment of inspectors and assistants.
The county and municipal governing bodies may appoint building, electrical, plumbing, gas, and
housing inspectors and employ other assistants as they may consider necessary and may prescribe
fees or charges for permits and inspections.
HISTORY: 1984 Act No. 481, 2, eff June 20, 1984.
EFFECT OF AMENDMENT
The 1984 amendment made grammatical changes which did not affect the substance of this section.
73
73
Sample EnablingActs
6-9-40. Notice and hearing required before adoption of code or regulations.
Prior to adoption of any of the codes or regulations permitted in this chapter, the gov ing body
shall hold public hearings on the codes or regulations. Not less than fifteen days' notice of the time
and place of the hearings must be published in a newspaper of general circulation in the cournty
HISTORY: 1984 Act No. 481, eff June 20, 1984.
2,
EFFECT OF AMENDMENT
The 1984 amendment made grammatical changes which did not affect the substance of this section.
6-9-50. Area of application of county codes.
County governing bo dies have the authority to establish codes and promulgate regulations under
this chapter for the entire unincorporated area of the county or for any specified portion of the
unincorporated area.
HISTORY: 1984 Act No. 481, 2, eff June 20,1984.
EFFECT OF AMENDMENT
The 1984 amendment made grammatical changes which did not affect the substance of this section.
6-9-60. Adoption and modification of certain standard codes by reference; creation,
membership, meetings and functions. of South Carolina Building Code Council.
Municipalities or counties are authorized to adopt by reference only the latest editions of the
following nationally known codes for regulation of construction within their respective
jurisdictions: Standard Building Code, Standard Housing Code, Standard Gas Code, Standard
Plumbing Code, Standard One and Txvo Family Dwelling Code, Standard Mechanical Code,
Standard Fire Prevention Code, Standard Swimming Pool Code, Standard Excavation and Grading
Code, National Electrical Code, and National Fire Protection Association Gas Codes.
Should any city, town, or county contend that the codes authorized by this chapter do not meet
its needs due to local physical or climatological conditions, the -variationsand modifications must be
submitted for approval to a South Carolina Building Code Council of thirteen members whicch is
established in this section. Memrrbers of this council must be appointed by the Governor. The council
shall include an architect, representatives from the Municipal Association of South Carolina the
South Carolina Association of Counties, the Building Officials' Association of South Carolina, South
Carolina Building Trade Council, a representative from the electric utility industry, a representative
of the Carolinas Branch of the Associated General Contractors of America, Inc., representatives from
the gas, electric, and plumbing industries, a representative of the Home Builders Association of
South Carolina, a handicapped person, and the Chief Engineer of the State Budget and Control
Board. At least one member of the council must be a member of each of the congressional districts,
to be appointed, if positions become vacant, in the order provided below or as resignations occur.
The primary function of the council is to decide to what extent any jurisdiction may vary from the
series of codes listed in this section in the establishment of standards. The council shall monitor the
adoption of building codes by cities and counties to insure compliance wi th this chapter.
Of the members initially appointed by the Governor, four shall serve for terms of two years,
four shall serve for four years, and five shall serve for terms of six years. After the initial
appointment, all appointments are for terms of six years.
Members of the council shall receive mileage, subsistence, and per diem as provided for other
state boards, committees, or commissions for attendance at board meetings cal led by the chairman.
The council shall elect from its appointive members a chairman and secretary. The council shall
adopt regulations not inconsistent with this chapter.
Meetings may be called by the chairman on his own initiative and must be called by him at the
request of three or more members of the council. All members must be notified by the chairman in
writing of the time and place of meeting at least seven days in advance of the meeting. Seven
members constitute a quorum. All meetings are open to the public. At least two-thirds vote of those
members in attendance at the meeting constitutes an official decision of the council.
HISTORY: 1977 Act No. 173 2; 1978 Act No. 629; 1984 Act No 481, 2;1993 Ad No 181 64, eff February 1, 1994.
Appendix B
74
South Carolina
EFFECT OF AMENDMENT
The 1977 amendment substituted the words ", National Fire Protection Association Gas Codes, Underwriters' Laboratories
Lightning Protection Code and Lightning Protection Institute Installation Code" for the words "and National Fire Protection
Association Gas Codes" in the first paragraph of this section.
The 1978 amendment substantially rewrote this section.
The 1984 amendment added the last sentence of the second paragraph, rewrote the fourth paragraph, and also made
grammatical changes which did not affect the substance of this section.
The 1993 amendment consolidated the former five paragraphs of this section into a single paragraph; and deleted
provisions regarding the Division of General Services of the State Budget and Control Board providing personnel for
enforcement of these laws and regulations and for carrying out the duties of the council.
6-9-65. Regulation of construction or improvement of farm structure; authority to issue
building permits.
(A) For purposes of this section, "farm structure" means a structure which is constructed on a farm,
other than a residence or a structure attached to it, for use on the farm, including but not limited to,
barns, sheds, and poultry houses, but not public livestock areas. For purposes of this section, "farm
structure" does not include a structure originally qualifying as a "farm structure" but later
converted to another use.
(B) The governing body of a county or municipality may not enforce that portion of any
nationally recognized building code it has adopted which regulates the construction or
improvement of a farm structure. Standards for flood plain management by the Southern Building
Code Congress International apply.
(C) The provisions of this section do not apply unless prior to constructing a farm structure the
person owning the property on which the structure is to be constructed files an affidavit with the
county or municipal official responsible for enforcing the building code stating that the structure is
being constructed as a farm structure. The affidavit must include a statement of purpose or
intended use of the proposed structure or addition.
(D) This section does not affect the authority of the governing body of a county or municipality
to issue building permits prior to the construction or improvement of a farm structure.
HISTORY: 1987 Act No. 24 1, eff April 13, 1987.
6-9-70.Penalties for violation of code or regulation.
The violation of any of the codes or regulations adopted pursuant to the provisions of this chapter
is declared to be a misdemeanor, and any person violating the codes or regulations is guilty of a
misdemeanor and, upon conviction, must be punished by a fine not to exceed one hundred dollars
or imprisonment of not more than thirty days. Each day the violation continues is a separate
offense.
HISTORY: 1984 Act No. 481, 2, eff June 20, 1984.
EFFECT OF AMENDMENT
The 1984 amendment made grammatical changes which did not affect the substance of this section.
6-9-80. Mandamus and injunctive relief for violation of code or regulation.
In case of any violation of or proposed violation of the codes or regulations adopted pursuant to
this chapter, the South Carolina Building Code Council, the building inspectors, municipal or
county attorneys, or other appropriate authority of the political subdivision, or any adjacent or
neighboring property owner who would be damaged by the violation may, in addition to other
remedies, apply for injunctive relief, mandamus, or other appropriate proceeding to prevent,
correct, or abate the violation or threatened violation.
HISTORY: 1984 Act No. 481, 2, eff June 20,1984.
EFFECT OF AMENDMENT
Sample Enabling Acts 75
The 1984 amendment added "the South Carolina Building Code Council" and also made grammatical changes which did not
affect the substance of this section.
6-9-90. Appropriations and expenditures.
County or municipal governing bodies are -authorized to appropriate and expend funds to
implement the provisions of this chapter.
HISTORY: 1984 Act No. 481, 2, eff June 20,1984.
EDITOR'S NOTE
Section 2, Act 481 of 1984, purported to amend this section. It is, however, identical with the provisions appearing in the parent
volume.
6-9-100. Provisions, of chapter shall be cumulative; use of other codes adopted prior to effective
date.
The provisions of this chapter are cumulative to other authority of counties and municipalities and
do not limit the authority of counties and municipalities.
A city or county that has adopted any of the national, regional, or model codes or any other
code prior to May 1, 1982, may continue its use.
HIUSTORY: 1982 Act No. 351, 3, eaf Mtlay 10, 1982; 1984 Act No. 481, 2, eaf Tune 20, 1984.
EFFECT 'OF AMENDMENT
The 1982 amendment substituted 'Itay 1,1982" for "Jtune 21,1972" in the second paragraph.
The 1984 amendment made grarnmatical changes which did not affect the substance of this section.
6-9-110. Inapplicability to state property of local ordinances which require permits, etc, as
mean s of enforcing building standards.
In no event may any county, municipal, or other local ordinance or regulation whluich requires the
purchase or acquisition of a permit, license, or other device utilized to enforce any building
standard be construed to apply to any state department, institutio n, or agency permanent
improvement project, construction project, renovation project, or property
HISTORY: 1982Act No. 466 Part H 28, effJune 15, 1982; 1984A.ct No. 481, 2, effJune 20, 1984; 1986ActNo 347, 6, eff
March 4, 1986.
EFFECT OF AMENDMENT
The 1984 amendment made grammnatical changes which did not affect the substance of this section, including deletion of the
phrase "Notwvithstanding any other provision of law," from the first sentence.
The 1986 amendment deleted a provision relative to inapplicability to state projects of local ordinances which prescribe
building standards, deleted a provision relative to mutually agreed upon inspections of state--owvned buildings by local
officials, and made grammatical changes.
Appendix B
76
Utah
CHAPTER 56
UTAH UNIFORM BUILDING STANDARDS ACT
Effective May 5, 1997
58-56-1. Short title.
This chapter is known as the "Utah Uniform Building Standards Act."
58-56-2. Chapter administration.
The provisions of this chapter shall be administered by the Division of Occupational
and Professional Licensing.
58-56-3. Definitions.
In addition to the definitions in Section 58-1-102, as used in this chapter:
(1) "ANSI" means American National Standards Institute, Inc.
(2) "Code(s)" means the NEC, building code, mechanical code, or plumbing code as defined in this
section and as applied in context.
(3) "Commission" means the Uniform Building Code Commission created under this chapter.
(4) "Compliance agency" means an agency of the state or any of its political subdivisions which
issue permits for construction regulated under the codes, or any other agency of the state or its
political subdivisions specifically empowered to enforce compliance with the codes.
(5) "Factory built housing" means manufactured homes or mobile homes.
(6) "HUD code" means the Federal Manufactured Housing Construction and Safety Standards Act.
(7) "Installation standard" means the standard adopted and published by the National Conference
of States on Building Codes and Standards (NCSBCS), for the installation of manufactured homes
titled "The Standard for Manufactured Home Installations", the accompanying manufacturer's
instructions for the installation of the manufactured home, or such equivalent standard as adopted
by rule.
(8) "Local regulator" means each political subdivision of the state which is empowered to engage in
the regulation of construction, alteration, remodeling, building, repair, and other activities subject
to the codes adopted pursuant to this chapter.
(9) "Manufactured home" means a transportable factory built housing unit constructed on or after
June 15, 1976, according to the Federal Home Construction and Safety Standards Act of 1974 (HUD
Code), in one or more sections, which, in the traveling mode, is eight body feet or more in width or
40 body feet or more in length, or when erected on site, is 400 or more square feet, and which is
built on a permanent chassis and designed to be used as a dwelling with or without a permanent
foundation when connected to the required utilities, and includes the plumbing, heating,
air-conditioning, and electrical systems. All manufactured homes constructed on or after June 15,
1976, shall be identifiable by the manufacturer's data plate bearing the date the unit was
manufactured and a HUD label attached to the exterior of the home certifying the home was
manufactured to HUD standards.
(10) "Factory built housing set-up contractor" means an individual licensed by the division to set
up or install factory built housing on a temporary or permanent basis. The scope of the work
included under the license includes the placement and or securing of the factory built housing on a
permanent or temporary foundation, securing the units together if required, and connection of the
utilities to the factory built housing unit, but does not include site preparation, construction of a
permanent foundation, and construction of utility services to the near proximity of the factory built
housing unit. If a dealer is not licensed as a factory built housing set up contractor, that individual
must subcontract the connection services to individuals who are licensed by the division to perform
those specific functions under Title 58, Chapter 55, Utah Construction Trades Licensing Act.
(11) "Mobile home" means a transportable factory built housing unit built prior to June 15, 1976, in
accordance with a state mobile home code which existed prior to the Federal Manufactured
Housing and Safety Standards Act (HUD Code).
77
Sample EnablingActs
(12) "Modular unit" means a structure built from sections which are manufactured in accordance
with the construction standards adopted pursuant to Section 58-564 and transported to a building
site, the purpose of which is for human habitation, occupancy or use.
(13) "NEC" means the National Electrical Code.
(14) 'Opinion" means a written, nonbinding and advisory statement issued by the commission
concerning an interpretation of the meaning of the codes or the application of the codes in a specific
circumstance issued in response to a specific request by a party to the issue.
(15) "State regulator" means an agency of the state which is empowered to engage in the regulation
of construction, alteration, remodeling, building, repair, and other activities subject to the codes
adopted pursuant to this chapter.
(16) "Unlawvful conduct" as defined in Section 58-1-501 includes:
(a) engaging in the sale of factory built housing without being registered with the division as a
dealer, unless the sale is exempt under Section 58-56-16; and
(b) selling factory built housing within the state as a dealer without collecting and remitting to
the division the fee required by Section 58-56-17.
58-56-4. Adoption of building codes - Am. endments.
(1) As used in this section:
(a) "Agricultural use' means a use which relates to the tilling of soil and raising of crops, or
keeping or raising domestic animals, for the purpose of commercial food production.
(b) "Not for human occupancy" means use of a structure for purposes other than protection or
comfort of human beings, but allows people to enter the structure for maintenance and repair
and for the care of livestock, crops, or equipment intended for agricultural use which are kept
there.
(2) Subject to the provisions of Subsections (4) and (5), the following are adopted as the construction
standards to which the state and each political subdivision of this state shall adhere in building
construction, alteration, remodeling and repair, and in the regulation of building construction,
alteration, remodeling and repair:
(a) a building code promulgated by a nationally recognized code authority;
(b) the National Electrical Code promulgated by the National Fire Protection Association;
(c) a plumbing code adopted by a nationally recognized code authority; and
(d) a mechanical code promulgated by a nationally recognized code authority
(3) The division, in collaboration with the commission, shall adopt by rule the edition of the NEC or
code and specific edition of the codes described in Subsections (l)(a), (c) and (d) to be used as the
standard and may adopt by rule successor editions of any adopted code.
(4) The division, in collaboration with the commission, may adopt amendments to the adopted
codes to be applicable to the entire state or within a political subdivision only in accordance with
58-56-7.
(5) Except in a residential area, a structure used solely in conjunction- with agriculture use, and not
for human occupancy, is exempted from the permit requirements of any building code adopted by
the division, how 'ever, unless otherwise exempted, plumbing, electrical, and mechanical permits
may be required when that work is included in the structure.
58-56-5. Building Code Commission - Composition of Commission - Commission duties and
responsibilities.
(1) There is established a Uniform Building Code Commission to advise the division 4ith respect to
the division's responsibilities in administering the codes under this chapter.
(2) The commission shall be appointed by the executive director e'ho shall submit his nominations
to the governor for confirmation or rejection. If a nominee is rejected, alternative names shall be
submitted until confirmation is receiv'ed. Following confirmation by the governor, the appointment
shall be made.
(3) The Commission shall consist of eleven members who shall be appointed in accordance with the
following:
(a) one member shall be from among candidates nominated by the Utah League of Cities and
Towvs and the Utah Association of Counties;
Appendix B
78
Utah
(b) one member shall be a licensed building inspector employed by a political subdivision of
the state;
(c) one member shall be a licensed professional engineer;
(d) one member shall be a licensed architect;
(e) one member shall be a fire official;
(f) three members shall be contractors licensed by the state, of which one shall be a general
contractor, one an electrical contractor, and one a plumbing contractor;
(g) two members shall be from the general public and have no affiliation with the construction
industry or real estate development industry; and
(h) one member shall be from the Division of Facilities Construction Management, Department
of Administrative Services.
(4) (a) Except as required by Subsection (b), as terms of current commission members expire, the
executive director shall appoint each new member or reappointed member to a four-year term.
(b) Notwithstanding the requirements of Subsection (a), the executive director shall, at the time of
appointment or reappointment, adjust the length of terms to ensure that the terms of commission
members are staggered so that approximately half of the commission is appointed every two years.
(5) When a vacancy occurs in the membership for any reason, the replacement shall be appointed
for the unexpired term.
(6) No commission member may serve more than two full terms, and no commission member who
ceases to serve may again serve on the commission until after the expiration of two years from the
date of cessation of service.
(7) A majority of the commission members shall constitute a quorum and may act in behalf of the
commission.
(8) (a) (i) Members who are not government employees shall receive no compensation or benefits
for their services, but may receive per diem and expenses incurred in the performance of the
member's official duties at the rates established by the Division of Finance under Sections
63A-3-106 and 63A-3-107.
(ii) Members may decline to receive per diem and expenses for their service.
(b) (i) State government officer and employee members who do not receive salary, per diem, or
expenses from their agency for their service may receive per diem and expenses incurred in the
performance of their official duties from the board at the rates established by the Division of
Finance under Sections 63A-3-106 and 63A-3-107.
(ii) State government officer and employee members may decline to receive per diem and expenses
for their service.
(c) (i) Local government members who do not receive salary, per diem, or expenses from the entity
that they represent for their service may receive per diem and expenses incurred in the
performance of their official duties at the rates established by the Division of Finance under
Sections 63A-3-106 and 63A-3-107.
(ii) Local government members may decline to receive per diem and expenses for their service.
(9) The commission shall annually designate one of its members to serve as chair of the
commission. The division shall provide a secretary to facilitate the function of the commission and
to record its actions and recommendations.
(10) The duties and responsibilities of the commission are to:
(a) recommend to the director the adoption by rule of the edition of the NEC, and the specific
codes and editions of the codes described in Subsections 58-56-4(1)(a), (c) and (d) adopted
pursuant to this chapter;
(b) recommend to the director the adoption by rule of amendments to the NEC, the building
code, the mechanical code, and plumbing code adopted pursuant to this chapter;
(c) offer an opinion regarding the interpretation of or the application of any of the codes
adopted pursuant to this chapter upon a formal submission by a party to the matter in question
which submission must clearly state the facts in question, the specific code citation involved
and the position taken by all parties;
(d) act as an appeals board as provided in 58-56-8(3);
79
Sample EnablEngActs
(e) establish advisory peer committees on either a standing or ad hoc basis. to advise
the commission with respect to building code matters, including a committee to
advise the commission regarding health matters related to the UPC; and
(f) assist the division in overseeing code related training in accordance with Section
58-56-9 of this chapter.
58-56-6. Building codes - Division duties and responsibilities.
(1) The division shall administer the adoption and amendment of the NEC, the building
*code, the mechanical, code, and the plumbing code adopted under Section 58-56-4
pursuant to this chapter; but,shall have no responsibility or duty to conduct inspections
to determine compliance with the codes, issue permits or assess building permit fees.
(2) Administration of the NEC, the building code, the mechanical code, and the plumbing
code adopted under Section 58-56-4 by the division shall include:
(a) receiving recommendations from the commission and thereafter adopting by rule
the editions of the codes and amendments to the codes;
(b) maintaining and publishing for reference on a current basis the editions of the
code in force and amendments thereto; and
(c) receiving requests for amendments and opinions from the comnissi-on, scheduling
appropriate hearings and publishing the amendments to the codes and the opinions
of the commission with respect to interpretation and application of the codes.
58-56-7. Code amendments - Commission recommendations - Division duties and
responsibilities.
(1) The division, with the commission, shall establish by rnle the procedure and manner
under which requests for amendments to codes shall be:
(a) filed with the division; and
(b) recommended or declined for adoption.
(2) The division shall accept from any local regulators, state regulators, state agencies
involved with the construction and design of buildings, the contractors, plumbers, or
electricians licensing boards, or from recognized construction-related associations a
request for amendment to the NEC, the building code, the mechanical code, or the
plumbing code adopted under Section 58-56-4.
(3) The division or the commission on its own initiative may make recommendations to
the commission for amendment to the NEC, the building code, the mechanical code, or
the plumbing code adopted under Section 58-56-4.
(4) On May 15 and November 15 of each calendar year, or the first government working
day thereafter if either date falls on a weekend or government holiday, the division shall
convene a public hearing, as a part of the rulemaking process, before the commnission
concerning requests for amendment of the codes, recommended by the division and
commission to be adopted by rule. The hearing shall be conducted in accordance with the
rules of the commission.
(5) WAlithin 15 days following completion of the hearing under Subsection (4) or (5), the
commission shall provide to the division a written recommendation concerning each
amendment.
(6) The division shall consider the recommendations and promulgate amendments by
rule in accordance with Title 63, Chapter 46a, Utah Administrative Rulemaking Act and as
prescribed by the director.
(7) The decision of the division to accept or reject the recommendation of the commission
shall be made within 15 days after receipt of the recommendation.
(8) All decisions of the division pertaining to adoption of a code edition or amendments to
any code, which are contrary to recommendations of the commission, may be overridden
by a two-thirds vote of the commission according to a procedure to be established by rule.
(9) (a) Amendments with statewide application:
(i) shall be effective on the January 1 or July 1 immediately following the public
hearing; or
(ii) may be effective prior to the dates in Subsection (i) if designated by the division
and the commission as necessary for the public health, safety, and welfare.
80 Appendix B
Utah
(b) Amendments with local application only shall be effective on a date to be determined by the
division and the commission.
(c) In making rules required by this chapter, the division shall comply with he provisions of Title
63, Chapter 46a, Administrative Rulemaking Act, the provisions of that chapter shall have control
over this section in case of any conflict.
(10) The commission shall study the necessity of an engineer's stamp on all building permits. This
study shall be reported to the Business and Labor Interim Committee by November 1996.
58-56-8. Compliance with codes - Responsibility for inspections - Appeals.
(1) The responsibility for inspection of construction projects and enforcement of compliance with
provisions of the codes shall be with the compliance agency having jurisdiction over the project
and the applicable codes.
(2) A finding by a compliance agency that a licensed contractor, electrician, or plumber has
materially violated the provisions of a code in a manner to jeopardize the public health, safety, and
welfare and failed to comply with corrective orders of the compliance agency shall be furnished in
writing to the division by the compliance agency. It shall be the responsibility of the compliance
agency to conduct a primary investigation to determine that, in fact, there has been a material
violation of the provisions of the code jeopardizing the public interest and provide the report of
investigation to the division.
(3) Each compliance agency shall establish a method of appeal by which a person disputing the
application and interpretation of a code may appeal and receive a timely review of the disputed
issues in accordance with provisions of the National Electrical Code, the building code, the
mechanical code, or the plumbing code adopted under Section 58-56-4. If a compliance agency
refuses to establish a method of appeal, the commission shall act as the appeals board and conduct
a hearing within 45 days. The findings of the commission shall be binding. An appeals board
established under this section shall have no authority to interpret the administrative provisions of
the codes nor shall the appeals board be empowered to waive requirements of the codes.
58-56-8.5 Building Inspector Licensing Board.
(1) There is created a Building Inspector Licensing Board consisting of four building inspectors and
one member of the general public.
(2) The board shall be appointed and serve in accordance with Section 58-1-201.
(3) The duties and responsibilities of the board shall be in accordance with Sections 58-1-202
through 58-1-203. In addition, the board shall designate one of its members on a permanent or
rotating basis to:
(a) assist the division in reviewing complaints concerning the unlawful or unprofessional
conduct of a licensee; and
(b) advise the division in its investigation of these complaints.
(4) A board member who has, under Subsection (3), reviewed a complaint or advised in its
investigation is disqualified from participating with the board when the board serves as a
presiding officer of an administrative proceeding concerning the complaint.
58-56-9. Qualifications of inspectors - Contract for inspection services.
(1) Effective July 1, 1993, all inspectors employed by a local regulator, state regulator, or
compliance agency to enforce provisions of the codes adopted pursuant to this chapter shall:
(a) meet minimum qualifications as established by the division in collaboration with the
commission or be certified by a nationally recognized organization which promulgates codes
adopted under this chapter, or pass an examination developed by the division in collaboration
with the commission;
(b) be currently licensed by the division as meeting those minimum qualifications; and
(c) be subject to revocation or suspension of their license or may be placed on probation if
found guilty of unlawful or unprofessional conduct.
(2) A local regulator, state regulator, or compliance agency may contract for the services of a
licensed inspector not regularly employed by the regulator or agency.
Sample EnablingActs al
(3) (a) The division shall use the monies received in Subsection (4) to provide education
regarding the codes and code amendments to:
(i) building inspectors; and
(ii) individuals engaged in construction-related trades.
(b) All funding available for the building inspector's education program shall be
nonlapsing.
(4) Each compliance agency shall charge a 1% surcharge on all building permits issued and
shall transmit 80% of the amount collected to the division to be utilized by the division to
fulfill the requirements of Subsection (3). The surcharge shall be deposited as a dedicated
credit.
58-56-10. Repealed.
58-56-11. Standards for specialized buildings.
(1) This chapter shall not be implied to repeal or otherwise affect authorities granted to a
state agency to make or administer standards for specialized buildings, as provided in Title
26, Chapter 21, Title 62A, Chapter 2, and Title 64, Chapter 13, or authorities granted to a
state agency by statute to make or administer other special standards. In the event of a
conflict between such special standards and codes adopted pursuant to this chapter, the
special standards shall prevail.
(2) The provisions of this chapter do not apply to the administration of the statutes
described in Subsection (1).
58-56-12. Factory built housing units.
Factory built housing unit construction, permit issuance for set-up, set-up and set-up
inspection shall be in accordance with the following:
(1) Manufactured homes:
(a) manufactured homes constructed, sold, or set-up in the state shall be constructed in
accordance with the HUJD code;
(b) manufactured homes set-up in the state shall be installed in accordance with the
"installation standard" defined in Section 58-56-3;
(c) the authority and responsibility for the issuance of building permits for the
modification or set-up of manufactured homes w%7ithin a political subdivision of the state
shall be with the local regulator within that political subdivision; and
(d) the inspection of modifications to or set-up shall be conducted and approvals given
by the local reg uator withi-n the political subdivision in which the set-up takes place.
(2) Mobile homes:
(a) mobile homes sold or set-up in the state shall be constructed in accordance with the
mobile home construction code in existence in the state in which the mobile home was
constructed at the time the mobile home was constructed;
(b) mobile homes set-up in the state shall be installed in accordance with the
"installation standard" defined in Section 58-56-3;
(c) the authority and responsibility for the issuance of building permits for the
modification of or set-up of mobile homes within a political subdivision of the state
shall be with the local regulator within that political subdivision; and
(d) the inspection of, modification to, or set-up shall be conducted and approvals given
by the local regulator within the political subdivision in which the set-up takes place.
58-56-13. Modular units.
Modular unit construction, set-up, issuance of permits for construction or set-up, and set-up
shall be in accordance with the following:
(1) construction and set up shall be in accordance with the building standards adopted
pursuant to Section 58-564, or equivalent standards adopted by rule;
(2) the responsibility and authority for plan review and issuance of permits for construction,
modification, or set-up shall be that of the local regulator of the political subdivision in
which the modular unit is to be set-up;
82Appendix B
82
Utah
(3) the inspection of the construction, modification of, or set-up of a modular unit to determine
conformance with the provisions of this chapter and the issuance of approvals shall be the
responsibility of the local regulator in the political subdivision in which the modular unit is to be
set-up or is set-up; and
(4) nothing in this section shall preclude a local regulator from contracting with a qualified third
party for the inspection or plan review provided in this section, or the state from entering into an
interstate compact for third party inspection of the construction of modular units.
58-56-14. Modification of factory built housing units and modular units.
(1) Any modification to factory built housing units shall be made in accordance with the following:
(a) Prior to set-up, modification to a manufactured home or mobile home prior to installation or
set-up of the unit for habitation shall be made in accordance with the HUD code.
(b) After set-up:
(i) modification to a manufactured home or mobile home after installation or set-up of the
unit for habitation, which modification does not include the addition of any space to the
existing unit or the attachment of any structure to the existing unit shall be made in
accordance with the HUD code; and
(ii) modification to a manufactured home or mobile home after installation or set-up of the
unit for habitation, which modification includes the addition of any space to the existing
unit or the attachment of any structure to the unit shall be made as follows:
(A) modifications to the existing unit shall be in accordance with the HUD code; and
(B) additional structure outside of the existing unit shall be in accordance with the Utah
Uniform Building Standards Act.
(2) Any modification to modular housing units shall be made in accordance with the Utah Uniform
Building Standards Act.
58-56-15. Factory built housing and modular units - Division responsibility.
The division:
(1) shall maintain current files with respect to the HUD code and amendments thereto with respect
to manufactured homes and the "installation standard" defined in Section 58-56-3 with respect to
installation of factory built housing; and will provide at reasonable cost such information to all
compliance agencies, local regulators, or state regulators requesting such information;
(2) shall provide qualified personnel to advise compliance agencies, local regulators, and state
regulators regarding the standards for construction and set-up, construction and set-up inspection,
and additions or modifications to factory built housing;
(3) may regularly inspect the work of all factory built housing manufacturers in the state during the
construction process to determine compliance of the manufacturer with the applicable standards of
the HUD code or the American National Standards Institute, Inc. or equivalent standards adopted
by rule; and upon a finding of any substantive deficiency furnish a written finding of such
deficiency to the standards agency;
(4) is hereby designated as the state administrative agency and shall act as such for all purposes
under the provisions of the HUD code; and
(5) may inspect the work of all modular unit manufacturers in the state during the construction
process to determine compliance of the manufacturer with the Utah Uniform Building Standard Act
for those units to be installed within the state; and upon a finding of any substantive deficiency
issue a corrective order to the manufacturer with a copy to the local regulator in the state's political
subdivision in the unit is to be installed.
58-56-16. Registration of dealers.
(1) Each person engaged in the sale of factory built housing in the state shall annually register with
the division as a "dealer" and shall pay an annual registration fee of $15.
(2) Subsection (1) does not apply to:
Sample EnablingActs a3
(a) a person not regularly engaged in the sale of factory built housing who is selling a unit he
owns for his own account;
(b) a principal broker licensed under Title 61, Chapter 2, Division of Real Estate; or
(c) a sales agent or associate broker licensed under Title 61, Chapter 2, Division of Real Estate,
sells factory built housing as an agent for, and under the supervision, of the licensed principal
broker with ivhom he is affiliated.
58-56-17. Fees on sale - Escrow agents - Sales tax.
*() Each dealer shall collect and remit a fee of $75 to the division for each factory built home the
dealer sells that has not been permanently affixed to real property. The fee shall be payable within
30 days following the close of each calendar quarter for all units sold during that calendar quarter.
The fee shall be deposited in a restricted account as provided in Section 58-56-17.5.
(2) Any principal real estate broker, associate broker or sales agent exempt from registration as a
dealer under Section 58-56-16 who sells a factory built home that has not been affixed to real
property shall close the sale only through a qualified escrow agent in this state registered with the
Insurance Department or the Department -ofFinancial Institutions.
(3) Each escrow agent through which a sale is closed under Subsection (2) shall remit all required
sales tax to the state.
58-56-17.5. Factory Building Housing Fees Restricted Account.
(1) There is created within the General Fund a restricted account know,%n as 'Factory Built Housing
Fees Account.'
(2) (a) The restricted account shall be funded from the fees the dealer collects and remits to the
division for each factory built home the dealer sells as provided in Subsection 58-56-17(1).
(b) The division shall deposit all monies collected under Subsection 58-56-17(l) in the restricted
account.
(c) The restricted account shall be used to pay for education and enforcement of the Uniform
Building Standards Act, including investigations and administrative actions and the funding of
additional employees to the amount of the legislative appropriation.
(d) The restricted account may accrue interest which shall be deposited into the restricted account.
58-56-18. Repealed.
UTAH UNIFORM BIJILDING STANDARDS ACT
Tite 58, Chapter 56
Utah Code Annotated 1953
As Amended by
Session Lawvs of Utah 1997
Issued Mway 5,1997
Division of Occupational and Professional Licensing
State o' Utah
84
| en |
converted_docs | 940143 | **DA 07-2156**
**May 24, 2007**
**NOTICE OF DOMESTIC SECTION 214 AUTHORIZATIONS GRANTED**
WC Docket Nos. 07-75, and 07-83
The applications listed in this notice have been granted pursuant to the
Commission's streamlined procedures for domestic section 214 transfer of
control applications, 47 C.F.R. § 63.03. The Wireline Competition Bureau
has determined that grant of these applications serves the public
interest.[^1] For purposes of computation of time for filing a petition
for reconsideration or application for review, or for judicial review of
the Commission's decision, the date of "public notice" shall be the
release date of this notice.[^2]
1\. Domestic Section 214 Application Filed for the Transfer of Control
of Eschelon Telecom, Inc., to Integra TelCom Holdings, Inc. WC Docket
No. 07-75, DA 07-1814 (rel. Apr. 23, 2007).
**Effective Grant Date: May 24, 2007**
2\. Domestic Section 214 Application Filed for the Transfer of Control
of Telephone Service Company to Hanson Communications, Inc., WC Docket
No. 07-83**,** DA 07-1811 (rel. Apr. 23, 2007).
**Effective Grant Date: May 24, 2007**
For further information, please contact Tracey Wilson-Parker at
202-418-1394, Competition Policy Division, Wireline Competition Bureau.
> **-- FCC --**
[^1]: *Implementation of Further Streamlining Measures for Domestic
Section 214 Authorizations*, Report and Order, 17 FCC Rcd 5517,
5529, para. 22 (2002).
[^2]: *Id.*; *see* 47 C.F.R. § 1.4 (Computation of time).
| en |
converted_docs | 501105 | # Chinese Spring Wheat Meiosis Spike cDNA Library (D-W Choi, TJ Close lab, UC Riverside, 1 May 2000) (TAcDNA0015; TA_CEg; TA026E1X)
**Source of RNA:**
- Plant: hexaploid wheat (*Triticum aestivum* L. cv Chinese Spring)
- Type of tissue: young spikes before anthesis
- Growth conditions: unstressed plants; University of Nebraska,
Lincoln (MM Shah with K Gill)
- Total RNA purification: hot phenol method. Nucleic Acid Res (1989)
17:2362.
- PolyA purification method: PolyATrack mRNA Isolation System IV
(Promega)
- cDNA synthesis method: cDNA Synthesis Kit (Stratagene)
**Name of vector: Uni-ZAP XR**
\- Uni-ZAP XR vector allows *in vivo* excision of the pBluescript
phagemid
**Description of Inserts:**
- cDNAs were directionally cloned with *Eco*RI on the 5' and *Xho*I on
the 3' end
- cDNAs larger than 0.5 kb were selected by size fractionation via gel
filtration
**Primary λ Phage Library:**
- cDNA ligation: 100 ng of cDNA and 1 μg of vector
> \- Packaging: Gigapack III Gold Packaging Extract (Stratagene)
- Lambda ZAP yield: 2.0 x 10^7^ pfu in 0.5 ml.
**Mass Excision Phagemid Library:**
- Complexity: 1 x 10^6^ λ ZAP pfu (25 μl of primary library) added to
975 μl SM Buffer
- Host cells: XL1-Blue-MRF\' (Stratagene), \~ 5 x 10^7^ log-phase
cells in 1 ml 10 mM MgSO~4~
- Helper phage: ExAssist (Stratagene), \~1 x 10^9^ pfu; 100 μl
- Addition of adsorbed mixture of above ingredients to 38 ml LB
medium, 37°C
- Mass excision performed for \~3 hrs and centrifuged to create a cell
pellet and supernatant
- Supernatant heated at 70°C for 20 min; this is the "Low
Amplification" library (L).
- Cell pellet resuspended in 40 ml fresh LB and grown at 37°C for an
additional 16 \~ 20 hr.
- Supernatant heated at 70°C for 20 min; this is the "High
Amplification" library (H).
- Titered on SOLR (Stratagene) cells:
---------------------------- --------------------- --------------------
Low Amplification High Amplification
Phagemid yield (cfu/ml) 5.4 x 10^5^ 1.0 x 10^9^
Total phagemid yield 2.16 x 10^7^ 4.0 x 10^10^
(cfu/40ml)
Amplification (cfu/plaque) 21.6 4.0 x 10^4^
Percent dark blue colonies \~ 3.7 \~ 3.0
---------------------------- --------------------- --------------------
- Non-recombinants: 0 of 34 randomly chosen clones contained no insert
- Insert size distribution:
| en |
converted_docs | 987360 | **Before the**
**Federal Communications Commission**
**Washington, D.C. 20554**
+----------------------------------+---+------------------------------+
| In re Application of | * | File No. DO95960 |
| | * | |
| GLM Communications, Inc. | ) | |
| | * | |
| Request for Waiver to Modify | * | |
| Station KNJK775, | | |
| | * | |
| Warrensville Township, Ohio | * | |
| | ) | |
| | * | |
| | * | |
| | | |
| | * | |
| | * | |
| | ) | |
| | * | |
| | * | |
| | | |
| | * | |
| | * | |
| | ) | |
| | * | |
| | * | |
| | | |
| | * | |
| | * | |
| | ) | |
| | * | |
| | * | |
| | | |
| | * | |
| | * | |
| | ) | |
| | * | |
| | * | |
+----------------------------------+---+------------------------------+
**ORDER ON RECONSIDERATION**
**Adopted: August 3, 2000 Released: August 7, 2000**
By the Chief, Public Safety and Private Wireless Division, Wireless
Telecommunications Bureau:
# I. INTRODUCTION {#i.-introduction .unnumbered}
1. On December 29, 1999, GLM Communications, Inc. (GLM) petitioned for
reconsideration[^1] of the November 29, 1999 action by the Public
Safety and Private Wireless Division, Licensing and Technical
Analysis Branch (Branch) denying GLM's request for a waiver of the
Commission's Rules and dismissing its associated application to
modify its license for 800 MHz Specialized Mobile Radio Service
(SMR) Station KNJK775, Warrensville Township, Ohio.[^2] For the
reasons discussed herein, we dismiss GLM's *Petition*.
## II. BACKGROUND
2\. On December 4, 1996, GLM filed an application to modify the license
for its one-channel SMR Station KNJK775, in the Warrensville Township of
Ohio.[^3] Specifically, GLM sought authority to add to Station KNJK775
six co-located conventional Business Category channels, licensed as
community repeaters to various end-users but operated by GLM. The
end-user licensees consented to the proposed consolidation. GLM proposed
to create a seven-channel trunked SMR system, on which it would provide
trunked commercial service to GLM's customers. In order to convert the
Business channels to SMR use, GLM needed a waiver of Section 90.621(e)
of the Commission's Rules, which does not permit inter-category sharing
by SMR applicants.[^4]
3\. On August 13, 1997, GLM filed a request for special temporary
authority (STA) to use the six channels in its proposed trunked SMR
system during the pendency of its application and waiver request. On
August 21, 1997, the Commercial Wireless Division granted an STA for a
period of 180 days, and subsequently granted four extensions of the STA,
the most recent of which expired on February 23, 2000.
4\. On November 29, 1999, the Branch dismissed GLM's application and
denied its waiver request,[^5] on the grounds that GLM had a reasonable
alternative under the Commission's current Rules.[^6] On December 29,
1999, GLM requested reconsideration of the Branch's decision. The
*Petition* was addressed to the Chief of the Branch, which is located in
Gettysburg, Pennsylvania. GLM argues that the Branch did not adequately
explain why its waiver request could not be granted, and did not address
the effect of the Branch's decision on GLM's continued operations under
its STA.
## III. DISCUSSION {#iii.-discussion .unnumbered}
5\. Section 405 of the Communications Act, as amended, sets forth the
requirements that a petitioner must satisfy before we may consider the
petitioner's pleadings on reconsideration.[^7] Section 405, as
implemented by Section 1.106(f) of the Commission's Rules, requires that
a petition for reconsideration be filed within thirty days of the
release date of the Commission's action.[^8] Furthermore, Section
1.106(i) states that a petition for reconsideration must be submitted to
the Secretary, Federal Communications Commission, Washington, D.C.
20554.[^9]
6\. The Commission maintains different offices for different purposes,
and persons filing documents with the Commission must take care to
ensure that their documents are filed at the correct location as
specified in the Commission's Rules.[^10] A document is filed with the
Commission upon its receipt at the location designated by the
Commission.[^11] Accordingly, based on the plain language of the
Commission's Rules, a petition for reconsideration submitted to the
FCC's Gettysburg, Pennsylvania office is not properly filed.[^12]
7\. We conclude that GLM did not satisfy the filing requirement in
accordance with Section 1.106 of the Commission's Rules when it
submitted its *Petition* to the Branch in Gettysburg, Pennsylvania
instead of submitting it to the FCC's Office of the Secretary in
Washington, D.C. Because the thirty-day window for the filing of a
petition for reconsideration, as determined under Section 1.4 of the
Commission's Rules,[^13] closed on December 29, 1999, the *Petition* was
not received by the Secretary within the thirty-day period, and no
request for waiver of the requisite filing location was submitted, we
conclude that the *Petition* should be dismissed.[^14] Therefore, we
dismiss GLM's Petition for Reconsideration.
8\. In addition to reconsideration of the Branch's decision, GLM seeks
clarification of the status of its STA[^15] and, in the event
reconsideration is not granted, requests that the STA be extended an
additional ninety days to allow the users to relocate to an alternative
system.[^16] The status of the STA is that it expired on February 23,
2000, and GLM did not request renewal pending resolution of its petition
for reconsideration. Moreover, because the STA has expired, there is
nothing before us to be extended.[^17]
**IV. ORDERING CLAUSES**
9\. Accordingly, **IT IS ORDERED** that, pursuant to Section 4(i) of the
Communications Act of 1934, as amended, 47 U.S.C. § 154(i), and Sections
1.106 and 1.925 of the Commission's Rules, 47 C.F.R. §§ 1.106, 1.925,
the Petition for Reconsideration filed by GLM Communications, Inc., on
December 29, 1999 **IS DENIED**.
10\. This action is taken under delegated authority pursuant to Sections
0.131 and 0.331 of the Commission's Rules, 47 C.F.R. §§ 0.131, 0.331.
FEDERAL COMMUNICATIONS COMMISSION
D'wana R. Terry Chief, Public Safety and Private Wireless Division
Wireless Telecommunications Bureau
[^1]: GLM Communications, Inc., Petition for Reconsideration (filed Dec.
29, 1999) (*Petition*).
[^2]: Letter from Mary Shultz, Chief, Licensing and Technical Analysis
Branch, Public Safety and Private Wireless Division, to Eugene
Maliszewskyj, Director of Engineering and Licensing -- Private
Radio, Blooston, Mordkofsky, Jackson and Dickens, dated Nov. 29,
1999 (*Branch Letter*).
[^3]: GLM's initial application was designated as File No. DO63361. In
1997, a new file number, DO95960, was assigned when the application
was returned to the Commission with the required frequency
coordination. File No. DO63361 was deleted from the Division's
database as duplicative. GLM requests that both file numbers be
retained pending a final determination. *Petition* at 1 n.1. We deny
this request because we believe that the retention of two file
numbers for this matter would not in any way enhance GLM's interests
and instead would create administrative uncertainty.
[^4]: *See* 47 C.F.R. § 90.621(e).
[^5]: *Branch Letter* at 1.
[^6]: *See* 47 C.F.R. § 90.151(a) (1996) (currently codified at 47
C.F.R. § 1.925(b)(3)).
[^7]: 47 U.S.C. § 405.
[^8]: 47 U.S.C. § 405; 47 C.F.R. § 1.106(f).
[^9]: 47 C.F.R. § 1.106(i).
[^10]: 47 C.F.R. § 0.401.
[^11]: 47 C.F.R. § 1.7; First Auction of Interactive Video and Data
Service (IVDS) Licenses, Request for Waiver of Applications
Deadline, *Memorandum Opinion and Order*, 11 FCC Rcd 1134, 1135
(1996); Complaints Regarding Cable Programming Service Prices,
*Amended Order on Reconsideration*, 10 FCC Rcd 12778, 12780 n.14
(CSB 1995).
[^12]: *See*, *e.g.*, Memorandum of Agreement between the Federal
Communications Commission and Elkins Institute, Inc., *Order on
Reconsideration*, 14 FCC Rcd 5080 (WTB 1999) (determining that a
facsimile copy to a division office neither complied with the
Commission's Rules nor ameliorated the late filing with the
Secretary's office); Columbia Millimeter Communications, LP, *Order
on Reconsideration*, 14 FCC Rcd 2782 (WTB PSPWD 1999) (finding that
a petition for reconsideration sent to the Commission's lock box at
Mellon Bank neither complied with the Commission's Rules nor
ameliorated the late filing with the Secretary's office), *aff'd*,
*Order on Reconsideration*, 15 FCC Rcd 10251 (WTB PSPWD 2000).
[^13]: 47 C.F.R. § 1.4(b)(5).
[^14]: Moreover, we note that the Branch correctly denied GLM's waiver
request. GLM argues that the alternative proffered by the Branch --
incorporating the SMR channel into a seven-channel trunked Business
community repeater through the use of a common trunking control
device -- is not reasonable because it is more cumbersome
administratively than GLM's proposed SMR system. We find
unpersuasive GLM's suggestion that an alternative which accomplishes
the desired purpose is unreasonable merely because it would not be
as easy to administer. *Cf.* State of South Carolina, *Order*, 13
FCC Rcd 22447, 22449 ¶ 5 (WTB PSPWD 1998).
[^15]: Petition at 3, 5.
[^16]: *Id.* at 5 n.3.
[^17]: *See* 47 C.F.R. § 1.931(a) (requests to extend STAs must be filed
ten days prior to the expiration date of the existing STA).
| en |
converted_docs | 809832 | **DA 01-1072**
**April 25, 2001**
**IN THE MATTER OF EXTENSION OF THE FIVE-YEAR**
**BUILD-OUT PERIOD FOR BTA AUTHORIZATION**
**HOLDERS IN THE MULTIPOINT DISTRIBUTION SERVICE**
**Comment Date: May 9, 2001**
**Reply Comment Date: May 16, 2001**
By the Chief, Mass Media Bureau:
1\. Pursuant to Sections 1.3 of the Commission's rules, 47 C.F.R. § 1.3,
the Mass Media Bureau ("Bureau"), on its own motion, hereby seeks
comment on a proposal to extend the current five-year build-out
requirement imposed upon Basic Trading Area ("BTA") authorization
holders in the Multipoint Distribution Service ("MDS") by two years. In
March 1996, the Commission completed its auction of the remaining unused
MDS spectrum with the expectation that such spectrum would be used for
the provision of wireless cable services. The United States was divided
into 493 BTAs and these markets were auctioned to the highest bidders.
Pursuant to 47 C.F.R. § 21.930, BTA authorization holders have five
years from the grant date of the initial BTA authorization to construct,
develop and expand MDS station operations in their respective protected
service areas. Specifically, within five years of the grant, the BTA
authorization holder must construct MDS stations to provide signals that
are capable of reaching at least two-thirds of the population of the
service area, excluding the populations within protected service areas
of incumbent stations. The purpose of this requirement was to ensure
that service was promptly delivered to the public. *See* 47 U.S.C. §
309(j)(4)(B).[^1] On August 16, 1996, the Commission granted 334 of the
493 BTA authorizations to 54 different entities. These BTA authorization
holders will be the first entities to reach the five-year build-out date
of August 16, 2001. By this Public Notice, we seek comment on our
proposal to extend the five-year build-out requirement set forth in 47
C.F.R. § 21.930 by two years, as described below.
2\. Traditionally, MDS spectrum has been used to deliver multichannel
video programming services similar to cable television. As noted above,
the Commission auctioned 493 BTAs for the provision of these wireless
cable services.[^2] Since the 1996 auction, the MDS industry has been
rapidly evolving. In July 1996, the Commission's *Digital* *Declaratory
Ruling* permitted licensees to digitize their MDS spectrum.[^3] In
October 1996, the Commission allowed MDS operators to use their spectrum
for high-speed digital data applications, including Internet access.[^4]
3\. In March 1997, the Wireless Cable Association International,
Inc.,[^5] along with over 100 participants, petitioned the Commission to
grant the industry the right to use MDS and Instructional Television
Fixed Service ("ITFS") spectrum for two-way services. Two-way
authorization would effectively enable voice, video, and data over the
spectrum. In 1998, the Commission approved the use of two-way
transmissions on MDS and ITFS frequencies. In the two-way proceeding,
the Commission decided to: (1) permit both MDS and ITFS licensees to
provide two-way services on a regular basis; (2) permit increased
flexibility on permissible modulation types; (3) permit increased
flexibility in spectrum use and channelization, including combining
multiple channels to accommodate wider bandwidths, dividing 6 MHz
channels into smaller bandwidths, and channel swapping; (4) adopt a
number of technical parameters to mitigate the potential for
interference among service providers and to ensure interference
protection to existing MDS and ITFS; (5) simplify and streamline the
licensing process for stations used in cellularized systems; and (6)
modify the ITFS programming requirements in a digital environment.[^6]
4\. In the initial filing window for two-way service, which was held
August 14 - 18, 2000, MDS and ITFS licensees filed approximately 2,267
applications. On April 6, 2001, the Bureau released its first Public
Notice announcing the grant of 1,024 of these applications.[^7] The
Bureau will continue to grant additional two-way applications and on
April 16, 2001, the Bureau began the transition to the rolling one-day
filing window procedure.[^8]
5\. Section 21.930(c)(1) of the Commission\'s rules, 47 C.F.R. §
21.930(c)(1), provides that within five years of the grant of a BTA
authorization, the authorization holder must construct MDS stations to
provide signals pursuant to Section 21.907, 47 C.F.R. § 21.907, that are
capable of reaching at least two-thirds of the population of the
applicable service area, excluding the populations within protected
service areas of incumbent stations. In addition, sixty days prior to
the end of the five-year build-out period, the BTA authorization holder
must file with the Commission proof that demonstrates that the holder
has met the build-out requirements. 47 C.F.R. § 21.930(c)(2).
6\. The build-out benchmarks were originally established in order to
ensure that BTA authorization holders would promptly deliver their
anticipated video programming service to the public. We propose to
extend the five-year build-out requirement as set forth in Section
21.930(a)(1) of the Commission\'s rules, 47 C.F.R. § 21.930(a)(1), by
two years. In light of the service rule changes promulgated in the
*Two-Way Order*, the timing of the initial filing window, the recent
two-way application grants allowing BTA authorization holders to provide
broadband service, the forthcoming grants of other pending two-way
applications, and the upcoming August 16, 2001 build-out deadline for
many BTAs, we tentatively conclude that extension of the five-year
build-out requirement by two years for all BTAs will promote the
maximization of efficient and effective use of this service. We believe
that it would be inequitable to require authorization holders to follow
build-out criteria applicable to rules governing wireless cable
operations since many of them are now providing high-speed broadband
services. We tentatively conclude that requiring BTA authorization
holders to meet the five-year construction build-out requirement would
be unreasonable, would not promote efficient use of the spectrum, and
would be contrary to the public interest.
7\. Accordingly, by this Public Notice, we propose to extend the
five-year build-out requirement by two years. [^9] For MDS BTA
authorization holders whose build-out requirement ends on August 16,
2001, the new build-out deadline would be August 16, 2003. For BTA
authorization holders whose build-out requirement ends after August 16,
2001, the new build-out deadline would be two years from the date that
the original five-year deadline was to have taken place.
8\. Persons making oral *ex parte* presentations are reminded that
memoranda summarizing the presentations must contain summaries of the
substance of the presentations and not merely a listing of the subjects
discussed. More than a one or two sentence description of the views and
arguments presented is generally required. *See* 47 C.F.R. § 1.1206(b).
Other rules pertaining to oral and written *ex parte* presentations in
permit-but disclose proceedings are set forth in Section 1.1206(b) of
the Commission\'s rules, 47 C.F.R. § 1.1206(b).
9\. Comments must be filed on or before May 9, 2001, and reply comments
by May 16, 2001. All documents filed in this proceeding should indicate
in the caption that this matter is before the Mass Media Bureau and
reference Public Notice DA No. 01-1072. Comments may be filed via the
Commission\'s Electronic Comment Filing System (ECFS) via the Internet
to http:/ www.fcc.gov/e - file/ecfc.html\>. In completing the
transmittal screen, commenters should include their full name and Postal
Service mailing address, and reference Public Notice DA No. 01-1072.
Parties may also submit electronic comments by Internet e-mail. To get
filing instructions for e-mail comments, commenters should send an
e-mail to: ecfs@fcc.gov, including \"get form \<your e-mail
address\>\'\' in the body of the message. A sample form and directions
will be sent in reply. Interested parties who choose to file by paper
must file an original and four copies of their comments with the Office
of the Secretary, Federal Communications Commission, 445 Twelfth Street,
S.W., Room TW-A325, Washington, D.C. 20554. In addition, parties should
send: one paper copy to Brad Lerner, Room 2-A733, Mass Media Bureau,
Federal Communications Commission, 445 Twelfth Street, S.W., Washington,
D.C. 20554; one paper copy to the Reference Information Center, Federal
Communications Commission, 445 Twelfth Street, S.W., 20554; and one
paper copy and one diskette copy to ITS, Room CYB-400, 445 Twelfth
Street, S.W., Washington, D.C. 20554.
For further information, contact Brad Lerner of the Mass Media Bureau,
at 202-418-7066 (email: blerner@fcc.gov).
\- FCC -
[^1]: The build-out requirement was also enacted to deter the
warehousing of spectrum. *See In the Matter of Amendment of Parts 21
and 74 of the Commission's Rules with Regard to Filing Procedures in
the Multipoint Distribution Service and in the Instructional
Television Fixed Service*, 10 FCC Rcd 9589, 9613 (1995).
[^2]: Although a BTA holder has rights to transmit throughout its
authorized area, incumbent licensees whose authorizations predate
the 1996 auction continue to operate within any BTA as before the
auction. *See* 47 C.F.R. § 21.902.
[^3]: *See In the Matter of Request for Declaratory Ruling on the Use of
Digital Modulation by Multipoint Distribution Service and
Instructional Television Fixed Service Stations*, 11 FCC Rcd 18839
(1996).
[^4]: *See Public Notice, The Mass Media Bureau Implements Policy for
Provision of Internet Service on MDS and Leased ITFS Frequencies*,
11 FCC Rcd 22419 (1996).
[^5]: The organization subsequently changed its name to the Wireless
Communications Association International, Inc.
[^6]: *See In the Matter of Amendment of Parts 21 and 74 to Enable
Multipoint Distribution Service and Instructional Television Fixed
Service Licensees to Engage in Fixed Two-Way Transmissions ("Two-Way
Order")*, 13 FCC Rcd 19112 (1998), *recon.*, 14 FCC Rcd 12764
(1999), *further recon.*, 15 FCC Rcd 14566 (2000).
[^7]: *Public Notice*, Report No. 337 (MMB April 6, 2001).
[^8]: *Public Notice*, DA 01‑751 (MMB March 26, 2001).
[^9]: We note that in similar proceedings, Nextel subsidiary FCI 900
("Nextel") and NeoWorld License Holdings, Inc. ("NeoWorld") filed
respective expedited waiver requests with the Wireless
Telecommunications Bureau regarding the five-year construction
period for 900 MHz major trading area ("MTA") licenses. Nextel asks
for extension of the deadline from August 12, 2001 to August 12,
2004, for all 900 MHz MTA licensees, while NeoWorld requests an
extension until December 31, 2002. Commission rules require MTA
licensees to provide coverage to at least two-thirds of the
population within five years of licenses being granted. Nextel and
NeoWorld assert that they need waivers because appropriate digital
equipment is not yet available and that deployment of that broadband
service would be delayed if they had to build analog 900 MHz systems
to meet the August 12 construction deadline. The Wireless
Telecommunications Bureau accepted comments on the waiver requests
through February 1, 2001 and reply comments were due on February 8,
2001. *See Public Notice, Wireless Telecommunications Bureau Seeks
Comment of FCI 900, Inc.'s Expedited Request for 3-year Extension of
900 MHz Band Construction Requirements*, DA 01-121 (Released January
18, 2001); *Public Notice, Wireless Telecommunications Bureau Seeks
Comment on NeoWorld License Holdings, Inc.'s Request for Waiver of
900 MHz Band Construction Requirements and Petition for Declaratory
Ruling*, DA 01-122 (Released January 18, 2001).
| en |
markdown | 359836 | # Presentation: 359836
## Cassini Tour Selection
- Dr. Kevin R. Grazier
- IS/SPE
- With Significant Viewgraph Assistance By:
- Linda Spilker
- Cassini Deputy Project Scientist
- July 26, 2005
## History
- Tour 89-01 was discussed in the Cassini Announcement of Opportunity (AO)
- Discussions about creating a “new tour” began at very first PSG meeting (in December, 1990)
- Tour 92-01 was created after Cassini descope.
- Very Galileo-like in its character.
- mostly updated tour 89-01 for new Cassini arrival date
- Linda J. Spilker
- 3/3/04
## Tour 92-01
- Characteristics of 92-01
- 63 Orbits
- 33 Titan flybys
- 12 inbound, 21 outbound, 10 solar/earth occulations
- 4 targeted icy satellite flybys: Enceladus, Dione, Rhea, Iapetus
- 12 non-targeted flybys (d<50,000 km)
- Saturn/ring occultations: 5 earth and sun during first 2 occultation sequences
- Linda J. Spilker
- 3/3/04
## Tour Trade Study
- PSG and Project agreed to a tour design trade study, scheduled between 1993 and 1996
- Discipline Working Groups (Atmospheres, MAPS, Satellites, Rings) developed a list of tour geometry objectives and guidelines
- DWG tour priorities generated over several PSG meetings
- Finalized by DWGs at ESTEC PSG in May 1995
- Tour design tool (STOCK) provided to teams
- With software and excel spreadsheets Cassini scientists could design a Titan-only tour
- New orbit rotation technique identified (Titan 180 transfer)
- Linda J. Spilker
- 3/3/04
## Tour Design Considerations
- Titan flyby strategy
- Tour redesign implications of change in minimum altitude, number of flybys and occultations
- Extent of CCW rotation at beginning of tour
- Number of moderately inclined (20-50 deg) orbits and location during tour
- Extent of CW rotation toward magnetotail
- Maximum value of high inclination orbits
- Saturn and Rings sun/earth occultation geometry strategy
- Icy satellite flyby strategy for given tour rotation/inclination profile
- Tour strategy relative to horseshoe/tadpole trapped particle risk regions
- Ground system requirements
- Linda J. Spilker
- 3/3/04
## Selecting a Tour
- Orbiter workshop held in July, 1995
- 3 IS-led interdisciplinary teams evaluated 8 classes of tours (38 Titan-only tours)
- Identified driving requirements and suggested possible compromise tours
- At end of tour design trade study, 17 Titan-only tours (T1 – T17) were available for further study
- Linda J. Spilker
- 3/3/04
## Some Tours Looked Rather Familiar
- Linda J. Spilker
- 3/3/04
## Others.... Didn’t
- Linda J. Spilker
- 3/3/04
## Selecting a Tour
- At 8/96 PSG, added one class of tour for further study– T18
- Three tours quickly emerged as favored:
- Linda J. Spilker
- 3/3/04
## T2
- Quickly eliminated largely because of low science return.
- Linda J. Spilker
- 3/3/04
## T9
- LOVED by MAPS, Rings, Titan (two 180 transfers; 51 Titan flybys)!
- Too difficult operationally (too many consecutive 16-day orbits)
- Linda J. Spilker
- 3/3/04
## The Winner Is: T18
- At 3/99 PSG selected T18-1 as final tour
- Less science return than T9-1
- Still difficult operationally, but we decided to “bite the bullet”.
- Since T18-1, there have been 4 major revisions and at least 14 minor.
- Linda J. Spilker
- 3/3/04
## Current Reference Tour
- 74 Orbits
- 45 Titan flybys
- 8 targeted icy satellite flybys: Phoebe, Enceladus (3), Dione, Rhea, Hyperion, Iapetus
- ~30 non-targeted flybys (d < 100,000 km)
- Many Saturn/ring occultation opportunities
- Early, middle and late in tour
- One Titan 180 transfer
- One high inclination sequence at end of tour
- Linda J. Spilker
- 3/3/04
## Our Pre-launch Goals
- Scan Platform Working Group: 11/91
- Sequencing process _must start early_, before launch, if possible
- Tour fully designed before SOI (minimizes impact of burnout, divorce, suicide, murder, etc. during tour)
- Linda J. Spilker
- 3/3/04
## Cassini Tour T18-5
**Looking down from Saturn’s North Pole**
**Outer dotted circle: Orbit of Iapetus**
**Inner dotted circle: Orbit of Titan**
**Sun along +X Axis – Plot shows phase**
**Looking in Saturn’s Ring Plane**
**Excursions in inclination different from Galileo**
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 Orbit Insertion and Huygens Mission
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 Huygens Mission – Rev B Probe Release
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 Huygens Mission – Rev B Probe Mission
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2005 FEB 15 to 2005 SEP 07 Mid-Rev 3 to Mid-Rev 14 Occultation Sequences
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2005 FEB 15 to 2005 SEP 07 Mid-Rev 3 to Mid-Rev 14 Occultation Sequences
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2005 SEP 07 to 2006 JUL 22 Mid-Rev 14 to Mid-Rev 26 Magnetotail and Icy Satellites
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2005 SEP 07 to 2006 JUL 22 Mid-Rev 14 to Mid-Rev 26 Magnetotail and Icy Satellites
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2006 JUL 22 to 2007 JUN 30 Mid-Rev 26 to Mid-Rev 47 180 Transfer: Rings and MAPS
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2006 JUL 22 to 2007 JUN 30 Mid-Rev 26 to Mid-Rev 47 180 Transfer: Rings and MAPS
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2007 JUN 30 to 2007 AUG 31 Mid-Rev 47 to Mid-Rev 49 Iapetus Flyby Preparation/Icy Satellites
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2007 AUG 09 to 2007 SEP 14 Rev 49 Titan Gravity Assist and Iapetus Flyby
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2007 AUG 09 to 2007 SEP 14 Rev 49 Titan Gravity Assist and Iapetus Flyby
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2007 AUG 31 to 2008 JUL 01 Mid-Rev 49 to EOM High Inclination Revs: Rings and MAPS
- All units in Rs
- Linda J. Spilker
- 3/3/04
## CASSINI TOUR T18-5 2007 AUG 31 to 2008 JUL 01 Mid-Rev 49 to EOM High Inclination Revs: Rings and MAPS
- Linda J. Spilker
- 3/3/04
## http://saturn.jpl.nasa.gov
- _[http://saturn.jpl.nasa.gov](http://saturn.jpl.nasa.gov/)_
- http://ciclops.org
- Linda J. Spilker
- 3/3/04 | en |
markdown | 139305 | # Presentation: 139305
## Improving Care for Schizophrenia: Process Evaluation of Implementation in EQUIP
- Alexander S. Young, MD MSHSAlison H. Brown, PhD
- Matthew J. Chinman, PhD
- Amy N. Cohen, PhD
- Christopher Reist, MD
- VA Desert Pacific MIRECCGreater Los Angeles VA & Long Beach VAUCLA
## Improving Care for Schizophrenia: Process Evaluation of Implementation in EQUIP
- Alexander S. Young, MD MSHSAlison H. Brown, PhD
- Matthew J. Chinman, PhD
- Amy N. Cohen, PhD
- Christopher Reist, MD
- VA Desert Pacific MIRECCGreater Los Angeles VA & Long Beach VAUCLA
## EQUIP Team
- _West Los Angeles VA_
- Alison H. Brown, PhD
- Matthew Chinman, PhD
- Jim Mintz, PhD
- Noosha Niv, PhD
- Jennifer Pope, BS
- Qing Chen
- Kuo-Chung Shih
- Julia Yosef, MA
- _Long Beach VA_
- Michelle Briggs, RN
- Kirk McNagny, MD
- Christopher Reist, MD
- _Sepulveda VA_
- Daniel Auerbach, MD
- Christopher Kessler, MD
- Daniel Mezzacapo, RN
- Alexander S. Young, MD, MSHS (PI)
- Amy N. Cohen, PhD (co-PI)
- _Support_
- VA HSR&D QUERI: RCD 00-033 & CPI 99–383
- VA Desert Pacific MIRECC
- NIMH Center for Research on Quality in Managed Care (MH 068639)
## Care for Schizophrenia
- Lifetime prevalence = 1.3%
- VA
- > 100,000 patients per year
- 12% of health care costs
- Outcomes are good with
- assertive community treatment / MHICM
- appropriate medication
- caregiver involvement and support
- IPS / supported employment
- Use of these is low to moderate
- outcomes in routine care are often poor
## Improving Care for Schizophrenia
- VA Strategic Plan for Mental Health
- recovery-oriented & evidence-based care
- VA has improved care nationally
- not as much in mental health
- How to improve care for schizophrenia?
- little research has been done
- need methods that are feasible at all sites
- apply chronic illness model
- informatics, reorganization, proactive service delivery
- Challenges
- lack of routine, valid outcomes data in CPRS
- clinicians not using recovery-oriented treatments
## EQUIP
- Evaluate a Chronic Care Model in Schizophrenia
- “Enhancing QUality of Care In Psychosis” (EQUIP)
- improve treatment quality, recovery-orientation
- Randomized, controlled trial
- design
- 2 clinics, 65 psychiatrists, 398 patients
- randomize by MD
- intervention (2003-2004)
- train clinicians in clozapine, wellness groups, family services
- routine patient evaluation
- nurse assessment before each visit
- info sent to MDs (“PopUp”) & managers (quality reports)
- implement chronic care principles
- control: usual care
**Notes:**
In chronic illness, it is important to adopt care models that integrate 1) greater availability of clinical information, 2) reorganize the practice system and clinician roles, 3) foster care coordination, and 4) focus on
evidence-based protocols. In mental health, the most successful efforts to improve care have involved implementation of collaborative care models. They are a blueprint for reorganizing practice, and involve
changing the division of labor and responsibility, adopting new care protocols, and becoming more responsive to patients’ needs. The day-to-day responsibility of illness management falls heavily on patients and their caregivers, and effective care must strengthen illness self-care while assuring that effective preventive and medical interventions occur. Follow-up needs to be active, sustained, and assertively monitored.
Clinical information has a central role in collaborative care, and improving this information can be a prerequisite to improving care.69 The VA has made progress with the national adoption of the Computerized
Patient Record System (CPRS), and associated reminder systems.70 Unfortunately, in mental health, the most critical clinical information is usually not documented in medical records.44 The sole mental health reminders are tardive dyskinesia (a side effect that is rarely caused by newer medications) and global functioning. In schizophrenia, effective care starts with accurate assessment, and includes attention to four domains
of evidence-based practices: 1) assertive care; 2) medication management; 3) caregiver services; and 4) rehabilitation.7, 16 Optimal treatment is team-based, involving collaboration between the patient, their
caregivers and a prepared, proactive practice team.10, 71 Problems with care are highly variable across VA clinics: 6 some sites use no clozapine, while others provide little care coordination. To improve care nationally,
information regarding the clinical needs of patients and treatment provision must be routinely and efficiently available, and intervention approaches developed must target each domain of evidence-based practice.
## Summative Results
- Improved
- prescribing for psychosis
- use of evidence-based weight intervention
- medication adherence
- No improvement
- use of clozapine
- use of family services
- patient quality of life
- patient satisfaction
**Notes:**
Medication treatment is probably inappropriate if:
(1) psychosis criterion: patient has
(A1) significant psychosis (BPRS hallucinations>=5 [moderately severe], suspiciousness>=5, unusual thought content [delusions] >=5, or disorganization>=5); and
(B) within the past 3 months: (i) no increase in dosage of an existing antipsychotic medication, and (ii) no start of a new antipsychotic medication (start can be an addition or a switch) and (iii) not on clozapine
## Process Evaluation: Domains
- Clinics
- structure and process of care
- Clinicians
- competencies, practices, burn-out
- Implementation activities
- Use of wellness, clozapine, and family services
**Notes:**
sub-sample
## Process Evaluation: Data from Clinicians
- Method: semi-structured interviews & questionnaires
- Pre-implementation (n=44)
- clinical practices
- expected barriers and facilitators
- Mid-implementation (n=18)
- usefulness and usability of PopUp and Quality Report
- Post-implementation (n=14)
- clinical practices
- attitudes, knowledge, skills: EBPs and recovery
- barriers and facilitators (especially family)
**Notes:**
sub-sample
## Results
- Challenges implementing evidence based practices differ by practice
- Family Services
- _pre & post survey_: most clinicians reported support for family services and involving families
- _utilization_: no patients who consented to family contact were referred to family intervention
- _post interview_: clinicians believed consumers lacked family contact (untrue) and that families could hurt patients
- _need_: reorganization & intensive negotiation between patients, families and clinicians
## Results
- Weight and wellness
- 1/3 to 1/2 of patients were obese
- evidence-based wellness intervention was implemented
- received by 73% of overweight patients
- psychiatrists did not change prescribing
- Clozapine and psychosis
- new clinic started but very few referrals
- pharmacy requirements cumbersome
- clinician competency low
- not trained or credentialed
- resistant: clozapine requires longer visits, more effort
- did not believe clozapine would helpful
## Informatics Results
- Quality reports
- little use by psychiatrists
- PopUp
- clinicians used
- data on side-effects and functioning
- messaging to collaborate
- did not use
- treatment guidelines
- symptom assessment
- Were critical for implementation
## Conclusions
- Implementation barriers vary by practice
- Common themes
- under-developed clinician competencies
- clinician burn-out
- low availability of psychosocial treatments
- organization of care not consistent with quality practice
- collaboration between services was very difficult (nutrition, pharmacy, primary care)
- needed more local input AND engagement of leadership (VISN)
## Lessons Learned
- Process evaluation critical
- lessons learned used midstream and in current work
- Challenges can only be fully understood during implementation
- In schizophrenia, implement
- routine outcome assessment
- resources for each treatment
- evidence-based quality improvement
## Slide 15
## References
- Brown AH, Cohen AN, Chinman MJ, Kessler C, Young AS. EQUIP: Implementing chronic care principles and applying formative evaluation methods to improve care for schizophrenia: QUERI Series. *Implementation Science *2008; 3: 9.
- Cradock J, Young AS, Sullivan G: The accuracy of medical record documentation in schizophrenia. *Journal of Behavioral Health Services & Research.* 2001; 28: 456-65
- Young AS, Sullivan G, Burnam MA, Brook RH: Measuring the quality of outpatient treatment for schizophrenia. *Archives of General Psychiatry.* 1998; 55: 611-7
- Young AS, Mintz J, Cohen AN: Clinical computing: using information systems to improve care for persons with schizophrenia. *Psychiatric Services* 2004; 55:253-5
- Young AS, Mintz J, Cohen AN, Chinman MJ: A network-based system to improve care for schizophrenia: the medical informatics network tool (MINT). *J Am Med Inform Assoc.* 2004; 11: 358-67.
- Young AS, Cohen AN, Mintz J: A vignette in the chapter on information systems. In: The Institute of Medicine. *Improving the Quality of Health Care for Mental and Substance-Use Conditions: Quality Chasm Series*. Washington DC: National Academies Press; 2005:241-242. | en |
all-txt-docs | 020507 |
// Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
// The Regents of the University of California. All rights reserved.
//
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that: (1) source code distributions
// retain the above copyright notice and this paragraph in its entirety, (2)
// distributions including binary code include the above copyright notice and
// this paragraph in its entirety in the documentation or other materials
// provided with the distribution, and (3) all advertising materials mentioning
// features or use of this software display the following acknowledgement:
// ``This product includes software developed by the University of California,
// Lawrence Berkeley Laboratory and its contributors.'' Neither the name of
// the University nor the names of its contributors may be used to endorse
// or promote products derived from this software without specific prior
// written permission.
// THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
// WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
// MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
// secondary proof of concept shell for bro communications
// project begin 6/22/05
#include <string>
#include <vector>
#include <iostream>
#include <iomanip>
#include <errno.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
#include <stdio.h>
#include <fcntl.h>
#include <sys/time.h>
#include <unistd.h>
#include <broccoli.h>
//#include "broccoli.h"
using std::string;
using std::vector;
using std::cout;
using std::cin;
using std::cerr;
char *host_default = "127.0.0.1";
char *port_default = "47758";
char *host_str;
char *port_str;
// prototypes
static void bro_pong_record(BroConn *conn, BroRecord *rec);
static void return_line(BroConn *conn, BroRecord *rec);
static void return_set(BroConn *conn, BroRecord *rec);
static void prompt();
static void tokenize(const string& str, vector<string>& tokens);
static void print_showhelp();
int main(int argc, char **argv)
{
int opt, port, rc;
BroConn *bc;
extern char *optarg;
extern int optind;
char hostname[512];
char buf[1024];
int n;
string command;
host_str = host_default;
port_str = port_default;
bro_debug_calltrace = 1;
bro_debug_messages = 1;
while ( (opt = getopt(argc, argv, "p:h?")) != -1)
{
switch (opt)
{
case 'p':
port_str = optarg;
break;
//default:
//usage();
}
}
argc -= optind;
argv += optind;
if (argc > 0)
host_str = argv[0];
port = strtol(port_str, NULL, 0);
if (errno == ERANGE)
{
printf("Please provide a port number with -p.\n");
exit(-1);
}
snprintf(hostname, 512, "%s:%s", host_str, port_str);
/* Connect to Bro */
if (! (bc = bro_connect_str(hostname, BRO_CFLAG_RECONNECT | BRO_CFLAG_ALWAYS_QUEUE)))
{
printf("Could not connect to Bro at %s:%s.\n", host_str, port_str);
exit(-1);
}
// define and register the response events with the host we have connected to
bro_event_registry_add(bc, "pong", (BroEventFunc) bro_pong_record);
bro_event_registry_add(bc, "return_line", (BroEventFunc) return_line);
bro_event_registry_add(bc, "return_set", (BroEventFunc) return_set);
bro_event_registry_request(bc);
if (! bro_conn_await_handshake(bc, 10))
{
printf("Could not complete handshake successfully.\n");
exit(-1);
}
printf("Handshake complete, starting shell...\n-->\n");
// we are now connected to the bro instance, begin the command line fun
while(1) // main loop
{
vector<string> tokens; // vector to hold parsed command line
string cmd; // first argument in command
BroEvent *ev; // new event
BroRecord *rec = bro_record_new(); // record (optional) for some events
bro_conn_process_input(bc); // this should get procesed on every loop
int process = 0; // default unknown command
prompt();
if ( fgets(buf, sizeof(buf), stdin) == NULL )
{
putchar('\n');
exit(0);
}
command = buf; // turn buf into c++ string
tokenize(command, tokens); // tokenize the raw command
cmd = tokens[0]; // initial 'key' token
if ( tokens[0] == "show" )
{
if ( tokens[1] == "cpu" )
{ // general cpu information
ev = bro_event_new("show_cpu");
process = 1;
}
else if ( tokens[1] == "memory" )
{ // general memory information
ev = bro_event_new("show_memory");
process = 1;
}
else if ( tokens[1] == "conn" )
{ // general connection information
ev = bro_event_new("show_conn");
process = 1;
}
else if ( tokens[1] == "dropped" )
{ // has this IP been dropped?
ev = bro_event_new("host_drop_check");
uint32 a = (uint32)inet_addr(tokens[2].c_str());
bro_event_add_val(ev, BRO_TYPE_IPADDR, &a);
process = 1;
}
else if ( tokens[1] == "scan" )
{ // scan data about the IP
uint32 a = (uint32)inet_addr(tokens[2].c_str());
ev = bro_event_new("show_scan");
bro_event_add_val(ev, BRO_TYPE_IPADDR, &a);
process = 1;
}
else if ( tokens[1] == "lookup" )
{ // this returns data on an IP/pair if the policy has
// been activated. all testing is done on the policy side.
if ( tokens[2] == "pair" )
{
ev = bro_event_new("lookup_pair");
uint32 a = (uint32)inet_addr(tokens[3].c_str());
uint32 a2 = (uint32)inet_addr(tokens[4].c_str());
bro_event_add_val(ev, BRO_TYPE_IPADDR, &a);
bro_event_add_val(ev, BRO_TYPE_IPADDR, &a2);
}
else
{
ev = bro_event_new("lookup");
uint32 a = (uint32)inet_addr(tokens[2].c_str());
bro_event_add_val(ev, BRO_TYPE_IPADDR, &a);
}
process = 1;
}
else if ( tokens[1] == "pcap" )
{ // print current pcap filter
ev = bro_event_new("show_pcap_filter");
process = 1;
}
else if ( tokens[1] == "fabric" )
{ // print current fabric structure
ev = bro_event_new("show_fabric");
process = 1;
}
else if ( tokens[1] == "notice" )
{ // print given notice data
ev = bro_event_new("show_notice");
BroString arg;
bro_string_init(&arg);
bro_string_set(&arg,tokens[2].c_str());
bro_event_add_val(ev, BRO_TYPE_STRING, &arg);
bro_string_cleanup(&arg);
process = 1;
}
else if ( tokens[1] == "help" || "?" )
print_showhelp();
}
else if ( tokens[0] == "set" )
{ // this is the scan related functionality
if ( tokens[1] == "scan" )
{
if ( tokens[2] == "on" )
{
ev = bro_event_new("scan_on");
process = 1;
}
else if ( tokens[2] == "off" )
{
ev = bro_event_new("scan_off");
process = 1;
}
else if ( tokens[2] == "clear" )
{
ev = bro_event_new("reset_scan");
uint32 a = (uint32)inet_addr(tokens[2].c_str());
bro_event_add_val(ev, BRO_TYPE_IPADDR, &a);
process = 1;
}
else
{
printf("unknown set scan option\n");
printf("\tuse: scan {on|off|clear <IP>}\n");
}
}
else if ( tokens[1] == "lookup" )
{
if ( tokens[2] == "on" )
{
ev = bro_event_new("lookup_on");
process = 1;
}
else if ( tokens[2] == "off" )
{
ev = bro_event_new("lookup_off");
process = 1;
}
}
else if ( tokens[1] == "drop" )
{
if ( tokens[2] == "on" )
{
ev = bro_event_new("drop_on");
process = 1;
}
else if ( tokens[2] == "off" )
{
ev = bro_event_new("drop_off");
process = 1;
}
}
else if ( tokens[1] == "pcap" )
{
// this may need a little work...
ev = bro_event_new("set_pcap");
BroString arg;
bro_string_init(&arg);
bro_string_set(&arg,tokens[2].c_str());
bro_event_add_val(ev, BRO_TYPE_STRING, &arg);
bro_string_cleanup(&arg);
process = 1;
}
else if ( tokens[1] == "help" || "?" )
//print_sethelp();
printf("SETHELP\n");
}
else if ( tokens[0] == "ping" )
{
ev = bro_event_new("ping");
int seq = 1;
double timestamp = bro_util_current_time();
bro_record_add_val(rec, "seq", BRO_TYPE_COUNT, &seq);
bro_record_add_val(rec, "src_time", BRO_TYPE_TIME, ×tamp);
bro_event_add_val(ev, BRO_TYPE_RECORD, rec);
bro_record_free(rec);
process=1;
}
else if ( tokens[0] == "drop" )
{
ev = bro_event_new("host_drop");
uint32 a = (uint32)inet_addr(tokens[1].c_str());
bro_event_add_val(ev, BRO_TYPE_IPADDR, &a);
process = 1;
}
else if ( tokens[0] == "undrop" )
{
ev = bro_event_new("host_undrop");
uint32 a = (uint32)inet_addr(tokens[1].c_str());
bro_event_add_val(ev, BRO_TYPE_IPADDR, &a);
process = 1;
}
if ( process == 1 )
{
bro_event_send(bc, ev);
bro_event_free(ev);
bro_conn_process_input(bc);
process = 0;
}
sleep(1);
}
} // end main
static void
bro_pong_record(BroConn *conn, BroRecord *rec)
{
double now = bro_util_current_time();
double *src_time, *dst_time;
uint32 *seq;
if (! bro_record_get_nth_val(rec, 0, BRO_TYPE_COUNT, &seq))
{
printf("Error getting sequence count from event.\n");
return;
}
if (! bro_record_get_nth_val(rec, 1, BRO_TYPE_TIME, &src_time))
{
printf("Error getting src time from event.\n");
return;
}
if (! bro_record_get_nth_val(rec, 2, BRO_TYPE_TIME, &dst_time))
{
printf("Error getting dst time from event.\n");
return;
}
printf("pong event from %s: seq=%i, time=%f/%f s\n",
host_str, *seq, *dst_time - *src_time,
now - *src_time);
conn = NULL;
}
static void return_line(BroConn *conn, BroRecord *rec)
{
BroString *string;
bro_record_get_nth_val(rec, 0, BRO_TYPE_STRING, &string);
printf("%s\n", string->str_val);
conn = NULL;
}
static void return_set(BroConn *conn, BroRecord *rec)
{
BroString *string;
int iter,i;
printf("in return set\n");
bro_record_get_nth_val(rec, 0, BRO_TYPE_COUNT, &iter);
printf("in return set iter=%d\n", iter);
for ( i = 0; i<iter; i++)
{
bro_record_get_nth_val(rec, (i+1), BRO_TYPE_STRING, &string);
printf("%s\n", string->str_val);
}
}
void prompt()
{
printf("--> ");
}
void tokenize(const string& str, vector<string>& tokens)
{
int num_tokens = 0;
char delim = '\0';
for ( unsigned int i = 0; i < str.length(); ++i )
{
while ( isspace(str[i]) )
++i;
string next_arg;
if (str[i] == '"' || str[i] == '\'')
{
delim = str[i];
++i;
}
else
delim = '\0';
for ( ; str[i]; ++i )
{
if ( delim && str[i] == '\\' &&
i < str.length() && str[i+1] == delim )
{
++i;
next_arg.push_back(str[i]);
}
else if ( delim && str[i] == delim )
{
++i;
break;
}
else if ( ! delim && isspace(str[i]) )
break;
else
next_arg.push_back(str[i]);
}
tokens.push_back(next_arg);
}
}
void print_showhelp()
{
printf("show\n");
printf("\tcpu\n");
printf("\tmemory|mem\n");
printf("\tconn\n");
printf("\tdroped [ip]\n");
printf("\tscan\n");
printf("\tlookup [ip]\n");
printf("\tlookup [ip] [ip]\n");
printf("\tpcap\n");
printf("\n");
}
| en |
converted_docs | 880659 | **114**
**Guidance for Industry**
Effectiveness of Anthelmintics:
Specific Recommendations
for Poultry-*Gallus gallus*
**VICH GL21**
**FINAL GUIDANCE**
This final guidance is intended to standardize and simplify methods used
in the evaluation of new anthelmintics submitted for approval to the
European Union, Japan, and the United States.
Comments and suggestions regarding the document should be submitted to
Dockets Management Branch (HFA-305), Food and Drug Administration, 5630
Fishers Lane, Rm. 1061, Rockville, MD 20852. All comments should be
identified with the Docket No. 00D-1629.
For questions regarding this document, contact Thomas Letonja, Center
for Veterinary Medicine, (HFV-135), Food and Drug Administration, 7500
Standish Place, Rockville, MD 20855, 301-827-7576, e-mail:
<tletonja@cvm.fda.gov>.
######### U.S. Department of Health and Human Services
######### Food and Drug Administration
**Center for Veterinary Medicine**
**June 19, 2002**
**VICH GL21 [(Anthelmintics: poultry -- *gallus gallus*)]{.smallcaps}**
**June 2002**
**For implementation at Step 7**
Effectiveness of Anthelmintics:
Specific Recommendations for
Poultry - *Gallus Gallus*
Recommended for Implementation
on June 2001
by the VICH Steering Committee
[This Guidance has been developed by the appropriate VICH Expert Working
Group and was subject to consultation by the parties, in accordance with
the VICH Process. At Step 7 of the Process the final draft is
recommended for adoption to the regulatory bodies of the European Union,
Japan and]{.smallcaps} USA.
Effectiveness of Anthelmintics:
Specific recommendations for Poultry - *Gallus Gallus*
**Endorsed by the VICH Steering Committee at Step 7 of the**
**VICH process at its meeting from June 2001**
***This guidance represents the agency\'s current thinking on the
subject matter and does not create or confer any rights for or on any
person and does not operate to bind FDA or the public. An alternative
method may be used as long as it satisfies the requirements of the
applicable statutes and regulations.***
# Introduction
The present guidance for poultry (*Gallus gallus*) was developed by the
Working Group established by the Veterinary International Cooperation on
Harmonization (VICH), Anthelmintic Guidances. It should be read in
conjunction with the VICH Effectiveness of Anthelmintic: General
Recommendations (EAGR) which should be referred to for discussion of
broad aspects for providing pivotal data to demonstrate product
anthelmintic effectiveness. The present document is structured similarly
to the EAGR with the aim of simplicity for readers comparing both
documents.
This guidance for poultry is part of this EAGR and the aim is (1) to be
more specific for certain specific issues for poultry not discussed in
the EAGR; (2) to highlight differences with the EAGR on effectiveness
data recommendations and (3) to give explanations for disparities with
the EAGR. Although technical procedures to be followed are not the aim
of this guidance, some details are given as until now the pertinent
procedures have not been described elsewhere.
# A. General Elements
## 1- The Evaluation of Effectiveness Data
Only controlled tests based on parasite counts of adults/larvae should
be acceptable both for the dose determination and dose confirmation
studies, since critical tests generally are not considered to be
reliable for chickens. Egg counts with identification of the genus
should be the preferred method to evaluate the effectiveness in field
studies. Adequate parasite infection should be defined in the protocol
according to regional prevalence or historic and/or statistical data.
## 2- Use of Natural or Induced Infections
Dose determination studies generally should be conducted using induced
infections with either laboratory or recent field isolates.
Dose confirmation studies could be conducted using naturally infected
birds which can have superimposed induced infections. This procedure
should allow a wide range of parasites to be present in the experimental
birds. Also, induced infections in one of the studies should be
acceptable. Studies for larval stages should be conducted with induced
infections only.
The history of the parasites used in the induced infection studies
should be included in the final report.
## 3- Number of Infective Forms Recommended for Induced Infections
Table 1 indicates the number of eggs/cysticercoids recommended to be
used and will depend on the isolate that is used. The final number of
eggs/cysticercoids used in the infection should be included in the final
report.
Table 1. Range of infective stages recommended to produce adequate
infections in chickens for anthelmintic evaluation.
+--------------------------------------+-------------------------------+
| Parasites | Range |
+--------------------------------------+-------------------------------+
| *Ascaridia galli* | 200-500 |
+--------------------------------------+-------------------------------+
| *Capillaria obsignata* | 100-300 |
+--------------------------------------+-------------------------------+
| *Heterakis gallinarum* | 200-300 |
+--------------------------------------+-------------------------------+
| *Raillietina cesticillus* | 50-100 |
| | |
| *Syngamus trachea* | 200 - 600 |
+--------------------------------------+-------------------------------+
Some factors to consider for induced infections in chickens are:
a\) Young birds should be used in the studies;
b\) To maximize the establishment of adequate infections it is
recommended to use low numbers of infective stages;
c\) Stress (e.g., poor diets) is not recommended to generate helminth
infections;
d\) Housing conditions should not allow accidental infections.
## 4- Recommendations for the Calculation of Effectiveness
### *4.1 Criteria to grant a claim*
To be granted a claim, the following pivotal data should be included:
a\) Two dose confirmation studies conducted with a minimum of six
adequately infected birds in each of the non-medicated group and the
treated group;
b\) The differences in parasite counts between treated and control birds
should be statistically significant (p\<0.05);
c\) Effectiveness should be 90% or higher calculated using transformed
(geometric means) data of worm counts;
d\) The infection of the birds in the study should be deemed adequate
based on historical, parasitological and/or statistical criteria.
### *4.2 Number of Animals (Dose Determination and Dose Confirmation Trials)*
The minimum number of birds used per experimental group is a crucial
point. Although the number of birds will depend on the ability to
process the data according to the adequate statistical analysis, it has
been recommended, to achieve harmonization, that the inclusion of at
least six birds in each experimental group is a minimum.
### *4.3 Adequacy of Infection*
Concerning the minimum adequate number of helminths, the decision should
be made when the final report is submitted based on statistical and
historical data, literature review, or expert testimony. The range of
chicken helminths (adults) considered adequate to grant a claim will
vary according to the species. Generally a mean number of 20 adult *A.
galli* is considered to be adequate. Lower counts may be expected with
*H. gallinarum*, *C. obsignata* and *R. cesticellus.* Necropsies should
be conducted within 10 days of treatment.
### *4.4 Label Claims*
For adult claims, as a general rule, the treatment should not be
administered earlier than 28 days after infection. It is recommended to
include at least six sentinel birds for helminth characterization and
quantification before treatment is initiated. For L4 claims, treatments
should be given, as a general rule, seven days after infection, except
for *A. galli and H. gallinarum* which should be 16 days after
infection.
### 5 - Treatment Procedures
The method of administration (oral, parenteral, topical, slow release,
etc.), formulation and extent of activity of a product will influence
the protocol design.
When the drug is to be administered in the water or in a premix, it
should be done as much as possible following the labelling
recommendations. Palatability/consumption studies may be recommended for
medicated premixes. Samples of medicated water or feed should be
collected to confirm drug concentration. The amount of medicated product
provided to each animal should be recorded to ensure that the treatment
satisfies the label recommendations.
### 6 - Bird Selection, Allocation and Handling
Test birds should be clinically healthy and representative of the age,
sex, and class for which the claim of the test anthelmintic is to be
made. In general, birds should be young and from a breed that is
susceptible to helminth infections. Birds should be randomly assigned to
each group. Blocking in replicates by weight, sex, age, and/or exposure
to parasites may aid in reducing trial variance. Faecal egg counts are
also acceptable to allocate the experimental birds. Control birds should
be of the same weight, age, breed, sex and history as the treated group.
For induced infections, the use of helminth naive birds is recommended.
Animal housing, feeding and care should follow recommendations for
welfare, including vaccination according to local practices. This
information should be provided in the final report. A minimum 10-day
acclimatization period is recommended. Housing and feed/water should be
adequate according to the geographical location. Birds should be
monitored daily to determine adverse reactions.
# B. Specific Evaluation Studies
## 1- Dose Determination Studies
If the treatment recommends extended administration, one or more studies
are recommended to determine the minimum treatment period for
effectiveness.
## 2 - Dose Confirmation
No species specific recommendations.
## 3 - Field Effectiveness Studies
Due to commercial constraints the experimental unit in these studies
invariably should be the shed/house. A shed/house should receive only
one treatment, i.e., control or medicated.
Clinical observations, production variables, and records of mortality
should be maintained and compared to historical data of the commercial
establishment. Slaughterhouse inspection reports should be included in
the final report, when the number of test animals can not be confirmed.
| en |
markdown | 240486 | # Presentation: 240486
## Characterizing the Landscape for Water-Quality Analysis
**Methods and implementation**
**2006 National Monitoring Conference, **
**San Jose, CA**
**Notes:**
Curtis Price, cprice@usgs.gov, Rapid City, SD
Gail P. Thelin, gpthelin@usgs.gov, Sacramento, CA
Naomi Nakagaki, nakagaki@usgs.gov, Sacramento, CA
Kerie J. Hitt, kjhitt@usgs.gov, Reston, VA
Sharon Qi, slqi@usgs.gov, Vancouver, WA
## Authors
**NAWQA National Synthesis**
**Curtis Price (cprice@usgs.gov)**
**Naomi Nakagaki**
**Kerie Hitt**
**Gail Thelin**
**High Plains Ground Water Study**
**Sharon Qi**
## Overview
**About NAWQA**
**Using GIS to describe the landscape**
**Area-weighted transfer techniques**
**Summary**
## NAWQA Study Units (“Cycle 1”)
## NAWQA Cycle II
## Slide 6
## Slide 7
## Slide 8
## Slide 9
## http://water.usgs.gov/nawqa/data
**http://water.usgs.gov/nawqa/data**
## Ancillary data
**Summarizes the landscape **** **
**Used to**
**Put water quality data in context**
**Develop statistical models**
## Using results of area characterization
**Example: ****Population density for areas around wells**
- less than 100 persons per square kilometer
- 100 to 1000 persons per square kilometer
- greater than 1000 persons per square kilometer
## Using results of area characterization
**VOC predictors from NAWQA national study:**** **
**Septic systems **
**Urban land **
**RCRA hazardous-waste facilities **
**Regulated underground storage tanks **
**Climatic conditions **
- Depth to top of well screen
**Hydric (anoxic) soils **
- Oxic ground water (dissolved-oxygen concentration greater than or equal to 0.5 milligram per liter)
- Type of well
*Source:* USGS Circular 1292
## GIS data representations
**Points**
**Point sources**
**Surfaces**
**Precipitation**** **
**Tabular data by geography**
** ****(for example, by county)**
**Population**
**Water Use**
**Agricultural statistics**
## One theme (land cover), different representations
**categories**
**(areas)**
**percentages**
** ****(grid cells)**
## Area characterization
**Well buffers, well recharge areas**
**Aquifer areas **
**Drainage basins**
## Characterizing a surface (ground-water conductivity)
## Characterizing thematic data (land cover)
## Geocoded data: Census
**Data linked to polygons from block to national level**
**Census data values required for different polygons (drainage basins) that do not coincide with Census polygons**
## Census Block Group and drainage basin
## Attribute transfer methods
**Simple Area-weighted transfer**
**Transfer of data values weighted by area**
**Assumes values evenly distributed**** **
## Simple area-weighting
**Simple area-weighting**
- Area-weighted mean(1.0*50%) + (10.0*25%) + (16.0*25%) = 7.0
## Census Block Group and drainage basin
## Problems with simple area-weighting
- Urban area
- Basin boundary
- Census polygon
## Attribute transfer methods
**Area-weighted transfer**
**Transfer of data values weighted by area**
**Assumes values evenly distributed**** **
**Spatial disaggregation**
**Refine georeferenced data (for example, data reported by county) using other data sets (such as land cover)**
## Summary
**Land characterization using GIS has played a key role in NAWQA design, site selection, and analysis of sampling results**
**Carefully selecting which data sets to use and how to represent them in the GIS is important**
**Simple area-weighted transfer methods work well, but assume that values are constant in space within a polygon (in this example, Census Block Group)** | en |
converted_docs | 392088 | {width="5.96875in" height="0.41944444444444445in"}
Top of Form
## Complete Summary
#### GUIDELINE TITLE
Procedure guideline for general imaging.
#### BIBLIOGRAPHIC SOURCE(S)
Society of Nuclear Medicine. Procedure guideline for general imaging.
Version 3.0. Reston (VA): Society of Nuclear Medicine; 2004 May 30. 10
p.
#### GUIDELINE STATUS
This is the current release of the guideline.
This guideline updates a previous version: Society of Nuclear Medicine.
Procedure guideline for general imaging, 2.0. Reston (VA): Society of
Nuclear Medicine; 1999 Feb. 36 p. (Society of Nuclear Medicine procedure
guidelines; no. 2.0).
### COMPLETE SUMMARY CONTENT
SCOPE\
METHODOLOGY - including Rating Scheme and Cost Analysis\
RECOMMENDATIONS\
EVIDENCE SUPPORTING THE RECOMMENDATIONS\
BENEFITS/HARMS OF IMPLEMENTING THE GUIDELINE RECOMMENDATIONS\
CONTRAINDICATIONS\
QUALIFYING STATEMENTS\
IMPLEMENTATION OF THE GUIDELINE\
INSTITUTE OF MEDICINE (IOM) NATIONAL HEALTHCARE QUALITY REPORT
CATEGORIES\
IDENTIFYING INFORMATION AND AVAILABILITY\
DISCLAIMER
### SCOPE
#### DISEASE/CONDITION(S)
Conditions for which general nuclear medicine imaging is indicated
#### GUIDELINE CATEGORY
Diagnosis\
Evaluation
#### CLINICAL SPECIALTY
Nuclear Medicine\
Radiology
#### INTENDED USERS
Allied Health Personnel\
Physicians
#### GUIDELINE OBJECTIVE(S)
To provide nuclear medicine practitioners with general guidelines on
imaging in the practice of nuclear medicine
#### TARGET POPULATION
Adults and children for whom nuclear medicine imaging procedures are
indicated
#### INTERVENTIONS AND PRACTICES CONSIDERED
**General Imaging**
1. Single photon scintillation cameras to obtain single photon emission
computed tomographic (SPECT, also know as SPET) images
2. Positron cameras to obtain positron emission tomographic (PET)
images
3. Nuclear medicine computer systems
#### MAJOR OUTCOMES CONSIDERED
Utility and safety of imaging procedures
### METHODOLOGY
#### METHODS USED TO COLLECT/SELECT EVIDENCE
Hand-searches of Published Literature (Primary Sources)\
Hand-searches of Published Literature (Secondary Sources)\
Searches of Electronic Databases
#### DESCRIPTION OF METHODS USED TO COLLECT/SELECT THE EVIDENCE
Literature searches were performed. In addition, references known to
experts and references from the nuclear medicine community were
considered.
#### NUMBER OF SOURCE DOCUMENTS
Not stated
#### METHODS USED TO ASSESS THE QUALITY AND STRENGTH OF THE EVIDENCE
Not stated
#### RATING SCHEME FOR THE STRENGTH OF THE EVIDENCE
Not applicable
#### METHODS USED TO ANALYZE THE EVIDENCE
Review
#### DESCRIPTION OF THE METHODS USED TO ANALYZE THE EVIDENCE
Not stated
#### METHODS USED TO FORMULATE THE RECOMMENDATIONS
Expert Consensus
#### DESCRIPTION OF METHODS USED TO FORMULATE THE RECOMMENDATIONS
Drafts of the guideline were submitted to members of the Guideline
Development subcommittee (methodologists) and the Task Force (subject
experts). These reviewers indicated on a line-by-line basis any
suggestions or recommendations for the revision of the guideline. The
percentage of agreement for all reviewers was calculated for each
revision and compiled by the Society of Nuclear Medicine (SNM) central
office. It is expected that the percentage of agreement will increase
with each revision.
#### RATING SCHEME FOR THE STRENGTH OF THE RECOMMENDATIONS
Not applicable
#### COST ANALYSIS
A formal cost analysis was not performed and published cost analyses
were not reviewed.
#### METHOD OF GUIDELINE VALIDATION
Internal Peer Review
#### DESCRIPTION OF METHOD OF GUIDELINE VALIDATION
When the Task Force and Guideline Development Subcommittee completed
their edits, draft procedure guidelines were distributed to the Society
of Nuclear Medicine (SNM) Sample Review Group for comment. (The SNM
Sample Review Group is a cross-section of approximately 100 nuclear
medicine practitioners representing every field of specialization).
The guideline was approved by the SNM Commission on Health Care Policy,
the Board of Directors, and the House of Delegates.
The update was approved May 30, 2004.
### RECOMMENDATIONS
#### MAJOR RECOMMENDATIONS
**Background Information and Definitions**
The strength of nuclear medicine lies in its ability to image and
quantify regional physiologic biochemical processes. This information
may complement anatomic information provided by other modalities.
A. *Single Photon Scintillation Cameras*
> Single-photon scintillation cameras provide static, dynamic, or gated
> images of the distribution of radiopharmaceuticals within the body.
> Single photon emission computed tomographic (SPECT, also known as
> SPET) images may be obtained by reconstruction of a number of planar
> images taken at different angles. Computed tomography (CT) scanners
> have been combined with some single-photon cameras that have SPECT
> capability in order to provide attenuation correction capability as
> well as localizing information. Use of combined SPECT/CT scanners is
> likely to increase in the future.
B. *Positron Cameras*
> Positron cameras provide static, dynamic, or gated images of the
> distribution of positron-emitting radionuclides within the body by
> detecting pairs of photons produced in coincidence by the annihilation
> of a positron and an electron. Positron emission tomographic (PET)
> images are produced by reconstruction from the coincidence pair data.
> CT scanners have been combined with some positron cameras to provide
> attenuation correction capability as well as localizing information.
> Use of combined PET/CT scanners is rapidly increasing.
C. *Nuclear Medicine Computer Systems*
> Nuclear medicine computer systems collect, quantitate, analyze, and
> display the imaging information.
**Procedure**
The detailed procedure recommendations in the guideline address the
following areas: patient preparation; information pertinent to
performing the procedure (i.e., important data that the physician should
have about the patient at the time the exam is performed and
interpreted); precautions; and quality control.
#### CLINICAL ALGORITHM(S)
None provided
### EVIDENCE SUPPORTING THE RECOMMENDATIONS
#### TYPE OF EVIDENCE SUPPORTING THE RECOMMENDATIONS
The type of evidence supporting the recommendations is not specifically
stated.
### BENEFITS/HARMS OF IMPLEMENTING THE GUIDELINE RECOMMENDATIONS
#### POTENTIAL BENEFITS
The intent of the procedure guideline is to describe general imaging
studies, in order to maximize the diagnostic information obtained in the
studies while minimizing the resources that are expended.
#### POTENTIAL HARMS
- A few diagnostic nuclear medicine studies (e.g., ^131^I whole-body
imaging) may have severe consequences for the developing fetus. The
risk of performing these studies in a pregnant woman should be
weighed against the benefits.
- Current Nuclear Regulatory Commission regulations require that
written instruction be given to breastfeeding women if the potential
radiation dose to the infant is likely to exceed 5 mSv (500 mrem);
oral instructions are required if the potential radiation dose to
the infant is likely to exceed 1 mSv (100 mrem). Pathways for
exposure include ingestion of tracer concentrated in breast milk and
external exposure as a result of close contact during breastfeeding.
There is considerable uncertainty about the actual dose to the
infant since little data are available for excretion into breast
milk for most radiopharmaceuticals.
- For a few diagnostic studies (e.g., ^131^I whole-body imaging), the
radiation dose to the lactating breast can be large (10 cSv \[10
rem\] or greater)\--as much as 10 times the dose to the nonlactating
breast. When possible it is best to delay these studies for at least
4 weeks after breastfeeding has stopped.
- Medical personnel should be instructed in the proper care of
patients after radioisotope administration. Generally, the hazard to
personnel is small and measures taken to protect workers from
biological hazards are sufficient to protect workers from
radiological hazards.
- In general, precautions taken to avoid biological hazards from
patient excreta are more than sufficient to avoid the often much
smaller radiation hazard.
- Instructions should be provided on methods of minimizing radiation
exposure to the patient\'s family and to the general public, where
appropriate.
- In general, there is no scientific or regulatory reason why a
pregnant nurse cannot provide routine care to a patient who has had
a diagnostic imaging study. The risk of caring for a patient
receiving therapy is small; however, it may be prudent not to assign
pregnant nurses to care for these patients.
### CONTRAINDICATIONS
#### CONTRAINDICATIONS
- Elective diagnostic nuclear medicine procedures should be delayed
until a patient is no longer pregnant or breastfeeding.
- For nonelective diagnostic procedures, breastfeeding should be
interrupted for an amount of time appropriate for the
radiopharmaceutical used. For a few diagnostic studies (e.g., ^131^I
whole-body imaging), breastfeeding must be stopped for 1-2 months;
therefore, it is impractical to resume breastfeeding for that child.
### QUALIFYING STATEMENTS
#### QUALIFYING STATEMENTS
- The Society of Nuclear Medicine (SNM) has written and approved these
guidelines as an educational tool to promote the cost-effective use
of high quality nuclear medicine procedures or in the conduct of
research and to assist practitioners in providing appropriate care
for patients. The guidelines should not be deemed inclusive of all
proper procedures nor exclusive of other procedures reasonably
directed to obtaining the same results. They are neither inflexible
rules nor requirements of practice and are not intended nor should
they be used to establish a legal standard of care. For these
reasons, SNM cautions against the use of these guidelines in
litigation in which the clinical decisions of a practitioner are
called into question.
- The ultimate judgment about the propriety of any specific procedure
or course of action must be made by the physician when considering
the circumstances presented. Thus, an approach that differs from the
guidelines is not necessarily below the standard of care. A
conscientious practitioner may responsibly adopt a course of action
different from that set forth in the guidelines when, in his or her
reasonable judgment, such course of action is indicated by the
condition of the patient, limitations on available resources, or
advances in knowledge or technology subsequent to publication of the
guidelines.
- All that should be expected is that practitioner will follow a
reasonable course of action based on current knowledge, available
resources, and the needs of the patient to deliver effective and
safe medical care. The sole purpose of these guidelines is to assist
practitioners in achieving this objective.
- Advances in medicine occur at a rapid rate. The date of a guideline
should always be considered in determining its current
applicability.
### IMPLEMENTATION OF THE GUIDELINE
#### DESCRIPTION OF IMPLEMENTATION STRATEGY
An implementation strategy was not provided.
### INSTITUTE OF MEDICINE (IOM) NATIONAL HEALTHCARE QUALITY REPORT CATEGORIES
#### IOM CARE NEED
Getting Better\
Living with Illness
#### IOM DOMAIN
Effectiveness\
Safety
### IDENTIFYING INFORMATION AND AVAILABILITY
#### BIBLIOGRAPHIC SOURCE(S)
Society of Nuclear Medicine. Procedure guideline for general imaging.
Version 3.0. Reston (VA): Society of Nuclear Medicine; 2004 May 30. 10
p.
#### ADAPTATION
Not applicable: The guideline was not adapted from another source.
#### DATE RELEASED
1999 Feb (revised 2004 May 30)
#### GUIDELINE DEVELOPER(S)
Society of Nuclear Medicine, Inc - Medical Specialty Society
#### SOURCE(S) OF FUNDING
Society of Nuclear Medicine (SNM)
#### GUIDELINE COMMITTEE
Task Force
#### COMPOSITION OF GROUP THAT AUTHORED THE GUIDELINE
*Authors*: J. Anthony Parker, MD, PhD (Beth Israel Hospital, Boston,
MA); Margaret E. Daube-Witherspoon, PhD (University of Pennsylvania,
Philadelphia, PA); L. Stephen Graham, PhD, FACR (West Los Angeles VA
Medical Center/UCLA School of Medicine, Los Angeles, CA); Henry D.
Royal, MD (Mallinckrodt Institute of Radiology, St. Louis, MO); Andrew
E. Todd-Pokropek, PhD (University College of London, United Kingdom);
Michael V. Yester, PhD (University of Alabama at Birmingham, Birmingham,
AL)
#### FINANCIAL DISCLOSURES/CONFLICTS OF INTEREST
Not stated
#### GUIDELINE STATUS
This is the current release of the guideline.
This guideline updates a previous version: Society of Nuclear Medicine.
Procedure guideline for general imaging, 2.0. Reston (VA): Society of
Nuclear Medicine; 1999 Feb. 36 p. (Society of Nuclear Medicine procedure
guidelines; no. 2.0).
#### GUIDELINE AVAILABILITY
Electronic copies: Available from the [Society of Nuclear Medicine (SNM)
Web site](http://interactive.snm.org/index.cfm?PageID=792&RPID=772).
Print copies: Available from SNM, Division of Health Care Policy, 1850
Samuel Morse Dr, Reston, VA 20190-5316; Phone: 1-800-513-6853 or
1-703-326-1186; Fax: 703-708-9015; E-Mail:
[ServiceCenter@snm.org](mailto:servicecenter@snm.org).
#### AVAILABILITY OF COMPANION DOCUMENTS
The following are available:
- Society of Nuclear Medicine. Procedure guideline for guideline
development. Reston (VA): Society of Nuclear Medicine; 2001 Jun
(version 3.0). Electronic copies: Available from the [Society of
Nuclear Medicine Web
site](http://interactive.snm.org/index.cfm?PageID=793&RPID=772).
- Society of Nuclear Medicine. Performance and responsibility
guidelines for NMT. Reston (VA): Society of Nuclear Medicine; 2003.
Electronic copies: Available from the [Society of Nuclear Medicine
Web
site](http://interactive.snm.org/index.cfm?PageID=1929&RPID=772).
Print copies: Available from SNM, Division of Health Care Policy, 1850
Samuel Morse Dr, Reston, VA 20190-5316; Phone: 1-800-513-6853 or
1-703-326-1186; Fax: 703-708-9015; E-Mail:
[ServiceCenter@snm.org](mailto:servicecenter@snm.org).
#### PATIENT RESOURCES
None available
#### NGC STATUS
This summary was completed by ECRI on July 20, 1999. It was verified by
the guideline developer as of August 5, 1999.This summary was updated on
May 18, 2005. The updated information was verified by the guideline
developer on June 30, 2005.
#### COPYRIGHT STATEMENT
This NGC summary is based on the original guideline, which is subject to
the guideline developer\'s copyright restrictions.
### DISCLAIMER
#### NGC DISCLAIMER
The National Guideline Clearinghouse™ (NGC) does not develop, produce,
approve, or endorse the guidelines represented on this site.
All guidelines summarized by NGC and hosted on our site are produced
under the auspices of medical specialty societies, relevant professional
associations, public or private organizations, other government
agencies, health care organizations or plans, and similar entities.
Guidelines represented on the NGC Web site are submitted by guideline
developers, and are screened solely to determine that they meet the NGC
Inclusion Criteria which may be found at
<http://www.guideline.gov/about/inclusion.aspx> .
NGC, AHRQ, and its contractor ECRI Institute make no warranties
concerning the content or clinical efficacy or effectiveness of the
clinical practice guidelines and related materials represented on this
site. Moreover, the views and opinions of developers or authors of
guidelines represented on this site do not necessarily state or reflect
those of NGC, AHRQ, or its contractor ECRI Institute, and inclusion or
hosting of guidelines in NGC may not be used for advertising or
commercial endorsement purposes.
Readers with questions regarding guideline content are directed to
contact the guideline developer.
Bottom of Form
© 1998-2008 National Guideline Clearinghouse
Date Modified: 11/3/2008
| en |
markdown | 581871 | # Presentation: 581871
## WinTR-55 Modeling Multiple Sub-area Watersheds
- WinTR-55 Development Team
## Sub-Area and Reach Concepts
## Sub-area/Reach Concepts
**Watershed **- system of sub-areas and reaches
**Sub-areas** - watersheds that generate runoff
**Reaches **- represent watershed flow paths (stream channels) or structures
- TR-55 Tutorial
## Sub-area/Reach Concepts
**Watershed **- system of sub-areas and reaches
**Sub-areas** - generate runoff
- feed into the upstream end of reaches
**Reaches** or Routing Elements- represent watershed stream flow paths or structures
_***Channel***_ Routing elements - Stream Reaches
_***Structure***_ Routing elements - Reservoir/Structure Reaches
- Watershed **Outlet** - downstream end of the watershed (required for all watersheds)
- TR-55 Tutorial
## Schematics
- Schematics** **
- TR-55 Tutorial
## Data Requirements
- Identification Data - User, State, and County
- Dimensionless Unit Hydrograph
- Storm Data – for specific County/State
- Sub-area Data - Name, flows to reach/outlet, area, runoff curve number, & time of concentration
- Reach Data -Name, receiving reach/outlet, reach length, Manning’s “n”, friction slope, bottom width, average side slopes
- TR-55 Tutorial
## Adding Sub-areas
## Adding Sub-areas
- TR-55 Tutorial
## Adding Stream Reaches and Developing Stream Reach Data
## Adding Stream Reaches
**WinTR-55 Main Window**
- Reach Data Window
- Reach Flow Path Window
- TR-55 Tutorial
## Watershed Schematic
**MainStem1**
**MainStem2**
**EastReach**
**WestReach**
- TR-55 Tutorial
## WinTR-55 Main Window
- TR-55 Tutorial
## Adding Stream Reaches
- WinTR-55 Main Window
**Reach Data Window**
- Reach Flow Path Window
- TR-55 Tutorial
## Stream Reach Data
- Data compiled prior to input:
- Reach Name
- Name of receiving (or downstream) reach (could be Outlet)
- Cross-section data:
*Manning’s “n”*
*Friction slope*
*Bottom Width*
*Average side slopes*
- TR-55 Tutorial
## Reach Data Window
- TR-55 Tutorial
## Reach Data Window
- TR-55 Tutorial
## Plotted Channel Rating
- TR-55 Tutorial
## Computing Stream Reach Ratings
- Manning’s Equation for Channel Flow:
*Q = discharge (cu ft/s)** ** **r = hydraulic radius = A/p**w*
*A = cross-sectional flow area (sq ft)** **p**w** = wetted perimeter (ft)*
*s = slope of hydraulic grade line (channel slope, ft/ft)*
*n = Manning’s roughness coefficient for open channel flow*
- TR-55 Tutorial
## Trapezoidal Cross-Section
- TR-55 Tutorial
## Reach Data Window
- TR-55 Tutorial
## Adding Stream Reaches
- WinTR-55 Main Window
- Reach Data Window
**Reach Flow Path Window**
- TR-55 Tutorial
## Reach Flow Path Window
- TR-55 Tutorial
## Capabilities & Limitations
- Number of sub-areas 1 - 10
- Number of reaches 0-10
- Types of reaches Channel or Structure
- Channel Reach
- Routing Procedure Muskingum-Cunge
- TR-55 Tutorial
## Sub-area and Reach Concepts
***Modeling Watersheds with Structures***
## Sub-area / Reach Concepts
**Stream Reach 1b**
**Stream Reach 2c**
**Sub-area A**
**Sub-area B**
**Sub-area C**
**Structure Reach Pond**
**Watershed **- system of sub-areas and reaches
**Sub-areas** - watersheds that generate runoff
**Reaches **- represent watershed flow paths (stream channels) or structures
**Outlet**
- TR-55 Tutorial
## Sub-area/Reach Concepts
**Watershed **- system of sub-areas and reaches
**Sub-areas** - generate runoff
- feed into the upstream end of reaches
**Reaches** or Routing Elements- represent watershed stream flow paths or structures
_***Channel***_ Routing elements - Stream Reaches
_***Structure***_ Routing elements - Reservoir/Structure Reaches
- Watershed **Outlet** - downstream end of the watershed (required for all watersheds)
- TR-55 Tutorial
## Schematics
- Schematics
- TR-55 Tutorial
## Adding Structure Reaches and Developing Structure Data
## Adding Structure Reaches
**WinTR-55 Main Window**
- Reach Data Window
- Structure Data Window
- Reach Flow Path Window
- TR-55 Tutorial
## WinTR-55 Main Window
- TR-55 Tutorial
## Adding Structure Reaches
- WinTR-55 Main Window
**Reach Data Window**
- Structure Data Window
- Reach Flow Path Window
- TR-55 Tutorial
**Notes:**
Next, proceed to the Reach Data Window where you will specify the name of the structure reach and the name of the structure itself.
## Reach Data Window
- TR-55 Tutorial
## Naming Reaches
- TR-55 Tutorial
## Adding Structure Reaches
- WinTR-55 Main Window
- Reach Data Window
**Structure Data Window**
- Reach Flow Path Window
- TR-55 Tutorial
## Structure Data Window
- TR-55 Tutorial
## Spillway Types
**Pipe**
- Weir
## Pipe Spillway
- TR-55 Tutorial
**Notes:**
To specify a pipe spillway, click the radio button for Pipe under Spillway Type.
The pipe spillway is the default, so when you open the Structure Data Window it will open to a pipe spillway configuration.
When specifying a pipe spillway, you may enter up to three different pipe diameters to test. The program will make as many runs through the data as pipe trial sizes are indicated. If you enter three pipe diameters the program will use the Trial #1 pipe diameter for the first run through, the Trial #2 pipe diameter for the second run, and the Trial #3 pipe diameter for the third run. This will be done for each storm event indicated, however the program will make no more than 3 runs for each storm even if multiple structures are included. In the event there are 2 or more structures in the watershed, all the Trial #1’s are run together, then all the Trial #2’s and then all the Trial #3’s.
You must also specify a Height from the pipe invert at the outlet end of the pipe to the spillway. You’ll see more clearly in the next illustrations how that is defined. One thing to keep in mind though is that this height must be at least 1⁄2 times the pipe diameter or greater. So, in the example of a 48” pipe diameter, a height from pipe invert at outlet to spillway crest elevation of no less than 2 feet could be specified. This is because of the way the program does the pipe flow computations we’ll look at in a moment.
One thing to notice here is that the pipe diameter is specified in inches, while the height from the pipe invert at outlet to the principal spillway crest is in feet. In the case of SI units, the values are in units of millimeters and meters, respectively.
Once sufficient data is entered for the pipe diameter and height from the pipe invert at outlet to the spillway crest, WinTR-55 automatically computes a pipe flow rating for the structure.
Pay attention to the note in red that says “Orifice Flow Assumed.” We’ll talk about that in just a moment.
## Straight Pipe
- TR-55 Tutorial
## Drop Inlet Pipe
- TR-55 Tutorial
## Pipe Flow Equations
- where:
- g = gravity
- cd =0.6
- Height, feet
- Headpipe,feet
- Stage, feet
- Dpipe ,inches
- Apipe,square feet
- Flowpipe,cfs
- TR-55 Tutorial
## Pipe Flow Assumptions
- Short-tube approximation – assumes orifice flow through the pipe at all stages
*Reasonable for drop inlet configuration*
*May be unreasonable for large straight pipes*
- If not appropriate, use other routing models
*SITES*
*WinTR-20*
- TR-55 Tutorial
## Pipe Flow Assumptions
- TR-55 Tutorial
## Spillway Types
- Pipe
**Weir**
## Weir Spillway
- TR-55 Tutorial
## Weir Configuration
- TR-55 Tutorial
## Weir Flow Equations
* **where: L**weir** = weir length, feet*
* **Stage, feet*
* **Flow**weir**, cfs*
- TR-55 Tutorial
## Weir Flow Assumptions
- Entry of a zero weir length indicates a 90° v-notch weir
- Other entry for weir length indicates a rectangular – *having vertical sides* - broad-crested weir
- TR-55 Tutorial
## Plotting Structure Ratings
- TR-55 Tutorial
## Structure Reach Routing
## Storage-Indication Routing Method
- Estimates how the hydrograph changes as it flows through a structure
- Storage = (inflow - outflow) * t
- TR-55 Tutorial
## Structure Reach Routing
- TR-55 Tutorial
## Structure Routing Plot
- TR-55 Tutorial
## Adding Structure Reaches
- WinTR-55 Main Window
- Reach Data Window
- Structure Data Window
**Reach Flow Path Window**
- TR-55 Tutorial
## Reach Flow Path
- TR-55 Tutorial
## Capabilities & Limitations
- Structure Routing Storage-Indication
- Structure Types Pipe or Weir
- Structure Trial Sizes 1-3
- TR-55 Tutorial
## WinTR-55 Web Site
- Download latest WinTR-55 version
- http://wsi.nrcs.usda.gov/products/W2Q/H&H/Tools_Models/WinTR55.html
- Update notes
- WinTR-55 User Manual
- WinTR-55 Support Team e-mail address
- ug-orportlan-4-TR55
- TR-55 Tutorial
## Development Team
- Claudia Hoeft NRCS, Washington DC
- Laurel Foreman NRCS, Iowa
- William Merkel NRCS-WNTSC, Maryland
- Helen Fox Moody NRCS-WNTSC, Maryland
- Quan D. Quan NRCS-WNTSC, Maryland
- Ralph Roberts ARS, Maryland
- John McClung NRCS-NWMC, Arkansas
- Al McNeill NRCS, South Carolina
- Jolyne Lee NRCS-NWCC, Oregon
- Don Woodward NRCS-retired
- Jon Werner NRCS-retired
- Roger Cronshey NRCS-retired
- TR-55 Tutorial | en |
all-txt-docs | 217538 | abiword 2.4.6-2ubuntu2
abiword-common 2.4.6-2ubuntu2
abiword-plugins 2.4.6-2ubuntu2
acpi 0.09-3ubuntu1
acpi-support 0.103
acpid 1.0.4-5ubuntu8
adduser 3.103ubuntu1
alsa-base 1.0.14-1ubuntu2
alsa-utils 1.0.14-1ubuntu4
anacron 2.3-13ubuntu2
apmd 3.2.2-8.1ubuntu1
app-install-data 0.4.7
app-install-data-commercial 8.3
apparmor 2.1+993-0ubuntu3
apparmor-utils 2.1+993-0ubuntu3
apport 0.98
apport-gtk 0.98
appres 1.0.1-0ubuntu1
apt 0.7.6ubuntu14
apt-utils 0.7.6ubuntu14
aptitude 0.4.6.1-1ubuntu3
apturl 0.1ubuntu1
at 3.1.10ubuntu4
at-spi 1.20.0-0ubuntu1
avahi-autoipd 0.6.20-2ubuntu3
avahi-daemon 0.6.20-2ubuntu3
base-files 4.0.0ubuntu5
base-passwd 3.5.11build1
bash 3.2-0ubuntu11
bc 1.06-20ubuntu2
beforelight 1.0.2-0ubuntu1
belocs-locales-bin 2.4-2.2ubuntu5
bind9-host 1:9.4.1-P1-3
binutils 2.18-0ubuntu3
binutils-static 2.18-0ubuntu3
bitmap 1.0.3-0ubuntu1
brasero 0.6.1-0ubuntu1
bsdmainutils 6.1.6ubuntu1
bsdutils 1:2.13-8ubuntu1
busybox-initramfs 1:1.1.3-5ubuntu7
bzip2 1.0.4-0ubuntu2
casper 1.110
cdparanoia 3.10+debian~pre0-5
command-not-found 0.2.8ubuntu2
command-not-found-data 0.2.8ubuntu2
console-setup 1.16ubuntu5
console-terminus 4.20-5.1
console-tools 1:0.2.3dbs-65ubuntu5
coreutils 5.97-5.3ubuntu3
cpio 2.8-1ubuntu2
cpp 4:4.1.2-9ubuntu2
cpp-4.1 4.1.2-16ubuntu2
cron 3.0pl1-100ubuntu1
cups-pdf 2.4.6-3ubuntu10
cupsys 1.3.2-1ubuntu7
cupsys-bsd 1.3.2-1ubuntu7
cupsys-client 1.3.2-1ubuntu7
cupsys-common 1.3.2-1ubuntu7
cupsys-driver-gutenprint 5.0.1-0ubuntu8
dash 0.5.4-1ubuntu3
dbus 1.1.1-3ubuntu4
dbus-x11 1.1.1-3ubuntu4
dc 1.06-20ubuntu2
debconf 1.5.14ubuntu1
debconf-i18n 1.5.14ubuntu1
debianutils 2.22.1
defoma 0.11.10-0.1
desktop-file-utils 0.13-0ubuntu3
dhcdbd 2.0-5ubuntu1
dhcp3-client 3.0.5-3ubuntu4
dhcp3-common 3.0.5-3ubuntu4
diff 2.8.1-12ubuntu1
discover1 1.7.21ubuntu1
discover1-data 2.2007.05.11ubuntu4
displayconfig-gtk 0.3.7
dmidecode 2.9-1ubuntu1
dmsetup 2:1.02.20-1ubuntu4
dmz-cursor-theme 0.4.1
dnsutils 1:9.4.1-P1-3
doc-base 0.8.4
docbook-xml 4.5-4
dosfstools 2.11-2.2ubuntu1
dpkg 1.14.5ubuntu16
dvd+rw-tools 7.0-7
e2fslibs 1.40.2-1ubuntu1
e2fsprogs 1.40.2-1ubuntu1
ed 0.7-1build1
editres 1.0.3-0ubuntu1
eject 2.1.5-2ubuntu2
esound-common 0.2.38-0ubuntu4
espeak-data 1.29-0ubuntu3
ethtool 5-2
evince-gtk 2.20.0-0ubuntu3
example-content 26
fdutils 5.5-20060227-1.1
feisty-gdm-themes 0.22
file 4.21-1
file-roller 2.20.0-0ubuntu1
findutils 4.2.31-1ubuntu2
finger 0.17-11
firefox 2.0.0.6+2nobinonly-0ubuntu1
fontconfig 2.4.2-1.2ubuntu4
fontconfig-config 2.4.2-1.2ubuntu4
foo2zjs 20070625-0ubuntu1
foomatic-db 20070919-0ubuntu3
foomatic-db-engine 3.0.2-20070719-0ubuntu4
foomatic-db-hpijs 20070813-0ubuntu1
foomatic-filters 3.0.2-20070719-0ubuntu1
fortune-mod 1:1.99.1-3ubuntu3
fortunes-min 1:1.99.1-3ubuntu3
freeglut3 2.4.0-5.1ubuntu1
fstobdf 1.0.2-0ubuntu1
ftp 0.17-16build1
fuse-utils 2.7.0-1ubuntu5
gamin 0.1.8-2ubuntu1
gcalctool 5.20.1-0ubuntu1
gcc 4:4.1.2-9ubuntu2
gcc-4.1 4.1.2-16ubuntu2
gcc-4.1-base 4.1.2-16ubuntu2
gcc-4.2-base 4.2.1-5ubuntu4
gconf2 2.20.0-0ubuntu1
gconf2-common 2.20.0-0ubuntu1
gdb 6.6.dfsg-1ubuntu7
gdebi 0.3.2ubuntu1
gdebi-core 0.3.2ubuntu1
gdm 2.20.0-0ubuntu6
genisoimage 9:1.1.6-1ubuntu3
gettext-base 0.16.1-2ubuntu3
ghostscript 8.61.dfsg.1~svn8187-0ubuntu3
ghostscript-x 8.61.dfsg.1~svn8187-0ubuntu3
gimp 2.4.0~rc3-1ubuntu7
gimp-data 2.4.0~rc3-1ubuntu7
gimp-print 5.0.1-0ubuntu8
gksu 2.0.0-4ubuntu2
gnome-accessibility-themes 2.20.0-0ubuntu1
gnome-app-install 0.4.13-0ubuntu1
gnome-cards-data 1:2.20.0.1-0ubuntu2
gnome-games 1:2.20.0.1-0ubuntu2
gnome-games-data 1:2.20.0.1-0ubuntu2
gnome-icon-theme 2.20.0-0ubuntu1
gnome-keyring 2.20-0ubuntu4
gnome-mag 1:0.14.10-0ubuntu1
gnome-media-common 2.20.1-0ubuntu1
gnome-mime-data 2.18.0-1
gnome-mount 0.6-1ubuntu4
gnome-orca 2.20.0-0ubuntu1
gnome-screensaver 2.20.0-0ubuntu4
gnome-system-monitor 2.20.0-0ubuntu1
gnome-system-tools 2.20.0-0ubuntu1
gnome-themes 2.20.0-0ubuntu1
gnumeric-common 1.7.11-1ubuntu3
gnumeric-gtk 1.7.11-1ubuntu3
gnupg 1.4.6-2ubuntu4
gparted 0.3.3-2ubuntu6
gpgv 1.4.6-2ubuntu4
gqview 2.0.4-0ubuntu1
grep 2.5.1.ds2-6build1
groff-base 1.18.1.1-12
grub 0.97-29ubuntu4
gsfonts 1:8.11+urwcyr1.0.7~pre41-3
gtk2-engines 1:2.12.1-0ubuntu1
gtk2-engines-murrine 0.53.1-0ubuntu2
gtk2-engines-pixbuf 2.12.0-1ubuntu3
gtk2-engines-ubuntulooks 0.9.12-8
gtk2-engines-xfce 2.4.1-1
gucharmap 1:1.10.1-0ubuntu1
guidance-backends 0.8.0svn20070928-0ubuntu7
guile-1.6-libs 1.6.8-6ubuntu1
gutsy-wallpapers 0.17
gzip 1.3.12-2ubuntu1
hal 0.5.9.1-6ubuntu5
hal-cups-utils 0.6.13+svn83-0ubuntu1
hal-info 20070618-1ubuntu3
hdparm 7.5-1ubuntu1
hicolor-icon-theme 0.10-1ubuntu1
hostname 2.93build1
hotkey-setup 0.1-17ubuntu20
hpijs 2.7.7+2.7.7.dfsg.1-0ubuntu5
hplip 2.7.7.dfsg.1-0ubuntu5
hplip-data 2.7.7.dfsg.1-0ubuntu5
human-icon-theme 0.23
human-theme 0.9
iceauth 1:1.0.2-0ubuntu1
ico 1:1.0.2-0ubuntu1
ifupdown 0.6.8ubuntu8
info 4.8.dfsg.1-6
initramfs-tools 0.85eubuntu20
initscripts 2.86.ds1-14.1ubuntu31
inputattach 1.23-0ubuntu2
iproute 20070313-1ubuntu2
iptables 1.3.6.0debian1-5ubuntu5
iputils-arping 3:20070202-1ubuntu2
iputils-ping 3:20070202-1ubuntu2
iputils-tracepath 3:20070202-1ubuntu2
iso-codes 1.0a-1ubuntu1
jfsutils 1.1.11-1build1
klibc-utils 1.5-4ubuntu3
klogd 1.4.1-21ubuntu3
landscape-client 0.1
language-pack-af 1:7.10+20071012
language-pack-af-base 1:7.10+20071012
language-pack-am 1:7.10+20071012
language-pack-am-base 1:7.10+20071012
language-pack-ar 1:7.10+20071012
language-pack-ar-base 1:7.10+20071012
language-pack-as 1:7.10+20071012
language-pack-as-base 1:7.10+20071012
language-pack-az 1:7.10+20071012
language-pack-az-base 1:7.10+20071012
language-pack-be 1:7.10+20071012
language-pack-be-base 1:7.10+20071012
language-pack-bg 1:7.10+20071012
language-pack-bg-base 1:7.10+20071012
language-pack-bn 1:7.10+20071012
language-pack-bn-base 1:7.10+20071012
language-pack-br 1:7.10+20071012
language-pack-br-base 1:7.10+20071012
language-pack-bs 1:7.10+20071012
language-pack-bs-base 1:7.10+20071012
language-pack-ca 1:7.10+20071012
language-pack-ca-base 1:7.10+20071012
language-pack-cs 1:7.10+20071012
language-pack-cs-base 1:7.10+20071012
language-pack-cy 1:7.10+20071012
language-pack-cy-base 1:7.10+20071012
language-pack-da 1:7.10+20071012
language-pack-da-base 1:7.10+20071012
language-pack-de 1:7.10+20071012
language-pack-de-base 1:7.10+20071012
language-pack-el 1:7.10+20071012
language-pack-el-base 1:7.10+20071012
language-pack-en 1:7.10+20071012
language-pack-en-base 1:7.10+20071012
language-pack-eo 1:7.10+20071012
language-pack-eo-base 1:7.10+20071012
language-pack-es 1:7.10+20071012
language-pack-es-base 1:7.10+20071012
language-pack-et 1:7.10+20071012
language-pack-et-base 1:7.10+20071012
language-pack-eu 1:7.10+20071012
language-pack-eu-base 1:7.10+20071012
language-pack-fa 1:7.10+20071012
language-pack-fa-base 1:7.10+20071012
language-pack-fi 1:7.10+20071012
language-pack-fi-base 1:7.10+20071012
language-pack-fr 1:7.10+20071012
language-pack-fr-base 1:7.10+20071012
language-pack-ga 1:7.10+20071012
language-pack-ga-base 1:7.10+20071012
language-pack-gl 1:7.10+20071012
language-pack-gl-base 1:7.10+20071012
language-pack-gnome-af 1:7.10+20071012
language-pack-gnome-af-base 1:7.10+20071012
language-pack-gnome-am 1:7.10+20071012
language-pack-gnome-am-base 1:7.10+20071012
language-pack-gnome-ar 1:7.10+20071012
language-pack-gnome-ar-base 1:7.10+20071012
language-pack-gnome-as 1:7.10+20071012
language-pack-gnome-as-base 1:7.10+20071012
language-pack-gnome-az 1:7.10+20071012
language-pack-gnome-az-base 1:7.10+20071012
language-pack-gnome-be 1:7.10+20071012
language-pack-gnome-be-base 1:7.10+20071012
language-pack-gnome-bg 1:7.10+20071012
language-pack-gnome-bg-base 1:7.10+20071012
language-pack-gnome-bn 1:7.10+20071012
language-pack-gnome-bn-base 1:7.10+20071012
language-pack-gnome-br 1:7.10+20071012
language-pack-gnome-br-base 1:7.10+20071012
language-pack-gnome-bs 1:7.10+20071012
language-pack-gnome-bs-base 1:7.10+20071012
language-pack-gnome-ca 1:7.10+20071012
language-pack-gnome-ca-base 1:7.10+20071012
language-pack-gnome-cs 1:7.10+20071012
language-pack-gnome-cs-base 1:7.10+20071012
language-pack-gnome-cy 1:7.10+20071012
language-pack-gnome-cy-base 1:7.10+20071012
language-pack-gnome-da 1:7.10+20071012
language-pack-gnome-da-base 1:7.10+20071012
language-pack-gnome-de 1:7.10+20071012
language-pack-gnome-de-base 1:7.10+20071012
language-pack-gnome-el 1:7.10+20071012
language-pack-gnome-el-base 1:7.10+20071012
language-pack-gnome-en 1:7.10+20071012
language-pack-gnome-en-base 1:7.10+20071012
language-pack-gnome-eo 1:7.10+20071012
language-pack-gnome-eo-base 1:7.10+20071012
language-pack-gnome-es 1:7.10+20071012
language-pack-gnome-es-base 1:7.10+20071012
language-pack-gnome-et 1:7.10+20071012
language-pack-gnome-et-base 1:7.10+20071012
language-pack-gnome-eu 1:7.10+20071012
language-pack-gnome-eu-base 1:7.10+20071012
language-pack-gnome-fa 1:7.10+20071012
language-pack-gnome-fa-base 1:7.10+20071012
language-pack-gnome-fi 1:7.10+20071012
language-pack-gnome-fi-base 1:7.10+20071012
language-pack-gnome-fr 1:7.10+20071012
language-pack-gnome-fr-base 1:7.10+20071012
language-pack-gnome-ga 1:7.10+20071012
language-pack-gnome-ga-base 1:7.10+20071012
language-pack-gnome-gl 1:7.10+20071012
language-pack-gnome-gl-base 1:7.10+20071012
language-pack-gnome-gu 1:7.10+20071012
language-pack-gnome-gu-base 1:7.10+20071012
language-pack-gnome-he 1:7.10+20071012
language-pack-gnome-he-base 1:7.10+20071012
language-pack-gnome-hi 1:7.10+20071012
language-pack-gnome-hi-base 1:7.10+20071012
language-pack-gnome-hr 1:7.10+20071012
language-pack-gnome-hr-base 1:7.10+20071012
language-pack-gnome-hu 1:7.10+20071012
language-pack-gnome-hu-base 1:7.10+20071012
language-pack-gnome-ia 1:7.10+20071012
language-pack-gnome-ia-base 1:7.10+20071012
language-pack-gnome-id 1:7.10+20071012
language-pack-gnome-id-base 1:7.10+20071012
language-pack-gnome-is 1:7.10+20071012
language-pack-gnome-is-base 1:7.10+20071012
language-pack-gnome-it 1:7.10+20071012
language-pack-gnome-it-base 1:7.10+20071012
language-pack-gnome-ja 1:7.10+20071012
language-pack-gnome-ja-base 1:7.10+20071012
language-pack-gnome-ka 1:7.10+20071012
language-pack-gnome-ka-base 1:7.10+20071012
language-pack-gnome-kn 1:7.10+20071012
language-pack-gnome-kn-base 1:7.10+20071012
language-pack-gnome-ko 1:7.10+20071012
language-pack-gnome-ko-base 1:7.10+20071012
language-pack-gnome-ku 1:7.10+20071012
language-pack-gnome-ku-base 1:7.10+20071012
language-pack-gnome-lg 1:7.10+20071012
language-pack-gnome-lg-base 1:7.10+20071012
language-pack-gnome-li 1:7.10+20071012
language-pack-gnome-li-base 1:7.10+20071012
language-pack-gnome-lo 1:7.10+20071012
language-pack-gnome-lo-base 1:7.10+20071012
language-pack-gnome-lt 1:7.10+20071012
language-pack-gnome-lt-base 1:7.10+20071012
language-pack-gnome-lv 1:7.10+20071012
language-pack-gnome-lv-base 1:7.10+20071012
language-pack-gnome-mg 1:7.10+20071012
language-pack-gnome-mg-base 1:7.10+20071012
language-pack-gnome-mi 1:7.10+20071012
language-pack-gnome-mi-base 1:7.10+20071012
language-pack-gnome-mk 1:7.10+20071012
language-pack-gnome-mk-base 1:7.10+20071012
language-pack-gnome-ml 1:7.10+20071012
language-pack-gnome-ml-base 1:7.10+20071012
language-pack-gnome-mn 1:7.10+20071012
language-pack-gnome-mn-base 1:7.10+20071012
language-pack-gnome-mr 1:7.10+20071012
language-pack-gnome-mr-base 1:7.10+20071012
language-pack-gnome-ms 1:7.10+20071012
language-pack-gnome-ms-base 1:7.10+20071012
language-pack-gnome-my 1:7.10+20071012
language-pack-gnome-my-base 1:7.10+20071012
language-pack-gnome-nb 1:7.10+20071012
language-pack-gnome-nb-base 1:7.10+20071012
language-pack-gnome-pt 1:7.10+20071012
language-pack-gnome-pt-base 1:7.10+20071012
language-pack-gnome-ro 1:7.10+20071012
language-pack-gnome-ro-base 1:7.10+20071012
language-pack-gnome-ru 1:7.10+20071012
language-pack-gnome-ru-base 1:7.10+20071012
language-pack-gnome-se 1:7.10+20071012
language-pack-gnome-se-base 1:7.10+20071012
language-pack-gnome-si 1:7.10+20071012
language-pack-gnome-si-base 1:7.10+20071012
language-pack-gnome-sk 1:7.10+20071012
language-pack-gnome-sk-base 1:7.10+20071012
language-pack-gnome-sl 1:7.10+20071012
language-pack-gnome-sl-base 1:7.10+20071012
language-pack-gnome-uk 1:7.10+20071012
language-pack-gnome-uk-base 1:7.10+20071012
language-pack-gnome-vi 1:7.10+20071012
language-pack-gnome-vi-base 1:7.10+20071012
language-pack-gnome-xh 1:7.10+20071012
language-pack-gnome-xh-base 1:7.10+20071012
language-pack-gnome-yi 1:7.10+20071012
language-pack-gnome-yi-base 1:7.10+20071012
language-pack-gnome-zh 1:7.10+20071012
language-pack-gnome-zh-base 1:7.10+20071012
language-pack-gnome-zu 1:7.10+20071012
language-pack-gnome-zu-base 1:7.10+20071012
language-pack-gu 1:7.10+20071012
language-pack-gu-base 1:7.10+20071012
language-pack-he 1:7.10+20071012
language-pack-he-base 1:7.10+20071012
language-pack-hi 1:7.10+20071012
language-pack-hi-base 1:7.10+20071012
language-pack-hr 1:7.10+20071012
language-pack-hr-base 1:7.10+20071012
language-pack-hu 1:7.10+20071012
language-pack-hu-base 1:7.10+20071012
language-pack-ia 1:7.10+20071012
language-pack-ia-base 1:7.10+20071012
language-pack-id 1:7.10+20071012
language-pack-id-base 1:7.10+20071012
language-pack-is 1:7.10+20071012
language-pack-is-base 1:7.10+20071012
language-pack-it 1:7.10+20071012
language-pack-it-base 1:7.10+20071012
language-pack-ja 1:7.10+20071012
language-pack-ja-base 1:7.10+20071012
language-pack-ka 1:7.10+20071012
language-pack-ka-base 1:7.10+20071012
language-pack-kn 1:7.10+20071012
language-pack-kn-base 1:7.10+20071012
language-pack-ko 1:7.10+20071012
language-pack-ko-base 1:7.10+20071012
language-pack-ku 1:7.10+20071012
language-pack-ku-base 1:7.10+20071012
language-pack-lg 1:7.10+20071012
language-pack-lg-base 1:7.10+20071012
language-pack-li 1:7.10+20071012
language-pack-li-base 1:7.10+20071012
language-pack-lo 1:7.10+20071012
language-pack-lo-base 1:7.10+20071012
language-pack-lt 1:7.10+20071012
language-pack-lt-base 1:7.10+20071012
language-pack-lv 1:7.10+20071012
language-pack-lv-base 1:7.10+20071012
language-pack-mg 1:7.10+20071012
language-pack-mg-base 1:7.10+20071012
language-pack-mi 1:7.10+20071012
language-pack-mi-base 1:7.10+20071012
language-pack-mk 1:7.10+20071012
language-pack-mk-base 1:7.10+20071012
language-pack-ml 1:7.10+20071012
language-pack-ml-base 1:7.10+20071012
language-pack-mn 1:7.10+20071012
language-pack-mn-base 1:7.10+20071012
language-pack-mr 1:7.10+20071012
language-pack-mr-base 1:7.10+20071012
language-pack-ms 1:7.10+20071012
language-pack-ms-base 1:7.10+20071012
language-pack-my 1:7.10+20071012
language-pack-my-base 1:7.10+20071012
language-pack-nb 1:7.10+20071012
language-pack-nb-base 1:7.10+20071012
language-pack-pt 1:7.10+20071012
language-pack-pt-base 1:7.10+20071012
language-pack-ro 1:7.10+20071012
language-pack-ro-base 1:7.10+20071012
language-pack-ru 1:7.10+20071012
language-pack-ru-base 1:7.10+20071012
language-pack-se 20050609
language-pack-se-base 20050609
language-pack-si 1:7.10+20071012
language-pack-si-base 1:7.10+20071012
language-pack-sk 1:7.10+20071012
language-pack-sk-base 1:7.10+20071012
language-pack-sl 1:7.10+20071012
language-pack-sl-base 1:7.10+20071012
language-pack-uk 1:7.10+20071012
language-pack-uk-base 1:7.10+20071012
language-pack-vi 1:7.10+20071012
language-pack-vi-base 1:7.10+20071012
language-pack-xh 1:7.10+20071012
language-pack-xh-base 1:7.10+20071012
language-pack-yi 1:7.10+20071012
language-pack-yi-base 1:7.10+20071012
language-pack-zh 1:7.10+20071012
language-pack-zh-base 1:7.10+20071012
language-pack-zu 1:7.10+20071012
language-pack-zu-base 1:7.10+20071012
language-selector 0.2.9
language-selector-common 0.2.9
laptop-detect 0.13.2ubuntu1
laptop-mode-tools 1.34-1ubuntu2
launchpad-integration 0.1.15
less 406-0
lftp 3.5.11-1
libaa1 1.4p5-32
libacl1 2.2.42-1ubuntu1
libaiksaurus-1.2-0c2a 1.2.1+dev-0.12-4ubuntu2
libaiksaurus-1.2-data 1.2.1+dev-0.12-4ubuntu2
libaiksaurusgtk-1.2-0c2a 1.2.1+dev-0.12-4ubuntu2
libapm1 3.2.2-8.1ubuntu1
libart-2.0-2 2.3.19-3
libasound2 1.0.14-1ubuntu8
libaspell15 0.60.5-1ubuntu1
libatk1.0-0 1.20.0-0ubuntu1
libatm1 2.4.1-17.1build1
libatspi1.0-0 1.20.0-0ubuntu1
libattr1 1:2.4.32-1.1ubuntu1
libaudiofile0 0.2.6-6ubuntu3
libavahi-client3 0.6.20-2ubuntu3
libavahi-common-data 0.6.20-2ubuntu3
libavahi-common3 0.6.20-2ubuntu3
libavahi-compat-libdnssd1 0.6.20-2ubuntu3
libavahi-core5 0.6.20-2ubuntu3
libavahi-glib1 0.6.20-2ubuntu3
libbind9-30 1:9.4.1-P1-3
libblkid1 1.40.2-1ubuntu1
libbonobo2-0 2.20.0-0ubuntu1
libbonobo2-common 2.20.0-0ubuntu1
libbonoboui2-0 2.20.0-0ubuntu1
libbonoboui2-common 2.20.0-0ubuntu1
libbrlapi1 3.7.2-7.1ubuntu1
libbz2-1.0 1.0.4-0ubuntu2
libc6 2.6.1-1ubuntu9
libc6-i686 2.6.1-1ubuntu9
libcairo-perl 1.041-1
libcairo2 1.4.10-1ubuntu4
libcairomm-1.0-1 1.2.4-2
libcap1 1:1.10-14build1
libcdparanoia0 3.10+debian~pre0-5
libcomerr2 1.40.2-1ubuntu1
libconsole 1:0.2.3dbs-65ubuntu5
libcroco3 0.6.1-1build2
libcupsimage2 1.3.2-1ubuntu7
libcupsys2 1.3.2-1ubuntu7
libcurl3-gnutls 7.16.4-2ubuntu1
libdaemon0 0.12-0.1
libdatrie0 0.1.1-4
libdb4.2 4.2.52+dfsg-2ubuntu1
libdb4.3 4.3.29-8ubuntu2
libdb4.4 4.4.20-8.1ubuntu3
libdb4.5 4.5.20-5ubuntu3
libdbus-1-3 1.1.1-3ubuntu4
libdbus-glib-1-2 0.74-1
libdebconfclient0 0.117build1
libdebian-installer4 0.52ubuntu1
libdevmapper1.02.1 2:1.02.20-1ubuntu4
libdirectfb-0.9-25 0.9.25.1-6ubuntu3
libdiscover1 1.7.21ubuntu1
libdjvulibre15 3.5.19-2ubuntu1
libdmx1 1:1.0.2-2build1
libdns32 1:9.4.1-P1-3
libdrm2 2.3.0-4ubuntu1
libedit2 2.9.cvs.20050518-3
libelfg0 0.8.6-4
libenchant1c2a 1.3.0-3
libesd-alsa0 0.2.38-0ubuntu4
libespeak1 1.29-0ubuntu3
libexif12 0.6.16-1
libexo-0.3-0 0.3.2-4ubuntu1
libexpat1 1.95.8-4ubuntu1
libflac8 1.1.4-3ubuntu1
libfontconfig1 2.4.2-1.2ubuntu4
libfontenc1 1:1.0.4-2
libfreetype6 2.3.5-1ubuntu4
libfribidi0 0.10.7-4build1
libfs6 2:1.0.0-4ubuntu2
libfuse2 2.7.0-1ubuntu5
libgadu3 1:1.7~rc2-2
libgail-common 1.20.0-0ubuntu1
libgail-gnome-module 1.20.0-0ubuntu1
libgail18 1.20.0-0ubuntu1
libgamin0 0.1.8-2ubuntu1
libgc1c2 1:6.8-1ubuntu2
libgcc1 1:4.2.1-5ubuntu4
libgconf2-4 2.20.0-0ubuntu1
libgcrypt11 1.2.4-2ubuntu2
libgdbm3 1.8.3-3
libgdome2-0 0.8.1+debian-2
libgdome2-cpp-smart0c2a 0.2.5-1ubuntu1
libgimp2.0 2.4.0~rc3-1ubuntu7
libgksu2-0 2.0.5-1ubuntu4
libgl1-mesa-glx 7.0.1-1ubuntu3
libglade2-0 1:2.6.2-1
libglib-perl 1:1.152-1
libglib2.0-0 2.14.1-1ubuntu1
libglib2.0-data 2.14.1-1ubuntu1
libglibmm-2.4-1c2a 2.14.0-0ubuntu1
libglu1-mesa 7.0.1-1ubuntu3
libglut3 3.7-25
libgnome-desktop-2 1:2.20.0-0ubuntu1
libgnome-keyring0 2.20-0ubuntu4
libgnome-mag2 1:0.14.10-0ubuntu1
libgnome-media0 2.20.1-0ubuntu1
libgnome-menu2 2.20.0-0ubuntu1
libgnome-speech7 1:0.4.16-0ubuntu2
libgnome2-0 2.20.0-1ubuntu4
libgnome2-canvas-perl 1.002-1ubuntu2
libgnome2-common 2.20.0-1ubuntu4
libgnome2-perl 1.040-1
libgnome2-vfs-perl 1.060-1
libgnomecanvas2-0 2.20.0-1ubuntu1
libgnomecanvas2-common 2.20.0-1ubuntu1
libgnomecups1.0-1 0.2.2-5ubuntu1
libgnomekbd-common 2.20.0-1
libgnomekbd1 2.20.0-1
libgnomekbdui1 2.20.0-1
libgnomeprint2.2-0 2.18.2-0ubuntu1
libgnomeprint2.2-data 2.18.2-0ubuntu1
libgnomeprintui2.2-0 2.18.1-0ubuntu1
libgnomeprintui2.2-common 2.18.1-0ubuntu1
libgnomeui-0 2.20.0-0ubuntu1
libgnomeui-common 2.20.0-0ubuntu1
libgnomevfs2-0 1:2.20.0-0ubuntu3
libgnomevfs2-common 1:2.20.0-0ubuntu3
libgnutls13 1.6.3-1build1
libgoffice-0-common 0.4.2-0ubuntu1
libgoffice-gtk-0-4 0.4.2-0ubuntu1
libgpg-error0 1.4-2ubuntu1
libgphoto2-2 2.4.0-2ubuntu2
libgphoto2-port0 2.4.0-2ubuntu2
libgpmg1 1.19.6-25
libgs8 8.61.dfsg.1~svn8187-0ubuntu3
libgsf-1-114 1.14.7-0ubuntu1
libgsf-1-common 1.14.7-0ubuntu1
libgstreamer-plugins-base0.10-0 0.10.14-1ubuntu3
libgstreamer0.10-0 0.10.14-1ubuntu3
libgtk2-perl 1:1.140-1build1
libgtk2.0-0 2.12.0-1ubuntu3
libgtk2.0-bin 2.12.0-1ubuntu3
libgtk2.0-common 2.12.0-1ubuntu3
libgtkhtml2-0 2.11.1-0ubuntu1
libgtkmathview0c2a 0.7.8-1
libgtkmm-2.4-1c2a 1:2.12.0-0ubuntu1
libgtksourceview-common 1.8.5-1
libgtksourceview1.0-0 1.8.5-1
libgtkspell0 2.0.10-3build1
libgtop2-7 2.20.0-0ubuntu1
libgtop2-common 2.20.0-0ubuntu1
libgucharmap6 1:1.10.1-0ubuntu1
libguile-ltdl-1 1.6.8-6ubuntu1
libgutenprint2 5.0.1-0ubuntu8
libgutenprintui2-1 5.0.1-0ubuntu8
libhal-storage1 0.5.9.1-6ubuntu5
libhal1 0.5.9.1-6ubuntu5
libhesiod0 3.0.2-18.1
libhtml-parser-perl 3.56-1
libhtml-tagset-perl 3.10-2
libhtml-tree-perl 3.23-1
libhunspell-1.1-0 1.1.5-6
libice6 2:1.0.3-3
libidl0 0.8.9-0ubuntu1
libidn11 1.0-0
libieee1284-3 0.2.10-8
libisc32 1:9.4.1-P1-3
libisccc30 1:9.4.1-P1-3
libisccfg30 1:9.4.1-P1-3
libiw29 29~pre20-1ubuntu1
libjasper1 1.900.1-3
libjpeg-progs 6b-14
libjpeg62 6b-14
libkeyutils1 1.2-3
libklibc 1.5-4ubuntu3
libkpathsea4 2007-12ubuntu3
libkrb53 1.6.dfsg.1-7build1
liblaunchpad-integration0 0.1.15
liblcms1 1.16-5ubuntu3
libldap2 2.1.30-13.4
liblink-grammar4 4.2.2-4
liblircclient0 0.8.2-0ubuntu8
liblocale-gettext-perl 1.05-1build1
libltdl3 1.5.24-1ubuntu1
liblwres30 1:9.4.1-P1-3
liblzo2-2 2.02-3
libmagic1 4.21-1
libmagick9 7:6.2.4.5.dfsg1-2ubuntu1
libmeanwhile1 1.0.2-3
libmetacity0 1:2.20.0-0ubuntu3
libmng1 1.0.9-1
libmodplug0c2 1:0.7-5.2ubuntu1
libmpcdec3 1.2.2-1build1
libnautilus-burn4 2.20.0-0ubuntu1
libnautilus-extension1 1:2.20.0-0ubuntu7
libncurses5 5.6+20070716-1ubuntu3
libncursesw5 5.6+20070716-1ubuntu3
libnet-dbus-perl 0.33.5-0.1
libnewt0.52 0.52.2-10ubuntu2
libnl1-pre6 1.0~pre6-5
libnm-glib0 0.6.5-0ubuntu16
libnm-util0 0.6.5-0ubuntu16
libnotify1 0.4.4-3build1
libnspr4-0d 4.6.6-3
libnss-mdns 0.10-0.1ubuntu1
libnss3-0d 3.11.5-3
libntfs-3g12 1:1.913-2ubuntu1
libntfs9 1.13.1-6
libogg0 1.1.3-2ubuntu2
liboobs-1-3 2.20.0-0ubuntu1
libopencdk8 0.5.13-2
liborbit2 1:2.14.9-0ubuntu1
libots0 0.4.2+cvs.2004.02.20-1.1build1
libpam-foreground 0.4-1
libpam-modules 0.99.7.1-5ubuntu1
libpam-runtime 0.99.7.1-5ubuntu1
libpam0g 0.99.7.1-5ubuntu1
libpanel-applet2-0 1:2.20.0.1-0ubuntu6
libpango1.0-0 1.18.2-0ubuntu1
libpango1.0-common 1.18.2-0ubuntu1
libpaper-utils 1.1.22ubuntu1
libpaper1 1.1.22ubuntu1
libparted1.7-1 1.7.1-5.1ubuntu8
libpcap0.8 0.9.7-1build1
libpci2 2:2.1.11-3build1
libpcre3 7.2-1ubuntu2
libpcrecpp0 7.2-1ubuntu2
libperl5.8 5.8.8-7ubuntu3
libpng12-0 1.2.15~beta5-2build1
libpoppler-glib2 0.6-0ubuntu2
libpoppler2 0.6-0ubuntu2
libpopt0 1.10-3build1
libportaudio0 18.1-6
libpulse0 0.9.6-1ubuntu2
libpurple0 1:2.2.1-1ubuntu4
libqthreads-12 1.6.8-6ubuntu1
libreadline5 5.2-3build1
librecode0 3.6-14
librpc-xml-perl 0.59-1
librsvg2-2 2.18.2-1
librsvg2-common 2.18.2-1
libsane 1.0.19~cvs20070505-3ubuntu2
libsasl2-2 2.1.22.dfsg1-9ubuntu2
libsasl2-modules 2.1.22.dfsg1-9ubuntu2
libscim8c2a 1.4.7-1ubuntu2
libscrollkeeper0 0.3.14-13ubuntu3
libsdl1.2debian 1.2.11-9ubuntu2
libsdl1.2debian-alsa 1.2.11-9ubuntu2
libselinux1 2.0.15-2ubuntu1
libsensors3 1:2.10.4-1ubuntu1
libsepol1 2.0.3-1
libsexy2 0.1.11-2
libsigc++-2.0-0c2a 2.0.17-2ubuntu2
libslang2 2.0.7-2
libslp1 1.2.1-6.2
libsm6 2:1.0.3-1
libsmbclient 3.0.26a-1ubuntu2
libsnmp-base 5.3.1-6ubuntu2
libsnmp10 5.3.1-6ubuntu2
libspeex1 1.1.12-3
libsqlite3-0 3.4.2-1build1
libss2 1.40.2-1ubuntu1
libssl0.9.8 0.9.8e-5ubuntu3
libstartup-notification0 0.9-1
libstdc++6 4.2.1-5ubuntu4
libsysfs2 2.1.0-2
libt1-5 5.1.0-3
libtag1c2a 1.4-8
libtagc0 1.4-8
libtasn1-3 0.3.9-1
libterm-readkey-perl 2.30-3ubuntu1
libtext-charwidth-perl 0.04-4build1
libtext-iconv-perl 1.4-3
libtext-wrapi18n-perl 0.06-5
libthai-data 0.1.9-1
libthai0 0.1.9-1
libtheora0 0.0.0.alpha7.dfsg-2ubuntu1
libthunar-vfs-1-2 0.8.0-6ubuntu3
libtiff4 3.8.2-7ubuntu2
libtotem-plparser7 2.20.0-0ubuntu3
libuniconf4.3 4.3-0ubuntu6
liburi-perl 1.35.dfsg.1-1
libusb-0.1-4 2:0.1.12-7
libusplash0 0.5.7
libuuid1 1.40.2-1ubuntu1
libvolume-id0 113-0ubuntu16
libvorbis0a 1.2.0.dfsg-1
libvte-common 1:0.16.9-0ubuntu3
libvte9 1:0.16.9-0ubuntu3
libwmf0.2-7 0.2.8.4-6
libwnck-common 2.20.0-0ubuntu1
libwnck22 2.20.0-0ubuntu1
libwpd-stream8c2a 0.8.10-1ubuntu1
libwpd8c2a 0.8.10-1ubuntu1
libwrap0 7.6.dbs-14
libwvstreams4.3-base 4.3-0ubuntu6
libwvstreams4.3-extras 4.3-0ubuntu6
libwww-perl 5.805-1
libx11-6 2:1.1.1-1ubuntu4
libx11-data 2:1.1.1-1ubuntu4
libx86-1 0.99-1.2ubuntu2
libxau6 1:1.0.3-2
libxaw7 2:1.0.3-3ubuntu1
libxcb-shape0 1.0-3
libxcb-shm0 1.0-3
libxcb-xv0 1.0-3
libxcb1 1.0-3
libxcomposite1 1:0.4.0-0ubuntu1
libxcursor1 1:1.1.8-2
libxdamage1 1:1.1.1-3
libxdmcp6 1:1.0.2-2
libxevie1 1:1.0.2-2
libxext6 2:1.0.3-2build1
libxfce4mcs-client3 4.4.1-1ubuntu1
libxfce4mcs-manager3 4.4.1-1ubuntu1
libxfce4util4 4.4.1-1ubuntu1
libxfcegui4-4 4.4.1-1ubuntu1
libxfixes3 1:4.0.3-2
libxfont1 1:1.3.0-0ubuntu1
libxft2 2.1.12-2ubuntu4
libxi6 2:1.1.2-1
libxine1 1.1.7-1ubuntu1
libxinerama1 2:1.0.2-1build1
libxkbfile1 1:1.0.4-1
libxklavier11 3.2-2
libxml-parser-perl 2.34-4.3
libxml-twig-perl 1:3.29-1
libxml2 2.6.30.dfsg-2ubuntu1
libxmu6 2:1.0.3-1ubuntu1
libxmuu1 2:1.0.3-1ubuntu1
libxp6 1:1.0.0.xsf1-1build1
libxplc0.3.13 0.3.13-1build1
libxpm4 1:3.5.6-3
libxrandr2 2:1.2.1-1
libxrender1 1:0.9.2-1
libxres1 2:1.0.3-1
libxslt1.1 1.1.21-2ubuntu2
libxss1 1:1.1.2-1
libxt6 1:1.0.5-3
libxtrap6 2:1.0.0-4build1
libxtst6 2:1.0.2-1ubuntu1
libxv1 2:1.0.3-1ubuntu1
libxvmc1 2:1.0.4-2ubuntu1
libxxf86dga1 2:1.0.1-2
libxxf86misc1 1:1.0.1-2
libxxf86vm1 1:1.0.1-2
libzephyr3 2.1.20070719.SNAPSHOT-1
link-grammar-dictionaries-en 4.2.2-4
linux-generic 2.6.22.14.21
linux-headers-2.6.22-14 2.6.22-14.46
linux-headers-2.6.22-14-generic 2.6.22-14.46
linux-headers-generic 2.6.22.14.21
linux-image-2.6.22-14-generic 2.6.22-14.46
linux-image-generic 2.6.22.14.21
linux-restricted-modules-2.6.22-14-generic 2.6.22.4-14.9
linux-restricted-modules-common 2.6.22.4-14.9
linux-restricted-modules-generic 2.6.22.14.21
linux-sound-base 1.0.14-1ubuntu2
linux-ubuntu-modules-2.6.22-14-generic 2.6.22-14.37
listres 1:1.0.1-0ubuntu2
locales 2.6.1-1
login 1:4.0.18.1-9
logrotate 3.7.1-3
lsb-base 3.1-23.1ubuntu3
lsb-release 3.1-23.1ubuntu3
lshw 02.10-4ubuntu2
lsof 4.78.dfsg.1-2
ltrace 0.4-1ubuntu2
lupin-casper 0.8
make 3.81-3build1
makedev 2.3.1-83ubuntu3
man-db 2.4.4-3
manpages 2.62-1
mawk 1.3.3-11ubuntu2
mcpp 2.6.4-1ubuntu2
memtest86+ 1.70-3ubuntu1
mesa-utils 7.0.1-1ubuntu3
metacity 1:2.20.0-0ubuntu3
metacity-common 1:2.20.0-0ubuntu3
mii-diag 2.11-2
mime-support 3.39-1
min12xxw 0.0.9-1build1
mktemp 1.5-3
module-init-tools 3.3-pre4-2ubuntu4
mount 2.13-8ubuntu1
mousepad 0.2.12-1ubuntu1
mozilla-firefox-locale-ar 2.0.0.7+1-0ubuntu2
mozilla-thunderbird 2.0.0.6+nobinonly-0ubuntu1
mscompress 0.3-2ubuntu1
mtr-tiny 0.72-2
nano 2.0.6-2
ncurses-base 5.6+20070716-1ubuntu3
ncurses-bin 5.6+20070716-1ubuntu3
net-tools 1.60-17ubuntu2
netbase 4.29ubuntu2
netcat 1.10-33
network-manager 0.6.5-0ubuntu16
network-manager-gnome 0.6.5-0ubuntu10
notification-daemon 0.3.7-1ubuntu8
ntfs-3g 1:1.913-2ubuntu1
ntfsprogs 1.13.1-6
ntpdate 1:4.2.4p0+dfsg-1ubuntu2
nvidia-kernel-common 20051028+1ubuntu7
oclock 1:1.0.1-0ubuntu2
onboard 0.87
openprinting-ppds 20070919-0ubuntu3
openssh-client 1:4.6p1-5build1
openssl 0.9.8e-5ubuntu3
orage 4.4.1-1ubuntu1
os-prober 1.21ubuntu4
parted 1.7.1-5.1ubuntu8
passwd 1:4.0.18.1-9
pciutils 1:2.2.4-1ubuntu2
pcmciautils 014-3ubuntu2
perl 5.8.8-7ubuntu3
perl-base 5.8.8-7ubuntu3
perl-modules 5.8.8-7ubuntu3
pidgin 1:2.2.1-1ubuntu4
pidgin-data 1:2.2.1-1ubuntu4
pnm2ppa 1.12-16
poppler-utils 0.6-0ubuntu2
popularity-contest 1.42ubuntu1
powermanagement-interface 0.3.17
powermgmt-base 1.29build1
powernowd 0.97-1ubuntu7
ppp 2.4.4rel-9ubuntu2
pppconfig 2.3.17ubuntu1
pppoeconf 1.16ubuntu1
procps 1:3.2.7-3ubuntu5
psmisc 22.5-1
pxljr 1.1-0ubuntu1
python 2.5.1-1ubuntu2
python-apport 0.98
python-apt 0.7.3.1ubuntu4
python-at-spi 0.6.1-1ubuntu2
python-cairo 1.4.0-2ubuntu1
python-central 0.5.15ubuntu2
python-cups 1.9.27-0ubuntu1
python-dbus 0.82.0-1ubuntu1
python-exo 0.3.2-4ubuntu1
python-gconf 2.20.0-0ubuntu1
python-gdbm 2.5.1-1ubuntu1
python-glade2 2.12.0-0ubuntu2
python-gnome2 2.20.0-0ubuntu1
python-gnome2-desktop 2.20.0-0ubuntu1
python-gnomecanvas 2.20.0-0ubuntu1
python-gnupginterface 0.3.2-9ubuntu1
python-gobject 2.14.0-0ubuntu1
python-gst0.10 0.10.8-1ubuntu1
python-gtk2 2.12.0-0ubuntu2
python-gtkhtml2 2.19.1-0ubuntu4
python-launchpad-bugs 0.2.21
python-launchpad-integration 0.1.15
python-libxml2 2.6.30.dfsg-2ubuntu1
python-minimal 2.5.1-1ubuntu2
python-notify 0.1.1-1ubuntu2
python-numeric 24.2-8
python-orca-brlapi 2.20.0-0ubuntu1
python-problem-report 0.98
python-pyorbit 2.14.3-1ubuntu1
python-sexy 0.1.9-1ubuntu1
python-software-properties 0.60
python-support 0.6.4ubuntu1
python-virtkey 0.42
python-vte 1:0.16.9-0ubuntu3
python-xdg 0.15-1.1ubuntu2
python-xml 0.8.4-8ubuntu1
python2.5 2.5.1-5ubuntu5
python2.5-minimal 2.5.1-5ubuntu5
radeontool 1.5-5build1
readahead 1:0.20050517.0220-0ubuntu11
readline-common 5.2-3build1
reiserfsprogs 1:3.6.19-6
restricted-manager 0.33.1
restricted-manager-core 0.33.1
rsync 2.6.9-5ubuntu1
samba-common 3.0.26a-1ubuntu2
scim 1.4.7-1ubuntu2
scim-gtk2-immodule 1.4.7-1ubuntu2
scim-modules-socket 1.4.7-1ubuntu2
scim-modules-table 0.5.7-1ubuntu2
scim-tables-additional 0.5.7-1ubuntu2
screen 4.0.3-0.4ubuntu2
screensaver-default-images 0.2-1
scrollkeeper 0.3.14-13ubuntu3
sed 4.1.5-2
sessreg 1:1.0.2-0ubuntu1
sgml-base 1.26
sgml-data 2.0.3
shared-mime-info 0.22-2ubuntu2
slocate 3.1-1ubuntu3
smartdimmer 0.1-2build1
smbclient 3.0.26a-1ubuntu2
smproxy 1:1.0.2-0ubuntu1
software-properties-gtk 0.60
splix 1.0.1.1-0ubuntu2
ssl-cert 1.0.14
startup-tasks 0.3.8-2
strace 4.5.15-1ubuntu1
sudo 1.6.8p12-5ubuntu2
synaptic 0.60ubuntu5
sysklogd 1.4.1-21ubuntu3
system-config-printer 0.7.75+svn1653-0ubuntu2
system-services 0.3.8-2
system-tools-backends 2.4.0-0ubuntu1
sysv-rc 2.86.ds1-14.1ubuntu31
sysvutils 2.86.ds1-14.1ubuntu31
tango-icon-theme 0.8.0~cvs070515-0ubuntu1
tango-icon-theme-common 0.7-0ubuntu1
tar 1.18-2ubuntu1
tasksel 2.67ubuntu10
tasksel-data 2.67ubuntu10
tcpd 7.6.dbs-14
tcpdump 3.9.7-1
telnet 0.17-35ubuntu1
thunar 0.8.0-6ubuntu3
thunar-archive-plugin 0.2.4-1ubuntu1
thunar-data 0.8.0-6ubuntu3
thunar-media-tags-plugin 0.1.2-1ubuntu1
thunar-volman 0.1.2-1ubuntu3
thunderbird 2.0.0.6+nobinonly-0ubuntu1
thunderbird-locale-de 1:2.0.0.0+1-0ubuntu1
thunderbird-locale-fr 1:2.0.0.0+1-0ubuntu1
thunderbird-locale-ja 1:2.0.0.0+1-0ubuntu1
thunderbird-locale-ru 1:2.0.0.0+1-0ubuntu1
time 1.7-21build1
toshset 1.72-4ubuntu1
totem 2.20.0-0ubuntu3
totem-xine 2.20.0-0ubuntu3
ttf-arabeyes 1.1-9
ttf-arphic-uming 0.1.20060928-2.1ubuntu1
ttf-bitstream-vera 1.10-7
ttf-dejavu 2.19-1ubuntu3
ttf-dejavu-core 2.19-1ubuntu3
ttf-dejavu-extra 2.19-1ubuntu3
ttf-freefont 20060501cvs-12
ttf-gentium 1.02-2ubuntu2
ttf-indic-fonts-core 1:0.5.0-0ubuntu1
ttf-kochi-gothic 1.0.20030809-4ubuntu2
ttf-kochi-mincho 1.0.20030809-4ubuntu2
ttf-lao 0.0.20060226-2
ttf-malayalam-fonts 1:0.5.0-0ubuntu1
ttf-mgopen 1.1-2
ttf-thai-tlwg 1:0.4.7-1
ttf-unfonts-core 1.0.1-6ubuntu1
tzdata 2007f-3ubuntu1
ubiquity 1.6.8
ubiquity-casper 1.110
ubiquity-frontend-gtk 1.6.8
ubiquity-ubuntu-artwork 1.6.8
ubufox 0.4~beta1-0ubuntu3
ubuntu-artwork 38
ubuntu-keyring 2007.06.11
ubuntu-minimal 1.79
ubuntu-standard 1.79
ucf 3.001
udev 113-0ubuntu16
unattended-upgrades 0.25.3ubuntu1
unzip 5.52-10ubuntu1
update-inetd 4.27-0.5
update-manager 1:0.81
update-manager-core 1:0.81
update-notifier 0.61
update-notifier-common 0.61
upstart 0.3.8-2
upstart-compat-sysv 0.3.8-2
upstart-logd 0.3.8-2
usbutils 0.72-8ubuntu1
user-setup 1.14ubuntu4
usplash 0.5.7
util-linux 2.13-8ubuntu1
util-linux-locales 2.13-8ubuntu1
vbetool 1.0-0ubuntu1
viewres 1:1.0.1-0ubuntu2
vim-common 1:7.1-056+2ubuntu2
vim-runtime 1:7.1-056+2ubuntu2
vim-tiny 1:7.1-056+2ubuntu2
volumeid 113-0ubuntu16
w3m 0.5.1-5.1ubuntu1
wget 1.10.2-3ubuntu1
whiptail 0.52.2-10ubuntu2
wireless-tools 29~pre20-1ubuntu1
wodim 9:1.1.6-1ubuntu3
wpasupplicant 0.6.0+0.5.8-0ubuntu1
wvdial 1.56-1.2ubuntu2
x-ttcidfont-conf 25.1
x11-common 1:7.2-5ubuntu13
x11perf 1:1.4.1-0ubuntu1
xauth 1:1.0.2-0ubuntu1
xbase-clients 1:7.2-5ubuntu13
xbiff 1:1.0.1-0ubuntu2
xbitmaps 1.0.1-2ubuntu1
xcalc 1:1.0.1-0ubuntu2
xclipboard 1:1.0.1-0ubuntu2
xclock 1:1.0.2-0ubuntu1
xconsole 1:1.0.2-0ubuntu1
xcursor-themes 1.0.1-5ubuntu1
xcursorgen 1:1.0.1-0ubuntu1
xdg-utils 1.0.1-2
xditview 1:1.0.1-0ubuntu2
xdpyinfo 1:1.0.2-0ubuntu1
xdriinfo 1:1.0.1-0ubuntu1
xev 1:1.0.2-0ubuntu1
xeyes 1:1.0.1-0ubuntu2
xf86dga 1:1.0.2-0ubuntu1
xfce4-appfinder 4.4.1-1ubuntu1
xfce4-battery-plugin 0.5.0-1ubuntu1
xfce4-clipman-plugin 2:0.8.0-1ubuntu1
xfce4-cpugraph-plugin 0.3.0-2ubuntu1
xfce4-dict-plugin 0.2.1-0ubuntu1
xfce4-fsguard-plugin 0.3.0-3ubuntu1
xfce4-icon-theme 4.4.1-1
xfce4-mailwatch-plugin 1.0.1-2ubuntu1
xfce4-mcs-manager 4.4.1-1ubuntu1
xfce4-mcs-plugins 4.4.1-1ubuntu3
xfce4-mixer 1:4.4.1-3ubuntu1
xfce4-mixer-alsa 1:4.4.1-3ubuntu1
xfce4-mount-plugin 0.5.3-0ubuntu1
xfce4-netload-plugin 0.4.0-3ubuntu1
xfce4-notes-plugin 1.4.1-1ubuntu1
xfce4-panel 4.4.1-1ubuntu3
xfce4-places-plugin 1.0~beta1-0ubuntu2
xfce4-quicklauncher-plugin 1.9.4-1ubuntu1
xfce4-screenshooter-plugin 1.0.0-3ubuntu1
xfce4-session 4.4.1-1ubuntu4
xfce4-smartbookmark-plugin 0.4.2-1ubuntu2
xfce4-systemload-plugin 1:0.4.2-1ubuntu1
xfce4-terminal 0.2.6-3ubuntu1
xfce4-utils 4.4.1-1ubuntu5
xfce4-verve-plugin 0.3.5-1ubuntu1
xfce4-weather-plugin 0.6.0-1ubuntu1
xfce4-xkb-plugin 0.4.3-1ubuntu1
xfd 1:1.0.1-0ubuntu2
xfdesktop4 4.4.1-5ubuntu3
xfdesktop4-data 4.4.1-5ubuntu3
xfonts-100dpi 1:1.0.0-3
xfonts-75dpi 1:1.0.0-3
xfonts-base 1:1.0.0-4
xfonts-encodings 1:1.0.2-1
xfonts-scalable 1:1.0.0-6
xfonts-utils 1:1.0.1-1ubuntu1
xfontsel 1:1.0.2-0ubuntu1
xfprint4 4.4.1-1ubuntu2
xfsprogs 2.9.0-1
xfwm4 4.4.1-2ubuntu2
xfwm4-themes 4.4.1-1ubuntu1
xgamma 1:1.0.1-0ubuntu2
xgc 1:1.0.1-0ubuntu2
xhost 1:1.0.2-0ubuntu1
xinit 1.0.2-0ubuntu3
xkb-data 0.9-4ubuntu3
xkbutils 1:1.0.2-0ubuntu1
xkill 1:1.0.1-0ubuntu2
xload 1:1.0.2-0ubuntu1
xlogo 1:1.0.1-0ubuntu2
xlsatoms 1:1.0.1-0ubuntu2
xlsclients 1:1.0.1-0ubuntu2
xlsfonts 1:1.0.2-0ubuntu1
xmag 1:1.0.1-0ubuntu2
xman 1:1.0.2-0ubuntu1
xmessage 1:1.0.1-0ubuntu2
xml-core 0.11
xmodmap 1:1.0.2-0ubuntu1
xmore 1:1.0.1-0ubuntu2
xorg 1:7.2-5ubuntu13
xpmutils 1:3.5.6-3
xprop 1:1.0.2-0ubuntu1
xrandr 1:1.2.2-0ubuntu1
xrdb 1:1.0.3-0ubuntu1
xrefresh 1:1.0.2-0ubuntu1
xresprobe 0.4.24ubuntu8
xrgb 1:1.0.0-0ubuntu3
xscreensaver-data 4.24-5ubuntu3
xscreensaver-gl 4.24-5ubuntu3
xserver-xorg 1:7.2-5ubuntu13
xserver-xorg-core 2:1.3.0.0.dfsg-12ubuntu8
xserver-xorg-input-all 1:7.2-5ubuntu13
xserver-xorg-input-elographics 1:1.1.0-1
xserver-xorg-input-evdev 1:1.1.5-3
xserver-xorg-input-kbd 1:1.2.0-1+1.2.1ubuntu1
xserver-xorg-input-mouse 1:1.2.1-1
xserver-xorg-input-synaptics 0.14.6-0ubuntu10
xserver-xorg-input-wacom 1:0.7.7.7-0ubuntu2
xserver-xorg-video-all 1:7.2-5ubuntu13
xserver-xorg-video-amd 2.7.7.0-1
xserver-xorg-video-apm 1:1.1.1-7
xserver-xorg-video-ark 1:0.6.0-6
xserver-xorg-video-ati 1:6.7.195-1ubuntu2
xserver-xorg-video-chips 1:1.1.1-4ubuntu1
xserver-xorg-video-cirrus 1:1.1.0-3ubuntu1
xserver-xorg-video-cyrix 1:1.1.0-4ubuntu1
xserver-xorg-video-dummy 1:0.2.0-3ubuntu1
xserver-xorg-video-fbdev 1:0.3.1-1ubuntu1
xserver-xorg-video-glint 1:1.1.1-6
xserver-xorg-video-i128 1:1.2.1-2
xserver-xorg-video-i740 1:1.1.0-3ubuntu1
xserver-xorg-video-i810 2:1.7.4-0ubuntu5
xserver-xorg-video-imstt 1:1.1.0-3ubuntu1
xserver-xorg-video-intel 2:2.1.1-0ubuntu9
xserver-xorg-video-mga 1:1.4.6.1.dfsg.1-3
xserver-xorg-video-neomagic 1:1.1.1-5ubuntu1
xserver-xorg-video-newport 1:0.2.1-2ubuntu1
xserver-xorg-video-nsc 1:2.8.2-2
xserver-xorg-video-nv 1:2.1.5-1ubuntu1
xserver-xorg-video-psb 0.2.1-1ubuntu3
xserver-xorg-video-rendition 1:4.1.3.dfsg.1-2
xserver-xorg-video-s3 1:0.5.0-2
xserver-xorg-video-s3virge 1:1.9.1-3ubuntu1
xserver-xorg-video-savage 1:2.1.2-6ubuntu1
xserver-xorg-video-siliconmotion 1:1.5.1-1
xserver-xorg-video-sis 1:0.9.3-2ubuntu1
xserver-xorg-video-sisusb 1:0.8.1-3ubuntu1
xserver-xorg-video-tdfx 1:1.3.0-1ubuntu1
xserver-xorg-video-tga 1:1.1.0-3ubuntu2
xserver-xorg-video-trident 1:1.2.3-1ubuntu1
xserver-xorg-video-tseng 1:1.1.1-1
xserver-xorg-video-v4l 1:0.1.1-0ubuntu2
xserver-xorg-video-vesa 1:1.3.0-1ubuntu5
xserver-xorg-video-vga 1:4.1.0-3ubuntu1
xserver-xorg-video-via 1:0.2.2-2
xserver-xorg-video-vmware 1:10.15.0-0ubuntu1
xserver-xorg-video-voodoo 1:1.1.1-2
xset 1:1.0.2-0ubuntu1
xsetmode 1:1.0.0-0ubuntu2
xsetpointer 1:1.0.1-0ubuntu1
xsetroot 1:1.0.1-0ubuntu2
xsm 1:1.0.1-0ubuntu2
xstdcmap 1:1.0.1-0ubuntu2
xterm 229-1
xtrap 1:1.0.2-0ubuntu1
xubuntu-artwork-usplash 0.19
xubuntu-default-settings 0.35
xubuntu-desktop 2.50
xubuntu-docs 7.10.1
xutils 1:7.2-5ubuntu13
xutils-dev 1:7.2.ds2-1ubuntu1
xvidtune 1:1.0.1-0ubuntu2
xvinfo 1:1.0.1-0ubuntu2
xvnc4viewer 4.1.1+xorg1.0.2-0ubuntu6
xwd 1:1.0.1-0ubuntu2
xwininfo 1:1.0.2-0ubuntu1
xwud 1:1.0.1-0ubuntu2
zenity 2.20.0-0ubuntu1
zip 2.32-1
zlib1g 1:1.2.3.3.dfsg-5ubuntu2
| en |
converted_docs | 426098 | This Book
Purpose
The primary purpose of *The Blue Book* is to provide guidance to school
business office personnel who handle fiscal recordkeeping, accounting,
and reporting functions for federal Title IV student financial aid
programs authorized by the Higher Education Act of 1965, as amended
(HEA). In addition, it provides a technical resource of Title IV
management responsibilities that are shared between various
administrative offices in a school. It also provides general information
about Title IV programs, policies, and procedures that are useful to all
institutional personnel who administer and manage Title IV programs.
Some procedures discussed in *The Blue Book* are recommended to help
institutions meet the fiscal responsibilities they agree to when they
sign a Title IV Program Participation Agreement (PPA) with the U.S.
Department of Education (ED). Other procedures described in *The Blue
Book* are required by federal laws and regulations. Although *The Blue
Book*'s primary focus is fiscal responsibilities, financial aid
administrators can also use *The Blue Book* as a reference tool for
shared responsibilities.
This edition of *The Blue Book* places special emphasis on the benefits
and challenges of managing Title IV programs electronically. The goals
of any electronic‑management system are to maintain accurate,
well‑organized records; submit required reports in an accurate and
timely manner; comply with federal laws and regulations; and provide
quality service to students.
Further, ED requires schools to use automated methods to meet certain
Title IV requirements, such as retrieving Institutional Student
Information Records (ISIRs) through the Internet, reporting Federal Pell
Grant disbursements through the Recipient Financial Management System
(RFMS), submitting the Fiscal Operations Report and Application to
Participate (FISAP) electronically, and reporting Title IV information
(including overpayments) online to the National Student Loan Data System
(NSLDS). Some schools also use ED's Grant Administration and Payment
System (GAPS) to request and draw down Title IV funds.\*
As a result, cooperation and communication across a school's
administrative offices, especially between the business office and the
financial aid office, are more important than ever. Schools also need to
be careful to ensure that electronic management does not blur the
legally required separation of *authorizing* Title IV funds and
*disbursing* Title IV funds. *The Blue Book* is designed to help schools
achieve these goals and to use ED's automated systems successfully.
What This Book Contains
{width="6.853472222222222in"
height="8.424305555555556in"}
Using *The Blue Book* at Your School
*The* *Blue Book* can perform several different functions for a school.
For example, it can serve as a:
- training guide for new employees (especially in conjunction with
ED's Fiscal Management Training Workshop and its Participant's
Guide),
- reference manual for any employee, *and*
- basis for a school's fiscal policies and procedures manual.
Regardless of how a school uses this book, remember that it is only a
guide, and it does not replace federal laws, regulations, or generally
accepted accounting principles (GAAP). School personnel are still
responsible for familiarizing themselves with all relevant primary
source documents.
Margin References
*The Blue Book* uses three icons in the margin notes to direct readers
to other resources for the material being discussed in the text.
{width="0.48680555555555555in"
height="0.5055555555555555in"}
> The Computer icon is for electronic references, directing readers to
> Web sites of particular interest.
>
> {width="0.44930555555555557in"
> height="0.45694444444444443in"}The Book icon is for published
> references and directs readers to specific regulations and other
> resources of particular interest (some of which might also be
> available electronically).
>
> {width="0.8201388888888889in"
> height="0.8111111111111111in"}
>
> The New icon is for newly available Web sites and published resources,
> as well as new program guidelines.
{width="0.24027777777777778in"
height="0.24444444444444444in"}Other Resources
A companion publication to *The Blue Book* is ED's *Student Financial
Aid Handbook* (Handbook), which is a primary resource for financial aid
administrators. The Handbook is mentioned frequently throughout *The
Blue Book*. The Handbook consists of nine volumes published individually
and successively by ED each year and distributed to school financial aid
offices. Fiscal office personnel should know where to locate their
school's copy of the Handbook, and they might want to copy pertinent
sections for their own use or print them from\
ED's Web site.\*
Another ED publication vital to the work of a fiscal officer is the\
*U.S. Department of Education Payee Guide for the Grant Administration
and Payment System (GAPS)* \[GAPS *Payee Guide*\]. It provides
information on systems operations and procedures for federal funds paid
to schools through GAPS.\
The GAPS *Payee Guide* helps schools fulfill their responsibilities in
expediting payments, completing forms and reports, and controlling
federal cash received through GAPS. It also serves as a guide to ED's
new ePayments Web site.
Effective Date
This edition of *The Blue Book* is written on the basis of laws,
regulations, policies, and procedures published by April 1, 2000 and in
effect for the 2001-02 award year. Schools should be aware, however,
these laws, regulations, policies, and procedures are subject to change.
It is a school's responsibility to keep abreast of such changes so it
remains in compliance with current rules. Regular updates and changes in
policy guidance are posted on a daily basis on ED's IFAP Web site.
Comments and Suggestions on *The Blue Book*
Your comments and suggestions about any aspect of *The Blue Book* are
welcome. We are particularly interested in learning:
- the purposes for which *The Blue Book* is being used (for example,
reference, self-study, training new staff);
- the appropriateness of the content and the usefulness of the
appendices; *and*
- whether you feel this publication is among those that ED's Office of
Student Financial Assistance (OSFA) should update on a regular
basis.
You may send your comments to:
*The Blue Book*/SFA University
SFA/U.S. Department of Education
Room 600-C, Portals Building
1280 Maryland Avenue, SW
Washington, DC 20202-5361
| en |
converted_docs | 260801 | **[Sample]{.underline} Blood and Body Fluid Exposure Report Form**
<table>
<colgroup>
<col style="width: 13%" />
<col style="width: 4%" />
<col style="width: 9%" />
<col style="width: 2%" />
<col style="width: 1%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><h2 id="facility-name">Facility name:</h2></td>
<td colspan="5"><h2 id="section"></h2></td>
<td colspan="3"><h2 id="section-1"></h2></td>
<td colspan="5"><h2 id="section-2"></h2></td>
<td colspan="3"><h2 id="section-3"></h2></td>
<td colspan="2"><h2 id="section-4"></h2></td>
</tr>
<tr class="even">
<td colspan="3"><h1 id="section-5"></h1></td>
<td colspan="3"><h1 id="section-6"></h1></td>
<td colspan="3"><h1 id="section-7"></h1></td>
<td colspan="2"><h1 id="section-8"></h1></td>
<td colspan="6"><h1 id="section-9"></h1></td>
<td><h1 id="section-10"></h1></td>
<td><h1 id="section-11"></h1></td>
</tr>
<tr class="odd">
<td colspan="3"><h1 id="name-of-exposed-worker-last">Name of exposed
worker: Last </h1></td>
<td colspan="3"><h1 id="section-12"></h1></td>
<td colspan="3"><h1 id="section-13"></h1></td>
<td><h1 id="first">First :</h1></td>
<td colspan="7"><h1 id="section-14"> </h1></td>
<td><h1 id="id">ID #:</h1></td>
<td><h1 id="section-15"></h1></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="7"><strong>Date of exposure: _________
/________/________</strong></td>
<td colspan="10"><h5 id="time-of-exposure-_____________">Time of
exposure: ______:_______</h5></td>
<td colspan="2"><strong>AM PM</strong> (Circle)</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"></td>
<td colspan="3"></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="2"><h1 id="job-titleoccupation">Job
title/occupation:</h1></td>
<td colspan="4"><h1 id="section-16"></h1></td>
<td colspan="3"><h1 id="section-17"></h1></td>
<td colspan="6"><h1 id="departmentwork-unit">Department/work unit:
</h1></td>
<td colspan="4"><h1 id="section-18"></h1></td>
</tr>
<tr class="even">
<td colspan="2"><h1 id="section-19"></h1></td>
<td colspan="4"><h1 id="section-20"></h1></td>
<td colspan="3"><h1 id="section-21"></h1></td>
<td colspan="4"><h1 id="section-22"></h1></td>
<td colspan="4"><h1 id="section-23"></h1></td>
<td colspan="2"><h1 id="section-24"></h1></td>
</tr>
<tr class="odd">
<td colspan="5"><h1 id="location-where-exposure-occurred">Location where
exposure occurred:</h1></td>
<td colspan="3"><h1 id="section-25"></h1></td>
<td colspan="4"><h1 id="section-26"></h1></td>
<td colspan="4"><h1 id="section-27"></h1></td>
<td colspan="3"><h1 id="section-28"></h1></td>
</tr>
<tr class="even">
<td colspan="4"><h1 id="section-29"></h1></td>
<td colspan="2"><h1 id="section-30"></h1></td>
<td colspan="3"><h1 id="section-31"></h1></td>
<td colspan="4"><h1 id="section-32"></h1></td>
<td colspan="4"><h1 id="section-33"></h1></td>
<td colspan="2"><h1 id="section-34"></h1></td>
</tr>
<tr class="odd">
<td colspan="4"><strong>Name of person completing form:</strong></td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="4"></td>
<td colspan="4"></td>
<td colspan="2"></td>
</tr>
</tbody>
</table>
-----------------------------------------------------------------------
-----------------------------------------------------------------------
**Section I. Type of Exposure** *(Check all that apply.)*
-- -- ------------------------------------------------------------------- --
**Percutaneous (Needle or sharp object that was in contact with
blood or body fluids)**
*(Complete Sections II, III, IV, and V.)*
**Mucocutaneous** *(Check below [and]{.underline} complete Sections
III, IV, and VI.)*
**\_\_\_ Mucous Membrane \_\_\_ Skin**
**Bite** *(Complete Sections III, IV, and VI.)*
-- -- ------------------------------------------------------------------- --
### {#section-35}
### Section II. Needle/Sharp Device Information
*(If exposure was [percutaneous]{.underline}, provide the following
information about the device involved.)*
<table style="width:100%;">
<colgroup>
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 14%" />
<col style="width: 2%" />
<col style="width: 19%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 24%" />
<col style="width: 0%" />
<col style="width: 0%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="2"></td>
<td colspan="3"><h1 id="name-of-device">Name of device:</h1></td>
<td colspan="11"><h1 id="section-36"></h1></td>
<td><h1 id="section-37"></h1></td>
<td><h1 id="section-38"></h1></td>
<td colspan="3"><h1 id="unknownunable-to-determine">Unknown/Unable to
determine</h1></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><h1 id="section-39"></h1></td>
<td colspan="10"><h1 id="section-40"></h1></td>
<td><h1 id="section-41"></h1></td>
<td><h1 id="section-42"></h1></td>
<td colspan="3"><h1 id="section-43"></h1></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Brand/manufacturer:</strong></td>
<td colspan="9"></td>
<td></td>
<td></td>
<td colspan="3"><h1 id="unknownunable-to-determine-1">Unknown/Unable to
determine</h1></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"></td>
<td colspan="9"></td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="19"><strong>Did the device have a sharps injury prevention
feature, i.e., a “safety device”?</strong></td>
<td></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td><h1 id="section-44"></h1></td>
<td colspan="4"><h1 id="yes">Yes</h1></td>
<td><h1 id="section-45"></h1></td>
<td><h1 id="no">No</h1></td>
<td colspan="2"><h1 id="section-46"></h1></td>
<td colspan="2"><h1 id="section-47"></h1></td>
<td colspan="6"><h1 id="unknownunable-to-determine-2">Unknown/Unable to
determine</h1></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="3"></td>
<td><h1 id="section-48"></h1></td>
<td colspan="4"><h1 id="section-49"></h1></td>
<td><h1 id="section-50"></h1></td>
<td><h1 id="section-51"></h1></td>
<td colspan="2"><h1 id="section-52"></h1></td>
<td colspan="2"><h1 id="section-53"></h1></td>
<td colspan="6"><h1 id="section-54"></h1></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="20"><h4 id="if-yes-when-did-the-injury-occur">If yes, when
did the injury occur?</h4></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="20"><h4 id="section-55"></h4></td>
<td></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td><h1 id="section-56"></h1></td>
<td colspan="7"><h1
id="before-activation-of-safety-feature-was-appropriate">Before
activation of safety feature was appropriate</h1></td>
<td colspan="2"><h1 id="section-57"></h1></td>
<td colspan="2"><h1 id="section-58"></h1></td>
<td colspan="6"><h1 id="safety-feature-failed-after-activation">Safety
feature failed after activation</h1></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3"></td>
<td></td>
<td colspan="7"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td></td>
<td colspan="7">During activation of the safety feature</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6">Safety feature not activated</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3"></td>
<td></td>
<td colspan="7"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td></td>
<td colspan="7">Safety feature improperly activated</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6">Other: __________________________________</td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="18"><strong>Describe what happened with the safety feature,
e.g., why it failed or why it was not activated:</strong></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td colspan="5"></td>
<td colspan="5"></td>
<td colspan="2"></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="22"></td>
</tr>
</tbody>
</table>
Section III. Employee Narrative *(Optional)*
------------------------------------------------ ----------------------
Describe how the exposure occurred and how it
might have been prevented:
------------------------------------------------ ----------------------
[**NOTE:** This is not a CDC or OSHA form.]{.underline} This form was
developed by CDC to help healthcare facilities collect detailed exposure
information that is specifically useful for the facilities' prevention
planning. [Information on this page (#1)]{.underline} [may]{.underline}
meet OSHA sharps injury documentation requirements and can be copied and
filed for purposes of maintaining a separate sharps injury log.
[Procedures for maintaining employee confidentiality must be
followed.]{.underline}
**Section IV. Exposure and Source Information**
A. Exposure Details: *(Check all that apply.)*
> **1. Type of fluid or material (For body fluid exposures
> [only]{.underline}, check which fluid in adjacent box.)**
+---+-------------------------------------------------------------------+
| | > Blood/blood products |
+---+-------------------------------------------------------------------+
| | |
+---+-------------------------------------------------------------------+
| | > Visibly bloody body fluid\* |
+---+-------------------------------------------------------------------+
| | |
+---+-------------------------------------------------------------------+
| | > Non-visibly bloody body fluid**\*** |
+---+-------------------------------------------------------------------+
| | |
+---+-------------------------------------------------------------------+
| | > Visibly bloody solution (e.g., water used to clean a blood |
| | > spill) |
+---+-------------------------------------------------------------------+
2. **Body site of exposure.** *(Check all that apply.)*
-- ----------------- -- ---------------- -- ----------------------------------------------------- -- -------------
Hand/finger Eye Mouth/nose Face
Arm Leg Other (Describe:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_)
-- ----------------- -- ---------------- -- ----------------------------------------------------- -- -------------
3. **If percutaneous exposure:**
**Depth of injury** *(Check only one.)*
+---+--------------------------------------------------------------------+
| | > Superficial (e.g., scratch, no or little blood) |
+---+--------------------------------------------------------------------+
| | |
+---+--------------------------------------------------------------------+
| | > Moderate (e.g., penetrated through skin, wound bled) |
+---+--------------------------------------------------------------------+
| | |
+---+--------------------------------------------------------------------+
| | > Deep (e.g., intramuscular penetration) |
+---+--------------------------------------------------------------------+
| | |
+---+--------------------------------------------------------------------+
| | > Unsure/Unknown |
+---+--------------------------------------------------------------------+
---------------------------------- -- --------- -- ------- -- ----------------
**Was blood visible on device Yes No Unsure/Unknown
before exposure?**
---------------------------------- -- --------- -- ------- -- ----------------
4. **If mucous membrane or skin exposure:** *(Check only one.)*
###### Approximate volume of material
+---+--------------------------------------------------------------------+
| | > Small (e.g., few drops) |
+---+--------------------------------------------------------------------+
| | |
+---+--------------------------------------------------------------------+
| | > Large (e.g., major blood splash) |
+---+--------------------------------------------------------------------+
---------------------------------- -- --------- -- ------- -- ----------------
**If skin exposure, was skin Yes No Unsure/Unknown
intact?**
---------------------------------- -- --------- -- ------- -- ----------------
# B. Source Information
----------------------------------- -- --------- -- ------- -- ----------------
**1. Was the source individual Yes No Unsure/Unknown
identified?**
----------------------------------- -- --------- -- ------- -- ----------------
**2. Provide the serostatus of the source patient for the following
pathogens.**
<table style="width:100%;">
<colgroup>
<col style="width: 28%" />
<col style="width: 6%" />
<col style="width: 3%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 6%" />
<col style="width: 3%" />
<col style="width: 6%" />
<col style="width: 3%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 5%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
<td colspan="3"><strong>Positive</strong></td>
<td></td>
<td colspan="3"><strong>Negative</strong></td>
<td></td>
<td colspan="3"><strong>Refused</strong></td>
<td></td>
<td colspan="3"><strong>Unknown</strong></td>
</tr>
<tr class="even">
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="2"><h4 id="hiv-antibody">HIV Antibody</h4></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"><blockquote>
<p>HCV Antibody</p>
</blockquote></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"><blockquote>
<p>HbsAg</p>
</blockquote></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
> **3. If known, when was the serostatus of the source determined?**
+---+--------------------------------------------------------------------+
| | > Known at the time of exposure |
+---+--------------------------------------------------------------------+
| | |
+---+--------------------------------------------------------------------+
| | > Determined through testing at the time of or soon after the |
| | > exposure |
+---+--------------------------------------------------------------------+
**Section V. Percutaneous Injury Circumstances**
**A. What device or item caused the injury?**
+---+------------------------------------------------------------------+
| # | |
| | |
| H | |
| o | |
| l | |
| l | |
| o | |
| w | |
| - | |
| b | |
| o | |
| r | |
| e | |
| | |
| n | |
| e | |
| e | |
| d | |
| l | |
| e | |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Hypodermic needle |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | \_\_ Attached to syringe \_\_ Attached to IV tubing |
| | |
| | \_\_ Unattached |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Prefilled cartridge syringe needle |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Winged steel needle (i.e., butterfly^R^ type devices) |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | \_\_ Attached to syringe, tube holder, or IV tubing |
| | |
| | \_\_ Unattached |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | IV stylet |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Phlebotomy needle |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Spinal or epidural needle |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Bone marrow needle |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Biopsy needle |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Huber needle |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Other type of hollow-bore needle (type: \_\_\_\_\_\_\_\_\_\_) |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Hollow-bore needle, type unknown |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| # | |
| # | |
| # | |
| # | |
| | |
| S | |
| u | |
| t | |
| u | |
| r | |
| e | |
| | |
| n | |
| e | |
| e | |
| d | |
| l | |
| e | |
+---+------------------------------------------------------------------+
| | Suture needle |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| # | |
| | |
| G | |
| l | |
| a | |
| s | |
| s | |
+---+------------------------------------------------------------------+
| | Capillary tube |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Pipette (glass) |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Slide |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Specimen/test/vacuum |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Other: |
| | \_\_\_\_ |
| | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
+---+------------------------------------------------------------------+
| * | |
| * | |
| O | |
| t | |
| h | |
| e | |
| r | |
| s | |
| h | |
| a | |
| r | |
| p | |
| o | |
| b | |
| j | |
| e | |
| c | |
| t | |
| s | |
| * | |
| * | |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Bone chip/chipped tooth |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Bone cutter |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Bovie electrocautery device |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Bur |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Explorer |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Extraction forceps |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Elevator |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Histology cutting blade |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Lancet |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Pin |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Razor |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Retractor |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Rod (orthopaedic applications) |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Root canal file |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Scaler/curette |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Scalpel blade |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Scissors |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Tenaculum |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Trocar |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Wire |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Other type of sharp object |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| | Sharp object, type unknown |
+---+------------------------------------------------------------------+
| | |
+---+------------------------------------------------------------------+
| # | |
| # | |
| # | |
| # | |
| | |
| O | |
| t | |
| h | |
| e | |
| r | |
| | |
| d | |
| e | |
| v | |
| i | |
| c | |
| e | |
| | |
| o | |
| r | |
| | |
| i | |
| t | |
| e | |
| m | |
+---+------------------------------------------------------------------+
| | Other: |
| | \_\_\_ |
| | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
+---+------------------------------------------------------------------+
**B. Purpose or procedure for which sharp item was used or intended.**
*(Check [one procedure]{.underline} type and complete information in
corresponding box as applicable.)*
--- -------------------------------------------------------------------
Establish intravenous or arterial access (Indicate type of line.)
Access established intravenous or arterial line
(Indicate type of line [and]{.underline} reason for line access.)
--- -------------------------------------------------------------------
--- ----------------------------------------------------- --------------
Injection through skin or mucous membrane
(Indicate type of injection.)
Obtain blood specimen (through skin)
(Indicate method of specimen collection.)
Other specimen collection
Suturing
Cutting
Other procedure
Unknown
--- ----------------------------------------------------- --------------
C. When and how did the injury occur? (From the left hand side of page,
select the point during or after use that most closely represents when
the injury occurred. In the corresponding right hand box, select *one or
two* circumstances that reflect how the injury happened.)
---- ------------------------- -----------------------------------------
During use of the item
After use, before
disposal of item
During or after disposal
of item
Other (Describe):
Unknown
---- ------------------------- -----------------------------------------
+---+---+---------------------------------------------------------------+
| * | | |
| * | | |
| S | | |
| e | | |
| l | | |
| e | | |
| c | | |
| t | | |
| o | | |
| n | | |
| e | | |
| o | | |
| r | | |
| t | | |
| w | | |
| o | | |
| c | | |
| h | | |
| o | | |
| i | | |
| c | | |
| e | | |
| s | | |
| : | | |
| * | | |
| * | | |
+---+---+---------------------------------------------------------------+
| | | |
+---+---+---------------------------------------------------------------+
| | | Patient moved and jarred device |
+---+---+---------------------------------------------------------------+
| | | While inserting needle/sharp |
+---+---+---------------------------------------------------------------+
| | | While manipulating needle/sharp |
+---+---+---------------------------------------------------------------+
| | | While withdrawing needle/sharp |
+---+---+---------------------------------------------------------------+
| | | Passing or receiving equipment |
+---+---+---------------------------------------------------------------+
| | | Suturing |
+---+---+---------------------------------------------------------------+
| | | Tying sutures |
+---+---+---------------------------------------------------------------+
| | | Manipulating suture needle in holder |
+---+---+---------------------------------------------------------------+
| | | Incising |
+---+---+---------------------------------------------------------------+
| | | Palpating/Exploring |
+---+---+---------------------------------------------------------------+
| | | Collided with co-worker or other during procedure |
+---+---+---------------------------------------------------------------+
| | | Collided with sharp during procedure |
+---+---+---------------------------------------------------------------+
| | | Sharp object dropped during procedure |
+---+---+---------------------------------------------------------------+
| | | |
+---+---+---------------------------------------------------------------+
| | | |
+---+---+---------------------------------------------------------------+
| * | | |
| * | | |
| S | | |
| e | | |
| l | | |
| e | | |
| c | | |
| t | | |
| o | | |
| n | | |
| e | | |
| o | | |
| r | | |
| t | | |
| w | | |
| o | | |
| c | | |
| h | | |
| o | | |
| i | | |
| c | | |
| e | | |
| s | | |
| : | | |
| * | | |
| * | | |
+---+---+---------------------------------------------------------------+
| | | |
+---+---+---------------------------------------------------------------+
| | | Handling equipment on a tray or stand |
+---+---+---------------------------------------------------------------+
| | | Transferring specimen into specimen container |
+---+---+---------------------------------------------------------------+
| | | Processing specimens |
+---+---+---------------------------------------------------------------+
| | | Passing or transferring equipment |
+---+---+---------------------------------------------------------------+
| | | Recapping (missed or pierced cap) |
+---+---+---------------------------------------------------------------+
| | | Cap fell off after recapping |
+---+---+---------------------------------------------------------------+
| | | Disassembling device or equipment |
+---+---+---------------------------------------------------------------+
| | | Decontamination/processing of used equipment |
+---+---+---------------------------------------------------------------+
| | | During clean-up |
+---+---+---------------------------------------------------------------+
| | | In transit to disposal |
+---+---+---------------------------------------------------------------+
| | | Opening/breaking glass containers |
+---+---+---------------------------------------------------------------+
| | | Collided with co-worker/other person |
+---+---+---------------------------------------------------------------+
| | | Collided with sharp after procedure |
+---+---+---------------------------------------------------------------+
| | | Sharp object dropped after procedure |
+---+---+---------------------------------------------------------------+
| | | Struck by detached IV line needle |
+---+---+---------------------------------------------------------------+
| | | |
+---+---+---------------------------------------------------------------+
| | | |
+---+---+---------------------------------------------------------------+
| * | | |
| * | | |
| S | | |
| e | | |
| l | | |
| e | | |
| c | | |
| t | | |
| o | | |
| n | | |
| e | | |
| o | | |
| r | | |
| t | | |
| w | | |
| o | | |
| c | | |
| h | | |
| o | | |
| i | | |
| c | | |
| e | | |
| s | | |
| : | | |
| * | | |
| * | | |
+---+---+---------------------------------------------------------------+
| | | |
+---+---+---------------------------------------------------------------+
| | | Placing sharp in container: |
+---+---+---------------------------------------------------------------+
| | | \_\_ Injured by sharp being disposed |
| | | |
| | | \_\_ Injured by sharp already in container |
+---+---+---------------------------------------------------------------+
| | | While manipulating container |
+---+---+---------------------------------------------------------------+
| | | Over-filled sharps container |
+---+---+---------------------------------------------------------------+
| | | Punctured sharps container |
+---+---+---------------------------------------------------------------+
| | | Sharp protruding from open container |
+---+---+---------------------------------------------------------------+
| | | Sharp in unusual location: |
+---+---+---------------------------------------------------------------+
| | | \_\_ In trash |
| | | |
| | | \_\_ In linen/laundry |
| | | |
| | | \_\_ Left on table/tray |
| | | |
| | | \_\_ Left in bed/mattress |
| | | |
| | | \_\_ On floor |
| | | |
| | | \_\_ In pocket/clothing |
| | | |
| | | \_\_ Other unusual location |
+---+---+---------------------------------------------------------------+
| | | Collided with co-worker or other person |
+---+---+---------------------------------------------------------------+
| | | Collided with sharp |
+---+---+---------------------------------------------------------------+
| | | Sharp object dropped |
+---+---+---------------------------------------------------------------+
| | | Struck by detached IV line needle |
+---+---+---------------------------------------------------------------+
| | | |
+---+---+---------------------------------------------------------------+
**Section VI. Mucous Membrane Exposures Circumstances**
**A. What barriers were used by worker at the time of the exposure?**
*(Check all that apply.)*
-- --------- -- --------- -- ------------ -- --------- -- -------- -- -----------
Gloves Goggles Eyeglasses Face Mask Gown
Shield
-- --------- -- --------- -- ------------ -- --------- -- -------- -- -----------
**B. Activity/Event when exposure occurred** *(Check one.)*
-- ----------------------------------------------------------------------------------------------------------------
Patient spit/coughed/vomited
Airway manipulation (e.g., suctioning airway, inducing sputum)
Endoscopic procedure
Dental procedure
Tube placement/removal/manipulation (e.g., chest, endotracheal, NG, rectal, urine catheter)
Phlebotomy
IV or arterial line insertion/removal/manipulation
Irrigation procedure
Vaginal delivery
Surgical procedure (e.g., all surgical procedures including C-section)
Bleeding vessel
Changing dressing/wound care
Manipulating blood tube/bottle/specimen container
Cleaning/transporting contaminated equipment
Other:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Unknown
-- ----------------------------------------------------------------------------------------------------------------
-- --------------- ------------ --------------------- -- --------------------------- --
**Comments:**
-- --------------- ------------ --------------------- -- --------------------------- --
| en |
converted_docs | 718422 | **STATEMENT OF WORK**
USDA, Natural Resources Conservation Service
Wisconsin
**Firebreak (394)**
**DESIGN (911)**
**Deliverables:**
1\. Design documents that demonstrate criteria in NRCS practice standard
have been met and are compatible with planned and applied practices.
> a\. Compliance with NRCS national and state utility safety policy (NEM
> part 503-Safety, Section 503.00 through 503.22).
>
> b\. List all required and/or facilitating practices.
>
> c\. Practice standard criteria-related computations and analyses to
> develop plans and specifications including but not limited to:
>
> i\. Firebreak location, width and length.
>
> ii\. Vegetative species selection and estimated quantities needed by
> species.
>
> iii\. Erosion control measures
2\. Written plans and specifications including location map, sketches
and drawings shall be provided to the client that adequately describes
the requirements to install the practice and obtain necessary permits.
3\. Operation and maintenance plan.
4\. Certification that the design meets practice standard criteria and
comply with applicable laws and regulations.
5\. Documentation requirements for design modifications during practice
installation.
6\. Itemized cost estimate.
**[CERTIFICATION OF COMPLETION]{.underline}**
**Firebreak (394)**
Design (911)
**[Program Participant Information]{.underline}**
Name (print):
Contract Number:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ Contract
Item #(s):
**[Technical Service Provider Information]{.underline}**
Name (print):
TSP ID Number:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Expiration Date:
*I hereby certify that the technical services I provided as a Technical
Service Provider for this component(s) checked above: (1) comply with
all applicable Federal, State, Tribal, and Local laws and requirements,
(2) meet applicable USDA NRCS conservation practice standards,
specifications, and program requirements, (3) are consistent with and
meet the particular conservation program goals and objectives, (4) that
I have provided the above named Program Participant the Deliverables in
this Statement of Work for this component, and (5) comply with all
"Certification Terms" as identified in the Technical Service Provider
Certification Agreement.*
*\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_*
***Technical Service Provider Signature Date***
*\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_*
***Received By (NRCS staff)** **Date***
**STATEMENT OF WORK**
USDA, Natural Resources Conservation Service
Wisconsin
**Firebreak (394)**
**INSTALLATION (912)**
**Deliverables**
1\. Documentation of pre-installation conference with client.
2\. Verification that client has obtained required permits.
3\. Staking and layout according to plans and specifications including
applicable layout notes.
4\. Installation guidance as needed.
5\. Facilitate, implement and document required design modifications
with client, original designer, permitting and funding agencies.
6\. Advise client/NRCS on compliance issues with all federal, state,
tribal, and local laws, regulations and NRCS policies during
application.
7\. Certification that the installation process and materials meets
design and permit requirements.
**[CERTIFICATION OF COMPLETION]{.underline}**
**Firebreak (394)**
Installation (912)
**[Program Participant Information]{.underline}**
Name (print):
Contract Number:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ Contract
Item #(s):
**[Technical Service Provider Information]{.underline}**
Name (print):
TSP ID Number:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Expiration Date:
*I hereby certify that the technical services I provided as a Technical
Service Provider for this component(s) checked above: (1) comply with
all applicable Federal, State, Tribal, and Local laws and requirements,
(2) meet applicable USDA NRCS conservation practice standards,
specifications, and program requirements, (3) are consistent with and
meet the particular conservation program goals and objectives, (4) that
I have provided the above named Program Participant the Deliverables in
this Statement of Work for this component, and (5) comply with all
"Certification Terms" as identified in the Technical Service Provider
Certification Agreement.*
*\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_*
***Technical Service Provider Signature Date***
*\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_*
***Received By (NRCS staff)** **Date***
**STATEMENT OF WORK**
USDA, Natural Resources Conservation Service
Wisconsin
**Firebreak (394)**
**CHECKOUT (913)**
**Deliverables**
1\. Records of installation.
> a\. Extent of practice units applied and location on a map.
>
> b\. Actual materials used.
2\. Certification that the installation meets NRCS standards and
specifications and is in compliance with permits.
3\. Provide the following information to the NRCS field office servicing
the relevant land unit for entry into the Performance Results System
(PRS):
> a\. Technical Service Provider Name
>
> b\. Customer name
>
> c\. USDA program funding the practice (if known)
>
> d\. Location of work (state, county, conservation district, land tract
> identifier)
>
> e\. Land use of field where the practice was installed (cropland,
> etc.)
>
> f\. NRCS practice name and quantity of practice installed in
> appropriate units
4\. Documentation of exit conference with client and contractor.
**[CERTIFICATION OF COMPLETION]{.underline}**
**Firebreak (394)**
Checkout (913)
**[Program Participant Information]{.underline}**
Name (print):
Contract Number:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ Contract
Item #(s):
**[Technical Service Provider Information]{.underline}**
Name (print):
TSP ID Number:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Expiration Date:
*I hereby certify that the technical services I provided as a Technical
Service Provider for this component(s) checked above: (1) comply with
all applicable Federal, State, Tribal, and Local laws and requirements,
(2) meet applicable USDA NRCS conservation practice standards,
specifications, and program requirements, (3) are consistent with and
meet the particular conservation program goals and objectives, (4) that
I have provided the above named Program Participant the Deliverables in
this Statement of Work for this component, and (5) comply with all
"Certification Terms" as identified in the Technical Service Provider
Certification Agreement.*
*\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_*
***Technical Service Provider Signature Date***
*\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_*
***Received By (NRCS staff)** **Date***
**STATEMENT OF WORK**
USDA, Natural Resources Conservation Service
Wisconsin
**Firebreak (394)**
**REFERENCES**
- WI NRCS Field Office Technical Guide (eFOTG), Section IV,
Conservation Practice Standard 394, Firebreak
```{=html}
<!-- -->
```
- NRCS National Forestry Manual
- NRCS National Forestry Handbook
- NRCS National Engineering Manual
```{=html}
<!-- -->
```
- NRCS National Environmental Compliance Handbook
- NRCS Cultural Resources Handbook
| en |
all-txt-docs | 445283 | The Administration of the Missions 89
upon it could make it go at sufficient rate to give the mill-
stone the requisite velocity. The wheel was constructed in
the following manner: A set of so-called spoons were stuck
into the periphery of the wheel which served in the place of
float boards. They were made of pieces of timber in some-
thing of the shape of spoons ; the handles were inserted into
the mortises on the edge of the wheel; and the bowls of the
spoons received the water which spouted on them and forced
round the small wheel with nearly the velocity which im-
pinged upon it.11
Besides agriculture, the Indians were taught various practical
trades by the friars. Pottery, carpentry, and masonry, the
making of shoes, hats, clothes, soap and candles, hide-tanning,
spinning, and blacksmithing, are some of the handicrafts men-
tioned in the reports of the missionaries.
While it would not be historically accurate to state that the
administration of the Texas missions can be completely learned
from the description we possess of the Franciscan missions in
California, nevertheless it must be remembered that the daily
routine and other regulations observed in California were com-
piled by Father Pedro Perez Mezquia, who till 1744, had labored
in the missions of Texas, and afterwards in those of Sierra Gorda,
Mexico, whence Father Junfpero Serra introduced them to his
beloved converts in the missions on the coast.12
This glorious picture is not without its shadows. The truth
is that, unless the Indians were under contract by piece-work,
he, or she, never worked unless a friar was present to direct the
labor. All the year's toil on the part of the missionaries failed
to eradicate the deepest of all the vices the Indian possessed
lazinessand the friars are not loath in their frank reports to
the guardians of Zacatecas and Queretaro to admit that with
many, if not with all, of their neophytes, the chief attraction
was free food. "Nothing seemed to give them greater pleasure
than to lie stretched out for hours upon the ground with their
faces down, doing absolutely nothing and indifferent to every-
thing."13 Yet in spite of this general laziness, the friars did not
neglect to provide amusements for the Indians. In fact, amuse-
ments of legitimate character had to be supplied in order to sup-
11 Ibid., II, p. 257-261.
u Missionary Labors, in the Franciscan Herald, June, 1916, p. 232.
" Bancroft, Native Races, I, pp. 393-394. | en |
log-files | 720072 | # Date 2008-01-16 Time 01:22:37 PST -0800 (1200475357.71 s)
#phil __OFF__
Command line arguments: "../404.param" "adp.set_b_iso=10" "sites.shake=0.5" "main.number_of_macro_cycles=5" "--overwrite"
HOST = sunbird.lbl.gov
HOSTTYPE = x86_64-linux
USER = phzwart
PID = 21933
JOB_ID = 5158
SGE_ARCH = lx24-amd64
SGE_TASK_FIRST = 1
SGE_TASK_LAST = 1330
SGE_TASK_ID = 404
-------------------------------------------------------------------------------
PHENIX: Python-based Hierarchical ENvironment for Integrated Xtallography
User: phzwart
-------------------------------------------------------------------------------
phenix.refine: Macromolecular Structure Refinement
-------------------------------------------------------------------------------
Phenix developers include:
Paul Adams, Pavel Afonine, Vicent Chen, Ian Davis, Kreshna Gopal,
Ralf Grosse-Kunstleve, Li-Wei Hung, Robert Immormino, Tom Ioerger,
Airlie McCoy, Erik McKee, Nigel Moriarty, Reetal Pai, Randy Read,
Jane Richardson, David Richardson, Tod Romo, Jim Sacchettini,
Nicholas Sauter, Jacob Smith, Laurent Storoni, Tom Terwilliger,
Peter Zwart
Phenix home page:
http://www.phenix-online.org/
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Phenix components are copyrighted by:
- Lawrence Berkeley National Laboratory
- Los Alamos National Laboratory
- University of Cambridge
- Duke University
- Texas Agricultural Experiment Station &
Texas Engineering Experiment Station
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Major third-party components of Phenix include:
Python, wxwidgets, wxPython, Boost, SCons, Clipper,
CCP4 Monomer Library, CCP4 I/O libraries, PyCifRW, FFTPACK, L-BFGS
Enter phenix.acknowledgments for details.
-------------------------------------------------------------------------------
Processing inputs. This may take a minute or two.
Command line parameter definitions:
refinement.modify_start_model.adp.set_b_iso = 10
refinement.modify_start_model.sites.shake = 0.5
refinement.main.number_of_macro_cycles = 5
Working crystal symmetry after inspecting all inputs:
Unit cell: (69.5475, 46.4607, 87.6859, 90, 90, 90)
Space group: P 21 21 21 (No. 19)
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/model.pdb
Monomer Library directory:
"/net/rosie/scratch3/phzwart/CCTBX/Sources/mon_lib"
Total number of atoms: 2823
Number of models: 1
Model: 0
Number of conformers: 2
Conformer: "A"
Number of atoms: 2769
Number of chains: 2
Number of residues, atoms: 302, 2333
Classifications: {'peptide': 302}
Modifications used: {'COO': 1}
Link IDs: {'PTRANS': 7, 'CIS': 1, 'TRANS': 293}
Number of residues, atoms: 436, 436
Classifications: {'water': 436}
Link IDs: {None: 435}
Conformer: "B"
Number of atoms: 2771
Common with "A": 2717
Number of chains: 2
Number of residues, atoms: 302, 2333
Classifications: {'peptide': 302}
Modifications used: {'COO': 1}
Link IDs: {'PTRANS': 7, 'CIS': 1, 'TRANS': 293}
bond proxies already assigned to first conformer: 2332
Number of residues, atoms: 438, 438
Classifications: {'water': 438}
Link IDs: {None: 437}
Time building chain proxies: 3.30, per 1000 atoms: 1.17
================================== X-ray data =================================
F-obs:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/1e0w.cns:FOBS,SIGMA
R-free flags:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/1e0w.cns:TEST
Miller array info: /net/cci-filer1/vol1/tmp/phzwart/tassos/trial/1e0w.cns:FOBS,SIGMA
Observation type: xray.amplitude
Type of data: double, size=19589
Type of sigmas: double, size=19589
Number of Miller indices: 19589
Anomalous flag: False
Unit cell: (69.5475, 46.4607, 87.6859, 90, 90, 90)
Space group: P 21 21 21 (No. 19)
Systematic absences: 0
Centric reflections: 2427
Resolution range: 14.9429 1.98041
Completeness in resolution range: 0.961471
Completeness with d_max=infinity: 0.958507
Number of F-obs in resolution range: 19589
Number of F-obs <= 0: 0
Refinement resolution range: d_max = 14.9429
d_min = 1.9804
Miller array info: /net/cci-filer1/vol1/tmp/phzwart/tassos/trial/1e0w.cns:TEST
Observation type: None
Type of data: int, size=19589
Type of sigmas: None
Number of Miller indices: 19589
Anomalous flag: False
Unit cell: (69.5475, 46.4607, 87.6859, 90, 90, 90)
Space group: P 21 21 21 (No. 19)
Systematic absences: 0
Centric reflections: 2427
Resolution range: 14.9429 1.98041
Completeness in resolution range: 0.961471
Completeness with d_max=infinity: 0.958507
Test (R-free flags) flag value: 1
Number of work/free reflections by resolution:
work free %free
bin 1: 14.9433 - 4.2373 [2143/2167] 1924 219 10.2%
bin 2: 4.2373 - 3.3760 [2050/2070] 1848 202 9.9%
bin 3: 3.3760 - 2.9530 [2032/2051] 1834 198 9.7%
bin 4: 2.9530 - 2.6847 [1994/2024] 1789 205 10.3%
bin 5: 2.6847 - 2.4932 [2003/2022] 1802 201 10.0%
bin 6: 2.4932 - 2.3468 [1997/2022] 1796 201 10.1%
bin 7: 2.3468 - 2.2297 [1982/2010] 1785 197 9.9%
bin 8: 2.2297 - 2.1329 [1955/1991] 1760 195 10.0%
bin 9: 2.1329 - 2.0510 [1960/2002] 1766 194 9.9%
bin 10: 2.0510 - 1.9804 [1473/2015] 1326 147 10.0%
overall 17630 1959 10.0%
Writing MTZ file:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/run_404/model_refine_data.mtz
========================== Anomalous scatterer groups =========================
All atoms refined with f_prime=0 and f_double_prime=0.
========================== Set up restraints manager ==========================
Number of disulfides: simple=3, symmetry=0
Simple disulfide: " SG CYS A 168 " - " SG ACYS A 201 " distance=2.08
Simple disulfide: " SG CYS A 168 " - " SG BCYS A 201 " distance=1.98
Simple disulfide: " SG CYS A 254 " - " SG CYS A 260 " distance=2.05
Time building geometry restraints manager: 0.14 seconds
Histogram of bond lengths:
1.21 - 1.38: 943
1.38 - 1.56: 1465
1.56 - 1.73: 7
1.73 - 1.90: 21
1.90 - 2.08: 3
Bond restraints sorted by residual:
atom i - atom j ideal model delta weight residual
" SG CYS A 168 " - " SG BCYS A 201 " 2.031 1.983 0.048 2.50e+03 5.87e+00
" C GLN A 88 " - " N GLN A 89 " 1.329 1.360 -0.031 5.10e+03 4.97e+00
" SG CYS A 168 " - " SG ACYS A 201 " 2.031 2.075 -0.044 2.50e+03 4.89e+00
" CB CYS A 201 " - " SG ACYS A 201 " 1.808 1.738 0.070 9.18e+02 4.46e+00
" C PRO A 198 " - " N ILE A 199 " 1.329 1.301 0.028 5.10e+03 4.10e+00
... (remaining 2434 not shown)
Histogram of nonbonded interaction distances:
1.51 - 2.19: 10
2.19 - 2.87: 1200
2.87 - 3.54: 4458
3.54 - 4.22: 9243
4.22 - 4.90: 13515
Nonbonded interactions sorted by model distance:
atom i - atom j model vdw sym.op. j
" OE1 GLN A 55 " - " O HOH Z 403 " 1.510 3.040 -x+1,y-1/2,-z+1/2
" CE BMET A 47 " - " O BHOH Z 74 " 1.806 3.460
" O HOH Z 42 " - " O HOH Z 183 " 1.888 3.040 -x+1,y+1/2,-z+1/2
" O HOH Z 41 " - " O HOH Z 182 " 1.942 3.040 -x+1,y+1/2,-z+1/2
" O HOH Z 43 " - " O HOH Z 169 " 1.957 3.040 -x+1,y+1/2,-z+1/2
... (remaining 28421 not shown)
Histogram of dihedral angle deviations from ideal:
0.01 - 17.19: 754
17.19 - 34.36: 62
34.36 - 51.54: 27
51.54 - 68.71: 23
68.71 - 85.89: 4
Dihedral angle restraints sorted by residual:
" CA PHE A 192 "
" CB PHE A 192 "
" CG PHE A 192 "
" CD1 PHE A 192 "
ideal model delta periodicty weight residual
90.00 7.91 82.09 2 2.50e-03 1.68e+01
" N PRO A 54 "
" CG PRO A 54 "
" CD PRO A 54 "
" CB PRO A 54 "
ideal model delta periodicty weight residual
30.00 -27.17 57.17 3 4.44e-03 1.45e+01
" N PRO A 280 "
" CA PRO A 280 "
" CB PRO A 280 "
" CG PRO A 280 "
ideal model delta periodicty weight residual
-25.00 38.44 56.56 3 4.44e-03 1.42e+01
... (remaining 867 not shown)
==================== Fixing bad ADP in input model (if any) ===================
============================== Scattering factors =============================
----------X-ray scattering dictionary----------
Number of scattering types: 4
Type Number sf(0) Gaussians
S 13 15.96 2
O 902 7.97 2
N 437 6.97 2
C 1471 5.97 2
sf(0) = scattering factor at diffraction angle 0.
====================== Modifying start model if requested =====================
Setting all isotropic ADP = 10.000: selected atoms: all (2823)
Shaking sites (RMS = 0.500): selected atoms: all (2823)
==================== Fixing bad ADP in input model (if any) ===================
================== Extract refinement strategy and selections =================
individual_sites = True
rigid_body = False
individual_adp = True
group_adp = False
tls = False
individual_occupancies = True
group_occupancies = False
group_anomalous = False
size = 2823
n_use = 2823
n_use_u_iso = 2823
n_use_u_aniso = 0
n_grad_site = 0
n_grad_u_iso = 0
n_grad_u_aniso = 0
n_grad_occupancy = 0
n_grad_fp = 0
n_grad_fdp = 0
n_anisotropic_flag = 0
total number of scatterers = 2823
==================== Process input NCS or/and find new NCS ====================
Using existing and finding new NCS is disabled.
Use refinement.main.ncs=true to activate it.
Look at refinement.ncs for more NCS related parameters.
=================== Write initial parameters into .eff file ===================
Writing effective parameters to file:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/run_404/model_refine_001.eff
Writing geometry restraints to file:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/run_404/model_refine_001.geo
CPU time processing inputs: 9.75
============================ Non-default parameters ===========================
A complete record of all parameters was written to the .eff file above.
Below are only the non-defaults.
#phil __ON__
refinement {
crystal_symmetry {
unit_cell = 69.5475 46.4607 87.68585 90 90 90
space_group = "P 21 21 21"
}
input {
pdb {
file_name = "/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/model.pdb"
}
xray_data {
file_name = "/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/1e0w.cns"
labels = "FOBS,SIGMA"
r_free_flags {
file_name = "/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/1e0w.cns"
label = "TEST"
test_flag_value = 1
}
}
}
output {
prefix = "model_refine"
serial = 1
}
main {
number_of_macro_cycles = 5
}
modify_start_model {
adp {
set_b_iso = 10
}
sites {
shake = 0.5
}
}
}
#phil __OFF__
============================= ml refinement start =============================
----------structure factors based statistics (before refinement)----------
----------X-ray data----------
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.4650 r_free= 0.4489 ksol= 0.00 Bsol= 0.00 scale= 0.806 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (0.00,0.00,0.00,0.00,0.00,0.00); trace/3= 0.00 |
| |
| maximum likelihood estimate for coordinate error: 0.66 A |
| x-ray target function (ml) for work reflections: 6.263870 |
|-----------------------------------------------------------------------------|
|-----------------------------------------------------------------------------|
| Bin Resolution Compl. No. Refl. R-factors Targets |
|number range work test work test work test|
| 1: 14.9433 - 4.7259 0.99 1394 152 0.3826 0.3630 6.5669 6.5073|
| 2: 4.7259 - 3.7709 0.99 1329 154 0.3618 0.3679 6.7061 6.7604|
| 3: 3.7709 - 3.3001 0.99 1307 143 0.4107 0.3730 6.6314 6.5977|
| 4: 3.3001 - 3.0010 0.99 1304 140 0.4547 0.4482 6.5164 6.4821|
| 5: 3.0010 - 2.7874 0.99 1292 147 0.4896 0.4510 6.3572 6.3508|
| 6: 2.7874 - 2.6240 0.99 1300 145 0.4887 0.5277 6.2664 6.2207|
| 7: 2.6240 - 2.4932 0.99 1271 144 0.5019 0.4997 6.2313 6.1717|
| 8: 2.4932 - 2.3852 0.98 1270 136 0.5162 0.4744 6.1856 6.1966|
| 9: 2.3852 - 2.2937 0.98 1282 148 0.5097 0.5275 6.1041 6.1672|
| 10: 2.2937 - 2.2148 1.00 1275 139 0.5425 0.4566 6.1313 6.0419|
| 11: 2.2148 - 2.1457 0.97 1267 134 0.5173 0.4937 6.0423 6.0548|
| 12: 2.1457 - 2.0846 0.98 1247 145 0.5219 0.4870 5.9724 6.0034|
| 13: 2.0846 - 2.0298 1.00 1271 138 0.5150 0.4794 5.8926 5.8246|
| 14: 2.0298 - 1.9804 0.63 821 94 0.5390 0.5265 5.8828 5.7665|
|-----------------------------------------------------------------------------|
|-----------------------------------------------------------------------------|
|R-free likelihood based estimates for figures of merit, absolute phase error,|
|and distribution parameters alpha and beta (Acta Cryst. (1995). A51, 880-887)|
| |
| Bin Resolution No. Refl. FOM Phase Scale Alpha Beta |
| # range work test error factor |
| 1: 14.9433 - 4.7259 1394 152 0.72 32.70 0.80 0.75 65210.22|
| 2: 4.7259 - 3.7709 1329 154 0.74 31.71 0.89 0.81 89548.37|
| 3: 3.7709 - 3.3001 1307 143 0.66 38.96 0.86 0.76 95993.97|
| 4: 3.3001 - 3.0010 1304 140 0.57 46.50 0.80 0.65 87408.12|
| 5: 3.0010 - 2.7874 1292 147 0.46 55.03 0.76 0.54 75874.15|
| 6: 2.7874 - 2.6240 1300 145 0.42 58.11 0.73 0.48 69108.29|
| 7: 2.6240 - 2.4932 1271 144 0.39 60.59 0.75 0.46 64546.57|
| 8: 2.4932 - 2.3852 1270 136 0.40 59.96 0.72 0.46 56749.77|
| 9: 2.3852 - 2.2937 1282 148 0.41 58.79 0.74 0.49 50347.35|
| 10: 2.2937 - 2.2148 1275 139 0.42 58.20 0.74 0.50 44020.20|
| 11: 2.2148 - 2.1457 1267 134 0.41 59.07 0.76 0.51 42935.04|
| 12: 2.1457 - 2.0846 1247 145 0.39 60.56 0.77 0.49 39108.20|
| 13: 2.0846 - 2.0298 1271 138 0.38 61.53 0.74 0.46 34572.10|
| 14: 2.0298 - 1.9804 821 94 0.40 60.05 0.73 0.43 28193.48|
|alpha: min = 0.43 max = 0.81 mean = 0.56|
|beta: min = 28193.48 max = 95993.97 mean = 61387.63|
|figures of merit: min = 0.00 max = 1.00 mean = 0.49|
|phase err.(work): min = 0.00 max = 90.00 mean = 52.55|
|phase err.(test): min = 0.00 max = 89.70 mean = 52.84|
|-----------------------------------------------------------------------------|
============================== Outliers rejection =============================
basic_wilson_outliers = 0
extreme_wilson_outliers = 0
beamstop_shadow_outliers = 0
total = 0
====================== Target weights (before refinement) =====================
|-----------------------------------------------------------------------------|
| XYZ refinement: T = Eexperimental * wxc * wxc_scale + Echem * wc |
| wxc = 10.606203 wxc_scale = 0.500 wc = 1.000 |
| angle between x-ray and geometry gradient vectors: 79.296 (deg) |
| |
| ADP refinement: T = Eexperimental * wxu * wxu_scale + Eadp * wu |
| wxc = 0.931640 wxc_scale = 1.000 wc = 1.000 |
| angle between Xray and ADP gradient vectors: 77.401 (deg) |
|-----------------------------------------------------------------------------|
----------Initial model statistics (before refinement)----------
|-Geometry statistics: start--------------------------------------------------|
| Histogram of deviations from ideal values for |
| Bonds | Angles | Nonbonded contacts |
| 0.000 - 0.140: 597 | 0.009 - 7.457: 713 | 1.196 - 1.566: 3 |
| 0.140 - 0.280: 585 | 7.457 - 14.906: 711 | 1.566 - 1.937: 25 |
| 0.280 - 0.420: 441 | 14.906 - 22.354: 630 | 1.937 - 2.307: 182 |
| 0.420 - 0.560: 366 | 22.354 - 29.802: 474 | 2.307 - 2.677: 688 |
| 0.560 - 0.700: 237 | 29.802 - 37.251: 338 | 2.677 - 3.048: 1513 |
| 0.700 - 0.840: 127 | 37.251 - 44.699: 241 | 3.048 - 3.418: 2642 |
| 0.840 - 0.980: 59 | 44.699 - 52.147: 125 | 3.418 - 3.789: 3927 |
| 0.980 - 1.120: 17 | 52.147 - 59.595: 51 | 3.789 - 4.159: 5111 |
| 1.120 - 1.260: 9 | 59.595 - 67.044: 13 | 4.159 - 4.530: 6613 |
| 1.260 - 1.400: 1 | 67.044 - 74.492: 3 | 4.530 - 4.900: 7675 |
|-----------------------------------------------------------------------------|
|-Geometry statistics: start--------------------------------------------------|
| Type | Count | Deviation from ideal | Targets | Target (sum) |
| | | rmsd max min | | |
| bond | 2439 | 0.414 1.400 0.000 | 454.651 | |
| angle | 3299 | 24.226 74.492 0.009 | 193.752 | |
| chirality | 348 | 2.119 6.404 0.009 | 112.240 | 53.647 |
| planarity | 436 | 0.145 0.405 0.000 | 250.485 | |
| dihedral | 870 | 33.790 144.062 0.019 | 20.704 | |
| nonbonded | 2439 | 4.089 4.900 1.196 | 1.904 | |
|-----------------------------------------------------------------------------|
|-ADP statistics (Wilson B = 11.778)------------------------------------------|
| Atom | Number of | Isotropic or equivalent| Anisotropy lmin/max |
| type |iso aniso | min max mean | min max mean |
| - - - - |- - - - - - -| - - - - - - - - - - - -| - - - - - - - - - - |
| all : 2823 0 10.00 10.00 10.00 None None None |
| all(noH): 2823 0 10.00 10.00 10.00 None None None |
| Sol. : 438 0 10.00 10.00 10.00 None None None |
| Mac. : 2385 0 10.00 10.00 10.00 None None None |
| Hyd. : 0 0 None None None None None None |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Distribution of isotropic (or equivalent) ADP for non-H atoms: |
| Bin# value range #atoms | Bin# value range #atoms |
| 0: 10.000 - 10.000: 2823 | 5: 10.000 - 10.000: 0 |
| 1: 10.000 - 10.000: 0 | 6: 10.000 - 10.000: 0 |
| 2: 10.000 - 10.000: 0 | 7: 10.000 - 10.000: 0 |
| 3: 10.000 - 10.000: 0 | 8: 10.000 - 10.000: 0 |
| 4: 10.000 - 10.000: 0 | 9: 10.000 - 10.000: 0 |
| =>continue=> |
|-----------------------------------------------------------------------------|
|-Occupancies statistics------------------------------------------------------|
| occupancies: max = 1.00 min = 0.30 number of occupancies < 0.1 = 0 |
|-----------------------------------------------------------------------------|
----------Modify initial isotropic ADP----------
Randomizing
|-ADP statistics (Wilson B = 11.778)------------------------------------------|
| Atom | Number of | Isotropic or equivalent| Anisotropy lmin/max |
| type |iso aniso | min max mean | min max mean |
| - - - - |- - - - - - -| - - - - - - - - - - - -| - - - - - - - - - - |
| all : 2823 0 0.01 19.99 9.86 None None None |
| all(noH): 2823 0 0.01 19.99 9.86 None None None |
| Sol. : 438 0 0.06 19.99 10.10 None None None |
| Mac. : 2385 0 0.01 19.98 9.82 None None None |
| Hyd. : 0 0 None None None None None None |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Distribution of isotropic (or equivalent) ADP for non-H atoms: |
| Bin# value range #atoms | Bin# value range #atoms |
| 0: 0.008 - 2.007: 301 | 5: 10.002 - 12.000: 285 |
| 1: 2.007 - 4.006: 276 | 6: 12.000 - 13.999: 292 |
| 2: 4.006 - 6.004: 309 | 7: 13.999 - 15.998: 289 |
| 3: 6.004 - 8.003: 285 | 8: 15.998 - 17.996: 266 |
| 4: 8.003 - 10.002: 251 | 9: 17.996 - 19.995: 269 |
| =>continue=> |
|-----------------------------------------------------------------------------|
*********************** REFINEMENT MACRO_CYCLE 1 OF 5 *************************
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.4729 r_free= 0.4519 ksol= 0.00 Bsol= 0.00 scale= 0.774 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (0.00,0.00,0.00,0.00,0.00,0.00); trace/3= 0.00 |
| |
| maximum likelihood estimate for coordinate error: 0.66 A |
| x-ray target function (ml) for work reflections: 6.267368 |
|-----------------------------------------------------------------------------|
====================== bulk solvent modeling and scaling ======================
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.4563 r_free= 0.4374 ksol= 0.35 Bsol= 18.34 scale= 1.014 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (7.09,8.73,10.28,0.00,0.00,0.00); trace/3= 8.70 |
| |
| maximum likelihood estimate for coordinate error: 0.65 A |
| x-ray target function (ml) for work reflections: 6.257280 |
|-----------------------------------------------------------------------------|
========================== Target weights: x-ray data =========================
|-----------------------------------------------------------------------------|
| XYZ refinement: T = Eexperimental * wxc * wxc_scale + Echem * wc |
| wxc = 8.645772 wxc_scale = 0.500 wc = 1.000 |
| angle between x-ray and geometry gradient vectors: 80.873 (deg) |
| |
| ADP refinement: T = Eexperimental * wxu * wxu_scale + Eadp * wu |
| wxc = 0.864300 wxc_scale = 1.000 wc = 1.000 |
| angle between Xray and ADP gradient vectors: 76.514 (deg) |
|-----------------------------------------------------------------------------|
================================ xyz refinement ===============================
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.4563 final r-factor (work) = 0.3633 |
| start r-factor (free) = 0.4374 final r-factor (free) = 0.3801 |
|-----------------------------------------------------------------------------|
| T_start = wxc * wxc_scale * Exray + wc * Echem |
| 80.7322 = 8.65 * 0.50 * 6.2655 + 1.00 * 53.6471 |
| |
| T_final = wxc * wxc_scale * Exray + wc * Echem |
| 26.7071 = 8.65 * 0.50 * 6.1482 + 1.00 * 0.1293 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 26 |
|-----------------------------------------------------------------------------|
================================ ADP refinement ===============================
----------Individual ADP refinement----------
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.3633 final r-factor (work) = 0.3126 |
| start r-factor (free) = 0.3801 final r-factor (free) = 0.3630 |
|-----------------------------------------------------------------------------|
| T_start = wxu * wxu_scale * Exray + wu * Eadp |
| 5.3282 = 0.86 * 1.00 * 6.1482 + 1.00 * 0.0144 |
| |
| T_final = wxu * wxu_scale * Exray + wu * Eadp |
| 5.2223 = 0.86 * 1.00 * 6.0251 + 1.00 * 0.0148 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 28 |
|-----------------------------------------------------------------------------|
|-ADP statistics (Wilson B = 11.778)------------------------------------------|
| Atom | Number of | Isotropic or equivalent| Anisotropy lmin/max |
| type |iso aniso | min max mean | min max mean |
| - - - - |- - - - - - -| - - - - - - - - - - - -| - - - - - - - - - - |
| all : 2823 0 0.00 69.00 12.41 None None None |
| all(noH): 2823 0 0.00 69.00 12.41 None None None |
| Sol. : 438 0 0.00 69.00 27.15 None None None |
| Mac. : 2385 0 0.00 59.96 9.70 None None None |
| Hyd. : 0 0 None None None None None None |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Distribution of isotropic (or equivalent) ADP for non-H atoms: |
| Bin# value range #atoms | Bin# value range #atoms |
| 0: 0.000 - 6.900: 1117 | 5: 34.500 - 41.400: 83 |
| 1: 6.900 - 13.800: 771 | 6: 41.400 - 48.300: 43 |
| 2: 13.800 - 20.700: 438 | 7: 48.300 - 55.200: 33 |
| 3: 20.700 - 27.600: 199 | 8: 55.200 - 62.100: 14 |
| 4: 27.600 - 34.500: 123 | 9: 62.100 - 69.000: 2 |
| =>continue=> |
|-----------------------------------------------------------------------------|
======================= Individual occupancy refinement =======================
|-individual occupancy refinement: start--------------------------------------|
| r_work = 0.3126 r_free = 0.3630 target_work(ml) = 6.001 |
| occupancies: max = 1.00 min = 0.30 number of occupancies < 0.1: 0 |
|-----------------------------------------------------------------------------|
|-individual occupancy refinement: end----------------------------------------|
| r_work = 0.3122 r_free = 0.3635 target_work(ml) = 6.000 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 6 |
|-----------------------------------------------------------------------------|
*********************** REFINEMENT MACRO_CYCLE 2 OF 5 *************************
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.3122 r_free= 0.3635 ksol= 0.35 Bsol= 18.34 scale= 1.114 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (7.09,8.73,10.28,0.00,0.00,0.00); trace/3= 8.70 |
| |
| maximum likelihood estimate for coordinate error: 0.43 A |
| x-ray target function (ml) for work reflections: 5.999972 |
|-----------------------------------------------------------------------------|
====================== bulk solvent modeling and scaling ======================
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.3078 r_free= 0.3581 ksol= 0.31 Bsol= 20.00 scale= 1.016 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (3.66,4.57,6.63,0.00,0.00,0.00); trace/3= 4.95 |
| |
| maximum likelihood estimate for coordinate error: 0.44 A |
| x-ray target function (ml) for work reflections: 5.999891 |
|-----------------------------------------------------------------------------|
========================== Target weights: x-ray data =========================
|-----------------------------------------------------------------------------|
| XYZ refinement: T = Eexperimental * wxc * wxc_scale + Echem * wc |
| wxc = 3.908957 wxc_scale = 0.500 wc = 1.000 |
| angle between x-ray and geometry gradient vectors: 97.482 (deg) |
| |
| ADP refinement: T = Eexperimental * wxu * wxu_scale + Eadp * wu |
| wxc = 0.395700 wxc_scale = 1.000 wc = 1.000 |
| angle between Xray and ADP gradient vectors: 142.445 (deg) |
|-----------------------------------------------------------------------------|
================================ xyz refinement ===============================
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.3078 final r-factor (work) = 0.2185 |
| start r-factor (free) = 0.3581 final r-factor (free) = 0.2681 |
|-----------------------------------------------------------------------------|
| T_start = wxc * wxc_scale * Exray + wc * Echem |
| 11.9024 = 3.91 * 0.50 * 6.0237 + 1.00 * 0.1293 |
| |
| T_final = wxc * wxc_scale * Exray + wc * Echem |
| 11.5046 = 3.91 * 0.50 * 5.8509 + 1.00 * 0.0692 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 28 |
|-----------------------------------------------------------------------------|
================================ ADP refinement ===============================
----------Individual ADP refinement----------
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.2185 final r-factor (work) = 0.1992 |
| start r-factor (free) = 0.2681 final r-factor (free) = 0.2527 |
|-----------------------------------------------------------------------------|
| T_start = wxu * wxu_scale * Exray + wu * Eadp |
| 2.3300 = 0.40 * 1.00 * 5.8509 + 1.00 * 0.0148 |
| |
| T_final = wxu * wxu_scale * Exray + wu * Eadp |
| 2.2494 = 0.40 * 1.00 * 5.6563 + 1.00 * 0.0112 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 30 |
|-----------------------------------------------------------------------------|
|-ADP statistics (Wilson B = 11.778)------------------------------------------|
| Atom | Number of | Isotropic or equivalent| Anisotropy lmin/max |
| type |iso aniso | min max mean | min max mean |
| - - - - |- - - - - - -| - - - - - - - - - - - -| - - - - - - - - - - |
| all : 2823 0 0.00 72.32 12.26 None None None |
| all(noH): 2823 0 0.00 72.32 12.26 None None None |
| Sol. : 438 0 0.00 72.32 31.07 None None None |
| Mac. : 2385 0 0.00 61.20 8.80 None None None |
| Hyd. : 0 0 None None None None None None |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Distribution of isotropic (or equivalent) ADP for non-H atoms: |
| Bin# value range #atoms | Bin# value range #atoms |
| 0: 0.000 - 7.232: 1307 | 5: 36.162 - 43.395: 97 |
| 1: 7.232 - 14.465: 743 | 6: 43.395 - 50.627: 47 |
| 2: 14.465 - 21.697: 285 | 7: 50.627 - 57.859: 27 |
| 3: 21.697 - 28.930: 153 | 8: 57.859 - 65.092: 5 |
| 4: 28.930 - 36.162: 158 | 9: 65.092 - 72.324: 1 |
| =>continue=> |
|-----------------------------------------------------------------------------|
======================= Individual occupancy refinement =======================
|-individual occupancy refinement: start--------------------------------------|
| r_work = 0.1992 r_free = 0.2527 target_work(ml) = 5.627 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 6 |
|-----------------------------------------------------------------------------|
|-individual occupancy refinement: end----------------------------------------|
| r_work = 0.1991 r_free = 0.2526 target_work(ml) = 5.627 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 8 |
|-----------------------------------------------------------------------------|
*********************** REFINEMENT MACRO_CYCLE 3 OF 5 *************************
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1991 r_free= 0.2526 ksol= 0.31 Bsol= 20.00 scale= 1.053 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (3.66,4.57,6.63,0.00,0.00,0.00); trace/3= 4.95 |
| |
| maximum likelihood estimate for coordinate error: 0.25 A |
| x-ray target function (ml) for work reflections: 5.626927 |
|-----------------------------------------------------------------------------|
====================== bulk solvent modeling and scaling ======================
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1973 r_free= 0.2520 ksol= 0.33 Bsol= 43.90 scale= 1.004 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (2.15,2.78,4.47,0.00,0.00,0.00); trace/3= 3.13 |
| |
| maximum likelihood estimate for coordinate error: 0.26 A |
| x-ray target function (ml) for work reflections: 5.627366 |
|-----------------------------------------------------------------------------|
========================== Target weights: x-ray data =========================
|-----------------------------------------------------------------------------|
| XYZ refinement: T = Eexperimental * wxc * wxc_scale + Echem * wc |
| wxc = 2.982293 wxc_scale = 0.500 wc = 1.000 |
| angle between x-ray and geometry gradient vectors: 103.845 (deg) |
| |
| ADP refinement: T = Eexperimental * wxu * wxu_scale + Eadp * wu |
| wxc = 11.598464 wxc_scale = 1.000 wc = 1.000 |
| angle between Xray and ADP gradient vectors: 136.339 (deg) |
|-----------------------------------------------------------------------------|
================================ xyz refinement ===============================
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.1973 final r-factor (work) = 0.1483 |
| start r-factor (free) = 0.2520 final r-factor (free) = 0.1956 |
|-----------------------------------------------------------------------------|
| T_start = wxc * wxc_scale * Exray + wc * Echem |
| 8.5196 = 2.98 * 0.50 * 5.6672 + 1.00 * 0.0689 |
| |
| T_final = wxc * wxc_scale * Exray + wc * Echem |
| 8.2718 = 2.98 * 0.50 * 5.5050 + 1.00 * 0.0630 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 28 |
|-----------------------------------------------------------------------------|
================================ ADP refinement ===============================
----------Individual ADP refinement----------
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.1483 final r-factor (work) = 0.1350 |
| start r-factor (free) = 0.1956 final r-factor (free) = 0.1875 |
|-----------------------------------------------------------------------------|
| T_start = wxu * wxu_scale * Exray + wu * Eadp |
| 63.8608 = 11.60 * 1.00 * 5.5050 + 1.00 * 0.0112 |
| |
| T_final = wxu * wxu_scale * Exray + wu * Eadp |
| 61.7930 = 11.60 * 1.00 * 5.3263 + 1.00 * 0.0159 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 28 |
|-----------------------------------------------------------------------------|
|-ADP statistics (Wilson B = 11.778)------------------------------------------|
| Atom | Number of | Isotropic or equivalent| Anisotropy lmin/max |
| type |iso aniso | min max mean | min max mean |
| - - - - |- - - - - - -| - - - - - - - - - - - -| - - - - - - - - - - |
| all : 2823 0 0.00 85.44 13.38 None None None |
| all(noH): 2823 0 0.00 85.44 13.38 None None None |
| Sol. : 438 0 1.01 85.44 38.86 None None None |
| Mac. : 2385 0 0.00 82.09 8.70 None None None |
| Hyd. : 0 0 None None None None None None |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Distribution of isotropic (or equivalent) ADP for non-H atoms: |
| Bin# value range #atoms | Bin# value range #atoms |
| 0: 0.000 - 8.544: 1566 | 5: 42.720 - 51.264: 103 |
| 1: 8.544 - 17.088: 629 | 6: 51.264 - 59.808: 70 |
| 2: 17.088 - 25.632: 183 | 7: 59.808 - 68.352: 48 |
| 3: 25.632 - 34.176: 111 | 8: 68.352 - 76.896: 15 |
| 4: 34.176 - 42.720: 93 | 9: 76.896 - 85.440: 5 |
| =>continue=> |
|-----------------------------------------------------------------------------|
======================= Individual occupancy refinement =======================
|-individual occupancy refinement: start--------------------------------------|
| r_work = 0.1350 r_free = 0.1875 target_work(ml) = 5.302 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 8 |
|-----------------------------------------------------------------------------|
|-individual occupancy refinement: end----------------------------------------|
| r_work = 0.1349 r_free = 0.1873 target_work(ml) = 5.301 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 7 |
|-----------------------------------------------------------------------------|
*********************** REFINEMENT MACRO_CYCLE 4 OF 5 *************************
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1349 r_free= 0.1873 ksol= 0.33 Bsol= 43.90 scale= 1.016 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (2.15,2.78,4.47,0.00,0.00,0.00); trace/3= 3.13 |
| |
| maximum likelihood estimate for coordinate error: 0.19 A |
| x-ray target function (ml) for work reflections: 5.301358 |
|-----------------------------------------------------------------------------|
====================== bulk solvent modeling and scaling ======================
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1350 r_free= 0.1872 ksol= 0.32 Bsol= 43.90 scale= 1.009 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (1.99,2.47,4.25,0.00,0.00,0.00); trace/3= 2.90 |
| |
| maximum likelihood estimate for coordinate error: 0.19 A |
| x-ray target function (ml) for work reflections: 5.300162 |
|-----------------------------------------------------------------------------|
========================== Target weights: x-ray data =========================
|-----------------------------------------------------------------------------|
| XYZ refinement: T = Eexperimental * wxc * wxc_scale + Echem * wc |
| wxc = 1.650177 wxc_scale = 0.500 wc = 1.000 |
| angle between x-ray and geometry gradient vectors: 110.909 (deg) |
| |
| ADP refinement: T = Eexperimental * wxu * wxu_scale + Eadp * wu |
| wxc = 0.979516 wxc_scale = 1.000 wc = 1.000 |
| angle between Xray and ADP gradient vectors: 125.204 (deg) |
|-----------------------------------------------------------------------------|
================================ xyz refinement ===============================
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.1350 final r-factor (work) = 0.1250 |
| start r-factor (free) = 0.1872 final r-factor (free) = 0.1754 |
|-----------------------------------------------------------------------------|
| T_start = wxc * wxc_scale * Exray + wc * Echem |
| 4.4577 = 1.65 * 0.50 * 5.3263 + 1.00 * 0.0630 |
| |
| T_final = wxc * wxc_scale * Exray + wc * Echem |
| 4.4021 = 1.65 * 0.50 * 5.2710 + 1.00 * 0.0531 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 28 |
|-----------------------------------------------------------------------------|
================================ ADP refinement ===============================
----------Individual ADP refinement----------
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.1250 final r-factor (work) = 0.1230 |
| start r-factor (free) = 0.1754 final r-factor (free) = 0.1714 |
|-----------------------------------------------------------------------------|
| T_start = wxu * wxu_scale * Exray + wu * Eadp |
| 5.1788 = 0.98 * 1.00 * 5.2710 + 1.00 * 0.0159 |
| |
| T_final = wxu * wxu_scale * Exray + wu * Eadp |
| 5.1531 = 0.98 * 1.00 * 5.2357 + 1.00 * 0.0247 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 26 |
|-----------------------------------------------------------------------------|
|-ADP statistics (Wilson B = 11.778)------------------------------------------|
| Atom | Number of | Isotropic or equivalent| Anisotropy lmin/max |
| type |iso aniso | min max mean | min max mean |
| - - - - |- - - - - - -| - - - - - - - - - - - -| - - - - - - - - - - |
| all : 2823 0 0.00 88.98 13.00 None None None |
| all(noH): 2823 0 0.00 88.98 13.00 None None None |
| Sol. : 438 0 1.06 87.74 38.06 None None None |
| Mac. : 2385 0 0.00 88.98 8.40 None None None |
| Hyd. : 0 0 None None None None None None |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Distribution of isotropic (or equivalent) ADP for non-H atoms: |
| Bin# value range #atoms | Bin# value range #atoms |
| 0: 0.000 - 8.898: 1688 | 5: 44.491 - 53.389: 90 |
| 1: 8.898 - 17.796: 562 | 6: 53.389 - 62.288: 52 |
| 2: 17.796 - 26.695: 156 | 7: 62.288 - 71.186: 43 |
| 3: 26.695 - 35.593: 117 | 8: 71.186 - 80.084: 10 |
| 4: 35.593 - 44.491: 101 | 9: 80.084 - 88.982: 4 |
| =>continue=> |
|-----------------------------------------------------------------------------|
======================= Individual occupancy refinement =======================
|-individual occupancy refinement: start--------------------------------------|
| r_work = 0.1230 r_free = 0.1714 target_work(ml) = 5.226 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 7 |
|-----------------------------------------------------------------------------|
|-individual occupancy refinement: end----------------------------------------|
| r_work = 0.1228 r_free = 0.1713 target_work(ml) = 5.225 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 6 |
|-----------------------------------------------------------------------------|
*********************** REFINEMENT MACRO_CYCLE 5 OF 5 *************************
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1228 r_free= 0.1713 ksol= 0.32 Bsol= 43.90 scale= 1.006 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (1.99,2.47,4.25,0.00,0.00,0.00); trace/3= 2.90 |
| |
| maximum likelihood estimate for coordinate error: 0.17 A |
| x-ray target function (ml) for work reflections: 5.225284 |
|-----------------------------------------------------------------------------|
====================== bulk solvent modeling and scaling ======================
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1228 r_free= 0.1712 ksol= 0.32 Bsol= 49.15 scale= 1.008 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (2.11,2.50,4.26,0.00,0.00,0.00); trace/3= 2.96 |
| |
| maximum likelihood estimate for coordinate error: 0.17 A |
| x-ray target function (ml) for work reflections: 5.225212 |
|-----------------------------------------------------------------------------|
========================== Target weights: x-ray data =========================
|-----------------------------------------------------------------------------|
| XYZ refinement: T = Eexperimental * wxc * wxc_scale + Echem * wc |
| wxc = 2.421701 wxc_scale = 0.500 wc = 1.000 |
| angle between x-ray and geometry gradient vectors: 138.907 (deg) |
| |
| ADP refinement: T = Eexperimental * wxu * wxu_scale + Eadp * wu |
| wxc = 0.813362 wxc_scale = 1.000 wc = 1.000 |
| angle between Xray and ADP gradient vectors: 94.626 (deg) |
|-----------------------------------------------------------------------------|
================================ xyz refinement ===============================
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.1228 final r-factor (work) = 0.1149 |
| start r-factor (free) = 0.1712 final r-factor (free) = 0.1620 |
|-----------------------------------------------------------------------------|
| T_start = wxc * wxc_scale * Exray + wc * Echem |
| 6.3927 = 2.42 * 0.50 * 5.2357 + 1.00 * 0.0531 |
| |
| T_final = wxc * wxc_scale * Exray + wc * Echem |
| 6.3537 = 2.42 * 0.50 * 5.1963 + 1.00 * 0.0618 |
|-----------------------------------------------------------------------------|
| number of iterations = 25 | number of function evaluations = 28 |
|-----------------------------------------------------------------------------|
================================ ADP refinement ===============================
----------Individual ADP refinement----------
|-LBFGS minimization----------------------------------------------------------|
| start r-factor (work) = 0.1149 final r-factor (work) = 0.1139 |
| start r-factor (free) = 0.1620 final r-factor (free) = 0.1603 |
|-----------------------------------------------------------------------------|
| T_start = wxu * wxu_scale * Exray + wu * Eadp |
| 4.2421 = 0.81 * 1.00 * 5.1963 + 1.00 * 0.0156 |
| |
| T_final = wxu * wxu_scale * Exray + wu * Eadp |
| 4.2174 = 0.81 * 1.00 * 5.1681 + 1.00 * 0.0138 |
|-----------------------------------------------------------------------------|
| number of iterations = 14 | number of function evaluations = 15 |
|-----------------------------------------------------------------------------|
|-ADP statistics (Wilson B = 11.778)------------------------------------------|
| Atom | Number of | Isotropic or equivalent| Anisotropy lmin/max |
| type |iso aniso | min max mean | min max mean |
| - - - - |- - - - - - -| - - - - - - - - - - - -| - - - - - - - - - - |
| all : 2823 0 0.00 90.67 12.73 None None None |
| all(noH): 2823 0 0.00 90.67 12.73 None None None |
| Sol. : 438 0 1.25 87.84 37.40 None None None |
| Mac. : 2385 0 0.00 90.67 8.20 None None None |
| Hyd. : 0 0 None None None None None None |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Distribution of isotropic (or equivalent) ADP for non-H atoms: |
| Bin# value range #atoms | Bin# value range #atoms |
| 0: 0.000 - 9.067: 1749 | 5: 45.334 - 54.401: 85 |
| 1: 9.067 - 18.134: 523 | 6: 54.401 - 63.468: 47 |
| 2: 18.134 - 27.201: 153 | 7: 63.468 - 72.535: 38 |
| 3: 27.201 - 36.267: 116 | 8: 72.535 - 81.602: 10 |
| 4: 36.267 - 45.334: 99 | 9: 81.602 - 90.669: 3 |
| =>continue=> |
|-----------------------------------------------------------------------------|
======================= Individual occupancy refinement =======================
|-individual occupancy refinement: start--------------------------------------|
| r_work = 0.1139 r_free = 0.1603 target_work(ml) = 5.163 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 6 |
|-----------------------------------------------------------------------------|
|-individual occupancy refinement: end----------------------------------------|
| r_work = 0.1139 r_free = 0.1603 target_work(ml) = 5.162 |
| occupancies: max = 1.00 min = 0.00 number of occupancies < 0.1: 5 |
|-----------------------------------------------------------------------------|
----------X-ray data----------
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1139 r_free= 0.1603 ksol= 0.32 Bsol= 49.15 scale= 1.005 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (2.11,2.50,4.26,0.00,0.00,0.00); trace/3= 2.96 |
| |
| maximum likelihood estimate for coordinate error: 0.16 A |
| x-ray target function (ml) for work reflections: 5.162463 |
|-----------------------------------------------------------------------------|
|-----------------------------------------------------------------------------|
| Bin Resolution Compl. No. Refl. R-factors Targets |
|number range work test work test work test|
| 1: 14.9433 - 4.7259 0.99 1394 152 0.0999 0.1277 5.3908 5.529|
| 2: 4.7259 - 3.7709 0.99 1329 154 0.0841 0.1094 5.4283 5.6285|
| 3: 3.7709 - 3.3001 0.99 1307 143 0.1058 0.1493 5.4806 5.8431|
| 4: 3.3001 - 3.0010 0.99 1304 140 0.1231 0.1778 5.4641 5.658|
| 5: 3.0010 - 2.7874 0.99 1292 147 0.1332 0.1646 5.342 5.5398|
| 6: 2.7874 - 2.6240 0.99 1300 145 0.1224 0.2070 5.2245 5.5385|
| 7: 2.6240 - 2.4932 0.99 1271 144 0.1319 0.1665 5.209 5.352|
| 8: 2.4932 - 2.3852 0.98 1270 136 0.1211 0.1631 5.1124 5.3502|
| 9: 2.3852 - 2.2937 0.98 1282 148 0.1215 0.1956 5.0603 5.3588|
| 10: 2.2937 - 2.2148 1.00 1275 139 0.1170 0.1606 4.9856 5.1858|
| 11: 2.2148 - 2.1457 0.97 1267 134 0.1179 0.1841 4.9774 5.2893|
| 12: 2.1457 - 2.0846 0.98 1247 145 0.1209 0.1749 4.9236 5.2619|
| 13: 2.0846 - 2.0298 1.00 1271 138 0.1137 0.1742 4.8002 5.0397|
| 14: 2.0298 - 1.9804 0.63 821 94 0.0962 0.1689 4.6271 4.9004|
|-----------------------------------------------------------------------------|
|-----------------------------------------------------------------------------|
|R-free likelihood based estimates for figures of merit, absolute phase error,|
|and distribution parameters alpha and beta (Acta Cryst. (1995). A51, 880-887)|
| |
| Bin Resolution No. Refl. FOM Phase Scale Alpha Beta |
| # range work test error factor |
| 1: 14.9433 - 4.7259 1394 152 0.94 9.39 0.98 0.95 7371.22|
| 2: 4.7259 - 3.7709 1329 154 0.95 7.94 1.02 1.01 9049.00|
| 3: 3.7709 - 3.3001 1307 143 0.93 11.26 1.04 1.03 10404.61|
| 4: 3.3001 - 3.0010 1304 140 0.92 13.60 1.02 1.01 10490.97|
| 5: 3.0010 - 2.7874 1292 147 0.90 15.87 1.01 0.98 8552.79|
| 6: 2.7874 - 2.6240 1300 145 0.89 16.66 0.98 0.96 7443.92|
| 7: 2.6240 - 2.4932 1271 144 0.90 16.20 0.99 0.95 6584.43|
| 8: 2.4932 - 2.3852 1270 136 0.90 15.75 0.99 0.97 5747.49|
| 9: 2.3852 - 2.2937 1282 148 0.91 15.58 1.00 0.97 5262.89|
| 10: 2.2937 - 2.2148 1275 139 0.89 16.73 1.00 0.97 4694.92|
| 11: 2.2148 - 2.1457 1267 134 0.89 16.89 1.00 0.96 4781.99|
| 12: 2.1457 - 2.0846 1247 145 0.90 16.82 1.01 1.01 4329.54|
| 13: 2.0846 - 2.0298 1271 138 0.91 15.63 1.00 0.97 3365.05|
| 14: 2.0298 - 1.9804 821 94 0.93 13.42 0.99 0.96 2374.67|
|alpha: min = 0.95 max = 1.03 mean = 0.98|
|beta: min = 2374.67 max = 10490.97 mean = 6602.01|
|figures of merit: min = 0.00 max = 1.00 mean = 0.91|
|phase err.(work): min = 0.00 max = 89.79 mean = 14.37|
|phase err.(test): min = 0.00 max = 89.80 mean = 13.85|
|-----------------------------------------------------------------------------|
====================== bulk solvent modeling and scaling ======================
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1139 r_free= 0.1602 ksol= 0.32 Bsol= 52.17 scale= 1.007 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (-0.83,-0.48,1.31,-0.00,0.00,0.00); trace/3= 0.00 |
| |
| maximum likelihood estimate for coordinate error: 0.16 A |
| x-ray target function (ml) for work reflections: 5.162470 |
|-----------------------------------------------------------------------------|
----------X-ray data----------
|--(resolution: 1.98 - 14.94 A; n_refl. = 19589)------------------------------|
| |
| r_work= 0.1139 r_free= 0.1602 ksol= 0.32 Bsol= 52.17 scale= 1.007 |
| |
| overall anisotropic scale matrix (Cartesian basis; B11,B22,B33,B12,B13,B23):|
| (-0.83,-0.48,1.31,-0.00,0.00,0.00); trace/3= 0.00 |
| |
| maximum likelihood estimate for coordinate error: 0.16 A |
| x-ray target function (ml) for work reflections: 5.162470 |
|-----------------------------------------------------------------------------|
|-----------------------------------------------------------------------------|
| Bin Resolution Compl. No. Refl. R-factors Targets |
|number range work test work test work test|
| 1: 14.9433 - 4.7259 0.99 1394 152 0.1000 0.1278 5.3909 5.5294|
| 2: 4.7259 - 3.7709 0.99 1329 154 0.0841 0.1094 5.4287 5.6287|
| 3: 3.7709 - 3.3001 0.99 1307 143 0.1058 0.1493 5.4808 5.8433|
| 4: 3.3001 - 3.0010 0.99 1304 140 0.1231 0.1778 5.4641 5.658|
| 5: 3.0010 - 2.7874 0.99 1292 147 0.1332 0.1646 5.3419 5.5396|
| 6: 2.7874 - 2.6240 0.99 1300 145 0.1224 0.2070 5.2244 5.5383|
| 7: 2.6240 - 2.4932 0.99 1271 144 0.1319 0.1666 5.209 5.3522|
| 8: 2.4932 - 2.3852 0.98 1270 136 0.1211 0.1631 5.1124 5.3501|
| 9: 2.3852 - 2.2937 0.98 1282 148 0.1215 0.1955 5.0603 5.3586|
| 10: 2.2937 - 2.2148 1.00 1275 139 0.1170 0.1607 4.9855 5.1863|
| 11: 2.2148 - 2.1457 0.97 1267 134 0.1179 0.1840 4.9774 5.2891|
| 12: 2.1457 - 2.0846 0.98 1247 145 0.1209 0.1749 4.9235 5.2617|
| 13: 2.0846 - 2.0298 1.00 1271 138 0.1137 0.1741 4.8 5.0395|
| 14: 2.0298 - 1.9804 0.63 821 94 0.0962 0.1687 4.6269 4.8999|
|-----------------------------------------------------------------------------|
|-----------------------------------------------------------------------------|
|R-free likelihood based estimates for figures of merit, absolute phase error,|
|and distribution parameters alpha and beta (Acta Cryst. (1995). A51, 880-887)|
| |
| Bin Resolution No. Refl. FOM Phase Scale Alpha Beta |
| # range work test error factor |
| 1: 14.9433 - 4.7259 1394 152 0.94 9.40 0.98 0.95 7376.15|
| 2: 4.7259 - 3.7709 1329 154 0.95 7.95 1.02 1.01 9055.55|
| 3: 3.7709 - 3.3001 1307 143 0.93 11.26 1.04 1.03 10410.20|
| 4: 3.3001 - 3.0010 1304 140 0.92 13.60 1.02 1.01 10490.75|
| 5: 3.0010 - 2.7874 1292 147 0.90 15.87 1.01 0.98 8550.36|
| 6: 2.7874 - 2.6240 1300 145 0.89 16.66 0.99 0.96 7442.37|
| 7: 2.6240 - 2.4932 1271 144 0.90 16.20 0.99 0.96 6584.69|
| 8: 2.4932 - 2.3852 1270 136 0.90 15.75 1.00 0.98 5747.51|
| 9: 2.3852 - 2.2937 1282 148 0.91 15.59 1.01 0.97 5263.37|
| 10: 2.2937 - 2.2148 1275 139 0.89 16.74 1.01 0.97 4695.08|
| 11: 2.2148 - 2.1457 1267 134 0.89 16.89 1.00 0.96 4782.26|
| 12: 2.1457 - 2.0846 1247 145 0.90 16.82 1.01 1.01 4329.41|
| 13: 2.0846 - 2.0298 1271 138 0.91 15.62 1.00 0.98 3363.06|
| 14: 2.0298 - 1.9804 821 94 0.93 13.41 0.99 0.96 2371.94|
|alpha: min = 0.95 max = 1.03 mean = 0.98|
|beta: min = 2371.94 max = 10490.75 mean = 6602.81|
|figures of merit: min = 0.00 max = 1.00 mean = 0.91|
|phase err.(work): min = 0.00 max = 89.81 mean = 14.38|
|phase err.(test): min = 0.00 max = 89.74 mean = 13.85|
|-----------------------------------------------------------------------------|
|-ADP statistics (Wilson B = 11.778)------------------------------------------|
| Atom | Number of | Isotropic or equivalent| Anisotropy lmin/max |
| type |iso aniso | min max mean | min max mean |
| - - - - |- - - - - - -| - - - - - - - - - - - -| - - - - - - - - - - |
| all : 2823 0 3.02 93.69 15.75 None None None |
| all(noH): 2823 0 3.02 93.69 15.75 None None None |
| Sol. : 438 0 4.28 90.86 40.42 None None None |
| Mac. : 2385 0 3.02 93.69 11.22 None None None |
| Hyd. : 0 0 None None None None None None |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Distribution of isotropic (or equivalent) ADP for non-H atoms: |
| Bin# value range #atoms | Bin# value range #atoms |
| 0: 3.025 - 12.091: 1749 | 5: 48.359 - 57.426: 85 |
| 1: 12.091 - 21.158: 523 | 6: 57.426 - 66.492: 47 |
| 2: 21.158 - 30.225: 153 | 7: 66.492 - 75.559: 38 |
| 3: 30.225 - 39.292: 116 | 8: 75.559 - 84.626: 10 |
| 4: 39.292 - 48.359: 99 | 9: 84.626 - 93.693: 3 |
| =>continue=> |
|-----------------------------------------------------------------------------|
========== residual map mFobs-DFmodel: highest peaks and deepst holes =========
----------peaks----------
Number of peaks found at mFobs-DFmodel map (map cutoff=3.00 sigma)= 304
Filter by distance & map next to the model:
mapped sites are within: 0.219 - 4.836
number of sites selected in [dist_min= 0.70, dist_max= 6.00]: 301 from: 304
mapped sites are within: 0.716 - 4.836
peak= 10.947 closest distance to " CB VAL A 230 " = 1.455
peak= 9.915 closest distance to " CB VAL A 296 " = 1.569
peak= 6.295 closest distance to " CD2 LEU A 5 " = 1.192
peak= 6.021 closest distance to " NE2 GLN A 11 " = 1.145
peak= 5.711 closest distance to " O HOH Z 130 " = 1.097
peak= 5.661 closest distance to " O HOH Z 9 " = 1.833
peak= 5.645 closest distance to " CG LEU A 5 " = 1.171
peak= 5.604 closest distance to " CG PRO A 54 " = 1.357
peak= 5.398 closest distance to " O HOH Z 142 " = 1.994
peak= 5.327 closest distance to " NH2 ARG A 56 " = 2.053
peak= 5.258 closest distance to " CG LEU A 228 " = 1.189
peak= 4.984 closest distance to " CB GLN A 223 " = 1.503
peak= 4.976 closest distance to " O HOH Z 427 " = 2.827
peak= 4.831 closest distance to " O HOH Z 232 " = 2.364
peak= 4.789 closest distance to " CB GLN A 183 " = 1.233
peak= 4.671 closest distance to " CB ARG A 275 " = 0.990
peak= 4.587 closest distance to " CB PRO A 54 " = 0.968
peak= 4.561 closest distance to " CB ASN A 142 " = 1.088
peak= 4.523 closest distance to " O HOH Z 313 " = 1.964
peak= 4.515 closest distance to " CD1AILE A 234 " = 0.917
peak= 4.477 closest distance to " CB ASN A 148 " = 1.364
peak= 4.467 closest distance to " CB VAL A 265 " = 1.379
peak= 4.448 closest distance to " O SER A 87 " = 2.307
peak= 4.380 closest distance to " O HOH Z 369 " = 2.263
peak= 4.375 closest distance to " ND2 ASN A 187 " = 1.690
peak= 4.375 closest distance to " O HOH Z 265 " = 2.103
peak= 4.346 closest distance to " O HOH Z 346 " = 1.548
peak= 4.293 closest distance to " CB ARG A 79 " = 1.465
peak= 4.285 closest distance to " O HOH Z 425 " = 1.464
peak= 4.260 closest distance to " O HOH Z 61 " = 1.700
peak= 4.233 closest distance to " O HOH Z 287 " = 1.955
peak= 4.231 closest distance to " CB BVAL A 41 " = 1.255
peak= 4.225 closest distance to " O HOH Z 248 " = 1.187
peak= 4.222 closest distance to " O HOH Z 422 " = 2.518
peak= 4.215 closest distance to " CG PRO A 213 " = 1.193
peak= 4.210 closest distance to " CB VAL A 230 " = 1.167
peak= 4.206 closest distance to " O HOH Z 130 " = 2.505
peak= 4.191 closest distance to " O HOH Z 209 " = 2.325
peak= 4.154 closest distance to " O HOH Z 303 " = 2.127
peak= 4.151 closest distance to " CG PRO A 198 " = 1.230
peak= 4.121 closest distance to " O HOH Z 272 " = 1.807
peak= 4.080 closest distance to " CB ARG A 190 " = 1.484
peak= 4.073 closest distance to " O HOH Z 403 " = 1.607
peak= 4.071 closest distance to " O HOH Z 112 " = 1.057
peak= 4.069 closest distance to " CB GLU A 277 " = 3.564
peak= 4.058 closest distance to " CB VAL A 202 " = 1.714
peak= 4.051 closest distance to " O HOH Z 78 " = 1.608
peak= 4.027 closest distance to " CG LEU A 167 " = 1.234
peak= 4.016 closest distance to " CB TRP A 266 " = 1.100
peak= 4.012 closest distance to " O PRO A 198 " = 1.570
peak= 3.983 closest distance to " CG PRO A 243 " = 1.190
peak= 3.964 closest distance to " O HOH Z 353 " = 2.582
peak= 3.963 closest distance to " CD2 TRP A 179 " = 1.295
peak= 3.962 closest distance to " O HOH Z 126 " = 2.147
peak= 3.956 closest distance to " O HOH Z 43 " = 1.975
peak= 3.947 closest distance to " O HOH Z 359 " = 1.420
peak= 3.942 closest distance to " CG AARG A 275 " = 1.139
peak= 3.936 closest distance to " CB SER A 63 " = 1.263
peak= 3.935 closest distance to " O HOH Z 3 " = 2.023
peak= 3.919 closest distance to " O HOH Z 193 " = 1.618
peak= 3.913 closest distance to " O HOH Z 411 " = 3.757
peak= 3.911 closest distance to " CB SER A 3 " = 1.307
peak= 3.884 closest distance to " CZ PHE A 218 " = 1.159
peak= 3.883 closest distance to " O HOH Z 234 " = 3.624
peak= 3.860 closest distance to " CA PHE A 283 " = 1.176
peak= 3.855 closest distance to " O BHOH Z 338 " = 2.427
peak= 3.835 closest distance to " O HOH Z 126 " = 1.552
peak= 3.824 closest distance to " OG ASER A 258 " = 3.017
peak= 3.816 closest distance to " CD ARG A 269 " = 1.066
peak= 3.809 closest distance to " O HOH Z 290 " = 1.008
peak= 3.808 closest distance to " O HOH Z 59 " = 1.709
peak= 3.807 closest distance to " O HOH Z 214 " = 2.412
peak= 3.807 closest distance to " O HOH Z 40 " = 1.569
peak= 3.800 closest distance to " N PHE A 130 " = 1.315
peak= 3.789 closest distance to " O HOH Z 30 " = 1.534
peak= 3.789 closest distance to " O HOH Z 97 " = 2.432
peak= 3.785 closest distance to " CB GLN A 88 " = 1.268
peak= 3.772 closest distance to " CB ARG A 79 " = 0.897
peak= 3.768 closest distance to " O HOH Z 10 " = 1.676
peak= 3.757 closest distance to " CG ARG A 138 " = 1.343
peak= 3.745 closest distance to " O HOH Z 124 " = 1.238
peak= 3.744 closest distance to " CA TYR A 30 " = 0.945
peak= 3.744 closest distance to " O HOH Z 380 " = 1.760
peak= 3.741 closest distance to " O HOH Z 251 " = 1.543
peak= 3.739 closest distance to " O HOH Z 188 " = 2.853
peak= 3.736 closest distance to " CB SER A 26 " = 1.725
peak= 3.732 closest distance to " CA ALA A 51 " = 0.981
peak= 3.732 closest distance to " N ASP A 162 " = 1.162
peak= 3.725 closest distance to " O HOH Z 402 " = 1.352
peak= 3.724 closest distance to " ND2 ASN A 249 " = 0.867
peak= 3.721 closest distance to " O HOH Z 258 " = 2.093
peak= 3.720 closest distance to " CG2 VAL A 257 " = 0.830
peak= 3.718 closest distance to " O HOH Z 389 " = 1.258
peak= 3.716 closest distance to " O HOH Z 298 " = 1.655
peak= 3.712 closest distance to " CG MET A 185 " = 1.263
peak= 3.712 closest distance to " CB ASN A 39 " = 0.966
peak= 3.705 closest distance to " CA LYS A 117 " = 1.211
peak= 3.705 closest distance to " OG BSER A 164 " = 2.105
peak= 3.694 closest distance to " O HOH Z 368 " = 2.127
peak= 3.686 closest distance to " CB LYS A 117 " = 1.204
peak= 3.686 closest distance to " CB ASN A 215 " = 1.151
peak= 3.672 closest distance to " CB TYR A 169 " = 0.718
peak= 3.660 closest distance to " O HOH Z 299 " = 4.116
peak= 3.656 closest distance to " CG2 ILE A 234 " = 0.987
peak= 3.652 closest distance to " CB ASN A 110 " = 1.091
peak= 3.648 closest distance to " CB PRO A 90 " = 1.122
peak= 3.640 closest distance to " O HOH Z 286 " = 2.462
peak= 3.630 closest distance to " O HOH Z 371 " = 2.821
peak= 3.627 closest distance to " CD2 LEU A 228 " = 1.223
peak= 3.627 closest distance to " O HOH Z 419 " = 2.057
peak= 3.627 closest distance to " CE LYS A 76 " = 0.897
peak= 3.623 closest distance to " CH2 TRP A 266 " = 1.089
peak= 3.620 closest distance to " NZ LYS A 117 " = 2.955
peak= 3.620 closest distance to " O HOH Z 85 " = 1.253
peak= 3.615 closest distance to " O HOH Z 143 " = 1.329
peak= 3.613 closest distance to " CG BARG A 102 " = 1.868
peak= 3.611 closest distance to " CB TRP A 179 " = 1.406
peak= 3.598 closest distance to " O HOH Z 406 " = 1.663
peak= 3.595 closest distance to " OE2 GLU A 2 " = 1.873
peak= 3.580 closest distance to " O HOH Z 423 " = 1.755
peak= 3.578 closest distance to " CG GLN A 88 " = 1.121
peak= 3.577 closest distance to " CB GLU A 152 " = 1.188
peak= 3.576 closest distance to " CD1 ILE A 33 " = 1.747
peak= 3.573 closest distance to " O HOH Z 44 " = 1.736
peak= 3.572 closest distance to " CB SER A 216 " = 0.814
peak= 3.564 closest distance to " O HOH Z 130 " = 2.183
peak= 3.559 closest distance to " CG2 ILE A 20 " = 1.565
peak= 3.559 closest distance to " O HOH Z 366 " = 2.891
peak= 3.556 closest distance to " O PRO A 198 " = 1.292
peak= 3.555 closest distance to " O HOH Z 88 " = 2.755
peak= 3.554 closest distance to " CD LYS A 76 " = 1.768
peak= 3.553 closest distance to " O HOH Z 123 " = 0.967
peak= 3.551 closest distance to " O HOH Z 261 " = 1.779
peak= 3.547 closest distance to " CA SER A 87 " = 1.019
peak= 3.546 closest distance to " OD1 ASN A 69 " = 2.407
peak= 3.539 closest distance to " O HOH Z 405 " = 1.193
peak= 3.536 closest distance to " CB ALA A 114 " = 1.445
peak= 3.531 closest distance to " NZ LYS A 48 " = 1.177
peak= 3.527 closest distance to " O HOH Z 368 " = 3.439
peak= 3.525 closest distance to " N ASN A 39 " = 1.228
peak= 3.523 closest distance to " O HOH Z 203 " = 1.704
peak= 3.523 closest distance to " CG GLN A 58 " = 0.882
peak= 3.520 closest distance to " NH2AARG A 145 " = 1.054
peak= 3.516 closest distance to " N ASN A 127 " = 1.346
peak= 3.515 closest distance to " O ASP A 124 " = 1.135
peak= 3.507 closest distance to " O HOH Z 128 " = 2.136
peak= 3.501 closest distance to " CA ASN A 215 " = 1.033
peak= 3.491 closest distance to " O HOH Z 117 " = 2.047
peak= 3.480 closest distance to " O HOH Z 180 " = 2.088
peak= 3.479 closest distance to " CE1 TYR A 186 " = 1.286
peak= 3.479 closest distance to " O HOH Z 80 " = 1.527
peak= 3.473 closest distance to " O HOH Z 193 " = 1.526
peak= 3.464 closest distance to " O HOH Z 22 " = 2.048
peak= 3.463 closest distance to " CB ALA A 9 " = 1.561
peak= 3.460 closest distance to " CB GLN A 89 " = 1.291
peak= 3.455 closest distance to " CA ASN A 127 " = 1.025
peak= 3.450 closest distance to " CD LYS A 166 " = 1.335
peak= 3.446 closest distance to " N ALA A 256 " = 0.967
peak= 3.443 closest distance to " CB GLU A 128 " = 1.020
peak= 3.438 closest distance to " OE2 GLU A 53 " = 2.009
peak= 3.437 closest distance to " CE3 TRP A 150 " = 0.992
peak= 3.436 closest distance to " O ASN A 74 " = 1.548
peak= 3.434 closest distance to " CG2 ILE A 120 " = 1.264
peak= 3.432 closest distance to " CB ASN A 187 " = 1.093
peak= 3.429 closest distance to " CB ASP A 124 " = 0.773
peak= 3.429 closest distance to " O HOH Z 329 " = 4.140
peak= 3.428 closest distance to " NH1AARG A 145 " = 1.174
peak= 3.425 closest distance to " CG1 ILE A 151 " = 1.122
peak= 3.419 closest distance to " CG1BVAL A 72 " = 1.604
peak= 3.417 closest distance to " CB THR A 52 " = 0.964
peak= 3.416 closest distance to " N SER A 135 " = 1.329
peak= 3.413 closest distance to " O HOH Z 172 " = 3.402
peak= 3.413 closest distance to " CG1 ILE A 49 " = 1.482
peak= 3.412 closest distance to " O HOH Z 261 " = 1.747
peak= 3.405 closest distance to " O HOH Z 1 " = 1.710
peak= 3.403 closest distance to " NZ LYS A 119 " = 2.729
peak= 3.400 closest distance to " O HOH Z 40 " = 2.429
peak= 3.398 closest distance to " CB HIS A 108 " = 0.844
peak= 3.396 closest distance to " CA ASN A 217 " = 1.214
peak= 3.392 closest distance to " O HOH Z 392 " = 3.070
peak= 3.391 closest distance to " NH2AARG A 275 " = 3.500
peak= 3.391 closest distance to " O HOH Z 59 " = 2.199
peak= 3.391 closest distance to " O HOH Z 158 " = 3.194
peak= 3.389 closest distance to " O HOH Z 437 " = 1.654
peak= 3.389 closest distance to " CA LYS A 290 " = 1.206
peak= 3.386 closest distance to " CA ARG A 36 " = 1.033
peak= 3.386 closest distance to " O HOH Z 126 " = 1.830
peak= 3.382 closest distance to " O HOH Z 303 " = 2.563
peak= 3.381 closest distance to " O HOH Z 88 " = 3.129
peak= 3.379 closest distance to " O HOH Z 2 " = 1.501
peak= 3.376 closest distance to " CA GLY A 267 " = 0.902
peak= 3.373 closest distance to " O HOH Z 196 " = 1.407
peak= 3.372 closest distance to " CB SER A 212 " = 1.292
peak= 3.372 closest distance to " CA ARG A 195 " = 1.170
peak= 3.372 closest distance to " O HOH Z 421 " = 2.115
peak= 3.372 closest distance to " O HOH Z 273 " = 3.023
peak= 3.371 closest distance to " NE ARG A 56 " = 3.511
peak= 3.368 closest distance to " CB PHE A 204 " = 1.074
peak= 3.366 closest distance to " CA ALA A 129 " = 1.477
peak= 3.366 closest distance to " OG BSER A 99 " = 2.187
peak= 3.366 closest distance to " O HOH Z 193 " = 1.120
peak= 3.364 closest distance to " N GLN A 278 " = 1.444
peak= 3.362 closest distance to " O HOH Z 68 " = 2.181
peak= 3.360 closest distance to " OG SER A 62 " = 2.858
peak= 3.352 closest distance to " O HOH Z 128 " = 2.081
peak= 3.346 closest distance to " O HOH Z 327 " = 1.963
peak= 3.343 closest distance to " O HOH Z 425 " = 2.106
peak= 3.343 closest distance to " CG LEU A 281 " = 0.988
peak= 3.329 closest distance to " O HOH Z 175 " = 2.040
peak= 3.326 closest distance to " O HOH Z 305 " = 3.411
peak= 3.325 closest distance to " O HOH Z 250 " = 1.356
peak= 3.322 closest distance to " CB THR A 31 " = 1.581
peak= 3.320 closest distance to " CA ALA A 291 " = 0.857
peak= 3.318 closest distance to " C ALA A 299 " = 0.914
peak= 3.316 closest distance to " OE1 GLU A 2 " = 1.873
peak= 3.316 closest distance to " O HOH Z 417 " = 1.086
peak= 3.315 closest distance to " O HOH Z 371 " = 3.326
peak= 3.311 closest distance to " CB LEU A 83 " = 0.716
peak= 3.306 closest distance to " CB GLU A 46 " = 0.961
peak= 3.304 closest distance to " CG MET A 113 " = 1.063
peak= 3.303 closest distance to " O HOH Z 193 " = 1.650
peak= 3.302 closest distance to " NH1 ARG A 138 " = 1.166
peak= 3.302 closest distance to " CB ALA A 248 " = 1.378
peak= 3.299 closest distance to " O HOH Z 153 " = 3.772
peak= 3.298 closest distance to " CA ALA A 158 " = 1.349
peak= 3.297 closest distance to " CG2 VAL A 197 " = 1.122
peak= 3.296 closest distance to " O HOH Z 322 " = 1.941
peak= 3.286 closest distance to " CG LYS A 119 " = 1.088
peak= 3.282 closest distance to " NE2 GLN A 73 " = 1.367
peak= 3.277 closest distance to " O HOH Z 423 " = 1.385
peak= 3.273 closest distance to " CB THR A 157 " = 1.201
peak= 3.272 closest distance to " N SER A 146 " = 1.773
peak= 3.269 closest distance to " CA ILE A 234 " = 1.038
peak= 3.262 closest distance to " CG2 THR A 221 " = 1.123
peak= 3.261 closest distance to " NE2 GLN A 77 " = 3.090
peak= 3.259 closest distance to " O THR A 182 " = 1.436
peak= 3.255 closest distance to " CB LEU A 300 " = 0.908
peak= 3.252 closest distance to " CG1 VAL A 153 " = 0.919
peak= 3.251 closest distance to " CB LEU A 228 " = 1.311
peak= 3.248 closest distance to " O HOH Z 59 " = 1.974
peak= 3.247 closest distance to " CB GLN A 278 " = 0.951
peak= 3.245 closest distance to " O HOH Z 92 " = 2.338
peak= 3.242 closest distance to " CA TRP A 150 " = 0.862
peak= 3.241 closest distance to " CB ALA A 248 " = 1.142
peak= 3.240 closest distance to " O HOH Z 61 " = 1.523
peak= 3.239 closest distance to " CA ASP A 162 " = 0.997
peak= 3.239 closest distance to " CD1 LEU A 96 " = 0.726
peak= 3.237 closest distance to " CB ASP A 140 " = 1.007
peak= 3.237 closest distance to " O HOH Z 21 " = 1.825
peak= 3.224 closest distance to " CD2 LEU A 297 " = 0.975
peak= 3.223 closest distance to " O HOH Z 280 " = 3.012
peak= 3.221 closest distance to " O HOH Z 233 " = 1.815
peak= 3.210 closest distance to " O HOH Z 357 " = 2.020
peak= 3.209 closest distance to " NE2 HIS A 207 " = 1.218
peak= 3.208 closest distance to " CA ALA A 160 " = 0.936
peak= 3.207 closest distance to " O HOH Z 145 " = 2.074
peak= 3.205 closest distance to " CZ PHE A 38 " = 1.129
peak= 3.204 closest distance to " O HOH Z 325 " = 2.102
peak= 3.193 closest distance to " CD2 TYR A 186 " = 1.079
peak= 3.193 closest distance to " O HOH Z 1 " = 1.703
peak= 3.193 closest distance to " O GLY A 57 " = 2.529
peak= 3.190 closest distance to " O PHE A 192 " = 1.410
peak= 3.189 closest distance to " O HOH Z 189 " = 2.719
peak= 3.188 closest distance to " O HOH Z 4 " = 1.454
peak= 3.185 closest distance to " O HOH Z 65 " = 0.864
peak= 3.180 closest distance to " CB ALA A 227 " = 1.134
peak= 3.172 closest distance to " CA ARG A 102 " = 1.128
peak= 3.165 closest distance to " CA LEU A 282 " = 1.165
peak= 3.164 closest distance to " N CYS A 260 " = 0.754
peak= 3.163 closest distance to " CB THR A 235 " = 1.280
peak= 3.162 closest distance to " O HOH Z 130 " = 1.933
peak= 3.159 closest distance to " OG SER A 62 " = 2.706
peak= 3.155 closest distance to " CG1 ILE A 120 " = 1.137
peak= 3.153 closest distance to " CB SER A 62 " = 1.104
peak= 3.150 closest distance to " O HOH Z 357 " = 2.651
peak= 3.150 closest distance to " CE LYS A 48 " = 1.095
peak= 3.146 closest distance to " NH2BARG A 145 " = 2.077
peak= 3.138 closest distance to " CB VAL A 268 " = 0.847
peak= 3.137 closest distance to " O HOH Z 213 " = 2.110
peak= 3.134 closest distance to " O HOH Z 222 " = 2.263
peak= 3.131 closest distance to " O HOH Z 40 " = 1.483
peak= 3.128 closest distance to " CA MET A 105 " = 0.972
peak= 3.128 closest distance to " CA THR A 264 " = 0.888
peak= 3.127 closest distance to " CA ALA A 233 " = 1.050
peak= 3.125 closest distance to " O HOH Z 285 " = 2.348
peak= 3.124 closest distance to " O HOH Z 259 " = 2.264
peak= 3.119 closest distance to " O HOH Z 48 " = 1.630
peak= 3.112 closest distance to " CD1 LEU A 228 " = 2.005
peak= 3.112 closest distance to " CA ASP A 191 " = 1.266
peak= 3.110 closest distance to " O LEU A 228 " = 1.889
peak= 3.110 closest distance to " O HOH Z 260 " = 1.590
peak= 3.105 closest distance to " CG GLN A 55 " = 2.380
peak= 3.100 closest distance to " CB ALA A 104 " = 0.736
peak= 3.090 closest distance to " CB VAL A 250 " = 1.095
peak= 3.070 closest distance to " CB ALA A 1 " = 4.836
peak= 3.069 closest distance to " O ALA A 158 " = 1.392
peak= 3.061 closest distance to " O HOH Z 89 " = 2.174
peak= 3.056 closest distance to " O HOH Z 132 " = 3.712
peak= 3.052 closest distance to " CG LYS A 289 " = 1.274
peak= 3.043 closest distance to " O HOH Z 272 " = 2.245
peak= 3.039 closest distance to " O HOH Z 344 " = 2.900
----------holes----------
Number of peaks found at mFobs-DFmodel map (map cutoff=3.00 sigma)= 204
Filter by distance & map next to the model:
mapped sites are within: 0.722 - 5.515
number of sites selected in [dist_min= 0.70, dist_max= 6.00]: 203 from: 204
mapped sites are within: 0.722 - 5.515
peak= -4.640 closest distance to " OG BSER A 134 " = 1.265
peak= -4.502 closest distance to " CG2 VAL A 230 " = 0.722
peak= -4.472 closest distance to " CD ARG A 156 " = 2.051
peak= -4.357 closest distance to " CD ARG A 14 " = 3.197
peak= -4.229 closest distance to " C HIS A 108 " = 1.212
peak= -4.220 closest distance to " CZ2 TRP A 92 " = 2.856
peak= -4.176 closest distance to " CG GLN A 58 " = 1.047
peak= -4.127 closest distance to " O HOH Z 266 " = 5.456
peak= -4.121 closest distance to " CB PRO A 243 " = 2.700
peak= -4.071 closest distance to " O VAL A 67 " = 2.481
peak= -4.043 closest distance to " CB PHE A 192 " = 1.897
peak= -4.036 closest distance to " CD GLN A 223 " = 2.239
peak= -3.981 closest distance to " O HOH Z 394 " = 1.533
peak= -3.927 closest distance to " CG2 VAL A 202 " = 2.708
peak= -3.896 closest distance to " O HOH Z 211 " = 1.302
peak= -3.888 closest distance to " O HOH Z 290 " = 1.199
peak= -3.864 closest distance to " O HOH Z 231 " = 2.044
peak= -3.855 closest distance to " CB ALA A 43 " = 2.570
peak= -3.849 closest distance to " O HOH Z 351 " = 1.517
peak= -3.844 closest distance to " O PRO A 163 " = 2.027
peak= -3.841 closest distance to " CE BMET A 47 " = 1.149
peak= -3.826 closest distance to " O HOH Z 185 " = 2.236
peak= -3.819 closest distance to " O HOH Z 131 " = 4.127
peak= -3.818 closest distance to " O PRO A 198 " = 1.193
peak= -3.765 closest distance to " N THR A 157 " = 1.441
peak= -3.758 closest distance to " O HOH Z 11 " = 1.785
peak= -3.756 closest distance to " N ALA A 43 " = 2.555
peak= -3.753 closest distance to " CD1 LEU A 255 " = 2.763
peak= -3.743 closest distance to " O HOH Z 193 " = 1.315
peak= -3.721 closest distance to " O HOH Z 429 " = 1.984
peak= -3.719 closest distance to " CA ASN A 127 " = 1.184
peak= -3.697 closest distance to " CA VAL A 67 " = 2.959
peak= -3.677 closest distance to " CB ALA A 161 " = 2.482
peak= -3.675 closest distance to " CE2 PHE A 218 " = 2.568
peak= -3.670 closest distance to " OG SER A 62 " = 4.328
peak= -3.653 closest distance to " O HOH Z 100 " = 1.093
peak= -3.643 closest distance to " CE2 TYR A 30 " = 2.676
peak= -3.640 closest distance to " O HOH Z 359 " = 3.093
peak= -3.637 closest distance to " CB ALA A 114 " = 2.456
peak= -3.631 closest distance to " NH2 ARG A 79 " = 2.051
peak= -3.616 closest distance to " O HOH Z 286 " = 1.671
peak= -3.615 closest distance to " CG1 VAL A 112 " = 2.860
peak= -3.615 closest distance to " ND2 ASN A 249 " = 2.369
peak= -3.609 closest distance to " CE1 PHE A 59 " = 1.973
peak= -3.599 closest distance to " O HOH Z 44 " = 2.323
peak= -3.599 closest distance to " N ALA A 226 " = 2.002
peak= -3.592 closest distance to " CG2 VAL A 296 " = 1.982
peak= -3.588 closest distance to " CD1 LEU A 101 " = 2.270
peak= -3.588 closest distance to " OH TYR A 172 " = 1.798
peak= -3.574 closest distance to " O HOH Z 114 " = 3.022
peak= -3.570 closest distance to " OG SER A 97 " = 2.230
peak= -3.566 closest distance to " OG SER A 87 " = 1.359
peak= -3.563 closest distance to " CE MET A 105 " = 2.401
peak= -3.555 closest distance to " CA ASP A 298 " = 1.075
peak= -3.552 closest distance to " CD1 ILE A 199 " = 2.438
peak= -3.548 closest distance to " O HOH Z 166 " = 2.046
peak= -3.542 closest distance to " CD PRO A 213 " = 2.030
peak= -3.538 closest distance to " O HOH Z 191 " = 5.515
peak= -3.531 closest distance to " O HOH Z 357 " = 2.064
peak= -3.530 closest distance to " CA GLY A 241 " = 2.378
peak= -3.526 closest distance to " NE2 GLN A 11 " = 1.884
peak= -3.525 closest distance to " CG TRP A 266 " = 1.926
peak= -3.523 closest distance to " N THR A 52 " = 1.731
peak= -3.515 closest distance to " O HOH Z 243 " = 1.995
peak= -3.504 closest distance to " CB ALA A 248 " = 2.331
peak= -3.499 closest distance to " CA GLY A 133 " = 1.940
peak= -3.498 closest distance to " O HOH Z 73 " = 2.399
peak= -3.491 closest distance to " CD2 TYR A 293 " = 1.940
peak= -3.483 closest distance to " O SER A 22 " = 2.331
peak= -3.480 closest distance to " ND2 ASN A 187 " = 1.518
peak= -3.478 closest distance to " OD2 ASP A 171 " = 2.228
peak= -3.469 closest distance to " C MET A 188 " = 1.453
peak= -3.463 closest distance to " CD2 LEU A 5 " = 1.123
peak= -3.458 closest distance to " CZ2 TRP A 274 " = 0.957
peak= -3.457 closest distance to " CG LEU A 5 " = 0.963
peak= -3.446 closest distance to " ND2 ASN A 252 " = 1.857
peak= -3.445 closest distance to " OXT GLY A 302 " = 2.967
peak= -3.444 closest distance to " CD2 HIS A 207 " = 2.282
peak= -3.442 closest distance to " CB PRO A 280 " = 2.150
peak= -3.436 closest distance to " ND2 ASN A 45 " = 2.026
peak= -3.431 closest distance to " N ALA A 248 " = 1.634
peak= -3.429 closest distance to " O HOH Z 43 " = 1.890
peak= -3.428 closest distance to " CD2 LEU A 237 " = 2.682
peak= -3.422 closest distance to " O HOH Z 102 " = 1.608
peak= -3.420 closest distance to " CD2 TYR A 247 " = 2.478
peak= -3.419 closest distance to " O HOH Z 389 " = 2.214
peak= -3.418 closest distance to " O HOH Z 421 " = 3.097
peak= -3.417 closest distance to " O HOH Z 295 " = 1.641
peak= -3.415 closest distance to " O HOH Z 352 " = 1.462
peak= -3.412 closest distance to " O PHE A 218 " = 1.480
peak= -3.411 closest distance to " ND2 ASN A 45 " = 1.236
peak= -3.394 closest distance to " CA GLY A 203 " = 2.476
peak= -3.391 closest distance to " O HOH Z 281 " = 2.822
peak= -3.390 closest distance to " OD2 ASP A 191 " = 1.303
peak= -3.384 closest distance to " O HOH Z 165 " = 2.082
peak= -3.381 closest distance to " OD1 ASN A 39 " = 2.163
peak= -3.380 closest distance to " O HOH Z 52 " = 1.325
peak= -3.376 closest distance to " CB PRO A 163 " = 2.398
peak= -3.372 closest distance to " O HOH Z 389 " = 1.430
peak= -3.369 closest distance to " OD1 ASN A 187 " = 1.695
peak= -3.364 closest distance to " O HOH Z 103 " = 1.786
peak= -3.364 closest distance to " CD LYS A 289 " = 2.344
peak= -3.361 closest distance to " O HOH Z 134 " = 4.039
peak= -3.349 closest distance to " OE2 GLU A 152 " = 1.300
peak= -3.344 closest distance to " CG1 VAL A 250 " = 2.681
peak= -3.343 closest distance to " O HOH Z 166 " = 2.053
peak= -3.341 closest distance to " O ALA A 10 " = 1.813
peak= -3.338 closest distance to " CE3 TRP A 150 " = 2.093
peak= -3.336 closest distance to " CB PRO A 213 " = 2.228
peak= -3.329 closest distance to " O HOH Z 65 " = 1.370
peak= -3.328 closest distance to " O HOH Z 140 " = 1.687
peak= -3.319 closest distance to " CE2 TRP A 70 " = 2.175
peak= -3.319 closest distance to " O HOH Z 236 " = 1.388
peak= -3.308 closest distance to " O HOH Z 313 " = 1.594
peak= -3.307 closest distance to " CG MET A 105 " = 0.933
peak= -3.307 closest distance to " CA GLY A 35 " = 2.100
peak= -3.304 closest distance to " CD2 PHE A 225 " = 1.137
peak= -3.299 closest distance to " O HOH Z 139 " = 3.076
peak= -3.297 closest distance to " OG SER A 63 " = 1.207
peak= -3.294 closest distance to " C GLN A 205 " = 1.841
peak= -3.291 closest distance to " O HOH Z 350 " = 1.732
peak= -3.291 closest distance to " CB ALA A 291 " = 2.209
peak= -3.288 closest distance to " NE2 GLN A 278 " = 1.697
peak= -3.287 closest distance to " N GLN A 58 " = 2.111
peak= -3.280 closest distance to " CZ ARG A 259 " = 0.995
peak= -3.279 closest distance to " CB SER A 210 " = 1.135
peak= -3.276 closest distance to " CB ALA A 10 " = 2.328
peak= -3.273 closest distance to " O HOH Z 318 " = 2.124
peak= -3.273 closest distance to " N SER A 276 " = 1.375
peak= -3.272 closest distance to " O HOH Z 345 " = 2.054
peak= -3.271 closest distance to " O HOH Z 51 " = 1.162
peak= -3.269 closest distance to " O HOH Z 238 " = 1.063
peak= -3.267 closest distance to " O MET A 40 " = 2.811
peak= -3.265 closest distance to " O HOH Z 90 " = 2.578
peak= -3.264 closest distance to " O VAL A 189 " = 2.578
peak= -3.263 closest distance to " O SER A 210 " = 1.806
peak= -3.263 closest distance to " CZ3 TRP A 179 " = 1.276
peak= -3.261 closest distance to " O HOH Z 384 " = 2.227
peak= -3.254 closest distance to " CA GLY A 98 " = 1.829
peak= -3.250 closest distance to " O SER A 271 " = 2.056
peak= -3.249 closest distance to " O HOH Z 198 " = 1.783
peak= -3.243 closest distance to " OE1 GLN A 183 " = 1.532
peak= -3.243 closest distance to " CZ TYR A 169 " = 1.790
peak= -3.242 closest distance to " O ASP A 27 " = 1.937
peak= -3.238 closest distance to " CE LYS A 76 " = 2.702
peak= -3.232 closest distance to " CG1 VAL A 125 " = 1.988
peak= -3.224 closest distance to " NH2AARG A 275 " = 5.056
peak= -3.217 closest distance to " O HOH Z 111 " = 1.967
peak= -3.217 closest distance to " O HOH Z 407 " = 2.907
peak= -3.215 closest distance to " O HOH Z 285 " = 2.149
peak= -3.215 closest distance to " O HOH Z 371 " = 2.220
peak= -3.210 closest distance to " O ARG A 145 " = 1.518
peak= -3.208 closest distance to " CB ASP A 132 " = 2.410
peak= -3.202 closest distance to " NE2 GLN A 278 " = 1.773
peak= -3.199 closest distance to " O SER A 276 " = 1.584
peak= -3.197 closest distance to " O HOH Z 359 " = 1.570
peak= -3.196 closest distance to " CB ASP A 231 " = 2.396
peak= -3.196 closest distance to " O HOH Z 346 " = 1.752
peak= -3.194 closest distance to " OE1 GLN A 88 " = 1.047
peak= -3.194 closest distance to " O HOH Z 411 " = 1.412
peak= -3.193 closest distance to " O HOH Z 149 " = 2.198
peak= -3.189 closest distance to " O HOH Z 231 " = 1.450
peak= -3.187 closest distance to " O HOH Z 11 " = 2.184
peak= -3.186 closest distance to " CB GLN A 55 " = 1.259
peak= -3.181 closest distance to " O TRP A 70 " = 1.488
peak= -3.179 closest distance to " CG2 ILE A 151 " = 2.486
peak= -3.176 closest distance to " O HOH Z 166 " = 1.554
peak= -3.174 closest distance to " N HIS A 115 " = 2.178
peak= -3.172 closest distance to " O HOH Z 111 " = 4.386
peak= -3.172 closest distance to " O HOH Z 377 " = 1.000
peak= -3.168 closest distance to " O PRO A 198 " = 1.336
peak= -3.168 closest distance to " C ASN A 285 " = 2.256
peak= -3.163 closest distance to " O SER A 135 " = 1.430
peak= -3.160 closest distance to " O HOH Z 423 " = 2.251
peak= -3.142 closest distance to " CG1 VAL A 197 " = 2.333
peak= -3.141 closest distance to " O GLN A 240 " = 2.479
peak= -3.136 closest distance to " O GLY A 80 " = 2.520
peak= -3.136 closest distance to " NE2 GLN A 88 " = 2.046
peak= -3.133 closest distance to " CB ASN A 39 " = 2.234
peak= -3.133 closest distance to " CB ALA A 291 " = 2.237
peak= -3.131 closest distance to " O GLN A 240 " = 2.105
peak= -3.131 closest distance to " O HOH Z 250 " = 1.668
peak= -3.130 closest distance to " NH2 ARG A 219 " = 1.684
peak= -3.129 closest distance to " CE1 HIS A 81 " = 1.652
peak= -3.129 closest distance to " C LEU A 222 " = 0.910
peak= -3.126 closest distance to " OD1 ASN A 301 " = 1.987
peak= -3.122 closest distance to " CB ALA A 64 " = 2.753
peak= -3.108 closest distance to " CG PHE A 283 " = 2.637
peak= -3.108 closest distance to " CA GLY A 57 " = 2.164
peak= -3.105 closest distance to " O HOH Z 9 " = 3.031
peak= -3.103 closest distance to " CG GLN A 88 " = 0.874
peak= -3.097 closest distance to " O HOH Z 124 " = 3.711
peak= -3.091 closest distance to " O HOH Z 252 " = 3.975
peak= -3.091 closest distance to " O HOH Z 216 " = 1.419
peak= -3.079 closest distance to " OG SER A 245 " = 1.407
peak= -3.075 closest distance to " CG ASP A 231 " = 0.811
peak= -3.072 closest distance to " O GLY A 75 " = 1.839
peak= -3.068 closest distance to " O HOH Z 412 " = 4.093
peak= -3.066 closest distance to " O HOH Z 134 " = 3.585
peak= -3.062 closest distance to " O HOH Z 410 " = 2.204
peak= -3.040 closest distance to " O HOH Z 89 " = 2.804
peak= -3.029 closest distance to " O HOH Z 244 " = 2.017
peak= -3.010 closest distance to " CD2 PHE A 61 " = 2.032
================= overall refinement statistics: step by step =================
****************** REFINEMENT STATISTICS STEP BY STEP ******************
leading digit, like 1_, means number of macro-cycle
0 : statistics at the very beginning when nothing is done yet
1_bss: bulk solvent correction and/or (anisotropic) scaling
1_xyz: refinement of coordinates
1_adp: refinement of ADPs (Atomic Displacement Parameters)
1_occ: refinement of individual occupancies
------------------------------------------------------------------------
R-factors, x-ray target values and norm of gradient of x-ray target
stage r-work r-free xray_target_w xray_target_t
0 : 0.4650 0.4489 6.263870e+00 6.242198e+00
1_bss: 0.4563 0.4374 6.257280e+00 6.230297e+00
1_xyz: 0.3633 0.3801 6.111772e+00 6.134047e+00
1_adp: 0.3126 0.3630 6.001047e+00 6.092274e+00
1_occ: 0.3122 0.3635 5.999972e+00 6.093868e+00
2_bss: 0.3078 0.3581 5.999891e+00 6.091860e+00
2_xyz: 0.2185 0.2681 5.703809e+00 5.865020e+00
2_adp: 0.1992 0.2527 5.626846e+00 5.802918e+00
2_occ: 0.1991 0.2526 5.626927e+00 5.803794e+00
3_bss: 0.1973 0.2520 5.627366e+00 5.803077e+00
3_xyz: 0.1483 0.1956 5.371577e+00 5.583575e+00
3_adp: 0.1350 0.1875 5.301960e+00 5.534403e+00
3_occ: 0.1349 0.1873 5.301358e+00 5.533751e+00
4_bss: 0.1350 0.1872 5.300162e+00 5.531347e+00
4_xyz: 0.1250 0.1754 5.241981e+00 5.478760e+00
4_adp: 0.1230 0.1714 5.225740e+00 5.459288e+00
4_occ: 0.1228 0.1713 5.225284e+00 5.458997e+00
5_bss: 0.1228 0.1712 5.225212e+00 5.458996e+00
5_xyz: 0.1149 0.1620 5.171474e+00 5.417567e+00
5_adp: 0.1139 0.1603 5.162633e+00 5.407144e+00
5_occ: 0.1139 0.1603 5.162463e+00 5.407046e+00
5_bss: 0.1139 0.1602 5.162470e+00 5.407049e+00
------------------------------------------------------------------------
stage k_sol b_sol b11 b22 b33 b12 b13 b23
0 : 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
1_bss: 0.354 18.342 7.088 8.728 10.281 0.000 0.000 0.000
1_xyz: 0.354 18.342 7.088 8.728 10.281 0.000 0.000 0.000
1_adp: 0.354 18.342 7.088 8.728 10.281 0.000 0.000 0.000
1_occ: 0.354 18.342 7.088 8.728 10.281 0.000 0.000 0.000
2_bss: 0.314 20.000 3.658 4.574 6.629 0.000 0.000 0.000
2_xyz: 0.314 20.000 3.658 4.574 6.629 0.000 0.000 0.000
2_adp: 0.314 20.000 3.658 4.574 6.629 0.000 0.000 0.000
2_occ: 0.314 20.000 3.658 4.574 6.629 0.000 0.000 0.000
3_bss: 0.330 43.896 2.150 2.778 4.473 0.000 0.000 0.000
3_xyz: 0.330 43.896 2.150 2.778 4.473 0.000 0.000 0.000
3_adp: 0.330 43.896 2.150 2.778 4.473 0.000 0.000 0.000
3_occ: 0.330 43.896 2.150 2.778 4.473 0.000 0.000 0.000
4_bss: 0.315 43.896 1.991 2.467 4.250 0.000 0.000 0.000
4_xyz: 0.315 43.896 1.991 2.467 4.250 0.000 0.000 0.000
4_adp: 0.315 43.896 1.991 2.467 4.250 0.000 0.000 0.000
4_occ: 0.315 43.896 1.991 2.467 4.250 0.000 0.000 0.000
5_bss: 0.324 49.147 2.109 2.497 4.260 0.000 0.000 0.000
5_xyz: 0.324 49.147 2.109 2.497 4.260 0.000 0.000 0.000
5_adp: 0.324 49.147 2.109 2.497 4.260 0.000 0.000 0.000
5_occ: 0.324 49.147 2.109 2.497 4.260 0.000 0.000 0.000
5_bss: 0.323 52.172 -0.828 -0.478 1.306 -0.000 0.000 0.000
------------------------------------------------------------------------
stage <pher> fom alpha beta
0 : 52.581 0.4890 0.5615 61388.165
1_bss: 52.211 0.4920 0.7320 58673.048
1_xyz: 41.695 0.6213 0.8942 39681.903
1_adp: 38.212 0.6632 0.9838 34712.959
1_occ: 38.314 0.6618 0.9798 34788.747
2_bss: 38.038 0.6649 0.8602 34363.521
2_xyz: 26.692 0.7933 0.9926 18224.784
2_adp: 24.243 0.8196 1.0096 15748.865
2_occ: 24.285 0.8191 1.0090 15764.714
3_bss: 24.230 0.8198 0.9465 15762.751
3_xyz: 18.273 0.8781 0.9858 9582.953
3_adp: 17.133 0.8885 0.9821 8697.179
3_occ: 17.116 0.8887 0.9822 8685.496
4_bss: 17.061 0.8891 0.9739 8627.373
4_xyz: 15.913 0.8991 0.9790 7667.301
4_adp: 15.433 0.9035 0.9748 7387.634
4_occ: 15.427 0.9035 0.9748 7381.046
5_bss: 15.423 0.9035 0.9770 7383.888
5_xyz: 14.570 0.9105 0.9814 6735.739
5_adp: 14.323 0.9127 0.9780 6606.766
5_occ: 14.322 0.9126 0.9780 6601.567
5_bss: 14.322 0.9126 0.9805 6602.363
------------------------------------------------------------------------
stage angl bond chir dihe plan repu geom_target
0 : 24.226 0.414 2.119 33.790 0.145 4.089 5.3647e+01
1_bss: 24.226 0.414 2.119 33.790 0.145 4.089 5.3647e+01
1_xyz: 1.624 0.012 0.104 18.026 0.006 4.108 1.2930e-01
1_adp: 1.624 0.012 0.104 18.026 0.006 4.108 1.2930e-01
1_occ: 1.624 0.012 0.104 18.026 0.006 4.108 1.2930e-01
2_bss: 1.624 0.012 0.104 18.026 0.006 4.108 1.2930e-01
2_xyz: 1.071 0.007 0.077 15.933 0.004 4.121 6.9160e-02
2_adp: 1.071 0.007 0.077 15.933 0.004 4.121 6.9160e-02
2_occ: 1.071 0.007 0.077 15.933 0.004 4.121 6.9160e-02
3_bss: 1.071 0.007 0.077 15.933 0.004 4.121 6.9160e-02
3_xyz: 1.019 0.007 0.078 15.828 0.003 4.124 6.2979e-02
3_adp: 1.019 0.007 0.078 15.828 0.003 4.124 6.2979e-02
3_occ: 1.019 0.007 0.078 15.828 0.003 4.124 6.2979e-02
4_bss: 1.019 0.007 0.078 15.828 0.003 4.124 6.2979e-02
4_xyz: 0.906 0.005 0.070 15.605 0.003 4.126 5.3100e-02
4_adp: 0.906 0.005 0.070 15.605 0.003 4.126 5.3100e-02
4_occ: 0.906 0.005 0.070 15.605 0.003 4.126 5.3100e-02
5_bss: 0.906 0.005 0.070 15.605 0.003 4.126 5.3100e-02
5_xyz: 1.004 0.007 0.077 15.485 0.004 4.110 6.1799e-02
5_adp: 1.004 0.007 0.077 15.485 0.004 4.110 6.1799e-02
5_occ: 1.004 0.007 0.077 15.485 0.004 4.110 6.1799e-02
5_bss: 1.004 0.007 0.077 15.485 0.004 4.110 6.1799e-02
------------------------------------------------------------------------
Maximal deviations:
stage angl bond chir dihe plan repu |grad|
0 : 74.492 1.400 6.404144.062 0.405 1.196 6.9540e+00
1_bss: 74.492 1.400 6.404144.062 0.405 1.196 6.9540e+00
1_xyz: 13.096 0.159 0.393 85.968 0.033 2.162 9.3383e-02
1_adp: 13.096 0.159 0.393 85.968 0.033 2.162 9.3383e-02
1_occ: 13.096 0.159 0.393 85.968 0.033 2.162 9.3383e-02
2_bss: 13.096 0.159 0.393 85.968 0.033 2.162 9.3383e-02
2_xyz: 5.530 0.064 0.243 84.687 0.039 2.328 4.8074e-02
2_adp: 5.530 0.064 0.243 84.687 0.039 2.328 4.8074e-02
2_occ: 5.530 0.064 0.243 84.687 0.039 2.328 4.8074e-02
3_bss: 5.530 0.064 0.243 84.687 0.039 2.328 4.8074e-02
3_xyz: 8.126 0.048 0.365 88.762 0.029 2.300 5.0324e-02
3_adp: 8.126 0.048 0.365 88.762 0.029 2.300 5.0324e-02
3_occ: 8.126 0.048 0.365 88.762 0.029 2.300 5.0324e-02
4_bss: 8.126 0.048 0.365 88.762 0.029 2.300 5.0324e-02
4_xyz: 7.308 0.039 0.263 82.917 0.034 2.382 3.0428e-02
4_adp: 7.308 0.039 0.263 82.917 0.034 2.382 3.0428e-02
4_occ: 7.308 0.039 0.263 82.917 0.034 2.382 3.0428e-02
5_bss: 7.308 0.039 0.263 82.917 0.034 2.382 3.0428e-02
5_xyz: 6.186 0.046 0.306 84.372 0.038 2.316 4.3588e-02
5_adp: 6.186 0.046 0.306 84.372 0.038 2.316 4.3588e-02
5_occ: 6.186 0.046 0.306 84.372 0.038 2.316 4.3588e-02
5_bss: 6.186 0.046 0.306 84.372 0.038 2.316 4.3588e-02
------------------------------------------------------------------------
|-----overall-----|---macromolecule----|------solvent-------|
stage b_max b_min b_ave b_max b_min b_ave b_max b_min b_ave
0 : 10.00 10.00 10.00 10.00 10.00 10.00 10.00 10.00 10.00
1_bss: 19.99 0.01 9.86 19.98 0.01 9.82 19.99 0.06 10.10
1_xyz: 19.99 0.01 9.86 19.98 0.01 9.82 19.99 0.06 10.10
1_adp: 69.00 0.00 12.41 59.96 0.00 9.70 69.00 0.00 27.15
1_occ: 69.00 0.00 12.41 59.96 0.00 9.70 69.00 0.00 27.15
2_bss: 69.00 0.00 12.41 59.96 0.00 9.70 69.00 0.00 27.15
2_xyz: 69.00 0.00 12.41 59.96 0.00 9.70 69.00 0.00 27.15
2_adp: 72.32 0.00 12.26 61.20 0.00 8.80 72.32 0.00 31.07
2_occ: 72.32 0.00 12.26 61.20 0.00 8.80 72.32 0.00 31.07
3_bss: 72.32 0.00 12.26 61.20 0.00 8.80 72.32 0.00 31.07
3_xyz: 72.32 0.00 12.26 61.20 0.00 8.80 72.32 0.00 31.07
3_adp: 85.44 0.00 13.38 82.09 0.00 8.70 85.44 1.01 38.86
3_occ: 85.44 0.00 13.38 82.09 0.00 8.70 85.44 1.01 38.86
4_bss: 85.44 0.00 13.38 82.09 0.00 8.70 85.44 1.01 38.86
4_xyz: 85.44 0.00 13.38 82.09 0.00 8.70 85.44 1.01 38.86
4_adp: 88.98 0.00 13.00 88.98 0.00 8.40 87.74 1.06 38.06
4_occ: 88.98 0.00 13.00 88.98 0.00 8.40 87.74 1.06 38.06
5_bss: 88.98 0.00 13.00 88.98 0.00 8.40 87.74 1.06 38.06
5_xyz: 88.98 0.00 13.00 88.98 0.00 8.40 87.74 1.06 38.06
5_adp: 90.67 0.00 12.73 90.67 0.00 8.20 87.84 1.25 37.40
5_occ: 90.67 0.00 12.73 90.67 0.00 8.20 87.84 1.25 37.40
5_bss: 93.69 3.02 15.75 93.69 3.02 11.22 90.86 4.28 40.42
------------------------------------------------------------------------
stage Deviation of refined
model from start model
max min mean
0 : 0.000 0.000 0.000
1_bss: 0.000 0.000 0.000
1_xyz: 1.265 0.007 0.405
1_adp: 1.265 0.007 0.405
1_occ: 1.265 0.007 0.405
2_bss: 1.265 0.007 0.405
2_xyz: 1.672 0.041 0.537
2_adp: 1.672 0.041 0.537
2_occ: 1.672 0.041 0.537
3_bss: 1.672 0.041 0.537
3_xyz: 1.604 0.032 0.601
3_adp: 1.604 0.032 0.601
3_occ: 1.604 0.032 0.601
4_bss: 1.604 0.032 0.601
4_xyz: 1.685 0.059 0.624
4_adp: 1.685 0.059 0.624
4_occ: 1.685 0.059 0.624
5_bss: 1.685 0.059 0.624
5_xyz: 1.694 0.070 0.643
5_adp: 1.694 0.070 0.643
5_occ: 1.694 0.070 0.643
5_bss: 1.694 0.070 0.643
------------------------------------------------------------------------
CPU time actual refinement: 350.57
============================== Exporting results ==============================
Writing refined structure to PDB file:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/run_404/model_refine_001.pdb
n_use = 2823
n_use_u_iso = 2823
n_use_u_aniso = 0
n_grad_site = 0
n_grad_u_iso = 0
n_grad_u_aniso = 0
n_grad_occupancy = 106
n_grad_fp = 0
n_grad_fdp = 0
n_anisotropic_flag = 0
total number of scatterers = 2823
Writing 2mFobs-DFmodel XPLOR map to file:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/run_404/model_refine_001_2mFobs-DFmodel.map
Writing mFobs-DFmodel XPLOR map to file:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/run_404/model_refine_001_mFobs-DFmodel.map
Writing map coefficients to MTZ file:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/run_404/model_refine_001_map_coeffs.mtz
Writing default parameters for subsequent refinement:
/net/cci-filer1/vol1/tmp/phzwart/tassos/trial/run_404/model_refine_002.def
=============================== Detailed timings ==============================
Pure refinement (no I/O, processing, etc)= 350.42
Macro-tasks:
bulk solvent and scale = 47.67
individual site refinement = 142.42
weights calculation = 32.91
collect and process = 6.55
model show statistics = 0.12
TOTAL for macro-tasks = 229.67
Micro-tasks:
mask = 1.86
f_calc = 106.60
alpha_beta = 8.41
target = 1.17
gradients_wrt_atomic_parameters = 117.48
fmodel = 8.23
r_factors = 0.20
phase_errors = 10.53
foms = 0.30
TOTAL for micro-tasks = 254.78
NUMBER OF MASK CALCS= 4
Time per interpreted Python bytecode instruction: 4.864 micro seconds
Total CPU time: 6.08 minutes
from_scatterers_fft: 671 calls, 106.26 s
gradients_fft: 616 calls, 103.53 s
=========================== phenix.refine: finished ===========================
# Date 2008-01-16 Time 01:28:40 PST -0800 (1200475720.58 s)
Start R-work = 0.4650, R-free = 0.4489 (no bulk solvent and anisotropic scale)
Final R-work = 0.1316, R-free = 0.1770 (no bulk solvent and anisotropic scale)
Start R-work = 0.4563, R-free = 0.4374
Final R-work = 0.1139, R-free = 0.1602
| en |
all-txt-docs | 480896 | MONTHLY WEATHER REVIEW OCTOBER 1934
ment, which, afterward, was found to have an excellent vacuum and to read apparently as a t first; this method of removing air is rarely successful. No. 1019, the errors of which apparently have remained unchanged since it was
purchased, appears to be the best of t,he four barometers and is considered the standarcl of the observatory. Director Patterson states that t,he Newman standard,
imported in 1839 and compared wit8h the standard of the Royal Society at, Somerset House, originally had a cor-
rection of -0.004 inc.h. Whether the British standard
has been changed from that of the. Royal Society is not known, but, in any case, the corwction, now $0.003
inc.h, has not changed more than 0.007 inch in 93 years. The author acknowledges indebtedness to Mr. Arthur
Rotch, of Boston, who kindly contributed the expenses
of travel incidental to t'his work, and to the Instrument Division of the Weather Bureau, and to Director Patter-
son of the Canadian Meteorologicd Office, for providing necessary facilities and assistance. At the time the coniparisons described herein were
completed (early in 1933) no normal or absolute standarcl was in use in America. Since t8hen two iniportitnt, advances in precision barometry have occurred, of which
one is the new primary standard of the National Physicd
Laboratory, England, and the other the const,ruction o
an instrumont at the United State.s Bureau of Standards. News of the latter will be welcomed by American mete- orologists who have hoped for the ma.intenance. of an
absolute standard of pressure in this country. The new British standard is described in a p p e r , A New Primary Standard Barometer, by J. E. Sears and J. S. Clark, in
the Proceedings of the Royal Society, A, vol. 139, 1933
of which the following summary is quoted:
The paper cont,ains an account of a new primary standard
barometer recently installed at the Nnt,ional Physical Laboratory t o serve as a basis of reference for all measurements relating t,o barometric pressures. The body of the instrument is constructed in stainless steel, wit.11
optically flat parallel glass windows through which the mercury surfaces are observed. These windows can be removed, if neces-
sary, for cleaning, and the vacuum can be restored by means of suitable punips whenever the instrument is required for use. The
average temperature of the mercury column is ascertained by means of a mercurial thermometer with a bulb 30 inches long, immersed
in a hole bored in the stainless-steel body parallel to the barometric column.
Two micrometer microscopes are fiT.ecl, one above the other, t o
a massive vertical column which can be translated laterally so as
t o view either the mercury surfaces, or the di\ ihions of a btandard
invar scale set up at the side of the barometer hody. The height of each mercury surface is taken t o be the mean of two microscope
readings, one of the direct image of a horizontal cross wire projected into the space above the mercury, and one of the reflection of this
image in the mercury.
The desiqn and general accuracy of workmanship are such t h a t individual readings should be correct to the order of 0.001 mm. In practice i t is found t h a t the mean residual error of a single
observation is of the order of 0.005 min., this being probably attri- butable in the main t o minute fluctuations of barometric pressure which are continually taking place, even when atmospheric con- ditions are reasonably steady.
The new instruments of the Bureau of Standards are
described briefly in the following estract from a letter recently received from the Director of the Bureau:
I n testing mercurial barometers me are using a Fuess barometer as the standard which had been modified so as t o have an all-
glass cistern. Special methods of filling tlie tube have been developed in which the mercury ib distilled into the tube while under a high vacuum. We have found that tlie vacuum above
the mercury column when so filled holds for a, number of years. This has been checked by intercomparison between 4 Fuess baro- meters, 3 of which are of the modified type. This intercomparison has usually taken place immediately after the refilling of one of the in3trurnents.
In order t o eliminate possible errors due t o the low of vacuum above the mercury column s e have recently constructed a mer- curial barometer in which the vacuum space above the mercury column is connected to a mercury vapor pump and t o a McLeod
gage. It is thus possible t o both control and measure the degree of vacuum. The scale and vernier from one of the Fuess barom- eters is used on this instrument which by comparison with the standard meter bar can be relied on t o about 0.01 mm. We esti- mate the over-all accuracy which will be secured with this new
arrangement t o be f 0.05 mm. of mercury. This accuracy is better than that of any portable barometer which is likely t o be
submitted for test.
METEOROLOGICAL CONDITIONS PRECEDING THUNDERSTORMS ON THE
NATIONAL FORESTS
1. WESTERN AND CENTRAL OREGON
By W. R . STEVENS
[Weather Bureau, Wnshington, D. C ., November 19341
The grea.t n1enac.e of thunderstorms to forested areas
in all the western fire-wen.t,her districts of the Weather Bureau has been emphssize,cl many times by ad1 offizials
connectecl with the fire-weathe,r work n.nd by forest- protection agencies. In t,he region uncler consideration
in this paper (western and c,entrad Oregon), 1ight)ning causes more than one-half of all the forest fires.
It is not apparent to the student of the daily weather map that lightning should be suc.h a great fire-causing factor in tlus region, because few thunderstorms are
observed a t first-order Wea.ther Bureau stations in t,his area. However, a t higher elevations in the national forests of western and central Oregon, thundershornis are
frequent, and occasionally so widespread, with so many cloud to ground flashes, that forest-protection a.gencies are not able to cope with the situation unless they are warned a t least a few hours in advance.
It is the purpose of this paper to discuss thunderstorms, particularly in relation to the national forests of western
and central Oregon, and to present an analysis of the meteorological conditions that ordinarily precede their
occurrence in that region.
CAUSES OF THUNDERSTORMS
The thunderstorni is the result of vigorous vertical
convection of humid air. The thunder and lightning which attend the storm play no part in its mechanism.
When vertical convection of air occurs, the air is said
to be unstable. Instability may be brought about by strong surface heating; by overrunning of one layer of air by another a t a considerably lower temperature; by underrunning and uplift of a saturated layer of air by ti
denser layer; and by forced ascent of humid air masses up mountain slopes. There are two classes of thunclerstorms, (1) the heat
thunderstorm, and (2) the cyclonic thunderstorm. This classification is based upon the cause of the instability
which produces the storms. There are other classifica- tions of thunderstorms, but this one suits best for the present discussion. Conditions are favorable for the genesis of heat thun-
derstorms when the pressure is nearly uniform and slightly below normal over a wide area. When this situation
prevails, the winds are light and the surface air becomes
OCTOBER 1934 MONTHLY WEATHER REVIEW 367
strongly heated, resulting in vigorous vertical convection currents and cumulo-nimbus clouds, provided the decrease of temperature with altitude (lapse rate) exceeds the dry adiabatic rate of 1 C. per 100 meters, and sufficient
water vapor is present to produce raindrops in the rising
air. Genesis of heat thunderstorms is favored by drafts
up the sides of mountain ranges, mountain peaks, and valleys. Storms of this type are very likely to form after
2 or 3 days of unusuully warm weather, when the lower air has become so heated that convection extends to high
nl titudes. Cyclonic thunderstorms may occur in the southeast,
quadrant of a cyclone, in which case the high lapse rate necessary for rapid convection results from the different
directions of the lower and upper air currents. The sur- face air in the southeast quadrant flows from warmer regions, while the currents aloft, which flow more nearly
from the west, are often sficiently colder to induce the convection necessary to the production of thunderstorms.
Cyclonic thunderstorms also occur along the cold
front of a cyclone. Warm tropical winds are associated
with the eastern portion of a cyclone, while cold polar
winds prevail over the western portion. The boundary
between these two systems of winds is usually well
marked, and ir known as a cold front. The cold air advances in the foriii of n wedge. Fiiction a t the surface
of the earth retards the advance of the cold air, while the cold air aloft udvmces unirnpeded. This results in a
wedge with its poirit some distance above the ground. Beneath the overhaiiging front of cold air, warm air is eii-
trapped, which results in strong convectioii, either through the overrunning cold air or out in front of it, ancl the
squally winds that are always associated with the passage
of a cold front.
That thunderstorms do not occur a t times when the pressure distribution appears favorable for their inception
is due to certain factors that are not apparent from sur-
face observations. For instance, the lapse rate may not
be high enough to permit strong convection currents, or there may not be sufficient water vapor present to cause
condensation within the limits of the vertical curren ts
that do form.
I n this study, moisture conditions a t the surface, as in- dicated by the vapor pressure, are used in the discussion
of thunderstorin forecasting. It is true that tempera- ture and moisture conditions aloft are as important, or
more so, as those a t the surface in producing thunder-
storms, but observations of these are not available for the region under consideration.
PRECIPITATION I N THUNDERSTORMS
Rain does not fall con huously during a thunderstorm,
(in fact, none may fall), but generally in very heavy
showers. Everyone is familiar with the fact that rain after almost ceasing may begin again with great violence
after a lightning flash.
Condensation occurs in the ascending current as soon as the temperature of the rising air is reduced to the dew-
point. The raindrops do not fall immediately, but are carried upward. Srnall raindrops fall very slowly through
still air, and can be carried upward by a relatively slow ascending current. Lenard has shown that raindrops
cannot fall through air of normal density whose upward
velocity is greater than 8 meters per second, nor fall
themselves with greater velocity through still air. When raindrops form larger than 5 or 6 millimeters in diameter,
1 Lenard. P., Met. Zeit., 21; 248, 1904.
they are unstable, a.nd imnrediat>ely break up into smaller
drops. The ascending current. in a thunderstorin is not steady,
so that the raindrops intermittently rise a.nd fa.11, alter-
nately breaking up into srnaller drops and coalescing into larger ones. The drops whic.h get to the edge of the
ascending current, or rea.ch the top of the current and
spread out, horizontally, fall to the ground, and produce the heavy rain during t8he early part of the storm.
The occasional occurrence of hail in thunderstorms
is definite proof that axending currents frequently are very violent, and estend t,o high altitudes. The rain-
drops a.re carried upwn.rd into the region of freezing temperature, where they congeal and obtain a coating
of snow. After a time, during a lull in t<he ascending current, they fall to the region of liquid drops where t8hey gather a layer of waber, part of which is frozen by
the low temperat,ure of the kernels. Thus, a hailstone which makes a number o journeys from the rain level
to t,he snow level alternately receives a covering of ice and snow. The sizes of the hailst,ones are roughly pro-
port,ional to the strength of the ascending current,s. Howeyer, since the weight,s of the stones vary approxi-
mately as the cubes of t>heir diameters, while the sup- porting force of the current vtwies approsiniately as the square of bhe dimiet,e,rs of the hailst,ones, n limiting
size is quickly reached. states t t h t . esperiment~ shows that the vertical velocity iiecessrtry to sustain a hailstone 1 inch
in diameter is at least 59 miles per hour, rind 116 miles per hour if the st,one is 3 inches in diameter. Formation of raindrops is essential t,o the occurrence
of lightning. However, it is a common occurrence in
semiarid regions, and less frequently in other sections, to see lightning but no rain reaching the ground. The reason for this phenomenon is that t.he lower air is so
dry that the drops are evaporated before t.hey reach
the earths surface.
Huniphreys
INSTABILITY I N NATIONAL FORESTS OF WESTERN AND
CENTRAL OREGON
The convect)ive processes which produce the majority of thunderstornis in the national f0rest.s of western and
central Oregon are induced by strong surface heating in c.onnection with a trough of low pres.sure which extends in a genernl north-south direckion from Brit<ish
Columbia to nort,hwestern Mesico. The convecbion is
aided by drafts up the niountain slopes, ancl probably at times by overrunning of relatively cool air currents.
Occurrence of t,he cyclonic t,ype of thiinderstorni in
this region is very rare.
DATA
The thunderstorm observations used in this st,udy
(1925-31, inclusive) were very kindly urnished by Dr.
Thornton T. Munger, Director of the Pacific Northwest Forest Experiment Station at Port,land, Oreg. These data have been made the subject of an article by William
G. Morris of that station entitled Lightning Storms and Fires on the National Forests of Oregon and Wash-
ingt>on. A summary of Mr. Morris paper immediately follows this art)icle on page 370.
TYPES OF THUNDERSTORM DAYS
Three types of thunderstorm days have been defined by Mr. Morris. The 10cal~ st8orm clay is one on which
one or a few storms occur that affect only a small area
3 Humphrey& W. J., Physic3 of the Air, second edition, p. 346.
368 MONTHLY WEATHER REVIEW OCTOBER 1934
of the region. The (general1 type either has many
small storms which affect two-thirds of the area, or hfts one or more storms which make a c.ont,inuous trac.k at least two-t,hirds the length of the region. The int,er-
mediate storm day is one on whkh the st,orms are more widespread than on the (local day, but less
extensive t8han on the general day. I n this paper, the terms (int8crmediate and (gen-
eral are replaced by scat,tered and wide-spread , respectively, because they correspond better with fore-
cast terminology. A local storm day caiise,s only one, forest fire, on
the Rverage. Fires started on t,his type of day are, as
R rule, quickly controlled and suppressed wit,liout, anv
extra preparat,ions being niade. For this reason, when
it is obvious from t,he weat,her map or relnt,ionships given in this paper that if any t<hunde,rstornis occ,ur nt,
all they will be sufficient to produce only a local st,orni day, a forecast of thunde,rst,ornis should include :I
modifying term, such as local , to indicabe t80 forest>ry officials t,liat meteorological conditions are not menacing,
but that a few storms are likely to develop. Modifying
terms such as scattered and wide-spread would indicate that st>orms of a more dangerous type, and
to a degree defined by the respective ternis, are, likely to develop.
SEASON OF LIGHTNING FIRE HAZARD
The sea.son of lightning fire hazard begins in w-estern
and centntra.1 Oregon in June and ends in September, n s a
rule. The following table shows the number of thunde,rst,orm
days on the. national forests of this area from June bo September, inclusive, classified with respect to type, for
the 7 years studied.
1 Local 1 Spattered 1 Wide-spread I Total
June ..-.-......--.-.-.-...---.-....---- 38
Julv ________....____....----.--....--.
Au~ust September _.___..._.__......_..--..... 50
lili .-
The season included in this study is the months of J d y
and August, as the above figures indicate that the thun- derstorm situation is most acute during this period.
RELATIONSHIPS
A number of relationships between various meteoro- logical element,s and the occurrence of thunderstorms will
be presented in t>lGs paper and in succee.ding articles trea t-
ing of other nntional forest,s. It, is emphasized thnt t,hese
re,lationships are intended as adjuncts to t,he daily went,her
maps. It is not presumed that bett,e,r forecasts can he,
made, from t,hese relationships alone than t,hose tha.t, nn esperience.d forecnster c,an make who is fa.milia,r w-i t,h
meteorologic.al conditions that ordinarily produce. t,hun-
derstorms in t,he region. However, it is believed that they are valuable aids in thunderstorm forecasting, because they indicate when conditions are relatively safe,
that is, if thunderstorms develop a t all the probability is
great t,hat there will be only a sufficient number to pro- duce a locnl storm day; a.nd when conditions are likely to be dangerous.
It must be borne in mind that only A 7-year period is
included in this study, and therefore the conclusions
reac.hed necessarily are provisional. Use of barometric pressure reduc.ed to sea level ns one
of the factors is obvious, as it has been known for long
time thnt there is a relation between pressure distribution
and thunderst,orm activity. Pressure difTerenc.es between various stations are used
as an indieatmion of t<he north-sout,li trough of low pressure
mentioned above, or the presence of a cyclonic disturbance to the north of the region.
Vapor pressure also is used to indicnte whether moisture conditions are favorable for thunderstorm incept,ion.
METEOROLOGICAL CONDITIONS I N MORNING AND THUNDER-
STORM ACTIVITY SAME DAY
When t,he thunderstorm reports were plotted against
the 8 a. m. E. S. T. pressure a t Senttle, a ra.ther definite
line of demarcation a t 30.05 inches was re,vea,led. When the pre,ssure was above this figure, those thunderstorms
that occurred t,he same. nfte,rnoon and evening were
usually only suffic,ient to prodwe a LLlocd storm dn.y. During the seven July months studied, only three wide-
spread and four (scittt,ered st)orni days occurred when the morning pressure a t Seattle was above 30.05 inches, as
w-as the case on 53 percent of bhe days. Four wide- spre.ad and two scattered storm days occurred during
the August months under this condition, which prevailed
on 50 perc.ent of tthe days. On the other hand, when the pressure was below 30.05 inche.s, the st>orms were more frequent and more dmgerous. On all (s~nttered and I wide-spread storm days thnt
occurred with pressure a.bove 30.05 inches a t Seattle, the
morning pre,ssure a t Roseburg was below 30.10 inc.lies during July, and below 30.12 inches in August.
No wide-spread storm days occurred during July when the Seattle pressure was below 30.05 inches and
t,he Roseburg pressure higher than 29.98 inches. Three
scatt.ered storm days occurred under these circum-
stances out of a total of 44 days. Here again we find a
very sharp line of demarcation. Whenever the pressure
in the morning is below 30.05 inches at Seattle in July and lower than 30 inches a t Roseburg, the day must, be
regarded as potentially dangerous, especially if other nieteorological conditions indicate that thunderst,ornis are
probable (fig. 1).
When the Seattle pressure is below 30.05 inches and the Rosebur pressure higher than 30.02 inches in
scattered or wide-spread storm day occurred under these conditions out of a total of 33 days.
Another important factor in thunderstorm activity which is apparent in August, but shows up to only a
small extent in July is the 24-hour pressure change at
Portland. Any day in August that the pressure is below
30.05 inches at Seattle, below 30.04 inches at Roseburg,
and the pressure at Portland has fallen 0.04 inch or more
in 24 hours must be regarded as dangerous (fig. 3).
During the July months, it was found that when the pressure is below 30.05 inches at Seattle, the vapor pres-
sure ahove 0.35 inch a t Roseburg, and in addition the pres- sure a t Roseburg is not more than 0.08 inch higher than at
Baker, a dangerous situation exjsts. Under these circum- stances many thunderstorm days of the sctittered and
(wide-spread types occur. However, any day that the Seattle pressure is below 30.05 inches and does not meet
the other requirements is relatively safe (fig. 4). Out of n totnl of 50 such cases, there wns only 1 L~vide-spreadl
and 1 scnttered storm day. When the pressure is above 30.05 inches at Seattle, the vapor pressure at Rose- burg and the pressure difference between Roseburg and
Baker seem to have little significance. During August, however, all the wide-spread and scattered storm
August, the lf ay is relatively safe (fig. 2). Not a single
OCTOEHB 1934 MONTHLY WEATHER REVIEW 369
0.04
' 0
-0.04
-0.08
-0.1 2
-DANGEROUS
I
ROSEBURG PRESSURE
SEATTLE PRESSURE BELOW 30.04
40'lb08 -0.04 0 004 0.08 0.12 0.16
SEATTLE PRESSURE MINUS
Rg. 7. KAMLOOPS PRESSURE
&. 2. I
SEAlTLE PRESSURE ABOVE 30.02
0.12
v)
3
z z 0.08
W %
con
E 5 0
==I
5 E 0.04
W W
w w
v)
m
g 3-0.04
w v)
*%08 -0.04 0 0.04 0.08 0.12
JULY SEATTLE PRESSURE MINUS
Rg. 9. KAMLOOPS PRESSURE
SEATTLE PRESSURE ABOVE 30.05 I
n
SEATTLE PRESSURE BELOW 30.05
SEATTLE PRESSURE BELOW 30.04 I SEATTLE PRESSURE ABOVE 30.02
v)
a
5g
W v ) =W
v)
=a con
z g
L s w w dco
Y v)
sg
AWUST SEATTLE PRESSURE MINUS AUGUST SEAlTLE PRESSURE MINUS JULY SEATTLE PRESSURE MINUS
Rg. IO. KAMLOOPS PRESSURE Rg. 11. KAMLOOPS PRESSURE Rg. 12. ROSEBURG PRESSURE
7
SEATTLE PRESSURE BELOW 30.05 I
tn 3
E
=W
n a
W E
;s
P
W
JULY ROSEBURG VAPOR PRESSURE AUGUST ROSEBURG VAPOR PRESSURE AUGUST ROSEBURG VAPOR PRESSURE
e. 4. I m.5. I &. 6.
0.08
0.04
0
-0.08 0 0.04 0.08 0.12 0.16 0.20 0.24
370 MONTHLY WEATHER REVIEW OCTOBEII 1934
days that occurred when the pressure was above 30.05
inches at Seattle came when the vapor pressure was above 0.34 inch at Roseburg, ancl the Roseburg pressure
was from 0.02 to 0.10 inch lower than a t Baker (fig. 5).
I n fact, when such a situation prevails, the probability is strongly in favor of dangerous storms over the area under
consideration. During the same month, when the pres-
sure is below 30.05 inches at Seattle, vapor pressure above
0.35 inch at Roseburg, and the pressure at Roseburg not
more than 0.12 inch higher than Baker, the lightning fire hazard is great. There was a total of 53 cases during
the August months when the pressure was below 30.05
inches at Seattle, but did not meet the other requirements,
and only four scattered and no wide-spread storm
days occurred (fig. 6).
METEOROLOGICAL CONDITIONS IN MORNING AND THUNDER-
STORM ACTIVITY NEXT DAY
Studies of the same character as the foregoing were made
to find relationships between meteorological elements observed at 8 a. m. E. S. T. and the occurrence of thun- derstorms the following day.
The relationships described hereunder for July are
intended for consideration in connection with the weather
maps from June 30 to July 31, inclusive. It was found that dumg July when the pressure is higher than 30.02 inches a t Seattle and the pressure is
higher at Roseburg than at Baker conditions are relatively safe (fig. 7). Out of a total of 98 observations no wide-
spread and only two scattered storm days occurred under these conditions. There is no well defined correla-
tion between these factors and the occurrence of thunder-
storms during August. During July conditions are relatively dangerous (thun-
derstorms occurring in about 50 percent of the cases)
when the morning pressure at Seattle is below 30.04
inches and not more than 0.12 inch higher than a t Kam-
loops, and in addition the pressure at Seattle is higher than a t Roseburg or not more than 0.04 inch lower. On the
other hand relatively safe conditions prevail when the
pressure at Seattle is below 30.04 inches and the other observations do not come within the above classification.
Out of a t,ot,al of 41 such cases, there were 2 wide-spread and 1 scatt,ered storm day (fig. 8).
During the same month, thunderstorms occurred in
about 50 percent of the cases when the pressure a t Seattle
was above 30.02 inches and higher than a t Roseburg, and
in addition the Seattle pressure was not more than 0.08
inch higher than a t Kamloops. Only 1 wide-sprend and 3 scattered storm days occurred out of the 119
days when the pressure at Seattle was above 30.02 inches,
and the other observations did not come within the above classification (fig. 9).
During August conditions are relatively safe when the
pressure a t Seattle is below 30.04 inches and more than
0.14 inch higher than a t Kamloops, or if the Seattle
pressure is either higher or not more than 0.04 inch lower
than a t Roseburg (fig. 10). Forty-five cases came within this classification and only one wide-spread and no
scattered storm days occurred. With pressure higher than 30.02 inches a t Seattle and more than 0.20 inch
higher than a t Kamloops, conditions are relatively safe (fig. 11). One wide-spread and one scattered
storm day occurred under these circumstances out of a
total of 35 observations. There were no wide-spread or scattered storm
days during July out of 57 cases with pressure at Seattle above 30.02 inches and the pressure a t Seattle the same
or lower than at Roseburg (fig. 12). Under these condi- tions during August, 1 wide-spread and 3 scattered storm days occurred out of 47 cases.
CONCLUSION
It is regretted that the record available for study is
short and the conclusions, as mentioned above, must
not be considered as final. However, it is believed that there are sufficient data to justify development of work-
ing hypotheses a t the present time.
LIGHTNING STORMS AND FIRES ON THE NATIONAL FORESTS OF OREGON
AND WASHINGTON
By WILLIAM G. MORRIS
[Paciflc Northwest Forest Experiment Station, Portland, Oreg. Summarized by W. R. Stevens, Weather Bureau, Washington]
Lightning causes more than one-half of all the fires on the national forests of Oregon and Washington, where
an average of 750 fires annually is att,ributed to this one cause. These lightning-caused fires cost hundreds of
thousands of dollars to extinguish; they destroy an enor-
mous amount of timber, imperil entire wnt,ersheds by destroying the cover at the headwaters of important
streams and wreak hea\y damnge in recreat,ional arens of these two States. Unlike man-caused fires, which are potentially pre- ventable, lightning fires can never be prevented. For
lightning fires, the forest protectionist has recourse only to prompt detection and suppression. A single storm may
start so many fires that the prot.ective forces are strained
to the ut.most to reach and extinguish every fire before any attains devastating size. Since, on most nntional
forests of the region, many of the lightning fires are at considerable distances from the areas of everyday man-
caused risk, special steps must be taken to protect the lightning fire zone whenever lightning storms are expected.
The study here reported on was made (1) to discover the fundamental characteristics of lightning storms andthe
fires they start so as to assist in planning the best possible systems of lightning fire control, and (2) to supply some
of the basic information needed for effective lightning
storm forecasting.
BASIC DATA
This study is based on more than 6,000 systematic reports describing lightning storms seen by United Stat,es
Forest, Service fire lookouts in Oregon and Washington during the summer months froin 1925 to 1931, inclusive.
During this period an average of about 200 lookouts have
submitted reports each year. Each report shows the following three points concerning the location nnd move-
ment of nn individual lightning storm: (1) Location of the storm and the time when it wits first seen by the look-
out; (2 ) location of the storm (nnd in many cases the time) when it was nearest the lookout; (3) location and
time when the storm was last seen by the lookout. The territ,ory for which these reports were made includes all of the Cnscade Range from southern Oregon to the
British Columbia boundary, the Coast Range in western
| en |
log-files | 115061 | Log_1 2002-06-26T11:43:51 blc_sa 1.7: Task blc_sa running in SINGLE mode
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Beginning parameters
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter obs_group = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter startLevel = COR
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter endLevel = IMA
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter only_clean = no
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter run_spiskymax = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter run_spiros = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter clobber = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_gain_corr_prpOG = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_gain_corr_inSWG =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_gain_corr_outfile =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_gain_corr_coeffDOL = $ISDC_IC_TREE/ic/spi/cal/spi_coef_cal_0004.fits[1]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_gain_corr_clobber = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter blc_spipoint_rwgroup = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter blc_spipoint_pointing-file = spi/pointings.fits
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_allgti_rogroup =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_allgti_rwgroup = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_allgti_ropointing =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_allgti_rwgti = spi/gti.fits(SPI.-OBS.-GTI.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_allgti_numdet = 85
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_allgti_det_id = 0-84
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spi_allgti_clobber = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spidead_in-og-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spidead_dead-time-dol = spi/dead_time.fits(SPI.-OBS.-DTI.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spidead_out-og-dol = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spidead_swg-index-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spidead_gti-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spidead_clobber = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spidead_chatter = 19
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spidead_deadtimecorrection = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_outfile =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_in-og-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_energy-boundaries-dol = spi/energy_boundaries.fits(SPI.-EBDS-SET.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_out-og-dol = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_swg-index-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_gti-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_deadtime-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_ebounds-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_clobber = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_binfile = none
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_nregions = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_regions = 1165,1180
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_nbins = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_telescope = INTEGRAL
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_instrume = SPI
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_filter =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_bintype = PI
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_chatter = 20
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_clobber = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spibounds_mode = h
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_outfile = hist
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_in-og-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_det-spec-dol = spi/evts_det_spec.fits(SPI.-OBS.-DSP.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_out-og-dol = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_swg-index-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_gti-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_deadtime-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_ebounds-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_clobber = yes
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_dtype = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_psdtype = raw
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_detnums = 0-84
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_multipointing = d
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_tstart = indef
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_tstop = indef
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_instrume = SPI
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_chatter = 20
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spihist_outputformat = ISDC
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_in-og-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_pointing-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_ebounds-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_evts-det-spec-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_gti-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_deadtime-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-mod-idx = spi/back_model_index.fits(SPI.-BMOD-DSP-IDX.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-mod-dol = back_model.fits(SPI.-BMOD-DSP.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_out-og-dol = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-const = YES
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-const-value = 2.0e-5
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-linear = NO
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-linear-mjd0 = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-linear-slope = 0.1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-sincos = NO
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-sincos-mjd0 = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-sincos-period = 0.15
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-sin-amp = 1.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-cos-amp = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-model-gen = NO
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiback_back-model-comp-1 =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_in-og-dol = og_spi.fits[1]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_pointing-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_gti-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_deadtime-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_ebounds-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_evts-det-spec-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_back-model-idx =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_source-cat-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_inst-resp-idx = $ISDC_IC_TREE/ic/spi/rsp/spi_irf_grp_0011.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_out-og-dol = spi/og_spiros.fits(GNRL-OBSG-GRP.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-idx = spi/spiros_image_index.fits(SPI.-SKY.-IMA-IDX.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-int = Y
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-err = Y
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-sig = Y
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_source-res = spi/source_res.fits(SPI.-SRCL-RES.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_source-spec-idx = spi/source_spec_index.fits(SPI.-SRC.-SPE-IDX.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_source-spec =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_back-det-spec-idx = spi/spiros_noise_backgr_index.fits(SPI.-BACK-DSP-IDX.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_back-det-spec =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_source-det-spec-idx = NO
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_source-det-spec =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_reference-coord = RADEC
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-proj = AIT
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-fov = POINTING+FCFOV
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_center-long = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_center-lat = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-dim-long = 81
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-dim-lat = 81
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-pixel-long = 0.2
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-pixel-lat = 0.2
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-orient = STANDARD
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-pole-long = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_image-pole-lat = 90.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_mode = IMAGING
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_nofsources = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter kofsources = POINT
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_sigmathres = 3.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_chilocstep = 0.05
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_srclocprec = 0.01
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_chiwidstep = 0.1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_srcwidprec = 0.1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_srclocbins = SUM
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_background-method = 2
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_iteration-output = Y
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_blur-size = 0.5
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_pixel-func =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_pixel-size = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_constrtype =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_constrmult = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_constrincr = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_constriter = 0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_nagoptions =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_optistat = CHI2
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_solution-constr = NONE
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_maxlikfile = spi/spiros_ml_residues(SPI.-MAXL-RES.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_location-max-error = 0.1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiros_energy-response = N
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_debug = 0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_display = 0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_title = spiskymax v23 processing
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_rogroup = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_rwgroup =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_counts_input_file =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_pointing_input_file =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_ebounds_input_file =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_deadtime-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_background_input_file =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_irf_input_file = $ISDC_IC_TREE/ic/spi/rsp/spi_irf_grp_0011.fits[GROUPING]
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_source-cat-dol =
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_image-idx = spi/skymax_index.fits(SPI.-SKY.-IMA-IDX.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_image-int = skymax_image.fits
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_source-res-dol = spi/spiskymax_sources.fits(SPI.-SRCL-RES.tpl)
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_skymap_system = C
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_image-fov = POINTING+FCFOV
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_center-long = 1.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_center-lat = 2.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_image-pixel-long = 0.5
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_image-pixel-lat = 0.5
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_image-dim-long = 40
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_image-dim-lat = 41
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_chi_0 = -10.
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_chi_1 = +10.
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_d_chi = 0.50
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_psi_0 = -10.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_psi_1 = +10.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_d_psi = 0.50
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_energy_range_min = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_energy_range_max = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_max_iter = 50
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_image_default = 1.0e-3
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_background_scaling_default = 1.0e-0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_background_entropy_factor = 1.0e-0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_background_method = 2
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_memsys_iBayes = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_memsys_iEntropy = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_memsys_fAim = 1.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_n_source_fluxes = 1
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_source_chi_1 = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_source_psi_1 = 0.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_source_ON_radius_1 = 2.00
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_source_OFF_radius_1 = 4.00
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_n_profiles = 0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_profile_chi_0 = 180.0 180.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_profile_chi_1 = 200.0 200.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_profile_d_chi = 1.0 2.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_profile_psi_0 = +2.0 +2.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_profile_psi_1 = +2.0 +2.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Parameter spiskymax_profile_d_psi = 2.0 2.0
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Ending parameters
Log_1 2002-06-26T11:43:51 blc_sa 1.7: Running in normal mode, default parameter prompting
Log_0 2002-06-26T11:43:51 blc_sa 1.7: Attempting to launch GUI for task blc_sa
Log_1 2002-06-26T11:44:10 blc_sa 1.7: Current ISDCLEVL is PRP
Log_0 2002-06-26T11:44:10 blc_sa 1.7: We will step forward in the standard analysis.
Log_0 2002-06-26T11:44:10 blc_sa 1.7: The only_cleaning is set to 0
Log_0 2002-06-26T11:44:10 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/spi_gain_corr prpOG="og_spi.fits[GROUPING]" inSWG="" outfile="" coeffDOL="$ISDC_IC_TREE/ic/spi/cal/spi_coef_cal_0004.fits[1]" clobber="yes" 2>&1
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Task spi_gain_corr running in SINGLE mode
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Beginning parameters
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Parameter prpOG = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Parameter inSWG =
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Parameter outfile =
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Parameter coeffDOL = /isdc/testdata/unit_test/ic_tree/4.5/ic/spi/cal/spi_coef_cal_0004.fits[1]
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Parameter clobber = yes
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Ending parameters
Log_1 2002-06-26T11:44:12 spi_gain_corr 0.8.0: Running in normal mode, default parameter prompting
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: ************************************************************
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: * spi_gain_corr *
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: * -------------------------------------------------------- *
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: * Version : 0.8.0 *
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: * Date : 17-December-2001 *
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: * Authors : Jurgen Knodlseder (CESR) / P.D. & V.B. (ISDC) *
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: * Low energy gain coefficients provided by MPE *
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: * High energy gain coefficients provided by CEA-CE Saclay *
Log_0 2002-06-26T11:44:12 spi_gain_corr 0.8.0: ************************************************************
Log_1 2002-06-26T11:44:14 spi_gain_corr 0.8.0: corrected data --STAMP-- og_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:44:14 spi_gain_corr 0.8.0: 30 SWG found in og_spi.fits[GROUPING]
Log_1 2002-06-26T11:44:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:18 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:21 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:25 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:25 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:25 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:25 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:25 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103100010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:44:27 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:29 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:35 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:35 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:36 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:36 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:37 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:37 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103200010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:44:39 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:41 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:42 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:47 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:49 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:49 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:50 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:50 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:51 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:51 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:52 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:52 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:52 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:52 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103300010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:44:53 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:44:59 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:01 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:02 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:02 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:02 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:03 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103500010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:45:06 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:08 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:12 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:14 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:16 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103600010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:45:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:28 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:31 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103700010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:45:34 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:37 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:40 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:42 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:42 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:42 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:42 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:43 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:44 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:44 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103800010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:45:46 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:48 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:49 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:52 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:55 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:57 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:45:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000103900010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:46:00 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:02 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:03 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:05 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:07 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:07 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:07 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:07 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:08 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104000010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:46:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:12 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:13 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:18 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104100010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:46:21 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:25 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:28 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:31 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104200010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:46:35 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:37 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:41 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:43 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:43 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:43 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:43 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:44 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:46 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:46 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:46 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104300010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:46:47 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:50 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:51 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:54 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:55 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:57 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:59 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:59 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:46:59 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104400010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:47:00 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:03 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:03 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:06 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:08 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:08 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104500010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:47:12 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:14 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:18 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:20 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:20 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:21 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:21 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104600010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:47:25 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:27 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:28 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:31 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:35 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:37 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:37 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:37 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:39 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:40 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:40 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:40 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000104700010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:47:41 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:47 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:50 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:53 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:54 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:54 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:54 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:55 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:57 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:57 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:57 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:47:57 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129100010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:47:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:01 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:02 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:05 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:06 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:07 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:07 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:07 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:08 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129200010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:48:11 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:14 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:20 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:20 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:20 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:21 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129300010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:48:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:26 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:27 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:34 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:34 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:34 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:35 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:35 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129400010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:48:36 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:39 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:42 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:44 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:46 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:47 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:47 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:47 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:47 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129500010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:48:49 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:53 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:55 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:48:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:00 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:00 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:00 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:00 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:02 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:03 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129600010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:49:05 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:08 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:12 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:17 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:18 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:18 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:18 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:18 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:18 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129700010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:49:20 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:27 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:29 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:31 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:32 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129800010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:49:35 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:39 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:40 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:42 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:43 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:44 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:44 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:44 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:45 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:46 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:46 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:46 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000129900010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:49:47 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:49 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:50 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:53 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:55 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:56 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:57 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:49:58 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130000010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:49:59 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:01 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:02 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:03 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:04 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:05 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:05 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:05 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:06 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:06 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:06 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130100010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:50:07 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:08 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:08 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:09 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:10 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130200010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:50:12 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:15 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:16 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:19 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:21 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:22 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:23 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:24 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130700010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T11:50:26 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OSGL-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:29 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OPSD-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:30 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OCRV-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:33 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OME2-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:35 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OME3-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:36 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OME4-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:36 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OME5-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:36 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OMEH-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:37 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OMP3-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OMP4-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OMP5-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OMP6-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/spi/cor/spi_cor_oper.fits[SPI.-OMPH-COR,1,BINTABLE]
Log_1 2002-06-26T11:50:38 spi_gain_corr 0.8.0: corrected data --STAMP-- scw/000130800010/swg_spi.fits[GROUPING,1,BINTABLE]
Log_0 2002-06-26T11:50:38 spi_gain_corr 0.8.0: Task terminated.
Log_1 2002-06-26T11:50:39 spi_gain_corr 0.8.0: Task spi_gain_corr terminating with status 0
Log_0 2002-06-26T11:50:39 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/blc_spipoint rwgroup="og_spi.fits[GROUPING]" pointing-file="spi/pointings.fits" 2>&1
Log_1 2002-06-26T11:50:45 blc_spipoint 2.1: Task blc_spipoint running in SINGLE mode
Log_1 2002-06-26T11:50:45 blc_spipoint 2.1: Beginning parameters
Log_1 2002-06-26T11:50:45 blc_spipoint 2.1: Parameter rwgroup = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:50:45 blc_spipoint 2.1: Parameter pointing-file = spi/pointings.fits
Log_1 2002-06-26T11:50:45 blc_spipoint 2.1: Ending parameters
Log_1 2002-06-26T11:50:45 blc_spipoint 2.1: Running in normal mode, default parameter prompting
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: 30 science window groups in index found
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[0]: 465.912062
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [0]: 465.927213
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[1]: 465.930477
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [1]: 465.945303
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[2]: 465.946877
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [2]: 465.961877
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[3]: 465.981738
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [3]: 465.997132
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[4]: 465.998335
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [4]: 466.014250
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[5]: 466.017085
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [5]: 466.033058
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[6]: 466.036113
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [6]: 466.050997
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[7]: 466.052155
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [7]: 466.067965
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[8]: 466.068856
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [8]: 466.083602
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[9]: 466.084655
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [9]: 466.099863
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[10]: 466.102629
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [10]: 466.118347
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[11]: 466.119458
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [11]: 466.133509
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[12]: 466.134562
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [12]: 466.149041
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[13]: 466.149852
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [13]: 466.164238
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[14]: 466.165187
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [14]: 466.179123
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[15]: 466.180153
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [15]: 466.194805
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[16]: 472.938636
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [16]: 472.952329
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[17]: 472.953509
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [17]: 472.967861
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[18]: 472.970569
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [18]: 472.984331
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[19]: 472.985581
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [19]: 472.999597
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[20]: 473.000558
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [20]: 473.014655
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[21]: 473.015558
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [21]: 473.030222
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[22]: 473.031923
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [22]: 473.048266
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[23]: 473.049285
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [23]: 473.065592
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[24]: 473.068324
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [24]: 473.083324
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[25]: 473.084747
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [25]: 473.105835
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[26]: 473.107178
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [26]: 473.128335
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[27]: 473.130129
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [27]: 473.150963
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[28]: 473.235523
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [28]: 473.249724
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTART[29]: 473.251090
Log_0 2002-06-26T11:50:48 blc_spipoint 2.1: TSTOP [29]: 473.264910
Log_1 2002-06-26T11:50:49 blc_spipoint 2.1: creation of pointing structure --STAMP-- spi/pointings.fits[SPI.-OBS.-PNT,1,BINTABLE]
Log_0 2002-06-26T11:50:49 blc_spipoint 2.1: Created successfully spi/pointings.fits(SPI.-OBS.-PNT.tpl)
Log_0 2002-06-26T11:50:49 blc_spipoint 2.1: Running dal_attach Parent="og_spi.fits[GROUPING]" Child1="spi/pointings.fits[1]" Child2="" Child3="" Child4="" Child5="" 2>&1
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Task dal_attach running in SINGLE mode
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Beginning parameters
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Parameter Parent = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Parameter Child1 = spi/pointings.fits[1]
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Parameter Child2 =
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Parameter Child3 =
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Parameter Child4 =
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Parameter Child5 =
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Ending parameters
Log_1 2002-06-26T11:50:49 dal_attach 1.2.1: Running in normal mode, default parameter prompting
Log_1 2002-06-26T11:50:51 dal_attach 1.2.1: Task dal_attach terminating with status 0
Log_0 2002-06-26T11:50:51 blc_spipoint 2.1: Attached spi/pointings.fits[1] to the OG og_spi.fits[GROUPING]
Log_1 2002-06-26T11:50:51 blc_spipoint 2.1: Reached the end of blc_spipoint. Status 0
Log_1 2002-06-26T11:50:51 blc_spipoint 2.1: Task blc_spipoint terminating with status 0
Log_0 2002-06-26T11:50:51 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/spi_allgti rogroup="" rwgroup="og_spi.fits[GROUPING]" ropointing="" rwgti="spi/gti.fits(SPI.-OBS.-GTI.tpl)" numdet="85" det_id="0-84" clobber="yes" 2>&1
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Task spi_allgti running in SINGLE mode
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Beginning parameters
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Parameter rogroup =
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Parameter rwgroup = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Parameter ropointing =
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Parameter rwgti = spi/gti.fits(SPI.-OBS.-GTI.tpl)
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Parameter numdet = 85
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Parameter det_id = 0-84
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Parameter clobber = yes
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Ending parameters
Log_1 2002-06-26T11:50:51 spi_allgti 1.0: Running in normal mode, default parameter prompting
Log_0 2002-06-26T11:50:51 spi_allgti 1.0: Start calculation of the SPI gti
Log_0 2002-06-26T11:50:53 spi_allgti 1.0: List of 85 detectors:
Log_0 2002-06-26T11:50:53 spi_allgti 1.0: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Log_0 2002-06-26T11:50:53 spi_allgti 1.0: 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
Log_0 2002-06-26T11:50:53 spi_allgti 1.0: 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
Log_0 2002-06-26T11:50:53 spi_allgti 1.0: 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59
Log_0 2002-06-26T11:50:53 spi_allgti 1.0: 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
Log_0 2002-06-26T11:50:53 spi_allgti 1.0: 75 76 77 78 79 80 81 82 83 84
Log_0 2002-06-26T11:50:54 spi_allgti 1.0: Columns added which depend on MAXNUMGTIS (3).
Log_0 2002-06-26T11:51:02 spi_allgti 1.0: Mean ontime for all detectors: 40043.000000
Log_1 2002-06-26T11:51:02 spi_allgti 1.0: creation of GTI structure --STAMP-- spi/gti.fits[SPI.-OBS.-GTI,1,BINTABLE]
Log_0 2002-06-26T11:51:02 spi_allgti 1.0: End of calculation of the SPI gti
Log_1 2002-06-26T11:51:02 spi_allgti 1.0: Task spi_allgti terminating with status 0
Log_0 2002-06-26T11:51:02 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/spidead in-og-dol="" dead-time-dol="spi/dead_time.fits(SPI.-OBS.-DTI.tpl)" out-og-dol="og_spi.fits[GROUPING]" swg-index-dol="" gti-dol="" clobber="yes" chatter="19" deadtimecorrection="0" 2>&1
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Task /isdc/integration/spi_int/sw_rep-linux/bin/spidead running in SINGLE mode
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Beginning parameters
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Parameter in-og-dol =
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Parameter dead-time-dol = spi/dead_time.fits(SPI.-OBS.-DTI.tpl)
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Parameter out-og-dol = og_spi.fits[GROUPING]
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Parameter swg-index-dol =
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Parameter gti-dol =
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Parameter clobber = yes
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Parameter chatter = 19
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Parameter deadtimecorrection = 0
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Ending parameters
Log_1 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Running in normal mode, default parameter prompting
Log_0 2002-06-26T11:51:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Start calculation of the SPI dead times
Log_0 2002-06-26T12:36:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:36:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:36:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:36:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:36:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:36:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:36:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:36:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:36:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:36:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:36:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:37:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:37:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:37:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:37:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:37:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:37:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:37:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:37:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:37:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:37:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:37:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:37:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:37:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:38:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:38:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:38:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:38:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:38:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:38:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:38:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:38:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:38:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:38:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:38:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:38:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:38:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:38:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:39:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:39:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:39:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:39:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:39:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:39:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:39:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:39:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:39:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:39:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:39:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:39:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:39:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:39:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:40:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:40:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:40:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:40:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:40:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:40:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:40:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:40:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:40:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:40:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:40:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:40:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:40:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:40:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:41:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:41:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:41:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:41:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:41:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:41:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:41:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:41:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:41:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:41:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:41:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:41:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:41:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:41:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:42:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:42:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:42:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:42:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:42:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:42:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:42:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:42:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:42:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:42:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:42:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:42:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:42:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:42:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:43:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:43:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:43:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:43:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:43:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:43:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:43:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:43:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:43:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:43:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:43:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:43:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:43:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:43:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:44:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:44:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:44:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:44:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:44:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:44:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:44:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:44:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:44:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:44:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:44:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:44:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:44:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:44:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:45:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:45:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:45:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:45:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:45:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:45:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:45:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:45:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:45:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:45:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:45:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:45:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:45:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:45:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:46:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:46:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:46:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:46:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:46:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:46:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:46:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:46:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:46:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:46:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:46:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:46:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:46:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:46:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:47:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:47:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:47:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:47:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:47:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:47:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:47:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:47:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:47:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:47:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:47:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:47:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:47:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:47:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:48:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:48:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:48:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:48:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:48:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:48:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:48:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:48:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:48:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:48:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:48:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:48:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:48:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:48:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:49:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:49:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:49:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:49:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:49:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:49:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:49:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:49:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:49:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:49:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:49:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:49:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:49:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:49:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:50:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:50:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:50:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:50:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:50:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:50:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:50:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:50:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:50:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:50:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:50:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:50:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:50:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:50:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:51:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:51:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:51:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:51:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:51:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:51:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:51:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:51:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:51:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:51:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:51:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:51:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:51:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:52:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:52:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:52:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:52:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:52:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:52:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:52:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:52:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:52:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:52:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:52:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:52:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:52:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:52:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:53:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:53:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:53:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:53:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:53:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:53:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:53:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:53:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:53:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:53:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:53:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:53:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:53:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:53:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:54:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:54:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:54:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:54:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:54:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:54:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:54:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:54:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:54:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:54:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:54:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:54:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:54:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:54:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:55:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:55:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:55:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:55:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:55:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:55:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:55:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:55:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:55:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:55:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T12:55:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:55:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:55:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:55:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T12:56:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:56:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T12:56:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T12:56:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:56:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:56:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:56:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:56:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:56:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:56:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:56:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:56:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:56:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:56:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:57:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:57:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:57:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:57:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:57:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T12:57:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:57:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:57:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:57:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:57:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:57:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:57:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T12:57:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:57:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:58:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T12:58:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:58:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T12:58:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T12:58:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:58:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:58:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:58:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:58:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:58:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T12:58:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:58:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T12:58:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T12:58:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:59:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:59:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:59:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:59:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:59:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T12:59:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:59:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T12:59:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T12:59:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T12:59:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T12:59:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T12:59:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T12:59:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:00:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:00:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T13:00:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:00:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T13:00:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:00:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:00:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:00:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:00:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:00:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:00:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T13:00:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:00:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T13:00:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:01:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:01:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:01:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T13:01:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:01:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:01:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T13:16:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:16:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:16:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:16:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:16:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:16:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:16:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:16:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:17:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T13:17:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T13:17:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T13:17:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T13:17:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T13:17:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:17:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T13:17:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:17:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T13:17:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:17:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T13:17:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:17:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:17:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:18:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:18:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:18:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:18:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:18:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:18:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:18:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:18:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:18:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:18:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:18:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:18:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:19:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:19:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:19:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:19:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T13:19:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:19:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T13:19:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:19:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:19:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:19:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T13:19:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:19:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T13:19:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:19:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T13:20:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:20:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:20:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:20:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T13:20:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:20:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T13:20:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:20:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:20:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:20:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:20:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:20:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:20:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T13:21:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:21:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:21:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:21:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:21:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:21:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:21:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:21:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T13:21:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:21:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:21:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:21:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:21:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:21:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:22:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:22:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T13:22:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:22:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T13:22:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:22:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T13:22:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T13:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T13:22:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T13:22:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T13:22:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T13:22:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T13:22:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T13:22:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T13:23:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T13:23:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:23:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:23:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T13:23:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T13:23:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:23:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T13:23:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T13:23:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:23:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:23:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T13:23:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:23:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:24:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:24:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:24:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:24:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:24:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:24:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:24:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:24:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:24:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:24:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:24:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:24:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:24:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T13:25:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:25:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:25:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:25:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:25:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T13:25:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:25:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:25:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:25:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:25:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:25:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T13:25:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T13:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T13:26:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T13:26:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:26:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:26:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T13:26:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:26:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T13:26:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T13:26:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T13:26:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T13:26:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T13:26:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:26:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:26:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:26:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:27:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T13:27:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T13:27:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T13:27:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T13:27:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:27:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:27:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:27:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:27:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:27:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T13:27:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T13:27:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T13:27:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T13:27:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:28:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:28:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:28:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:28:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:28:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T13:28:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T13:28:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T13:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T13:28:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:28:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:28:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T13:28:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T13:28:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T13:28:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T13:29:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T15:14:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:14:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:14:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:14:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:14:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:14:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:14:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:14:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T15:14:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T15:14:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T15:14:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T15:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T15:15:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T15:15:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T15:15:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T15:15:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T15:15:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T15:15:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T15:15:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T15:15:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:15:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:15:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:15:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:15:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:15:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:15:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:16:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:16:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:16:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:16:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:16:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:16:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:16:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:16:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:16:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:16:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:16:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T15:16:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:16:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T15:16:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:17:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T15:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:17:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:17:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:17:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T15:17:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:17:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T15:17:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:17:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T15:17:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:17:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:17:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:17:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T15:17:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:18:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T15:18:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:18:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T15:18:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:18:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:18:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:18:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T15:18:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:18:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T15:18:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:18:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T15:18:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:18:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:18:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:19:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T15:19:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:19:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T15:19:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:19:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T15:19:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:19:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T15:19:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:19:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T15:19:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:19:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T15:19:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T15:19:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T15:19:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T15:20:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T15:20:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T15:20:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T15:20:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T15:20:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T15:20:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T15:20:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T15:20:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T15:20:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T15:20:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T15:20:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T15:20:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T15:20:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T15:20:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T15:21:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T15:21:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T15:21:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T15:21:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T15:21:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T15:21:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T15:21:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T15:21:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:21:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:21:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:21:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:21:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:21:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:21:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:22:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:22:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:22:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:22:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:22:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:22:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:22:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:22:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:22:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T15:22:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:22:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:22:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:22:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:22:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T15:23:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:23:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:23:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T15:23:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:23:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T15:23:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T15:23:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T15:23:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T15:23:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T15:23:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:23:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:23:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T15:23:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:23:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T15:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T15:24:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T15:24:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T15:24:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T15:24:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:24:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:24:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T15:24:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:24:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T15:24:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T15:24:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T15:24:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T15:24:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T15:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:25:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:25:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T15:25:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:25:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T15:25:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T15:25:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T15:25:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T15:25:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T15:25:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:25:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:25:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T15:25:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T15:26:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T15:26:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T15:26:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T15:26:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T15:26:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:26:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T15:26:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T15:26:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T15:26:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T15:26:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T16:25:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:25:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:25:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:25:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:26:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:26:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:26:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:26:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T16:26:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T16:26:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T16:26:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T16:26:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T16:26:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T16:26:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T16:26:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T16:26:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T16:26:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T16:27:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T16:27:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T16:27:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:27:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:27:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:27:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:27:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:27:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:27:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:27:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:27:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:27:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:28:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:28:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:28:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:28:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:28:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:28:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:28:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T16:28:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:28:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T16:28:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:28:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T16:28:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:29:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:29:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:29:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T16:29:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:29:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T16:29:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:29:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T16:29:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:29:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:29:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:29:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T16:29:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:30:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T16:30:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:30:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T16:30:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:30:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:30:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:30:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T16:30:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:30:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T16:30:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:30:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T16:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:30:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:31:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:31:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T16:31:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:31:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T16:31:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:31:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T16:31:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:31:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T16:31:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:31:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T16:31:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:31:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T16:31:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T16:32:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T16:32:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T16:32:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T16:32:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T16:32:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T16:32:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T16:32:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T16:32:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T16:32:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T16:32:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T16:32:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T16:32:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T16:33:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T16:33:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T16:33:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T16:33:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T16:33:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T16:33:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T16:33:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T16:33:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T16:33:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T16:33:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T16:33:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T16:33:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:33:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:34:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:34:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:34:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:34:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:34:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:34:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:34:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:34:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:34:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:34:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:34:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:34:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:34:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:35:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T16:35:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:35:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:35:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:35:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:35:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T16:35:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:35:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:35:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T16:35:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:35:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T16:35:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T16:35:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T16:36:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T16:36:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T16:36:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:36:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:36:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T16:36:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:36:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T16:36:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T16:36:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T16:36:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T16:36:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T16:36:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:37:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:37:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T16:37:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:37:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T16:37:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T16:37:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T16:37:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T16:37:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T16:37:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:37:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:37:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T16:37:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:37:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T16:38:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T16:38:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T16:38:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T16:38:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T16:38:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:38:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:38:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T16:38:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:38:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T16:38:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T16:38:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T16:38:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T16:39:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T16:39:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:39:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T16:39:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T16:39:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T16:39:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T16:39:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T18:39:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:39:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:39:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:39:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:39:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:39:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:39:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:39:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T18:39:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T18:40:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T18:40:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T18:40:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T18:40:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T18:40:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T18:40:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T18:40:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T18:40:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T18:40:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T18:40:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T18:40:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:40:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:41:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:41:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:41:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:41:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:41:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:41:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:41:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:41:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:41:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:41:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:41:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:41:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:42:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:42:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:42:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:42:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T18:42:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:42:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T18:42:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:42:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T18:42:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:42:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:42:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:42:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T18:43:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:43:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T18:43:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:43:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T18:43:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:43:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:43:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:43:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T18:43:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:43:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T18:43:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:44:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T18:44:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:44:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:44:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:44:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T18:44:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:44:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T18:44:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:44:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T18:44:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:44:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:44:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:45:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T18:45:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:45:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T18:45:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:45:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T18:45:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:45:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T18:45:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:45:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T18:45:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:45:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T18:45:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T18:46:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T18:46:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T18:46:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T18:46:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T18:46:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T18:46:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T18:46:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T18:46:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T18:46:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T18:46:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T18:46:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T18:46:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T18:47:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T18:47:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T18:47:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T18:47:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T18:47:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T18:47:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T18:47:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T18:47:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T18:47:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T18:47:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T18:47:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T18:47:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:48:03 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:48:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:48:14 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:48:19 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:48:24 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:48:29 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:48:34 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:48:39 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:48:44 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:48:49 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:48:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:48:59 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:49:04 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:49:09 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:49:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 0 of SPI.-OBS.-GTI on P__DF__CAFDT__L0: status -1412
Log_0 2002-06-26T18:49:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:49:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:49:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:49:35 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:49:40 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T18:49:45 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:49:50 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:49:55 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T18:50:00 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:50:05 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T18:50:10 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T18:50:15 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 1 of SPI.-OBS.-GTI on P__DF__CAFDT__L1: status -1412
Log_0 2002-06-26T18:50:20 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 8 of SPI.-OBS.-GTI on P__DF__CAFDT__L8: status -1412
Log_0 2002-06-26T18:50:25 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T18:50:30 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:50:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:50:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T18:50:46 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:50:51 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 9 of SPI.-OBS.-GTI on P__DF__CAFDT__L9: status -1412
Log_0 2002-06-26T18:50:56 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T18:51:01 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 2 of SPI.-OBS.-GTI on P__DF__CAFDT__L2: status -1412
Log_0 2002-06-26T18:51:06 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 10 of SPI.-OBS.-GTI on P__DF__CAFDT__L10: status -1412
Log_0 2002-06-26T18:51:11 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T18:51:16 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:51:21 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:51:26 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T18:51:31 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:51:36 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 11 of SPI.-OBS.-GTI on P__DF__CAFDT__L11: status -1412
Log_0 2002-06-26T18:51:41 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T18:51:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 3 of SPI.-OBS.-GTI on P__DF__CAFDT__L3: status -1412
Log_0 2002-06-26T18:51:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 12 of SPI.-OBS.-GTI on P__DF__CAFDT__L12: status -1412
Log_0 2002-06-26T18:51:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T18:52:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:52:07 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:52:12 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T18:52:17 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:52:22 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 13 of SPI.-OBS.-GTI on P__DF__CAFDT__L13: status -1412
Log_0 2002-06-26T18:52:27 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T18:52:32 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 4 of SPI.-OBS.-GTI on P__DF__CAFDT__L4: status -1412
Log_0 2002-06-26T18:52:37 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 14 of SPI.-OBS.-GTI on P__DF__CAFDT__L14: status -1412
Log_0 2002-06-26T18:52:42 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T18:52:47 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:52:52 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:52:57 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T18:53:02 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:53:08 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 15 of SPI.-OBS.-GTI on P__DF__CAFDT__L15: status -1412
Log_0 2002-06-26T18:53:13 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T18:53:18 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 5 of SPI.-OBS.-GTI on P__DF__CAFDT__L5: status -1412
Log_0 2002-06-26T18:53:23 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 16 of SPI.-OBS.-GTI on P__DF__CAFDT__L16: status -1412
Log_0 2002-06-26T18:53:28 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T18:53:33 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:53:38 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 7 of SPI.-OBS.-GTI on P__DF__CAFDT__L7: status -1412
Log_0 2002-06-26T18:53:43 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T18:53:48 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 6 of SPI.-OBS.-GTI on P__DF__CAFDT__L6: status -1412
Log_0 2002-06-26T18:53:53 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 17 of SPI.-OBS.-GTI on P__DF__CAFDT__L17: status -1412
Log_0 2002-06-26T18:53:58 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: DAL3SPIgetSCHK for detector 18 of SPI.-OBS.-GTI on P__DF__CAFDT__L18: status -1412
Log_0 2002-06-26T19:08:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Mean dead time correction for all detectors: 0.980239 (minimum: 0.890142, maximum 1.000000)
Log_1 2002-06-26T19:08:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: creation of DTI structure --STAMP-- spi/dead_time.fits[SPI.-OBS.-DTI,1,BINTABLE]
Log_0 2002-06-26T19:08:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: End of calculation of the SPI dead times
Log_1 2002-06-26T19:08:54 /isdc/integration/spi_int/sw_rep-linux/bin/spidead 1.6: Task /isdc/integration/spi_int/sw_rep-linux/bin/spidead terminating with status 0
Log_0 2002-06-26T19:08:57 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/spibounds outfile="" in-og-dol="" energy-boundaries-dol="spi/energy_boundaries.fits(SPI.-EBDS-SET.tpl)" out-og-dol="og_spi.fits[GROUPING]" swg-index-dol="" gti-dol="" deadtime-dol="" ebounds-dol="" clobber="yes" binfile="none" nregions="1" regions="1165,1180" nbins="1" telescope="INTEGRAL" instrume="SPI" filter="" bintype="PI" chatter="20" clobber="yes" mode="h" 2>&1
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Task /isdc/integration/spi_int/sw_rep-linux/bin/spibounds running in SINGLE mode
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Beginning parameters
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter outfile =
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter in-og-dol =
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter energy-boundaries-dol = spi/energy_boundaries.fits(SPI.-EBDS-SET.tpl)
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter out-og-dol = og_spi.fits[GROUPING]
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter swg-index-dol =
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter gti-dol =
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter deadtime-dol =
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter ebounds-dol =
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter clobber = yes
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter binfile = none
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter nregions = 1
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter regions = 1165,1180
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter nbins = 1
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter telescope = INTEGRAL
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter instrume = SPI
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter filter =
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter bintype = PI
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter chatter = 20
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter clobber = yes
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Parameter mode = h
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Ending parameters
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Running in normal mode, default parameter prompting
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8:
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: SPIBOUNDS Version 1.0.8
Log_1 2002-06-26T19:09:00 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8:
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8:
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Group: /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/og_spi.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: binfile: NONE
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: nregions: 1
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: region: 1165.000000 - 1180.000000 number of bins: 1
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: telescope: INTEGRAL
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: instrume: SPI
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: filter:
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: chantype: PI
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: chatter: 20
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: clobber: 1
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8:
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Creating Binning File...
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8:
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: ... Using CreateEboundsExt 1.0.0
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: ... Written the extension header keywords
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: ... Successfully written the EBOUNDS extension
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Cleaning up...
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Program executed successfully.
Log_1 2002-06-26T19:09:03 /isdc/integration/spi_int/sw_rep-linux/bin/spibounds 1.0.8: Task /isdc/integration/spi_int/sw_rep-linux/bin/spibounds terminating with status 0
Log_0 2002-06-26T19:09:04 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/spihist outfile="hist" in-og-dol="" det-spec-dol="spi/evts_det_spec.fits(SPI.-OBS.-DSP.tpl)" out-og-dol="og_spi.fits[GROUPING]" swg-index-dol="" gti-dol="" deadtime-dol="" ebounds-dol="" clobber="yes" dtype="1" psdtype="raw" detnums="0-84" multipointing="d" tstart="indef" tstop="indef" instrume="SPI" chatter="20" outputformat="ISDC" 2>&1
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Task /isdc/integration/spi_int/sw_rep-linux/bin/spihist running in SINGLE mode
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Beginning parameters
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter outfile = hist
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter in-og-dol =
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter det-spec-dol = spi/evts_det_spec.fits(SPI.-OBS.-DSP.tpl)
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter out-og-dol = og_spi.fits[GROUPING]
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter swg-index-dol =
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter gti-dol =
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter deadtime-dol =
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter ebounds-dol =
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter clobber = yes
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter dtype = 1
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter psdtype = raw
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter detnums = 0-84
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter multipointing = d
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter tstart = indef
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter tstop = indef
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter instrume = SPI
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter chatter = 20
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Parameter outputformat = ISDC
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Ending parameters
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Running in normal mode, default parameter prompting
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPIHIST Version 2.1.8
Log_1 2002-06-26T19:09:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: tstart: INDEF
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: tstop: INDEF
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: format: ISDC
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: instrumet: SPI
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: clobber: 1
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: chatter: 20
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Verifying input parameters...
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading Binning File...
Log_1 2002-06-26T19:09:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading Pointing Extension...
Log_1 2002-06-26T19:09:11 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading Good Time Extension...
Log_1 2002-06-26T19:09:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (1-1):
Log_1 2002-06-26T19:09:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 465.912479 - 465.927629
Log_1 2002-06-26T19:09:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:09:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:09:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:09:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.912574 465.927541
Log_1 2002-06-26T19:09:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 334097 numGoodEvents: 333960
Log_1 2002-06-26T19:09:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:09:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:09:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:09:34 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.912574 465.927541
Log_1 2002-06-26T19:09:34 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 217536 numGoodEvents: 215236
Log_1 2002-06-26T19:09:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:09:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:09:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:09:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.912574 465.927541
Log_1 2002-06-26T19:09:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 246491 numGoodEvents: 244272
Log_1 2002-06-26T19:09:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:09:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:09:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.912575 465.927541
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 41682 numGoodEvents: 41624
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: ... Using DataExtension 1.0.0
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: ... Written the extension header keywords
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: --STAMP-- spi/evts_det_spec.fits[SPI.-OBS.-DSP,1,BINTABLE]
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (2-2):
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 465.930893 - 465.945720
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:09:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:10:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.930986 465.945634
Log_1 2002-06-26T19:10:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 328384 numGoodEvents: 328262
Log_1 2002-06-26T19:10:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:10:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:10:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:10:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.930986 465.945634
Log_1 2002-06-26T19:10:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 212284 numGoodEvents: 210001
Log_1 2002-06-26T19:10:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:10:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:10:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:10:22 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.930986 465.945634
Log_1 2002-06-26T19:10:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 242005 numGoodEvents: 239838
Log_1 2002-06-26T19:10:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:10:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:10:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:10:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.930987 465.945633
Log_1 2002-06-26T19:10:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 40374 numGoodEvents: 40314
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (3-3):
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 465.947294 - 465.962294
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:10:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:10:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.947389 465.962208
Log_1 2002-06-26T19:10:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 331203 numGoodEvents: 331080
Log_1 2002-06-26T19:10:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:10:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:10:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:10:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.947389 465.962208
Log_1 2002-06-26T19:10:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 214636 numGoodEvents: 212393
Log_1 2002-06-26T19:10:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:10:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:10:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:10:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:11:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.947389 465.962208
Log_1 2002-06-26T19:11:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 244430 numGoodEvents: 242310
Log_1 2002-06-26T19:11:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:11:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:11:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.947390 465.962208
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 40975 numGoodEvents: 40912
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (4-4):
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 465.982155 - 465.997548
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:11:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:11:21 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.982256 465.997461
Log_1 2002-06-26T19:11:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 343899 numGoodEvents: 343771
Log_1 2002-06-26T19:11:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:11:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:11:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:11:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.982256 465.997461
Log_1 2002-06-26T19:11:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 220751 numGoodEvents: 218315
Log_1 2002-06-26T19:11:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:11:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:11:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:11:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.982256 465.997461
Log_1 2002-06-26T19:11:41 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 250986 numGoodEvents: 248814
Log_1 2002-06-26T19:11:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:11:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:11:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:11:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.982257 465.997461
Log_1 2002-06-26T19:11:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 42221 numGoodEvents: 42159
Log_1 2002-06-26T19:11:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (5-5):
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 465.998752 - 466.014666
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:11:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:12:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.998843 466.014578
Log_1 2002-06-26T19:12:14 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 358377 numGoodEvents: 358248
Log_1 2002-06-26T19:12:15 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:12:16 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:16 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:12:16 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:12:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.998843 466.014578
Log_1 2002-06-26T19:12:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 229681 numGoodEvents: 227197
Log_1 2002-06-26T19:12:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:12:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:12:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:12:41 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.998843 466.014578
Log_1 2002-06-26T19:12:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 260168 numGoodEvents: 257776
Log_1 2002-06-26T19:12:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:12:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:12:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:12:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 465.998843 466.014578
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 43732 numGoodEvents: 43674
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (6-6):
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.017502 - 466.033474
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:12:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:13:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.017602 466.033387
Log_1 2002-06-26T19:13:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 359891 numGoodEvents: 359751
Log_1 2002-06-26T19:13:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:13:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:13:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:13:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.017602 466.033387
Log_1 2002-06-26T19:13:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 230018 numGoodEvents: 226733
Log_1 2002-06-26T19:13:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:13:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:13:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:13:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.017602 466.033387
Log_1 2002-06-26T19:13:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 256692 numGoodEvents: 254368
Log_1 2002-06-26T19:13:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:13:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:13:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.017602 466.033387
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 42041 numGoodEvents: 41985
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (7-7):
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.036530 - 466.051414
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:13:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:13:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.036621 466.051324
Log_1 2002-06-26T19:13:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 318497 numGoodEvents: 318373
Log_1 2002-06-26T19:13:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:13:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:13:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:13:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.036621 466.051324
Log_1 2002-06-26T19:13:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 207412 numGoodEvents: 205254
Log_1 2002-06-26T19:13:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:13:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:13:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:13:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:14:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.036621 466.051324
Log_1 2002-06-26T19:14:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 209601 numGoodEvents: 208024
Log_1 2002-06-26T19:14:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:14:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:14:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.036621 466.051324
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 32742 numGoodEvents: 32711
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (8-8):
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.052572 - 466.068382
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:14:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:14:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.052667 466.068295
Log_1 2002-06-26T19:14:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 283759 numGoodEvents: 283666
Log_1 2002-06-26T19:14:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:14:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:14:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:14:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.052667 466.068295
Log_1 2002-06-26T19:14:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 193046 numGoodEvents: 191212
Log_1 2002-06-26T19:14:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:14:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:14:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:14:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.052667 466.068295
Log_1 2002-06-26T19:14:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 194020 numGoodEvents: 192857
Log_1 2002-06-26T19:14:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:14:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:14:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:14:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.052667 466.068293
Log_1 2002-06-26T19:14:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 31168 numGoodEvents: 31137
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (9-9):
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.069273 - 466.084018
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:14:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:15:16 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.069365 466.083930
Log_1 2002-06-26T19:15:17 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 225286 numGoodEvents: 225231
Log_1 2002-06-26T19:15:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:15:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:15:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:15:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.069365 466.083930
Log_1 2002-06-26T19:15:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 158995 numGoodEvents: 157680
Log_1 2002-06-26T19:15:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:15:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:15:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:15:36 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.069365 466.083930
Log_1 2002-06-26T19:15:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 169574 numGoodEvents: 168554
Log_1 2002-06-26T19:15:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:15:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:15:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.069366 466.083930
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 28488 numGoodEvents: 28467
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (10-10):
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.085072 - 466.100280
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:15:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:16:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.085167 466.100188
Log_1 2002-06-26T19:16:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 248221 numGoodEvents: 248144
Log_1 2002-06-26T19:16:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:16:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:16:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:16:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.085167 466.100188
Log_1 2002-06-26T19:16:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 162784 numGoodEvents: 161346
Log_1 2002-06-26T19:16:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:16:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:16:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:16:20 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.085167 466.100188
Log_1 2002-06-26T19:16:21 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 186282 numGoodEvents: 185029
Log_1 2002-06-26T19:16:21 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:16:22 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:22 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:16:22 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:16:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.085168 466.100188
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 32281 numGoodEvents: 32254
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (11-11):
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.103046 - 466.118764
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:16:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:16:41 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.103140 466.118680
Log_1 2002-06-26T19:16:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 346178 numGoodEvents: 346038
Log_1 2002-06-26T19:16:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:16:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:16:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:16:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.103140 466.118679
Log_1 2002-06-26T19:16:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 224224 numGoodEvents: 221795
Log_1 2002-06-26T19:16:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:16:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:16:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:16:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:17:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.103140 466.118679
Log_1 2002-06-26T19:17:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 254234 numGoodEvents: 252034
Log_1 2002-06-26T19:17:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:17:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:17:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.103140 466.118679
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 42844 numGoodEvents: 42805
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (12-12):
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.119875 - 466.133926
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:17:05 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:17:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.119967 466.133837
Log_1 2002-06-26T19:17:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 308625 numGoodEvents: 308504
Log_1 2002-06-26T19:17:34 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:17:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:17:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:17:41 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.119967 466.133837
Log_1 2002-06-26T19:17:41 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 200520 numGoodEvents: 198358
Log_1 2002-06-26T19:17:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:17:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:17:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:17:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:17:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.119967 466.133837
Log_1 2002-06-26T19:18:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 227865 numGoodEvents: 225916
Log_1 2002-06-26T19:18:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:18:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:18:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.119968 466.133837
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 38418 numGoodEvents: 38371
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (13-13):
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.134979 - 466.149458
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:18:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:18:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.135074 466.149370
Log_1 2002-06-26T19:18:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 317221 numGoodEvents: 317108
Log_1 2002-06-26T19:18:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:18:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:18:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:18:39 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.135074 466.149370
Log_1 2002-06-26T19:18:39 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 205820 numGoodEvents: 203599
Log_1 2002-06-26T19:18:39 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:18:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:18:40 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:18:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.135074 466.149370
Log_1 2002-06-26T19:18:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 234413 numGoodEvents: 232347
Log_1 2002-06-26T19:18:58 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:18:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:18:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:18:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.135075 466.149369
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 39503 numGoodEvents: 39458
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (14-14):
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.150268 - 466.164655
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:19:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:19:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.150362 466.164565
Log_1 2002-06-26T19:19:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 318131 numGoodEvents: 317997
Log_1 2002-06-26T19:19:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:19:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:19:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:19:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.150362 466.164565
Log_1 2002-06-26T19:19:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 204733 numGoodEvents: 202509
Log_1 2002-06-26T19:19:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:19:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:19:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:19:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.150362 466.164565
Log_1 2002-06-26T19:19:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 233545 numGoodEvents: 231474
Log_1 2002-06-26T19:19:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:19:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:19:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.150362 466.164564
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 38947 numGoodEvents: 38903
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (15-15):
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.165604 - 466.179539
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:19:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:20:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.165695 466.179448
Log_1 2002-06-26T19:20:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 311091 numGoodEvents: 310957
Log_1 2002-06-26T19:20:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:20:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:20:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:20:34 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.165695 466.179448
Log_1 2002-06-26T19:20:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 198743 numGoodEvents: 196555
Log_1 2002-06-26T19:20:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:20:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:20:35 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:20:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.165695 466.179448
Log_1 2002-06-26T19:20:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 227215 numGoodEvents: 225185
Log_1 2002-06-26T19:20:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:20:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:20:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:20:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.165695 466.179448
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 37943 numGoodEvents: 37891
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (16-16):
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 466.180569 - 466.195222
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:20:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:21:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.180662 466.195134
Log_1 2002-06-26T19:21:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 327027 numGoodEvents: 326895
Log_1 2002-06-26T19:21:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:21:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:21:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:21:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.180662 466.195134
Log_1 2002-06-26T19:21:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 207119 numGoodEvents: 204906
Log_1 2002-06-26T19:21:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:21:34 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:34 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:21:34 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:21:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.180662 466.195133
Log_1 2002-06-26T19:21:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 242138 numGoodEvents: 239988
Log_1 2002-06-26T19:21:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:21:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:21:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:21:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 466.180662 466.195133
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 40764 numGoodEvents: 40712
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (17-17):
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 472.938636 - 472.952329
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:21:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:22:10 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.938737 472.952240
Log_1 2002-06-26T19:22:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 294832 numGoodEvents: 294716
Log_1 2002-06-26T19:22:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:22:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:22:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:22:17 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.938737 472.952240
Log_1 2002-06-26T19:22:17 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 190498 numGoodEvents: 188478
Log_1 2002-06-26T19:22:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:22:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:22:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:22:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.938738 472.952240
Log_1 2002-06-26T19:22:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 218396 numGoodEvents: 216538
Log_1 2002-06-26T19:22:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:22:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:22:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.938738 472.952240
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 36789 numGoodEvents: 36748
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:22:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (18-18):
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 472.953509 - 472.967861
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:22:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:22:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.953604 472.967775
Log_1 2002-06-26T19:22:58 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 309581 numGoodEvents: 309464
Log_1 2002-06-26T19:22:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:23:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:23:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:23:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.953604 472.967775
Log_1 2002-06-26T19:23:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 200315 numGoodEvents: 198167
Log_1 2002-06-26T19:23:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:23:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:23:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:23:22 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.953604 472.967775
Log_1 2002-06-26T19:23:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 228922 numGoodEvents: 227025
Log_1 2002-06-26T19:23:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:23:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:23:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:23:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.953605 472.967775
Log_1 2002-06-26T19:23:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 38541 numGoodEvents: 38491
Log_1 2002-06-26T19:23:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (19-19):
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 472.970569 - 472.984331
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:23:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:23:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.970669 472.984247
Log_1 2002-06-26T19:23:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 297001 numGoodEvents: 296888
Log_1 2002-06-26T19:23:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:23:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:23:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:23:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.970669 472.984247
Log_1 2002-06-26T19:23:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 190642 numGoodEvents: 188692
Log_1 2002-06-26T19:23:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:23:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:23:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:23:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:23:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.970669 472.984247
Log_1 2002-06-26T19:24:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 219144 numGoodEvents: 217179
Log_1 2002-06-26T19:24:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:24:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:24:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.970669 472.984246
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 37037 numGoodEvents: 36991
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:03 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (20-20):
Log_1 2002-06-26T19:24:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 472.985581 - 472.999597
Log_1 2002-06-26T19:24:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:24:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:24:04 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:24:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.985672 472.999513
Log_1 2002-06-26T19:24:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 301604 numGoodEvents: 301503
Log_1 2002-06-26T19:24:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:24:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:24:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:24:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.985672 472.999513
Log_1 2002-06-26T19:24:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 194685 numGoodEvents: 192632
Log_1 2002-06-26T19:24:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:24:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:24:38 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:24:53 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.985672 472.999513
Log_1 2002-06-26T19:24:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 223719 numGoodEvents: 221723
Log_1 2002-06-26T19:24:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:24:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:24:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:24:58 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 472.985673 472.999513
Log_1 2002-06-26T19:24:58 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 37413 numGoodEvents: 37361
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (21-21):
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.000558 - 473.014655
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:24:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:25:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.000651 473.014565
Log_1 2002-06-26T19:25:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 303225 numGoodEvents: 303113
Log_1 2002-06-26T19:25:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:25:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:25:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:25:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.000651 473.014565
Log_1 2002-06-26T19:25:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 195559 numGoodEvents: 193509
Log_1 2002-06-26T19:25:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:25:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:25:33 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:25:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.000652 473.014565
Log_1 2002-06-26T19:25:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 224829 numGoodEvents: 222922
Log_1 2002-06-26T19:25:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:25:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:25:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.000652 473.014564
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 37731 numGoodEvents: 37689
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:25:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (22-22):
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.015558 - 473.030222
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:25:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:26:20 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.015652 473.030135
Log_1 2002-06-26T19:26:22 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 309154 numGoodEvents: 309027
Log_1 2002-06-26T19:26:22 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:26:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:26:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:26:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.015652 473.030135
Log_1 2002-06-26T19:26:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 203429 numGoodEvents: 201255
Log_1 2002-06-26T19:26:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:26:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:26:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:26:46 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.015652 473.030135
Log_1 2002-06-26T19:26:48 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 232567 numGoodEvents: 230572
Log_1 2002-06-26T19:26:48 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:26:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:26:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:26:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.015652 473.030135
Log_1 2002-06-26T19:26:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 38896 numGoodEvents: 38852
Log_1 2002-06-26T19:26:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (23-23):
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.031923 - 473.048266
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:26:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:27:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.032019 473.048176
Log_1 2002-06-26T19:27:09 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 318146 numGoodEvents: 318041
Log_1 2002-06-26T19:27:10 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:27:10 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:10 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:27:10 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:27:15 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.032019 473.048176
Log_1 2002-06-26T19:27:15 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 216554 numGoodEvents: 214353
Log_1 2002-06-26T19:27:16 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:27:16 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:16 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:27:16 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:27:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.032019 473.048176
Log_1 2002-06-26T19:27:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 236319 numGoodEvents: 234563
Log_1 2002-06-26T19:27:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:27:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:27:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:27:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.032019 473.048176
Log_1 2002-06-26T19:27:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 40037 numGoodEvents: 40000
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (24-24):
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.049285 - 473.065592
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:27:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:27:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.049386 473.065505
Log_1 2002-06-26T19:27:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 310297 numGoodEvents: 310190
Log_1 2002-06-26T19:27:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:28:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:28:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:28:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.049386 473.065505
Log_1 2002-06-26T19:28:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 213596 numGoodEvents: 211481
Log_1 2002-06-26T19:28:07 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:28:08 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:08 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:28:08 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:28:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.049386 473.065505
Log_1 2002-06-26T19:28:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 231651 numGoodEvents: 229998
Log_1 2002-06-26T19:28:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:28:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:28:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.049386 473.065505
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 39205 numGoodEvents: 39169
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:29 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (25-25):
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.068324 - 473.083324
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:28:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:28:42 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.068419 473.083238
Log_1 2002-06-26T19:28:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 243290 numGoodEvents: 243215
Log_1 2002-06-26T19:28:43 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:28:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:28:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:28:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.068419 473.083238
Log_1 2002-06-26T19:28:48 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 167912 numGoodEvents: 166489
Log_1 2002-06-26T19:28:48 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:28:48 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:48 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:28:48 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:28:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.068419 473.083238
Log_1 2002-06-26T19:28:56 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 167827 numGoodEvents: 166736
Log_1 2002-06-26T19:28:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:28:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:28:57 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:28:58 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.068419 473.083238
Log_1 2002-06-26T19:28:58 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 27036 numGoodEvents: 27011
Log_1 2002-06-26T19:28:58 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (26-26):
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.084782 - 473.105870
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:28:59 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:29:11 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.084876 473.105783
Log_1 2002-06-26T19:29:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 244507 numGoodEvents: 244463
Log_1 2002-06-26T19:29:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:29:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:29:13 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:29:17 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.084876 473.105783
Log_1 2002-06-26T19:29:17 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 180869 numGoodEvents: 179635
Log_1 2002-06-26T19:29:17 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:29:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:29:18 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:29:25 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.084876 473.105783
Log_1 2002-06-26T19:29:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 172486 numGoodEvents: 171807
Log_1 2002-06-26T19:29:26 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:29:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:29:27 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.084877 473.105783
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 27839 numGoodEvents: 27822
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (27-27):
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.107213 - 473.128370
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:29:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:29:44 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.107308 473.128281
Log_1 2002-06-26T19:29:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 148416 numGoodEvents: 148398
Log_1 2002-06-26T19:29:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:29:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:29:45 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:29:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.107308 473.128281
Log_1 2002-06-26T19:29:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 149507 numGoodEvents: 148639
Log_1 2002-06-26T19:29:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:29:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:29:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:29:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.107308 473.128282
Log_1 2002-06-26T19:30:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 105224 numGoodEvents: 104949
Log_1 2002-06-26T19:30:00 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:01 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.107309 473.128281
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 16045 numGoodEvents: 16043
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (28-28):
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.130164 - 473.150998
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:02 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.130260 473.150912
Log_1 2002-06-26T19:30:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 80373 numGoodEvents: 80366
Log_1 2002-06-26T19:30:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:30:06 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:09 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.130260 473.150912
Log_1 2002-06-26T19:30:09 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 120947 numGoodEvents: 120435
Log_1 2002-06-26T19:30:09 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:09 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:09 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:30:09 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:11 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.130260 473.150912
Log_1 2002-06-26T19:30:11 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 55827 numGoodEvents: 55735
Log_1 2002-06-26T19:30:11 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:11 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:11 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:11 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.130260 473.150911
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 8692 numGoodEvents: 8691
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (29-29):
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.235558 - 473.249759
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:12 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:28 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.235657 473.249672
Log_1 2002-06-26T19:30:30 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 333163 numGoodEvents: 333025
Log_1 2002-06-26T19:30:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:30:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:36 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.235657 473.249672
Log_1 2002-06-26T19:30:36 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 203272 numGoodEvents: 200998
Log_1 2002-06-26T19:30:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:30:37 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:47 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.235657 473.249672
Log_1 2002-06-26T19:30:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 239892 numGoodEvents: 237681
Log_1 2002-06-26T19:30:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.235657 473.249672
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 39742 numGoodEvents: 39691
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Pointing(s) (30-30):
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: 473.251125 - 473.264944
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: OPERATIONAL
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:30:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:31:21 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.251217 473.264857
Log_1 2002-06-26T19:31:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 351750 numGoodEvents: 351575
Log_1 2002-06-26T19:31:23 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:31:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:31:24 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:31:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.251217 473.264857
Log_1 2002-06-26T19:31:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 205184 numGoodEvents: 202899
Log_1 2002-06-26T19:31:31 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:31:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:31:32 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:31:49 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.251217 473.264857
Log_1 2002-06-26T19:31:50 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 245842 numGoodEvents: 243515
Log_1 2002-06-26T19:31:51 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:31:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:31:52 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: time selected: 473.251218 473.264857
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: nEvents: 40182 numGoodEvents: 40131
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing Data...
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: EMERGENCY
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:31:54 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: SPI_mode: DIAGNOSTIC
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 0...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 1...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 2...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8:
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Processing detectors of multiplicity 3...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Reading events...
Alert_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: No events accumulated...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Cleaning up...
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Program executed successfully.
Log_1 2002-06-26T19:31:55 /isdc/integration/spi_int/sw_rep-linux/bin/spihist 2.1.8: Task /isdc/integration/spi_int/sw_rep-linux/bin/spihist terminating with status 0
Log_0 2002-06-26T19:31:57 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/spiback in-og-dol="" pointing-dol="" ebounds-dol="" evts-det-spec-dol="" gti-dol="" deadtime-dol="" back-mod-idx="spi/back_model_index.fits(SPI.-BMOD-DSP-IDX.tpl)" back-mod-dol="back_model.fits(SPI.-BMOD-DSP.tpl)" out-og-dol="og_spi.fits[GROUPING]" back-const="YES" back-const-value="2e-05" back-linear="NO" back-linear-mjd0="0" back-linear-slope="0.1" back-sincos="NO" back-sincos-mjd0="0" back-sincos-period="0.15" back-sin-amp="1" back-cos-amp="0" back-model-gen="NO" back-model-comp-1="" 2>&1
Log_1 2002-06-26T19:32:02 spiback 2.3: Task spiback running in SINGLE mode
Log_1 2002-06-26T19:32:02 spiback 2.3: Beginning parameters
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter in-og-dol =
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter pointing-dol =
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter ebounds-dol =
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter evts-det-spec-dol =
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter gti-dol =
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter deadtime-dol =
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-mod-idx = spi/back_model_index.fits(SPI.-BMOD-DSP-IDX.tpl)
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-mod-dol = back_model.fits(SPI.-BMOD-DSP.tpl)
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter out-og-dol = og_spi.fits[GROUPING]
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-const = YES
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-const-value = 2e-05
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-linear = NO
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-linear-mjd0 = 0
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-linear-slope = 0.1
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-sincos = NO
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-sincos-mjd0 = 0
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-sincos-period = 0.15
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-sin-amp = 1
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-cos-amp = 0
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-model-gen = NO
Log_1 2002-06-26T19:32:02 spiback 2.3: Parameter back-model-comp-1 =
Log_1 2002-06-26T19:32:02 spiback 2.3: Ending parameters
Log_1 2002-06-26T19:32:02 spiback 2.3: Running in normal mode, default parameter prompting
Log_0 2002-06-26T19:32:02 spiback 2.3: Reading input parameters for executable program spiback_main
Log_0 2002-06-26T19:32:02 spiback 2.3: Background has a CONSTANT component with amplitude 0.000020000 cnts/sec/kev/det.
Log_0 2002-06-26T19:32:04 spiback 2.3:
Log_0 2002-06-26T19:32:04 spiback 2.3: <spiback_count_parameters> will read in no of detectors, pointings and energy bins.
Log_0 2002-06-26T19:32:05 spiback 2.3: Count data is for 85 detectors, 30 pointings and 1 energy bins
Log_0 2002-06-26T19:32:05 spiback 2.3: Allocating data arrays for <spiback> in memory.
Log_0 2002-06-26T19:32:05 spiback 2.3: Creating output background response data and its index file
Log_1 2002-06-26T19:32:05 spiback 2.3: Created by subroutine "spiback_output_index" --STAMP-- spi/back_model_index.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T19:32:07 spiback 2.3: Created by subroutine "spiback_output_component" --STAMP-- spi/back_model.fits[SPI.-BMOD-DSP,1,BINTABLE]
Log_0 2002-06-26T19:32:07 spiback 2.3: CONSTANT component 1 has been created and attached to background model index.
Log_0 2002-06-26T19:32:07 spiback 2.3:
Log_0 2002-06-26T19:32:07 spiback 2.3: Exiting SPIBACK
Log_0 2002-06-26T19:32:07 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/spiros in-og-dol="og_spi.fits[1]" pointing-dol="" gti-dol="" deadtime-dol="" ebounds-dol="" evts-det-spec-dol="" out-og-dol="spi/og_spiros.fits(GNRL-OBSG-GRP.tpl)" inst-resp-idx="$ISDC_IC_TREE/ic/spi/rsp/spi_irf_grp_0011.fits[GROUPING]" energy-response="N" back-model-idx="" background-method="2" mode="IMAGING" source-cat-dol="" location-max-error="0.1" optistat="CHI2" solution-constr="NONE" maxlikprec="0.2" nagoptions="" chilocstep="0.05" chiwidstep="0.1" image-idx="spi/spiros_image_index.fits(SPI.-SKY.-IMA-IDX.tpl)" image-int="Y" image-err="Y" image-sig="Y" source-res="spi/source_res.fits(SPI.-SRCL-RES.tpl)" maxlikfile="spi/spiros_ml_residues(SPI.-MAXL-RES.tpl)" reference-coord="RADEC" image-fov="POINTING+FCFOV" center-long="0" center-lat="0" image-dim-long="81" image-dim-lat="81" image-pixel-long="0.2" image-pixel-lat="0.2" image-orient="STANDARD" image-pole-long="0" image-pole-lat="90" image-proj="AIT" blur-size="0.5" kofsources="POINT" nofsources="1" srclocbins="SUM" searchstep="0.5" sigmathres="3" srclocprec="0.01" srcwidprec="0.1" iteration-output="Y" source-relocation="NO" pixel-func="" pixel-size="0" constrtype="" constrmult="0" constrincr="0" constriter="0" source-spec-idx="spi/source_spec_index.fits(SPI.-SRC.-SPE-IDX.tpl)" source-spec="" back-det-spec-idx="spi/spiros_noise_backgr_index.fits(SPI.-BACK-DSP-IDX.tpl)" back-det-spec="" source-det-spec-idx="NO" source-det-spec="" source-timing-mode="QUICKLOOK" source-timing-scale="0" source-timing-idx="cygnus_region_obs_timing_index.fits(SPI.-SRC.-LCR-IDX.tpl)" source-timing="cygnus_region_obs_timing_data.fits" 2>&1
Log_1 2002-06-26T19:32:08 spiros 3.4: Task spiros running in SINGLE mode
Log_1 2002-06-26T19:32:08 spiros 3.4: Beginning parameters
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter in-og-dol = og_spi.fits[1]
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter pointing-dol =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter gti-dol =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter deadtime-dol =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter ebounds-dol =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter evts-det-spec-dol =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter out-og-dol = spi/og_spiros.fits(GNRL-OBSG-GRP.tpl)
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter inst-resp-idx = /isdc/testdata/unit_test/ic_tree/4.5/ic/spi/rsp/spi_irf_grp_0011.fits[GROUPING]
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter energy-response = N
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter back-model-idx =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter background-method = 2
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter mode = IMAGING
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-cat-dol =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter location-max-error = 0.1
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter optistat = CHI2
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter solution-constr = NONE
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter maxlikprec = 0.2
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter nagoptions =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter chilocstep = 0.05
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter chiwidstep = 0.1
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-idx = spi/spiros_image_index.fits(SPI.-SKY.-IMA-IDX.tpl)
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-int = Y
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-err = Y
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-sig = Y
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-res = spi/source_res.fits(SPI.-SRCL-RES.tpl)
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter maxlikfile = spi/spiros_ml_residues(SPI.-MAXL-RES.tpl)
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter reference-coord = RADEC
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-fov = POINTING+FCFOV
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter center-long = 0
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter center-lat = 0
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-dim-long = 81
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-dim-lat = 81
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-pixel-long = 0.2
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-pixel-lat = 0.2
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-orient = STANDARD
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-pole-long = 0
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-pole-lat = 90
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter image-proj = AIT
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter blur-size = 0.5
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter kofsources = POINT
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter nofsources = 1
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter srclocbins = SUM
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter searchstep = 0.5
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter sigmathres = 3
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter srclocprec = 0.01
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter srcwidprec = 0.1
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter iteration-output = Y
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-relocation = NO
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter pixel-func =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter pixel-size = 0
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter constrtype =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter constrmult = 0
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter constrincr = 0
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter constriter = 0
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-spec-idx = spi/source_spec_index.fits(SPI.-SRC.-SPE-IDX.tpl)
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-spec =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter back-det-spec-idx = spi/spiros_noise_backgr_index.fits(SPI.-BACK-DSP-IDX.tpl)
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter back-det-spec =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-det-spec-idx = NO
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-det-spec =
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-timing-mode = QUICKLOOK
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-timing-scale = 0
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-timing-idx = cygnus_region_obs_timing_index.fits(SPI.-SRC.-LCR-IDX.tpl)
Log_1 2002-06-26T19:32:08 spiros 3.4: Parameter source-timing = cygnus_region_obs_timing_data.fits
Log_1 2002-06-26T19:32:08 spiros 3.4: Ending parameters
Log_1 2002-06-26T19:32:08 spiros 3.4: Running in normal mode, default parameter prompting
Log_0 2002-06-26T19:32:08 spiros 3.4:
Log_0 2002-06-26T19:32:08 spiros 3.4: ===================================================================================================
Log_0 2002-06-26T19:32:08 spiros 3.4: <spiros_main> will now initiate all data preprocessing steps required prior to image reconstruction
Log_0 2002-06-26T19:32:08 spiros 3.4: ===================================================================================================
Log_0 2002-06-26T19:32:08 spiros 3.4:
Log_0 2002-06-26T19:32:08 spiros 3.4: --------------------------------------------------------------------
Log_0 2002-06-26T19:32:08 spiros 3.4: Checking for the existence of all observation and catalogue datasets
Log_0 2002-06-26T19:32:08 spiros 3.4: --------------------------------------------------------------------
Log_0 2002-06-26T19:32:08 spiros 3.4: Input observation group dataset "og_spi.fits" has been found.
Log_0 2002-06-26T19:32:08 spiros 3.4: Input instrument response function "/isdc/testdata/unit_test/ic_tree/4.5/ic/spi/rsp/spi_irf_grp_0011.fits" has been found.
Log_0 2002-06-26T19:32:08 spiros 3.4: Output observation group dataset "spi/og_spiros.fits" will be created by ISDC subroutine COMMON_PREPARE_PAR
Log_0 2002-06-26T19:32:08 spiros 3.4:
Log_0 2002-06-26T19:32:08 spiros 3.4: -----------------------------------------------------
Log_0 2002-06-26T19:32:08 spiros 3.4: Reading input parameters common to all analysis modes
Log_0 2002-06-26T19:32:08 spiros 3.4: -----------------------------------------------------
Log_0 2002-06-26T19:32:08 spiros 3.4: SPIROS will be executed in IROS mode.
Log_0 2002-06-26T19:32:08 spiros 3.4: Source imaging and location will be made assuming GAUSSIAN count statistics.
Log_0 2002-06-26T19:32:08 spiros 3.4: Output ML residues file"spi/spiros_ml_residues" will be created with template type SPI.-MAXL-RES
Log_0 2002-06-26T19:32:08 spiros 3.4: Will solve for image or source intensities linearly via a set of simultaneous equations.
Log_0 2002-06-26T19:32:08 spiros 3.4: Background model values will be handled as floating independent values.
Log_0 2002-06-26T19:32:08 spiros 3.4: Only diagonal terms of energy response matrix will be used
Log_0 2002-06-26T19:32:08 spiros 3.4: There are no special options expected for NAG subroutines.
Log_0 2002-06-26T19:32:08 spiros 3.4:
Log_0 2002-06-26T19:32:08 spiros 3.4: --------------------------------------------------
Log_0 2002-06-26T19:32:08 spiros 3.4: Reading input parameters for IMAGING location mode
Log_0 2002-06-26T19:32:08 spiros 3.4: --------------------------------------------------
Log_0 2002-06-26T19:32:08 spiros 3.4: SPIROS will search for POINT sources one by one in IROS mode.
Log_0 2002-06-26T19:32:08 spiros 3.4: Output source catalogue "spi/source_res.fits" will be created with template type SPI.-SRCL-RES
Log_0 2002-06-26T19:32:08 spiros 3.4: Output image archive index "spi/spiros_image_index.fits" will be created with template type SPI.-SKY.-IMA-IDX
Error_1 2002-06-26T19:32:08 spiros 3.4: PIL_get_string(image-obs) : not found
Log_0 2002-06-26T19:32:08 spiros 3.4:
Log_0 2002-06-26T19:32:08 spiros 3.4: -----------------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:08 spiros 3.4: SPIROS will run COMMON_PREPARE_PAR to access observation group datasets and create the imaging output group
Log_0 2002-06-26T19:32:08 spiros 3.4: -----------------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:13 spiros 3.4:
Log_0 2002-06-26T19:32:13 spiros 3.4: Input parameters have been read in and correctly processed
Log_0 2002-06-26T19:32:13 spiros 3.4:
Log_0 2002-06-26T19:32:13 spiros 3.4: ---------------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:13 spiros 3.4: <spiros_main> will read observation and instrument parameters prior to memory allocation for data buffers
Log_0 2002-06-26T19:32:13 spiros 3.4: ---------------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:13 spiros 3.4:
Log_0 2002-06-26T19:32:13 spiros 3.4: <spibham_input_observ_parm> will read in no of detectors, pointings and energy bins.
Alert_1 2002-06-26T19:32:13 spiros 3.4: Source catalogue not specified in the OGDI so will assume there are no known sources
Log_0 2002-06-26T19:32:13 spiros 3.4: Count data is for 85 detectors, 30 pointings, 1 energy bins and 1 background model components
Log_0 2002-06-26T19:32:13 spiros 3.4: Image and pointing coordinate system will be RADEC
Log_0 2002-06-26T19:32:13 spiros 3.4:
Log_0 2002-06-26T19:32:13 spiros 3.4: <spiros_main> configuring IRF control blocks in <DAL3SPIgetDetectorIRF_config>!
Log_0 2002-06-26T19:32:17 spiros 3.4: <DAL3SPIgetDetectorIRF> will allocate 469480500 bytes of memory for all IRF images.
Log_0 2002-06-26T19:32:17 spiros 3.4:
Log_0 2002-06-26T19:32:17 spiros 3.4: --------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_allocate_observation_data> will allocate memory for observation exposure and count buffers
Log_0 2002-06-26T19:32:17 spiros 3.4: --------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_allocate_observation_data> allocating 120 bytes for exposure parameter (P) array <pexp>.
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_allocate_observation_data> allocating 10200 bytes for good time interval (D,P) array <pexp>.
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_allocate_observation_data> allocating 10200 bytes each for count spectrum and variance (D,P,E) arrays <pcnt,pvar,pint>.
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_allocate_observation_data> allocating 10200 bytes each for count spectrum (D,P,E) work arrays <qcnt,rcnt,scnt,tcnt>.
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_allocate_observation_data> allocating 10200 bytes for background component response (D,P,B,E) array <bkgr>.
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_allocate_observation_data> has allocated a total of 91920 bytes for observation count and exposure parameter arrays.
Log_0 2002-06-26T19:32:17 spiros 3.4:
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_imaging_count_data> reading in observation exposure and count data with <spibham_input_observ_data>.
Log_0 2002-06-26T19:32:17 spiros 3.4: Count variance values will be modified with a mean value for low counts using CHI2 optimization
Log_0 2002-06-26T19:32:17 spiros 3.4: Count variance values below 2 have been overwritten with an average value of 0.1000000E+01 in 2 (D,P,E) count bins.
Log_0 2002-06-26T19:32:17 spiros 3.4:
Log_0 2002-06-26T19:32:17 spiros 3.4: <spiros_imaging_count_data> reading in background model component response with <spibham_input_backgr_data>.
Log_0 2002-06-26T19:32:18 spiros 3.4: Observation count spectrum energy range is 1165.0000 to 1180.0000 keV.
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: Image FOV is a 239 by 117 grid of 0.20 by 0.20 degree pixels centred at 8.250, 0.000
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: ------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> will allocate memory for image reconstruction arrays and matrices
Log_0 2002-06-26T19:32:18 spiros 3.4: ------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 600 bytes for source description array <srce> of length 3
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 2175 bytes for source pixel parameter array <spix> of length 87
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 1914 bytes for source spectrum energy bin array <sbin> of length 87
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 696 bytes for NAG gradient vector <Grad>.
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 60552 bytes for each (N,N) NAG Hessian, constraint and work matrix <Hess,Cmat,Wmat>.
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 696 bytes for each NAG solution and bound vector <Alfa,Lbnd,Ubnd>.
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 44544 bytes for NAG double precision work vector <Wvec>.
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 348 bytes for NAG integer work vector <ibuf>.
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 29580 bytes for spectrum pointing response (D,E,N) array <prsp>.
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 20400 bytes for a double precison count accumulation (D,P,E) array <Drsp>.
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> allocating 111852 bytes for each of the image arrays <flux,erro,sgma,mxli> of length 27963
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_allocate_imaging_data> has allocated a total of 731409 bytes in total for image reconstruction arrays and matrices.
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: ----------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:18 spiros 3.4: S P I R O S i m a g i n g a n d e x e c u t i o n t i m e f o r a 1 . 4 G H z C P U
Log_0 2002-06-26T19:32:18 spiros 3.4: ----------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:18 spiros 3.4: Pixel creation time is the sum of the following linear regression components with a Lahey compiler:
Log_0 2002-06-26T19:32:18 spiros 3.4: Image time parameter-1 0.1333513E-06*10*[LOG10(emax)-LOG10(emin)]*nofd*nofp
Log_0 2002-06-26T19:32:18 spiros 3.4: Image time parameter-2 0.7549628E-05*10*[LOG10(emax)-LOG10(emin)]*nofp
Log_0 2002-06-26T19:32:18 spiros 3.4: Image time parameter-3 0.1074232E-04*10*[LOG10(emax)-LOG10(emin)]*nofd
Log_0 2002-06-26T19:32:18 spiros 3.4: Image time parameter-4 0.2006798E-06*nofd*nofp*(nofs+1)
Log_0 2002-06-26T19:32:18 spiros 3.4: Image time parameter-5 0.2575555E-05*nofd*nofp
Log_0 2002-06-26T19:32:18 spiros 3.4: Image time parameter-6 0.6631367E-06*nofs*nofs
Log_0 2002-06-26T19:32:18 spiros 3.4: where
Log_0 2002-06-26T19:32:18 spiros 3.4: nofd = No of detectors
Log_0 2002-06-26T19:32:18 spiros 3.4: nofp = No of pointing exposures
Log_0 2002-06-26T19:32:18 spiros 3.4: nofb = No of background model components
Log_0 2002-06-26T19:32:18 spiros 3.4: nofv = No of detector background values calculated per component (0,1 or nofd)
Log_0 2002-06-26T19:32:18 spiros 3.4: nofs = No of sources to be solved for including background = nofb*nofv + 1
Log_0 2002-06-26T19:32:18 spiros 3.4: emin = Minimum energy (keV)
Log_0 2002-06-26T19:32:18 spiros 3.4: emax = Minimum energy (keV)
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: SPIROS calculates a residue location pixel creation time of about 0.064871 seconds for energy bin 20.000 to 8000.000
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: SPIROS calculates a residue location image creation time of about 3.40 minutes for energy bin 20.000 to 8000.000
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: Pixel creation time is the sum of the following linear regression components with a Lahey compiler:
Log_0 2002-06-26T19:32:18 spiros 3.4: Image time parameter-1 0.1049304E+01*itim*(nofs+1) or (nofs+2) if no of energy bins > 1.
Log_0 2002-06-26T19:32:18 spiros 3.4: Image time parameter-2 0.0000000E+00*ptim*nofs*(nofs+1).
Log_0 2002-06-26T19:32:18 spiros 3.4: where
Log_0 2002-06-26T19:32:18 spiros 3.4: itim = Sum of times above to create an image in each energy bin.
Log_0 2002-06-26T19:32:18 spiros 3.4: ptim = Sum of times above to create a pixel in each energy bin.
Log_0 2002-06-26T19:32:18 spiros 3.4: nofs = Number of sources to be searched for.
Log_0 2002-06-26T19:32:18 spiros 3.4: This implies a total execution time of about 7.14 minutes
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: This estimate of execution time is currently valid when searching for one, two or
Log_0 2002-06-26T19:32:18 spiros 3.4: three sources. If a search is made for more sources this time could be up to 1.5
Log_0 2002-06-26T19:32:18 spiros 3.4: times greater due to the extra time to "float" sources to more precise locations.
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: SPIROS has also allocated 470303829 of memory for internal storage buffers.
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: You should check that this amount of storage is available, either because your
Log_0 2002-06-26T19:32:18 spiros 3.4: computer might not have sufficient memory or is sharing it with other users.
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: If this is so memory may be made available by swapping it to and from disk
Log_0 2002-06-26T19:32:18 spiros 3.4: in which case the above mentioned minutes of execution time may turn into hours!
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: ==========================================================================
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_source_location> will reconstruct sources in each count energy bin
Log_0 2002-06-26T19:32:18 spiros 3.4: ==========================================================================
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_source_location_binwise> will search for a maximum of 1 POINT sources.
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_source_location_binwise> will search for sources above a sigma level of 3.0
Log_0 2002-06-26T19:32:18 spiros 3.4: <spiros_source_location_binwise> will locate sources with a precison of 0.01000 degrees
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: <spibham_append_backgr_model> has appended 1 background sources.
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: Source catalogue not found in OG dataset - assuming no known sources
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: ----------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:18 spiros 3.4: Sources and background will be reconstructed for count spectrum bin-no 1 from 1165.000 to 1180.000 keV.
Log_0 2002-06-26T19:32:18 spiros 3.4: ----------------------------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:18 spiros 3.4:
Log_0 2002-06-26T19:32:18 spiros 3.4: <spibham_source_width_location> will find new source flux values, their locations and any width they might have.
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_source_width_location> finds no sky sources with variable locations.
Log_0 2002-06-26T19:32:20 spiros 3.4:
Log_0 2002-06-26T19:32:20 spiros 3.4: ---------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_source_location_iros> will get count residuals for search iteration-no 1
Log_0 2002-06-26T19:32:20 spiros 3.4: ---------------------------------------------------------------------------------
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will allocate memory for imaging data buffers
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will allocate memory for 2 source data structures
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will allocate memory for 86 source pixel data structures
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will allocate memory for 86 source energy bin data structures
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will allocate memory for 688 bytes of NAG gradient buffer <Grad>
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will allocate memory for 177504 bytes of NAG Hessian matrices <Hess,Cmat,Wmat>
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will allocate memory for 2064 bytes of NAG solution and upper/lower boundary vectors <Alfa,Lbnd,Ubnd>
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will allocate memory for 44376 bytes of NAG work vectors <Wvec,ibuf>
Log_0 2002-06-26T19:32:20 spiros 3.4:
Log_0 2002-06-26T19:32:20 spiros 3.4: <spibham_correlation_imaging> will create a count residue location map and scan it for the most significant source.
Log_0 2002-06-26T19:45:08 spiros 3.4: <spibham_correlation_imaging> has found a new source at [ 0.048 , 0.000 ] with 1816.119 sigma.
Log_0 2002-06-26T19:45:08 spiros 3.4:
Log_0 2002-06-26T19:45:08 spiros 3.4: Sending new image to spi/spiros_image_index.fits
Log_1 2002-06-26T19:45:08 spiros 3.4: Created by subroutine "spibham_output_sky_image_index" --STAMP-- spi/spiros_image_index.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T19:45:08 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_intensity_1.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:45:08 spiros 3.4: Image spi/spiros_image_index_intensity_1.fits has been appended to image catalogue index.
Log_1 2002-06-26T19:45:08 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_error_1.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:45:08 spiros 3.4: Image spi/spiros_image_index_error_1.fits has been appended to image catalogue index.
Log_1 2002-06-26T19:45:09 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_sigma_1.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:45:09 spiros 3.4: Image spi/spiros_image_index_sigma_1.fits has been appended to image catalogue index.
Log_0 2002-06-26T19:45:09 spiros 3.4:
Log_0 2002-06-26T19:45:09 spiros 3.4:
Log_0 2002-06-26T19:45:09 spiros 3.4: <spibham_source_width_location> will find new source flux values, their locations and any width they might have.
Log_0 2002-06-26T19:45:10 spiros 3.4: <spibham_source_width_location> Search Path ML-parameter ML-change X-pos Y-pos Width Minimum-no Location
Log_0 2002-06-26T19:45:10 spiros 3.4: <spibham_source_width_location> 0 0 48561.854 0.000 0.048 0.000 0.000 0 V
Log_0 2002-06-26T19:45:10 spiros 3.4: <spibham_source_location_path>
Log_0 2002-06-26T19:45:14 spiros 3.4: <spibham_source_location_search> 1 1 26494.335 -22067.515 -0.042 -0.003 0.000 1 V
Log_0 2002-06-26T19:45:16 spiros 3.4: <spibham_source_location_search> 1 1 26492.144 -2.191 -0.042 -0.003 0.000 2 V
Log_0 2002-06-26T19:45:16 spiros 3.4: <spibham_source_location_path>
Log_0 2002-06-26T19:45:20 spiros 3.4: <spibham_source_location_search> 1 2 26457.957 -34.187 -0.042 -0.007 0.000 1 V
Log_0 2002-06-26T19:45:20 spiros 3.4: <spibham_source_location_path>
Log_0 2002-06-26T19:45:24 spiros 3.4: <spibham_source_location_search> 1 3 26456.441 -1.526 -0.043 -0.007 0.000 1 V
Log_0 2002-06-26T19:45:24 spiros 3.4: <spibham_source_location_path>
Log_0 2002-06-26T19:45:28 spiros 3.4: <spibham_source_location_search> 1 4 26456.398 -0.043 -0.043 -0.007 0.000 1 V
Log_0 2002-06-26T19:45:28 spiros 3.4:
Log_0 2002-06-26T19:45:28 spiros 3.4: <spibham_output_imaging_sources> has source-no 1 at [ -0.043, -0.007] with flux 0.174188E+01 at 1822.2 sigma with width 0.000 - FLOATING POINT
Log_0 2002-06-26T19:45:28 spiros 3.4:
Log_0 2002-06-26T19:45:28 spiros 3.4: ---------------------------------------------------------------------------------
Log_0 2002-06-26T19:45:28 spiros 3.4: <spibham_source_location_iros> will get count residuals for search iteration-no 2
Log_0 2002-06-26T19:45:28 spiros 3.4: ---------------------------------------------------------------------------------
Log_0 2002-06-26T19:45:28 spiros 3.4: <spibham_correlation_imaging> will create a count residue location map and scan it for the most significant source.
Log_0 2002-06-26T19:58:12 spiros 3.4: SPIROS has reached limit of number of sources requested and will stop searching.
Log_0 2002-06-26T19:58:12 spiros 3.4:
Log_1 2002-06-26T19:58:13 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_intensity_2.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:58:13 spiros 3.4: Image spi/spiros_image_index_intensity_2.fits has been appended to image catalogue index.
Log_1 2002-06-26T19:58:13 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_error_2.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:58:13 spiros 3.4: Image spi/spiros_image_index_error_2.fits has been appended to image catalogue index.
Log_1 2002-06-26T19:58:13 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_sigma_2.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:58:13 spiros 3.4: Image spi/spiros_image_index_sigma_2.fits has been appended to image catalogue index.
Log_0 2002-06-26T19:58:13 spiros 3.4:
Log_0 2002-06-26T19:58:13 spiros 3.4:
Log_0 2002-06-26T19:58:13 spiros 3.4: <spibham_source_width_location> will find new source flux values, their locations and any width they might have.
Log_0 2002-06-26T19:58:14 spiros 3.4: <spibham_source_width_location> Search Path ML-parameter ML-change X-pos Y-pos Width Minimum-no Location
Log_0 2002-06-26T19:58:14 spiros 3.4: <spibham_source_width_location> 0 0 26456.398 0.000 -0.043 -0.007 0.000 0 V
Log_0 2002-06-26T19:58:14 spiros 3.4: <spibham_source_location_path>
Log_0 2002-06-26T19:58:19 spiros 3.4: <spibham_source_location_search> 1 1 26456.280 -0.118 -0.043 -0.007 0.000 1 V
Log_0 2002-06-26T19:58:19 spiros 3.4:
Log_0 2002-06-26T19:58:19 spiros 3.4: <spibham_output_imaging_sources> has source-no 1 at [ -0.043, -0.007] with flux 0.174188E+01 at 1822.2 sigma with width 0.000 - FLOATING POINT
Log_0 2002-06-26T19:58:19 spiros 3.4: There are no more sources to be found.
Log_0 2002-06-26T19:58:19 spiros 3.4:
Log_0 2002-06-26T19:58:19 spiros 3.4: <spiros_imaging_errors> will calculate ROBUST errors in the output solution.
Log_0 2002-06-26T19:58:19 spiros 3.4: <spiros_maxli_imageq_errors> will return LINEAR errors in a Gaussian optimization of source flux values.
Log_0 2002-06-26T19:58:21 spiros 3.4:
Log_0 2002-06-26T19:58:21 spiros 3.4: ===========================================================================
Log_0 2002-06-26T19:58:21 spiros 3.4: <spiros_source_location> will output results of source imaging and location
Log_0 2002-06-26T19:58:21 spiros 3.4: ===========================================================================
Log_0 2002-06-26T19:58:21 spiros 3.4: 1 detector background and 1 sky sources returned.
Log_0 2002-06-26T19:58:21 spiros 3.4: CHI-square parameter is 26456.28 for 2464 DOF and difference of 341.77 stdev.
Log_0 2002-06-26T19:58:21 spiros 3.4:
Log_0 2002-06-26T19:58:21 spiros 3.4: ----------------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:21 spiros 3.4: <spiros_source_location> will output a source catalogue and result images before exiting
Log_0 2002-06-26T19:58:21 spiros 3.4: ----------------------------------------------------------------------------------------
Log_1 2002-06-26T19:58:21 spiros 3.4: Created by subroutine "spibham_output_source_catalogue" --STAMP-- spi/source_res.fits[SPI.-SRCL-RES,1,BINTABLE]
Log_0 2002-06-26T19:58:21 spiros 3.4: Creating output to source catalogue /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/spi/source_res.fits
Log_1 2002-06-26T19:58:22 spiros 3.4: Created by subroutine "spibham_output_source_catadata" --STAMP-- spi/source_res.fits[SPI.-SRCL-RES,1,BINTABLE]
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: <spiros_imaging_output_iros> will output images of final results.
Log_1 2002-06-26T19:58:22 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_intensity_result.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:58:22 spiros 3.4: Image spi/spiros_image_index_intensity_result.fits has been appended to image catalogue index.
Log_1 2002-06-26T19:58:22 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_error_result.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:58:22 spiros 3.4: Image spi/spiros_image_index_error_result.fits has been appended to image catalogue index.
Log_1 2002-06-26T19:58:22 spiros 3.4: Created by subroutine "spibham_output_sky_image" --STAMP-- spi/spiros_image_index_sigma_result.fits[SPI.-SKY.-IMA,1,IMAGE]
Log_0 2002-06-26T19:58:22 spiros 3.4: Image spi/spiros_image_index_sigma_result.fits has been appended to image catalogue index.
Log_1 2002-06-26T19:58:22 spiros 3.4: Created by subroutine "spibham_output_maxli_residues" --STAMP-- spi/spiros_ml_residues.fits[SPI.-MAXL-RES,1,BINTABLE]
Log_0 2002-06-26T19:58:22 spiros 3.4: Creating output to ML residue file /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/spi/spiros_ml_residues.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: ================================================================================
Log_0 2002-06-26T19:58:22 spiros 3.4: = =
Log_0 2002-06-26T19:58:22 spiros 3.4: = Summary of results from SPIROS-3.4 in IROS analysis mode =
Log_0 2002-06-26T19:58:22 spiros 3.4: = =
Log_0 2002-06-26T19:58:22 spiros 3.4: ================================================================================
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: ------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: Observation Group and input datasets
Log_0 2002-06-26T19:58:22 spiros 3.4: ------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Observation Group datasets for input]
Log_0 2002-06-26T19:58:22 spiros 3.4: og_spi.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Pointing data]
Log_0 2002-06-26T19:58:22 spiros 3.4: /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/spi/pointings.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Good time intervals]
Log_0 2002-06-26T19:58:22 spiros 3.4: /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/spi/gti.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Dead time intervals]
Log_0 2002-06-26T19:58:22 spiros 3.4: /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/spi/dead_time.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Count spectra energy bounds]
Log_0 2002-06-26T19:58:22 spiros 3.4: /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/spi/energy_boundaries.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Count spectra]
Log_0 2002-06-26T19:58:22 spiros 3.4: /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/spi/evts_det_spec.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Catalogue of known sources]
Log_0 2002-06-26T19:58:22 spiros 3.4: NOT SPECIFIED
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Background model count response]
Log_0 2002-06-26T19:58:22 spiros 3.4: /unsaved_data/spi_int/long_runs/obs/obs_co_jun26_linux/spi/back_model_index.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Observation Group datasets for output]
Log_0 2002-06-26T19:58:22 spiros 3.4: spi/og_spiros.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: [Instrument response function]
Log_0 2002-06-26T19:58:22 spiros 3.4: /isdc/testdata/unit_test/ic_tree/4.5/ic/spi/rsp/spi_irf_grp_0011.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: ----------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: Miscellaneous parameters from SPIROS execution
Log_0 2002-06-26T19:58:22 spiros 3.4: ----------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Observation count data is for 85 detectors, 30 pointings and 1 energy bins
Log_0 2002-06-26T19:58:22 spiros 3.4: Observation count data energy range is from 1165.000 to 1180.000 keV
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: There is only one background component
Log_0 2002-06-26T19:58:22 spiros 3.4: Background model component-no 1 is CONSTANT
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Source location coordinate system is RADEC
Log_0 2002-06-26T19:58:22 spiros 3.4: There are no catalogue sources
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Area searched is +/- 23.900 by +/- 11.700 degrees, centred on [ 8.250 , 0.000 ]
Log_0 2002-06-26T19:58:22 spiros 3.4: A search was made for a maximum of 1 POINT sources above a sigma level of 3.0
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Analysis using a CHI2 likelihood parameter for positive and negative flux values
Log_0 2002-06-26T19:58:22 spiros 3.4: Estimated execution time was 428 seconds for an actual time of 1574 seconds
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: 1 detector background and 1 sky sources returned.
Log_0 2002-06-26T19:58:22 spiros 3.4: CHI-square parameter is 26456.28 for 2464 DOF and difference of 341.77 stdev.
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: --------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: Sources located in a single energy bin from 1165.0 to 1180.0 keV
Log_0 2002-06-26T19:58:22 spiros 3.4: Sources from catalogue are flagged with "C" and those newly found with "F"
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Source Source-name + origin Flux/error Sigma Location/error Width
Log_0 2002-06-26T19:58:22 spiros 3.4: -no (ph/cm2/sec) (RA-deg) (DEC-deg) (deg)
Log_0 2002-06-26T19:58:22 spiros 3.4: --------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: 1 SOURCE-1 F 1.742 1822.2 -0.043 -0.007 0.000
Log_0 2002-06-26T19:58:22 spiros 3.4: 0.9559E-03 0.001 0.001
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Images for output are indexed and stored in the following files:
Log_0 2002-06-26T19:58:22 spiros 3.4: Index: spi/spiros_image_index.fits
Log_0 2002-06-26T19:58:22 spiros 3.4: Flux : spi/spiros_image_index_intensity-*.fits
Log_0 2002-06-26T19:58:22 spiros 3.4: Error: spi/spiros_image_index_error-*.fits
Log_0 2002-06-26T19:58:22 spiros 3.4: Sigma: spi/spiros_image_index_sigma-*.fits
Log_0 2002-06-26T19:58:22 spiros 3.4: where * is the source search iteration-no 1,2,3,....
Log_0 2002-06-26T19:58:22 spiros 3.4: or "result" for images of final source locations.
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Source output catalogue is stored in the file:
Log_0 2002-06-26T19:58:22 spiros 3.4: spi/source_res.fits
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: --------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: Detector background components and contributions to final CHI2 parameter
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Detector component-1 --------Total--------- Maximum Likelihood parameter
Log_0 2002-06-26T19:58:22 spiros 3.4: -no amplitude Counts/s Counts/s/keV Contribution Expectation
Log_0 2002-06-26T19:58:22 spiros 3.4: --------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: 1 11.77 -0.7265E-01 -0.4843E-02 1022. 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 2 11.77 -0.7438E-01 -0.4959E-02 429.8 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 3 11.78 -0.1621 -0.1080E-01 1834. 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 4 11.77 0.2152E-01 0.1434E-02 788.4 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 5 11.78 -0.5043E-01 -0.3362E-02 1627. 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 6 11.77 0.4449E-02 0.2966E-03 642.2 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 7 11.78 -0.4166E-01 -0.2777E-02 856.3 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 8 11.77 -0.1846E-02 -0.1230E-03 385.8 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 9 11.77 -0.3770E-01 -0.2513E-02 587.5 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 10 11.78 -0.6405E-01 -0.4270E-02 1806. 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 11 11.78 -0.9052E-01 -0.6034E-02 1756. 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 12 11.77 -0.3888E-02 -0.2592E-03 786.8 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 13 11.77 0.5674E-02 0.3783E-03 391.3 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 14 11.78 0.5571E-03 0.3714E-04 519.8 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 15 11.78 -0.6222E-03 -0.4148E-04 1197. 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 16 11.77 -0.3426E-02 -0.2284E-03 1226. 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 17 11.78 0.6600E-02 0.4400E-03 321.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 18 11.78 0.1202E-02 0.8015E-04 923.0 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 19 11.78 -0.8454E-03 -0.5636E-04 591.3 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 20 11.77 -0.1931E-01 -0.1287E-02 167.3 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 21 11.77 -0.1377E-01 -0.9183E-03 134.3 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 22 11.77 -0.9910E-02 -0.6607E-03 105.4 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 23 11.77 -0.7684E-03 -0.5123E-04 148.7 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 24 11.77 0.8530E-02 0.5686E-03 174.7 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 25 11.77 -0.8801E-03 -0.5867E-04 206.5 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 26 11.77 -0.2056E-01 -0.1371E-02 140.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 27 11.77 -0.9372E-02 -0.6248E-03 187.6 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 28 11.77 0.2741E-02 0.1827E-03 143.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 29 11.77 -0.2178E-01 -0.1452E-02 128.2 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 30 11.77 -0.2775E-01 -0.1850E-02 157.7 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 31 11.77 0.2919E-02 0.1946E-03 242.4 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 32 11.77 -0.1041E-01 -0.6943E-03 330.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 33 11.77 -0.2406E-01 -0.1604E-02 253.6 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 34 11.77 -0.2107E-02 -0.1405E-03 135.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 35 11.77 0.1003E-02 0.6687E-04 176.4 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 36 11.77 0.1215E-01 0.8103E-03 64.95 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 37 11.77 -0.1098E-01 -0.7322E-03 147.0 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 38 11.77 0.3038E-02 0.2025E-03 127.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 39 11.77 0.2923E-02 0.1949E-03 98.09 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 40 11.78 -0.4095E-02 -0.2730E-03 167.3 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 41 11.78 -0.4643E-02 -0.3096E-03 279.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 42 11.77 -0.5338E-02 -0.3559E-03 326.2 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 43 11.77 0.4733E-02 0.3155E-03 76.98 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 44 11.77 -0.3018E-02 -0.2012E-03 103.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 45 11.77 0.1075E-02 0.7167E-04 120.5 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 46 11.77 0.2544E-02 0.1696E-03 119.4 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 47 11.77 0.3401E-02 0.2267E-03 140.5 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 48 11.78 0.2318E-03 0.1545E-04 101.3 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 49 11.78 0.2294E-02 0.1529E-03 47.42 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 50 11.77 -0.7614E-02 -0.5076E-03 145.8 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 51 11.77 0.7096E-03 0.4731E-04 178.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 52 11.77 -0.1177E-01 -0.7844E-03 187.8 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 53 11.77 0.1413E-01 0.9417E-03 203.2 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 54 11.77 0.1158E-01 0.7719E-03 162.1 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 55 11.77 -0.1770E-01 -0.1180E-02 105.5 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 56 11.77 -0.1228E-01 -0.8183E-03 151.3 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 57 11.78 0.2047E-02 0.1364E-03 71.00 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 58 11.77 -0.2175E-03 -0.1450E-04 149.6 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 59 11.77 -0.6211E-04 -0.4141E-05 175.2 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 60 11.77 0.1497E-02 0.9978E-04 89.81 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 61 11.78 0.1391E-02 0.9274E-04 54.58 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 62 11.77 -0.1213E-01 -0.8089E-03 113.4 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 63 11.77 -0.9506E-02 -0.6337E-03 109.2 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 64 11.77 -0.5293E-02 -0.3529E-03 132.4 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 65 11.77 -0.3001E-03 -0.2001E-04 53.77 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 66 11.77 -0.5129E-02 -0.3420E-03 154.9 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 67 11.77 -0.3508E-02 -0.2339E-03 86.51 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 68 11.77 -0.8127E-02 -0.5418E-03 87.38 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 69 11.77 -0.1738E-02 -0.1159E-03 58.80 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 70 11.77 -0.6887E-02 -0.4591E-03 133.6 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 71 11.77 -0.1249E-01 -0.8324E-03 103.9 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 72 11.77 -0.9635E-02 -0.6423E-03 78.36 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 73 11.77 -0.5761E-02 -0.3841E-03 81.59 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 74 11.77 -0.1491E-01 -0.9942E-03 53.12 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 75 11.77 -0.3216E-02 -0.2144E-03 62.41 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 76 11.77 -0.8959E-02 -0.5973E-03 85.57 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 77 11.77 -0.5898E-02 -0.3932E-03 83.26 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 78 11.77 0.8955E-04 0.5970E-05 133.9 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 79 11.78 -0.1917E-02 -0.1278E-03 74.51 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 80 11.77 -0.1211E-02 -0.8072E-04 103.5 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 81 11.77 -0.3623E-03 -0.2415E-04 50.69 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 82 11.77 -0.6003E-03 -0.4002E-04 198.0 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 83 11.77 -0.1611E-02 -0.1074E-03 139.0 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 84 11.77 -0.3408E-02 -0.2272E-03 108.0 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4: 85 11.78 -0.1293E-02 -0.8622E-04 55.40 30.00
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: --------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: Contributions to CHI2 parameter, minus expectation value, by science window-no
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: SWG Contribution SWG Contribution SWG Contribution SWG Contribution
Log_0 2002-06-26T19:58:22 spiros 3.4: --------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: 1 426.0 9 436.9 17 265.2 25 1207.0
Log_0 2002-06-26T19:58:22 spiros 3.4: 2 1202.6 10 1894.3 18 377.6 26 2139.4
Log_0 2002-06-26T19:58:22 spiros 3.4: 3 1453.7 11 424.4 19 396.6 27 734.3
Log_0 2002-06-26T19:58:22 spiros 3.4: 4 328.2 12 405.4 20 562.2 28 530.6
Log_0 2002-06-26T19:58:22 spiros 3.4: 5 268.3 13 1026.7 21 849.0 29 2513.2
Log_0 2002-06-26T19:58:22 spiros 3.4: 6 267.7 14 347.1 22 624.5 30 810.3
Log_0 2002-06-26T19:58:22 spiros 3.4: 7 394.1 15 428.9 23 1051.5
Log_0 2002-06-26T19:58:22 spiros 3.4: 8 582.6 16 351.3 24 1606.5
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: --------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: Contributions to CHI2 parameter, minus expectation value, by energy bin
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Bin Contribution Bin Contribution Bin Contribution Bin Contribution
Log_0 2002-06-26T19:58:22 spiros 3.4: --------------------------------------------------------------------------------
Log_0 2002-06-26T19:58:22 spiros 3.4: 1 23906.3
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Details of CHI2 parameter residues for each detector, pointing and energy bin
Log_0 2002-06-26T19:58:22 spiros 3.4: may be found in the file:
Log_0 2002-06-26T19:58:22 spiros 3.4: spi/spiros_ml_residues
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: Execution and imaging time parameters: 26.233 12.733 85 30 1 1 85 1 1165.00 1180.00 239 117 0.200 0.500
Log_0 2002-06-26T19:58:22 spiros 3.4:
Log_0 2002-06-26T19:58:22 spiros 3.4: <spiros_main> exiting after successful execution.
Log_1 2002-06-26T19:58:23 spiros 3.4: Task spiros terminating with status 0
Log_0 2002-06-26T19:58:23 blc_sa 1.7: Running /isdc/integration/spi_int/sw_rep-linux/bin/spiskymax debug="0" display="0" title="spiskymax v23 processing" rogroup="og_spi.fits[GROUPING]" rwgroup="" counts_input_file="" pointing_input_file="" ebounds_input_file="" deadtime-dol="" background_input_file="" irf_input_file="$ISDC_IC_TREE/ic/spi/rsp/spi_irf_grp_0011.fits[GROUPING]" source-cat-dol="" image-idx="spi/skymax_index.fits(SPI.-SKY.-IMA-IDX.tpl)" image-int="skymax_image.fits" source-res-dol="spi/spiskymax_sources.fits(SPI.-SRCL-RES.tpl)" skymap_system="C" image-fov="POINTING+FCFOV" center-long="1" center-lat="2" image-pixel-long="0.5" image-pixel-lat="0.5" image-dim-long="40" image-dim-lat="41" chi_0="-10" chi_1="10" d_chi="0.5" psi_0="-10" psi_1="10" d_psi="0.5" energy_range_min="1" energy_range_max="1" max_iter="50" image_default="0.001" background_scaling_default="1" background_entropy_factor="1" background_method="2" memsys_iBayes="1" memsys_iEntropy="1" memsys_fAim="1" n_source_fluxes="1" source_chi_1="0" source_psi_1="0" source_ON_radius_1="2" source_OFF_radius_1="4" n_profiles="0" profile_chi_0="180.0 180.0" profile_chi_1="200.0 200.0" profile_d_chi=" 1.0 2.0" profile_psi_0=" +2.0 +2.0" profile_psi_1=" +2.0 +2.0" profile_d_psi="2.0 2.0" 2>&1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Task spiskymax running in SINGLE mode
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Beginning parameters
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter debug = 0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter display = 0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter title = spiskymax v23 processing
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter rogroup = og_spi.fits[GROUPING]
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter rwgroup =
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter counts_input_file =
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter pointing_input_file =
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter ebounds_input_file =
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter deadtime-dol =
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter background_input_file =
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter irf_input_file = /isdc/testdata/unit_test/ic_tree/4.5/ic/spi/rsp/spi_irf_grp_0011.fits[GROUPING]
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter source-cat-dol =
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter image-idx = spi/skymax_index.fits(SPI.-SKY.-IMA-IDX.tpl)
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter image-int = skymax_image.fits
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter source-res-dol = spi/spiskymax_sources.fits(SPI.-SRCL-RES.tpl)
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter skymap_system = C
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter image-fov = POINTING+FCFOV
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter center-long = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter center-lat = 2
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter image-pixel-long = 0.5
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter image-pixel-lat = 0.5
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter image-dim-long = 40
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter image-dim-lat = 41
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter chi_0 = -10
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter chi_1 = 10
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter d_chi = 0.5
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter psi_0 = -10
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter psi_1 = 10
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter d_psi = 0.5
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter energy_range_min = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter energy_range_max = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter max_iter = 50
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter image_default = 0.001
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter background_scaling_default = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter background_entropy_factor = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter background_method = 2
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter memsys_iBayes = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter memsys_iEntropy = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter memsys_fAim = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter n_source_fluxes = 1
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter source_chi_1 = 0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter source_psi_1 = 0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter source_ON_radius_1 = 2
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter source_OFF_radius_1 = 4
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter n_profiles = 0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter profile_chi_0 = 180.0 180.0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter profile_chi_1 = 200.0 200.0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter profile_d_chi = 1.0 2.0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter profile_psi_0 = +2.0 +2.0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter profile_psi_1 = +2.0 +2.0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Parameter profile_d_psi = 2.0 2.0
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Ending parameters
Log_1 2002-06-26T19:58:29 spiskymax 23.0: Running in normal mode, default parameter prompting
Log_1 2002-06-26T19:58:34 spiskymax 23.0: CommonPreparePARsStrings status=0
Log_1 2002-06-26T19:58:34 spiskymax 23.0: spiskymax_get_par ends
Log_1 2002-06-26T19:58:34 spiskymax 23.0: >> spiskymax_processing begins
Log_1 2002-06-26T19:58:34 spiskymax 23.0: read_SPI_OBS_DSP begins
Log_1 2002-06-26T19:58:34 spiskymax 23.0: read_SPI_OBS_DSP ends
Log_1 2002-06-26T19:58:34 spiskymax 23.0: DALobjectFindElement status=0
Log_1 2002-06-26T19:58:34 spiskymax 23.0: DAL3GENindexGetNumMembers status=0
Log_1 2002-06-26T19:58:34 spiskymax 23.0: DAL3GENindexGetNumMembers NumMembers=1
Log_1 2002-06-26T19:58:34 spiskymax 23.0: DAL3GENindexGetMember status=0
Log_1 2002-06-26T19:58:34 spiskymax 23.0: image_definition begins
Log_1 2002-06-26T19:58:34 spiskymax 23.0: image_definition:POINTING+FCFOV
Log_1 2002-06-26T19:58:34 spiskymax 23.0: image_definition ends
Log_1 2002-06-26T19:58:47 spiskymax 23.0: +++++++++ memsys5 analysis for energy range #1 +++++++++++++++
Log_1 2002-06-26T19:58:47 spiskymax 23.0: Iteration 1
Log_1 2002-06-26T19:58:51 spiskymax 23.0: Iteration 2
Log_1 2002-06-26T19:58:57 spiskymax 23.0: Iteration 3
Log_1 2002-06-26T19:59:03 spiskymax 23.0: Iteration 4
Log_1 2002-06-26T19:59:09 spiskymax 23.0: Iteration 5
Log_1 2002-06-26T19:59:16 spiskymax 23.0: Iteration 6
Log_1 2002-06-26T19:59:22 spiskymax 23.0: Iteration 7
Log_1 2002-06-26T19:59:28 spiskymax 23.0: Iteration 8
Log_1 2002-06-26T19:59:34 spiskymax 23.0: Iteration 9
Log_1 2002-06-26T19:59:40 spiskymax 23.0: Iteration 10
Log_1 2002-06-26T19:59:47 spiskymax 23.0: Iteration 11
Log_1 2002-06-26T19:59:53 spiskymax 23.0: Iteration 12
Log_1 2002-06-26T19:59:59 spiskymax 23.0: Iteration 13
Log_1 2002-06-26T20:00:05 spiskymax 23.0: Iteration 14
Log_1 2002-06-26T20:00:11 spiskymax 23.0: Iteration 15
Log_1 2002-06-26T20:00:16 spiskymax 23.0: Iteration 16
Log_1 2002-06-26T20:00:22 spiskymax 23.0: Iteration 17
Log_1 2002-06-26T20:00:27 spiskymax 23.0: Iteration 18
Log_1 2002-06-26T20:00:33 spiskymax 23.0: Iteration 19
Log_1 2002-06-26T20:00:39 spiskymax 23.0: Iteration 20
Log_1 2002-06-26T20:00:44 spiskymax 23.0: Iteration 21
Log_1 2002-06-26T20:00:50 spiskymax 23.0: Iteration 22
Log_1 2002-06-26T20:00:55 spiskymax 23.0: Iteration 23
Log_1 2002-06-26T20:01:01 spiskymax 23.0: Iteration 24
Log_1 2002-06-26T20:01:06 spiskymax 23.0: Iteration 25
Log_1 2002-06-26T20:01:12 spiskymax 23.0: Iteration 26
Log_1 2002-06-26T20:01:18 spiskymax 23.0: Iteration 27
Log_1 2002-06-26T20:01:24 spiskymax 23.0: Iteration 28
Log_1 2002-06-26T20:01:30 spiskymax 23.0: Iteration 29
Log_1 2002-06-26T20:01:37 spiskymax 23.0: Iteration 30
Log_1 2002-06-26T20:01:43 spiskymax 23.0: Iteration 31
Log_1 2002-06-26T20:01:49 spiskymax 23.0: Iteration 32
Log_1 2002-06-26T20:01:56 spiskymax 23.0: Iteration 33
Log_1 2002-06-26T20:02:03 spiskymax 23.0: Iteration 34
Log_1 2002-06-26T20:02:09 spiskymax 23.0: Iteration 35
Log_1 2002-06-26T20:02:16 spiskymax 23.0: Iteration 36
Log_1 2002-06-26T20:02:24 spiskymax 23.0: Iteration 37
Log_1 2002-06-26T20:02:31 spiskymax 23.0: Iteration 38
Log_1 2002-06-26T20:02:37 spiskymax 23.0: Iteration 39
Log_1 2002-06-26T20:02:44 spiskymax 23.0: Iteration 40
Log_1 2002-06-26T20:02:52 spiskymax 23.0: Iteration 41
Log_1 2002-06-26T20:02:58 spiskymax 23.0: Iteration 42
Log_1 2002-06-26T20:03:05 spiskymax 23.0: Iteration 43
Log_1 2002-06-26T20:03:13 spiskymax 23.0: Iteration 44
Log_1 2002-06-26T20:03:19 spiskymax 23.0: Iteration 45
Log_1 2002-06-26T20:03:27 spiskymax 23.0: Iteration 46
Log_1 2002-06-26T20:03:34 spiskymax 23.0: Iteration 47
Log_1 2002-06-26T20:03:41 spiskymax 23.0: Iteration 48
Log_1 2002-06-26T20:03:48 spiskymax 23.0: Iteration 49
Log_1 2002-06-26T20:03:55 spiskymax 23.0: Iteration 50
Log_1 2002-06-26T20:04:02 spiskymax 23.0: +++++++++Statistics+++++++++
Log_1 2002-06-26T20:04:07 spiskymax 23.0: Good = 3.0 = [ 3.0 , 3.1 ]
Log_1 2002-06-26T20:04:07 spiskymax 23.0: Evidence = -4455003.0 = [ -4455003.0 , -4455003.0 ] = Log[e]Prob(Data)
Log_1 2002-06-26T20:04:10 spiskymax 23.0: ------------------- source fluxes and error analysis -----------------
Log_1 2002-06-26T20:04:10 spiskymax 23.0: ------------------- source flux units: photons cm^-2 s^-1 ------------
Log_1 2002-06-26T20:04:13 spiskymax 23.0: === Testing for source 1 at 0.00 0.00 ON radius= 2.00 OFF radius= 4.00 : flux=4.051e-01 +-5.062e-04 sigma= 800.30
Log_1 2002-06-26T20:04:13 spiskymax 23.0: ------------ end of source fluxes and error analysis -----------------
Log_1 2002-06-26T20:04:13 spiskymax 23.0:
------------- Analysing source catalogue for energy range 1165.00-1180.00 keV
Log_1 2002-06-26T20:04:13 spiskymax 23.0: total number of sources in input catalogue=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: total number of sources in output catalogue=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0:
----------End analysing source catalogue for energy range 1165.00-1180.00 keV
Log_1 2002-06-26T20:04:13 spiskymax 23.0: +++++++++ end of memsys5 analysis for energy range #1 +++++++++++++++
Log_1 2002-06-26T20:04:13 spiskymax 23.0: write_SKY_IMA begins
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALobjectFindElement status=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALGetBaseType status=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALGetBaseType baseType=6
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DAL3GENindexCreateMember status=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALarrayModStruct status=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALarrayPutSection status=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALindexUpdate status=-1207
Log_1 2002-06-26T20:04:13 spiskymax 23.0: spiskymax v23 processing --STAMP-- spi/skymax_index.fits[GROUPING,1,BINTABLE]
Log_1 2002-06-26T20:04:13 spiskymax 23.0: write_SKY_IMA ends
Log_1 2002-06-26T20:04:13 spiskymax 23.0: write_profiles begins
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALobjectFindElement status=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALGetBaseType status=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: DALGetBaseType baseType=6
Log_1 2002-06-26T20:04:13 spiskymax 23.0: write_profiles ends
Log_1 2002-06-26T20:04:13 spiskymax 23.0: CommonCloseSWG=0
Log_1 2002-06-26T20:04:13 spiskymax 23.0: << spiskymax_processing ends
Log_1 2002-06-26T20:04:13 spiskymax 23.0: Task spiskymax terminating with status 0
Log_0 2002-06-26T20:04:14 blc_sa 1.7: SPI data analysis finished. Status 0
Log_1 2002-06-26T20:04:14 blc_sa 1.7: Task blc_sa terminating with status 0
| en |
converted_docs | 689028 | > DIRECTORY OF SERVICE CONTACTS
>
> OFFICE OF HEADQUARTERS OPERATIONS (CODE OC)
>
> August 2004
>
> Continual updates can be found on
> <http://www.hq.nasa.gov/office/codec/services.html>
>
> Contact Sherry McAllister on (202) 358-1633 to report changes to the
> directory
>
> OFFICE OF HEADQUARTERS OPERATIONS (CODE OC)
>
> DIRECTORY OF SERVICE CONTACTS
>
> **OFFICE OF HEADQUARTERS OPERATIONS, CODE OC**
>
> **SERVICE CONTACT TELEPHONE**
>
> Director James Frelk 202-358-2100
>
> James.Frelk@nasa.gov
>
> Deputy Director
> .............................................Christopher T. Jedrey
> 202-358-0483
>
> <Christopher.Jedrey@nasa.gov>
>
> Executive Officer Bruce King 202-358-0461
>
> <Bruce.C.King@nasa.gov>
Administrative Officer.......................................Margie
Team.....................................202-358-0343
mteam@nasa.gov
Occupational Specialist ................................. .Sarah
Conlin.....................................202-358-0948
sconlin@hq.nasa.gov
> HEADQUARTERS EQUAL OPPORTUNITY & DIVERSITY MANAGEMENT DIVISION, CODE
> OCE
>
> **SERVICE CONTACT TELEPHONE**
Division Director
> Affirmative Employment ................................... Al Castillo
>
> Diversity Management al.castillo@nasa.gov 202-358-1098
>
> Alternative Dispute Resolution (ADR) Claudia Silver 202-358-4468
>
> <claudia.silver-1@nasa.gov>
>
> Discrimination Complaints
>
> (Pre-Complaint Process, Sign Language ............ Craig
> Cassidy....................................202-358-1538
>
> Interpreters and Reasonable Accommodations.....
> craig.cassidy-1@nasa.gov
>
> **Special Emphasis Programs**
>
> Asian/Pacific American Program &................... Craig
> Cassidy.....................................202-358-1538
>
> Individuals With Disabilities/Disabled.................
> craig.cassidy-1@nasa.gov
>
> ..
>
> Hispanic & African Americans Program ............. Craig Cassidy
> .202-358-1538
>
> craig.cassidy-1@nasa.gov
>
> American Indians & Federal Women's Program Claudia Silver
> .202-358-4468
>
> claudia.silver-1@nasa.gov
>
> Affirmative Employment Plan (AEP) &
>
> Workforce Statistics....................................... Claudia
> Silver................. ...................202-358-4468
>
> claudia.silver-1@nasa.gov
>
> Equal Opportunity Assistant
>
> Administrative Functions LaShawn
> McDuffie............................202-358-0965
>
> LaShawn.McDuffie-1@nasa.gov
>
> **HEADQUARTERS BUSINESS MANAGEMENT DIVISION, CODE OCF**
>
> **SERVICE CONTACT TELEPHONE**
Division Director ................Dennis
Bridge....................................202-358-1294
<dennis.c.bridge@nasa.gov>
Deputy Division Director ................Vacant
.................202-358-1298
Headquarters Budget Officer ................Ruth Krat
.................202-358-1706
<ruth.krat-1@nasa.gov>
Personnel and Training Budget.............................Debbie Randall
.................202-358-1173
<debra.l.randall@nasa.gov>
Travel Budget ................Toni Wyatt .................202-358-1526
<toni.wyatt@nasa.gov>
Budget Execution (Senior Analyst) ................Eric Plumer
................................ 202-358-
Budget Formulation
(Senior Analystt) ................Debbi
Martin-Edwards..........................202-358-4737
debbi.Edwards@nasa.gov
Reimbursables Budget ................Clara
Rogers......................................202-358-4683
<clara.roger@nasa.gov>
Debbie Randall...................................202-358-1173
<debra.1.randall@nasa.gov>
Peer Review Contract ................Gregory Lindsay
...........202-358-4832
glindsay@nasa.gov
Headquarters Payroll Supervisor ................Bernadette Keane
.................202-358-1051
<bernadette.m.keane@nasa.gov>
Business and Administrative
Systems Office (BASO) ................Roger Sachse
.................202-358-0686
<rsachse@nasa.gov>
BASO Reports Management
Business Process Lead (BPL) ................David Neumann
.................202-358-0459
<david.neumann@nasa.gov>
BASO Travel Manager BPL ................Kathryn Karmazin
.................202-358-0764
k<athryn.karmaxin-1@nasa.gov>
BASO Travel Manager
System Administrator ................Barbara Birch
.................202-358-0316
b<arbara.a.birch@nasa.gov>
BASO Budget Formulation BP..............................Nadine Tremper
.................202-358-1197
<nadine.tremper@nasa.gov>
> **HEADQUARTERS BUSINESS MANAGEMENT DIVISION, Code OCF**
**SERVICE CONTACT TELEPHONE**
FAX ...............\...202-358-3561
IFMP HELP DESK (Travel Manager, Business Warehouse,
Core Financial, Budget Formulation) ..........................
....202-358-4367
> PAYROLL/TIME & ATTENDANCE HELP
> DESK...........................................................202-358-1082
>
> **REGIONAL FINANCE OFFICE, GSFC, CODE 151**
>
> **SERVICE CONTACT TELEPHONE**
>
> Division Office Director Jon Wolz 301-286-5744
>
> Jon.T.Wolz@nasa.gov
>
> Deputy Director Pamela Doucoure 301-286-8599
>
> pdoucour@pop100.gsfc.nasa.gov
>
> Secretary to the Director DaJuana Morris .301-286-5744
>
> <ddmorris@pop100.gsfc.nasa.gov>
>
> Secretary to the Deputy Director.........................Eileen J.
> ONeill...................................301-286-8599
>
> Eileen.J.ONeill@nasa.gov
>
> **SYSTEMS and POLICY OFFICE, CODE 151.1**
>
> **SERVICE CONTACT TELEPHONE**
>
> HQ/Goddard Systems Support, Reimbursable Billing System,
>
> Cash and Fast Systems Ken Davidson 301-286-5644
>
> Kenneth.W.Davidson@nasa.gov
>
> **COST AND COMMERCIAL ACCOUNTS DEPARTMENT, CODE 155**
>
> **SERVICE CONTACT TELEPHONE**
>
> Department Chief Sandra Brown 301-286-0785
>
> Sandra.K.Brown@nasa.gov
>
> **CONTRACTS AND CLOSING TEAM, CODE 155**
>
> **SERVICE CONTACT TELEPHONE**
>
> Team Lead Evette Blackwell 301-286-2839
>
> <Evette.J.Blackwell@nasa.gov>
>
> **CONTRACTS AND CLOSING TEAM, CODE 155**
>
> **SERVICE CONTACT TELEPHONE**
>
> Interagency Agreements Shaeedah Quinones 301-286-5515
>
> Shaeedah.Quinones-1@nasa.gov
>
> Contracts/NASW Rodney Green 301-286-2117
>
> Rodney.R.Green@nasa.gov
>
> **PURCHASE ORDERS AND GRANTS TEAM, CODE 155**
>
> **SERVICE CONTACT TELEPHONE**
>
> Team Lead.....................................................Lionel
> Walton....................................301-286-3826
>
> Lionel.Walton-1@nasa.gov
>
> Small Purchases, W-9's and w-2's Josephine Triplett 301-286-5520
>
> Josephine.L.Triplett@nasa.gov
>
> Grants Lionel Walton 301-286-3826
>
> Lionel.Walton-1@nasa.gov
>
> Small Purchases, W-3's and W-2's Lori Shavatt 301-286-5586
>
> Lori.J.Shavatt@nasa.gov
>
> Data Entry Ruth Johnson 301-286-7387
>
> Ruth.Johnson-1@nasa.gov
>
> ChiefTraining Kathleen McNulty 301-286-3675
>
> Kathleen.Fernandez-1@nasa.gov
>
> Letter of Credit, Contracts Sharon Moser 301-286-2787
>
> Sharon.K.Moser@nasa.gov
>
> **IFMP IMPLEMENTATION AND OPERATIONS OFFICE, CODE 156**
>
> **SERVICE CONTACT TELEPHONE**
>
> IFMP Transition and Operation Chief Joanne Sprunk 301-614-6900
>
> Joanne.l.Sprunk@nasa.gov
>
> **GENERAL ACCOUNTING DEPARTMENT, CODE 157**
>
> **SERVICE CONTACT TELEPHONE**
>
> Chief Marilyn Mitchell 301-286-9014
>
> Marilyn.E.Mitchell@nasa.gov
>
> **PROPERTY AND REPORTING, CODE 157 (Continued)**
>
> **SERVICE CONTACT TELEPHONE**
>
> Team Lead Donald Jackson 301-614-6090
>
> Donald.E.Jackson@nasa.gov
>
> 224, Property and Commitments Tanya.S. Marbury 301-286-6191
>
> TMarbury@pop100.gsfc.nasa.gov
>
> General Ledger Tonya Jones 301-286-6125
>
> Tonya.M.Jones@nasa.gov
>
> **RESOURCES TEAM, CODE 157**
>
> **SERVICE CONTACT TELEPHONE**
>
> Team Lead & Twix's Denise Brown 301-286-6122
>
> Denise.C.Brown@nasa.gov
>
> FACS, B/C, Suspense and 506's Cassandra McRae 301-286-6231
>
> Cassandra.L.McRae@nasa.gov
>
> **FINANCIAL SERVICES DEPARTMENT, CODE 159**
>
> **SERVICE CONTACT TELEPHONE**
>
> Department Chief (Acting) Alvin Frazier 301-286-6926
>
> Alvin.A.Frazier@nasa.gov
>
> **PAYROLL AND TRAVEL TEAM CODE 159**
>
> **SERVICE CONTACT TELEPHONE**
>
> Voucher Examinations Melissa Mouer 301-286-6089
>
> Melissa.E.Mouer@nasa.gov
>
> Travel Accountants Melissa Mouer 301-286-6089
>
> Melissa.E.Mouer@nasa.gov
>
> Barbara Prather 301-286-3183
>
> Barbara.M.Prather@nasa.gov
>
> Authorizations Linda Ouzts 301-286-5138
>
> <louzts@pop100.gsfc.nasa.gov>
>
> Team Lead, Reimbursable Billings
>
> And Close-out Lorrie Simonds 301-286-3098
>
> Lorrie.A.Simonds@nasa.gov
>
> **PAYROLL AND TRAVEL TEAM CODE 159 (Continued)**
>
> **SERVICE CONTACT TELEPHONE**
>
> JPL Contract...................................................Sharon
> Most 301-286-7884
Sharon.A.Most@nasa.gov
> Accounts Receivable and Collections Stefanie Taylor 301-286-6010
>
> Stefanie.D.Taylor@nasa.gov
HEADQUARTERS INFORMATION TECHNOLOGY & COMMUNICATIONS DIVISION, CODE OCI
> **SERVICE CONTACT TELEPHONE**
>
> Division Director/HQ
>
> Chief Information Officer Sandra Daniels-Gibson 202-358-1340
>
> <Sandra.Gibson@nasa.gov>
>
> IT HELP DESK HQ 202-358-HELP
>
> Off-site 1-866-462-7247
>
> HQ IT Security Manager Gregory (Gregg) Kerr 202-358-2218
>
> <gkerr@nasa.gov>
>
> ODIN Services Noah Nason 202-358-1334
>
> <NNason@nasa.gov>
>
> ISEM Services Dale Stigberg 202-358-4601
>
> <Dale.Stigberg@nasa.gov>
>
> Software Applications.......................................Roger
> Bullock....................................202-358-1332
>
> roger bullock@nasa.gov
>
> IT Training Brenda Williams 202-358-1479
>
> <brenda.c.williams@nasa.gov>
>
> User Resource Center Brenda Williams 202-358-1479
>
> <brenda.c.williams@nasa.gov>
>
> Telephone, Voice Mail, Pager &
>
> Video Teleconferencing Services Mike.Barrett 202-358-2516
>
> <Mike.Barrett@nasa.gov>
>
> Voice Teleconferencing, Wide Area
>
> Network & Facsimile Services Jeff.Anderson 202-358-2516
>
> [Jeff.Anderson@nasa.gov](mailto:Mike.Barrett@nasa.gov)
>
> NASA HQ Computer Center Mike Barrett 202-358-2516
>
> <Mike.Barrett@nasa.gov>
>
> HQ Webmaster Scott Glasser 202-358-2361
>
> <scott.glasser@nasa.gov>
>
> HQ Postmaster Andrew Schain 202-358-0066
>
> HQ Engineering systems Mgr.
> [andrew,schain@nasa.gov](mailto:Andy.Schain@nasa.gov)
HEADQUARTERS INFORMATION TECHNOLOGY & COMMUNICATIONS DIVISION, CODE OCI
> **SERVICE CONTACT TELEPHONE**
>
> HQ Systems Operations Sam Ramos 202-358-1840
>
> <Sam.Ramos@nasa.gov>
>
> Account Administration (X.500) Elaine Bowman .........................
> 202-358-1342
>
> <Elaine.Bowman@nasa.gov>
>
> Information Center Elaine Bowman 202-358-1342
>
> <Elaine.Bowman@nasa.gov>
>
> Printing, Design, & Duplicating Services Mike Crnkovic 202-358-0617
>
> <michael.j.crnkovic@nasa.gov>
>
> HQ Design & Exhibits Officer Laurette Langlois 202-358-1666
>
> <Laurette.Langlois@nasa.gov>
>
> Copier & Duplication Services Leroy Chase 202-358-0214
>
> <leroy.e.chase@nasa.gov>
>
> HQ Correspondence Management Larry Box 202-358-0000
>
> larry.box-1@nasa.gov
>
> HQ Mail Management Program Teresa K. Grimes 202-358-1280
>
> <teresa.k.grimes@nasa.gov>
>
> Document Services Center NCI 202-358-4701
>
> **HEADQUARTERS FACILITIES AND ADMINISTRATIVE SERVICES DIVISION, CODE
> OCO**
>
> **SERVICE CONTACT TELEPHONE**
>
> Division Director Annie O\'Donoghue 202-358-1293
>
> <Annie.ODonoghue@nasa.gov>
>
> Aircraft Scheduling John Stumpf 202-358-1242
>
> <John.C.Stumpf@nasa.gov>
>
> Ed Hurley 202-358-0698
>
> <Edward.J.Hurley@nasa.gov>
>
> Audiovisual Support Services Conference Scheduling 202-358-1183
>
> https:intranet.hq.nasa.gov/FHDS
>
> Colonial Parking Garage Elena Weston 202-358-2415
>
> <Elena.Weston@nasa.gov>
>
> **HEADQUARTERS FACILITIES AND ADMINISTRATIVE SERVICES DIVISION, CODE
> OCO**
>
> **SERVICE CONTACT TELEPHONE**
>
> Conference and Meeting Services Ron B. Hoffman 202-358-1596
> <Ronald.B.Hoffman@nasa.gov>
>
> Equipment and Disposal Donnell Little 202-358-0432
<Donnell.Little@nasa.gov>
> Exhibit Display Services Eric Rountree 202-358-0209
>
> <Eric.Rountree-1@nasa.gov>
>
> Malicha Day 202-358-0206
>
> <MaIicha.Day@nasa.gov>
>
> Facilities Help Desk LESCO 202-358-4357
>
> https://intranet.hq.nasa.gov/FHDS
>
> Concourse Patrick Horty 202-358-1739
>
> Patrick.horty@hq.nasa.gov
>
> 1st floor, 3rd floor Ed Hurley 202-358-0698
>
> <edhurley@hq.nasa.gov>
>
> 4^th^ floor Rebecca Bythewood 202-358-1253
>
> <rbythewo@hq.nasa.gov>
>
> 5th floor, 6th floor, 7th floor, Auditorium,
>
> West Lobby, R&I, Loading Dock Eric Rountree 202-358-0209
>
> <Eric.Rountree-1@nasa.gov>
>
> Forms and Records Management Baruti Jahi 202-358-0918
>
> <Baruti.a.jahi@nasa.gov>
>
> Travel Card Rose Butler 202-358-0184
>
> <Rose.butler@hq.nasa.gov>
>
> Vera Edmunds 202-358-0106
<Vera.A.Edmunds@nasa.gov>
> Industrial Property (GSFC) David Gruntman 301-286-3265
>
> <DGruntman@pop100.gsfc.nasa.gov>
>
> NASA Parking Permits Vera Edmunds 202-358-0106
>
> <Vera.A.Edmunds@nasa.gov>
>
> Malicha Day 202-358-0206
>
> <Malicha.A.Day@nasa.gov>
>
> Passport and Visas John Pettit 202-358-0009
>
> <John.Pettit@nasa.gov>
>
> Rose Butler 202-358-0184
>
> <Rose.T.Butler@nasa.gov>
>
> **HEADQUARTERS FACILITIES AND ADMINISTRATIVE SERVICES DIVISION, CODE
> OCO**
>
> **SERVICE CONTACT TELEPHONE**
>
> Property Management (GSFC) Connie Higgs 301-286-7420
>
> <CHiggs@pop200.gsfc.nasa.gov>
>
> Receiving and Inspection Terry Lewis 202-358-0196
>
> <T.Lewis-1@mail.nasa.gov>
>
> Recycling, Environmental Management Rebecca Bythewood 202-358-1253
>
> rbythewo@hq.nasa.gov
>
> Safety and Emergency Preparedness Angela Stowes 202-358-1239
>
> <astowes@mail.hq.nasa.gov>
>
> Darrius Lewis 202-358-0608
>
> <Dlewis2@hq.nasa.gov>
>
> Space Planning. .............................................John
> C.Stumpf 202-358-1242
>
> <John.C.Stumpf@nasa.gov>
>
> Ron Beach 202-358-0050
>
> rbeach@hq.nasa.gov
>
> Supply Bob Clark 301-286-7740
>
> <RCIark@pop200.gsfc.nasa.gov>
>
> Transportation (GSFC) Clint Green 301-286-8980
>
> Clgreen@pop200.gsfc.nasa.gov
>
> Warehousing, Storage, Publications (GSFC) Fran Teel 301-286-5677
>
> <Fran.C.Teel-1@nasa.gov>
>
> **HEADQUARTERS HUMAN RESOURCES MANAGEMENT DIVISION, CODE OCP**
>
> **SERVICE CONTACT TELEPHONE**
Acting Director Christopher T. Jedrey 202-358-0483
<christopher.t.jedrey@nasa.gov>
Deputy Director Yvette R. Coles 202-358-1210
> <yvette.r.coles@nasa.gov>
Acting Chief, HQS Systems Paulette Q. Britt 202-358-1275
and Data Branch <paulette.q.britt@nasa.gov>
Secretary Lora J. Dunn 202-358-1998
Division Administrative Services <lora.j.dunn@nasa.gov>
Employee Checkout
Human Resources Specialist Chris D. Beidel 202-358-3831
(Policy) <cbeidel@hq.nasa.gov>
Human Resources Specialist Donna L. Burgess 202-358-2158
(Customer Service Liaison) <donna.burgess@nasa.gov>
> **HEADQUARTERS HUMAN RESOURCES MANAGEMENT DIVISION, CODE OCP**
>
> **SERVICE CONTACT TELEPHONE**
>
> (Cont'd)
>
> Retirement Counselor James Reeves (Al) 202-358-1793
>
> (Contractor) jreeves1@mail.hq.nasa.gov
>
> **Systems & Data Branch**
>
> Human Resources Specialist Linda L. Pultz 202-358-1568
>
> <linda.l.pultz@nasa.gov>
>
> Employee Relations Officer Dorothy S.Egbert 202-358-1162
>
> dorothy.s.egbert@nasa.gov
>
> HR Management Analyst Angela L. White 202-358-0803
<angela.white-1@nasa.gov>
> HR Management Analyst Luke Weaver 202-358-1218
>
> l<uke.weaver-1@nasa.gov>
>
> Administrative Advisor Jody B. Williams 202-358-3706
>
> <jody.b.williams@nasa.gov>
>
> **Operations Branch Team A -- Codes A, B, G, H, K, L, O, Q, R, T, V,
> X, Z and Executive Services**
>
> Supervisory Human Resources Specialist Brenda L. Spicer 202-358-1561
>
> Team A Lead <brenda.l.Spicer@nasa.gov>
>
> Human Resources Specialist Theresa A. Graves 202-358-1299
>
> <theresa.a.graves@nasa.gov>
>
> Human Resources Specialist Sharlene A. Speir 202-358-2127
>
> <shon.speir@nasa.gov>
>
> Human Resources Management Specialist, Laigen Sanet 202-358-2457
>
> Executives Services <laigen.sanet-1@nasa.gov>
>
> SES, ST, SL, NEX, Schedule C
Human Resources Specialist........................... Walita M.
Wilkins-Willis ...................202-358-0945
<walita.m.winslow@nasa.gov>
Human Resources Specialist........................... Julie F.
Porter................................... 202-358-1546
<jporter@nasa.gov>
TAG Secretary............................................... Elaine J.
Grunther 202-358-2336
> Executive Services Support <Elaine.grunther-1@nasa.gov>
>
> TAG Secretary................................................Michelle
> D. Corneilus 202-358-1574
>
> Human Resources Assistant <michelle.Cornelius-1@nasa.gov>
>
> **HEADQUARTERS HUMAN RESOURCES MANAGEMENT DIVISION, CODE OCP**
>
> **SERVICE CONTACT TELEPHONE**
>
> **Operations Branch Team B -- Codes D, E, F, I, M, N, P, S, U, Y and
> IPA's and Detailees Services**
>
> Supervisory Human Resources Specialist.............Michelle E.
> Batie................................202-358-1424
>
> Team B Lead <michelle.e.batie@nasa.gov>
Human Resources Specialist Tonya D. Brown 202-358-1562
> <tonya.d.brown@nasa.gov>
>
> Human Resources Specialist Mitchell D. DeShong 202-358-1564
>
> <mitchell.d.deshong@nasa.gov>
>
> Human Resources Specialist Fred A. Johnson, Jr. 202-358-1581
>
> <fjohnson@nasa.gov>
>
> Personnel Assistant Rayseen I.Reynolds 202-358-0619
>
> <rayseen.i.reynolds@nasa.gov>
>
> TAG Secretary Alethea Mack 202-358-3787
>
> <alethea.mack-1@nasa.gov>
>
> **Special Programs & Policy Branch**
>
> Chief, Special Program & Policy Branch Laura Farrior 202-358-4754
>
> Supervisory Human Resources Specialist <laura.m.farrior@nasa.gov>
>
> Occupational Health Programs Cherie Zieschang 202-358-1569
>
> Health Unit/Fitness/EAP/OWCP <czieschan@nasa.gov>
>
> Human Resources Specialist Rhonda L. Horton-Taylor 202-358-0444
>
> PMFs, Experts & Consultants, <rhonda.l.taylor@nasa.gov>
>
> Agency Honor Awards
>
> Human Resources Specialist Scott Howell 202-358-1558
>
> (Employee Benefits) <scott.howell@nasa.gov>
>
> Thrift Savings Plan, Employee Express
>
> FEHB, FEGLI
>
> Human Resources Services Specialist, Denise Hurey 202-358-2105
>
> TAG Program, Permanent Change of Station <denise.m.hurey@nasa.gov>
Headquarter Honor Awards
Human Resources Services Specialist Marian Beverly 202-358-2318
> Student Program, Suggestion Program <marian.g.beverly@nasa.gov>
>
> Customer Service Awards Program
>
> Administrative Support Assistant Angela Thompson 202-358-1214
Fare Subsidy Program <angela.thompson-1@nasa.gov>
> TAG Secretary.................................................Cenceria
> Hirschowitz..........................202-358-1344
>
> <cenceria.hirscbowitz-1@nasa.gov>
>
> **HEADQUARTERS CAREER MANAGEMENT OFFICE, CODE OCS**
>
> **SERVICE CONTACT TELEPHONE**
>
> Director, Career Management Vicki Thorne 202-358-2339
>
> victoria.r.thorne-1@nasa.gov
>
> Career Management Specialist.. Sherry McAllister 202-358-1633
>
> Sherry.l.mcallister@nasa.gov
>
> Career Counseling Program Elizabeth Piper 202-358-0565
>
> <Epiper@hq.nasa.gov>
>
> Work/Life Coordinator...................................... Evelin
> Saxinger................................. 202-358-1311
>
> <Esaxinger@hq.nasa.gov>
>
> **HEADQUARTERS TRAINING OFFICE, GSFC, CODE 114.H**
>
> **SERVICE CONTACT TELEPHONE**
>
> Group Leader/HQ Training Officer Jim Wilk 301-286-2021
>
> <James.H.Wilk@nasa.gov>
>
> Career Management Training Mary Alice Diedrich 301-286-5393
>
> <Mary.A.Diedrich@nasa.gov> 202-358-1159
>
> Clerical Training Sharon Boykins 301-286-7508
>
> [Sharon.L.Boykins-1@nasa.gov](mailto:Sharon.L.Boykins@nasa.gov)
>
> Code Training Allocations Mary Alice Diedrich 301-286-5393
>
> <Mary.A.Diedrich@nasa.gov> 202-358-1159
>
> Communication Skills Training Sharon Boykins 301-286-7508
>
> <Sharon.L.Boykins-1@nasa.gov>
>
> Computer Training (CTC) Heather Osterman 202-358-1111
>
> Heather.Osterman@nasa.gov
>
> Continuing Education Program Mary Alice Diedrich 301-286-5393
>
> <Mary.A.Diedrich@nasa.gov>
>
> Executive Development Kim Haney 301-286-6112
>
> Kim.R.Haney@nasa.gov
>
> Graduate Study Program Mary Alice Diedrich 301-286-5393
>
> Mary.Alice.Diedrich@nasa.gov 202-358-1159
>
> Health & Safety Training Sheila Jackson 301-286-2022
>
> <Sheila.M.Jackson@nasa.gov>
>
> Invoices for Training (Regional Finance Office) Katrina
> Whitaker................................301-286-5744
>
> <Katrina.Whitaker@nasa.gov>
>
> **HEADQUARTERS TRAINING OFFICE, GSFC, CODE 114.H**
>
> **SERVICE CONTACT TELEPHONE**
>
> Information Technology (IT) Security
>
> Training Sharon Boykins 301-286-7508
>
> <Sharon.L.Boykins-1@nasa.gov>
>
> Leadership/Management/Supervisor Kim Haney 301-286-6112
>
> Development Kim.R.Haney@nasa.gov
>
> Mentoring Program Mary Alice Diedrich 301-286-5393
>
> <Mary.A.Diedrich@nasa.gov> 202-358-1159
>
> Technology Based Training/Distance Learning Caren Wilkins 202-358-0092
>
> <cwilkins@hq.nasa.gov>
>
> **On‑Site Courses See Course Description:
> http://ohr.gsfc.nasa.gov/DevGuide/Hq/hqtrngopps.htm**
>
> Leadership Development Program (LDP) Kim Haney 301-286-6112
>
> [Kim R. Haney@nasa.gov](mailto:Kim R. Haney@nasa.gov)
>
> Processing of Off-Site Training 56\'s Serena Rounceville 301-286-8250
>
> Srouncev@pop100.gsfc.nasa.gov
>
> Organization Development Kim Haney 301-286-6112
Kim.R.Haney@nasa.gov
> HQ Training -- Website Information Sean Hoover 301-286-4616
>
> Shoover@pop100.gsfc.nasa.gov
>
> Training Policy-General Jim Wilk 301-286-2021
>
> <James.H.Wilk@nasa.gov>
>
> **HEADQUARTERS PROCUREMENT OFFICE, CODE 210.H**
>
> **SERVICE CONTACT TELEPHONE**
>
> Associate Division Chief Leigh Anne C Giraldi 301-286-3616
>
> Leigh.Anne.Giraldi@nasa.gov
>
> Procurement Manager C. Sue Gonser 301-286-3294
>
> Carolyn.S.Gonser@nasa.gov
Procurement Manager Chris Whyte 301-286-4309
> <Christopher.D.Whyte@nasa.gov>
>
> **HEADQUARTERS PROCUREMENT OFFICE, CODE 210.H**
>
> **SERVICE CONTACT TELEPHONE**
>
> Procurement Manager Claudia Womble 301-286-4118
>
> <Claudia.S.Womble@nasa.gov>
>
> Contracting Officers........................................ Jamiel
> Commodore 301-286-5451
>
> <Jamiel.C.Commodore@nasa.gov>
>
> Michele' Hull 301-286-2749
>
> <Mary.M.Hull@nasa.gov>
>
> Janet Langweil 301-286-3807
>
> <Janet.S.Langweil@nasa.gov>
>
> Karen Place 301-286-6717
>
> <Karen.M.Place@nasa.gov>
>
> Susan Richards 301-286-5245
>
> <Susan.C.Richards@nasa.gov>
Delia Robey 301-286-8109
> <Delia.B.Robey@nasa.gov>
>
> Contract Specialists ........................................ Donna
> Hardy 301-286-3936
>
> <Donna.M.Hardy.1@nasa.gov>
Kim Harris. 301-286-6362
> <Kimberly.M.Harris@nasa.gov>
>
> Alpana Jenne 301-286-6638
>
> <Alpana.K.Jenne@nasa.gov>
>
> Doris Wood 301-286-6162
>
> <Doris.S.Wood@nasa.gov>
>
> Michael Alexander 301-286-6718
>
> <Michael.K.Alexander@nasa.gov>
>
> Contract Administrators.....................................Sandy
> Russo 301-286-6693
>
> <Sandra.R.Russo@nasa.gov>
Amy Mento 301-286-5029
> <Amy.M.Mento.1@nasa.gov>
>
> Closeouts Peg Bradley 301-286-2499
>
> <Peg.A.Bradley.1@nasa.gov>
>
> Laurie Friederich 301-286-6684
>
> <Laurie.A.Friederich.1@nasa.gov>
>
> **HEADQUARTERS PROCUREMENT OFFICE, CODE 210.H**
>
> **SERVICE CONTACT TELEPHONE**
>
> Small Purchases Felecia London 301-286-4112
>
> <Felecia.London.1@nasa.gov>
>
> Genia Lyons 301-286-6638
>
> <Genia.M.Lyons@nasa.gov>
>
> Jeanne Moschetti 301-286-8150
>
> <Jeanne.V.Moschetti@nasa.gov>
>
> Fax Machines S111 301-286-0356
>
> 301-286-0357
>
> **Grants Office**
>
> Grants Officers................................................[C. Sue
> Gonser 301-286-3294](mailto:Steven.R.Lloyd@nasa.gov)
>
> [Carolyn.S.Gonser@nasa.gov](mailto:Steven.R.Lloyd@nasa.gov)
>
> Chris Whyte 301-286-4309
>
> <Christopher.D.Whyte@nasa.gov>
>
> Claudia Womble 301-286-4118
>
> <Claudia.S.Womble@nasa.gov>
>
> Grants Specialist Team Leader Theresa A.
> Bryant..............................301-286-3048
>
> <Theresa.A.Bryant.1@nasa.gov>
>
> Fax Machine.................................................... ....
> 301-286-6648
>
> Grants Information
> Homepage............................<http://genesis.gsfc.nasa.gov/grants/grants.html>
| en |
markdown | 211769 | # Presentation: 211769
## Support Organizations Reporting to the Director’s Office ISO14001 Environmental Management System & OHSAS 18001 Occupational Heath and Safety System Management Review 12/04/08
## Support Organizations Reporting to the Director’s Office ISO14001 Environmental Management System SORD EMS Management Review EMS Rep: Anna Bou 12/04/08
## Agenda
**Agenda**
**Scope**
**Recent changes to EMS program**
**Significant Environmental Aspects**
**Results of Audits**
**Status of Objectives and Targets (Follow-up from FY07 MR)**
**Noteworthy E-practices and Improvements**
**Status of Corrective/Preventative Actions**
**Stakeholder Issues**
**FY09 Suggested Objectives (Improvements)**
**Request for feedback**
## Recent Changes
**Recent Changes**
_**Description of ESHD EMS Program: **_
- Located at ESH EMS Web Site: _[http://](http://intranet.bnl.gov/eshq/ems/)__[intranet.bnl.gov/eshq/ems](http://intranet.bnl.gov/eshq/ems/)__[/](http://intranet.bnl.gov/eshq/ems/)_
- The scope of ESH's EMS includes all activities internal to the ESH Directorate, as well as all activities internal to the Director's Office (DO), Community, Education, Government & Public Affairs (CEGPA) and Finance Directorate (DI).
- Activities conducted by the above to support institutional systems are not included in the scope of this EMS, but instead covered under BNL's Institutional-Level EMS.
**Recommendations for change:**
**Decision A:** Combine the **ESH Directorate** + **BOP (SORD)** OHSAS _into one program_
**Decision B:** Combine the ESH Directorate + BOP **OSH Rep** + **EMS Rep** _to one person_
- (Suggestion: A. Bou or N. Bernholc)
## Significant Environmental Aspects
**Significant Environmental****Aspects**
_**Information Technology Division (ITD)**_
- Storage or use of hazardous material (battery banks)
- Spills (potential)
- Hazardous waste (cleaners, light bulbs, aerosol cans, etc...)
_**Human Resources: Occupational Medicine Clinic (OMC)**_
- Industrial & Hazardous waste (Photo Processor)
- Spill Potential (Photo Processor)
- Medical waste (Clinical)
## Significant Environmental Aspects
**Significant Environmental****Aspects**
_**CEGPA: Office of Educational Programs (OEP) & Production Services**_
- Educational Demonstrations:
- Hazardous waste
- Spill Potential
- Production Services:
- Industrial waste (Press Ink)
- Liquid Discharges (Press cleaning)
- Atmospheric Discharges (Press Ink) Emissions Unit of Title V Permit, and use of filtration.
## Significant Environmental Aspects
**Significant Environmental****Aspects**
**Other groups don’t have significant aspects; however, they are still covered by the EMS. **
**These organizations can and do contribute to continual improvement initiatives.**
## Results of Evaluations of Compliance
**Results of Evaluations of Compliance**
**Compliance Audits:**
**Tier I **
** **All findings closed
**New York State RCRA Audit**** (Sitewide)– **One Notice of Violation, none applicable to SORD organizations
** ****EPD Multi-Topic Assessment**
- No non-conformance or non-compliance issues identified.
## Systems Audits:
EMS Internal Assessment (February 2008)
One minor nonconformance: An obsolete version of an OMC waste procedure (dated 2002) was not removed from circulation
One Observation: The Correspondence and Commitment Tracking Subject Area is unclear as to whether external environmental inquiries received informally are required to be entered into CCTS. Not clear that the system is being routinely used.
NSF Recertification Assessment (June 2008)
OFI – CEGPA – Consider capturing quality improvement and community involvement goals with positive ESH impacts when setting future objectives and target (Educational Program’s Open Space Stewardship Program).
**Systems Audits:**
**EMS Internal Assessment (February 2008)**
- One minor nonconformance: An obsolete version of an OMC waste procedure (dated 2002) was not removed from circulation
- One Observation: The Correspondence and Commitment Tracking Subject Area is unclear as to whether external environmental inquiries received informally are required to be entered into CCTS. Not clear that the system is being routinely used.
**NSF Recertification Assessment (June 2008) **
- OFI – CEGPA – Consider capturing quality improvement and community involvement goals with positive ESH impacts when setting future objectives and target (Educational Program’s Open Space Stewardship Program).
**Results of EMS Assessments**
**Notes:**
Overall EMS internal audit issues:
Management Reviews missing required sections
EP work order not closed out to show an alarm was fixed.
## SORD
Objective: Train purchasers and specifiers on the requirements of the Environmentally Preferable Purchasing (EPP) Program by participating in EPP awareness training for all credit card holders.
Results: EPP awareness training was provided to credit card holders in April 2008. Training was also provided at the institutional level.
**First objective written that applies to SORD as a whole – Improvement!
HR, Diversity Office, OMC, and CDC
Objective: Improve Electronics Stewardship - Enable ENERGY STAR features on computer monitors
_***SORD***_
_**Objective:**_ Train purchasers and specifiers on the requirements of the Environmentally Preferable Purchasing (EPP) Program by participating in EPP awareness training for all credit card holders.
**Results: **EPP awareness training was provided to credit card holders in April 2008. Training was also provided at the institutional level.
***First objective written that applies to SORD as a whole – *_*Improvement!*_
_***HR, Diversity Office, OMC, and CDC***_
_**Objective:**_** **Improve Electronics Stewardship - Enable ENERGY STAR features on computer monitors
**FY 08 Objectives and Targets**
## Noteworthy Practices
**Noteworthy Practices **
_***CEGPA – Office of Educational Programs (OEP)***_
- _“__Computers for Learning” Program_
**Results:** Donated 20 computers and monitors and 4 printers valued at $22K to LI schools.
## Other Improvements
**Other Improvements**
_***CEGPA – Production Services***_
- Added 100% recycled, Forest Stewardship Council (FSC) certified paper where possible.
- Used 100% biodegradable foam boards for displays.
- Soy inks reviewed for replacement due to metal content and discharge concerns. No substitute available.
- Graphic Arts – bicycle used as delivery option.
**Notes:**
Bicycle use about 5%, but shows positive attitude
## Other EMS Information
**Other EMS Information**
**Stakeholder Concerns – No issues with external stakeholders.**
**No formal “e”-related corrective and preventive actions.**
## FY09 Objectives - Suggestions
**FY09 Objectives - Suggestions**
- _Suggested EMS Objectives:_
- Improve Environmentally Preferable Purchasing Program (PEMP EO13423)
- Evaluate available biobased products as replacements for currently used materials.
- Refresher training to purchasers and credit card holders.
- Reduce paper consumption – promote a policy addressing the use of duplex printing and copying
- Ensure Electronic Product Environmental Assessment Tool (EPEAT) products are being purchased (ensure ENERGY STAR functions are enabled)
## FY 09 Objectives - Suggestions
**FY 09 Objectives - Suggestions**
- Assign personnel to turn off lights at the end of the day in remote facilities or install sensors
- Identify and implement at least one opportunity to use electronic signatures that will reduce printed copies and traveling time.
## FY09 Suggestions
**FY09 Suggestions**
**Any additional objectives or other suggestions?**
## Support Organizations Reporting to the Director’s Office - “SORD”
**Support Organizations Reporting to the Director’s Office - “SORD”**
**OSH Management Review**
**12/04/08 **
**OSH Rep: N. Bernholc**
## Management Review Scope – Topics (per OHSAS 18001)
**Management Review Scope –**** ****Topics (per OHSAS 18001)**
**Overview of Management System**
**Resource Assessment /Financial Investment**
**Evaluation of Completeness of Hazard evaluations**
**Review of OSH Performance – **
- Audits and Assessments
- Leading and Trailing Indicators
- Review of Performance on FY08 OSH Objectives
**Communication, participation and consultation**
**Changing Circumstances **
**Stakeholder concerns**
**Objectives for FY09 **
**Management Review Questions**
## Overview of the OSH Management System For SORD
**Overview of the ****OSH Management System For SORD **
_**Written OSH Program: Centralized at Site level**_** **
- Site OHSAS Web Site
- Site Objectives and suggested objectives for line organizations to adopt
- Internal Audit
- OHSAS 18001 Subject Area
_**Written Program: Maintained at Division/Office Level**_
- Division OSH Web Sites will only contain the following.
- DISCUSS: Will no longer have their own OSH Management. *Should we be In process of removing it from the websites ?*
- Objectives
- Hazard List & Risk Assessments (JRA and FRA) – Should we reduce the individual JRA/FRA’s and use the site wide?
- Records and Document Control Management
- OSH Program Descriptions
## ESSH Policy
**ESSH Policy**
- The SORD organizations have posted copies of the Policy in their buildings.
- The Policy is also accessible from multiple BNL Web Sites
- No issues were raised in the Internal Audit or NSF Audits regarding BNL staff understanding or accessing the policy.
**Output: Decision & Action Related **
**to Possible Change **
- Record of Decision: No new action
- or changes needed in Policy
## Resource Assessment
**Resource Assessment **
| SORD OHSAS 18001- OSH Representative | Nicole Bernholc
|
| --- | --- |
| Division/Office | OSH Point of Contact |
| CEGPA | Scott Bronson, Richard Backofen |
| Computational Science Center | Mary Lynn Heinrich |
| Northeast Regional Counterintelligence Office | Nicole Bernholc |
| Director’s Office (including Legal and Office of Strategic Planning ) | Nicole Bernholc |
| Diversity, HR/OMC | Terry Maugeri |
| Finance Directorate (Fiscal/Business Systems/Budget) | Toni Hoffmann |
| Information Services | Patricia Flood |
| Information Technology Division | Mary Lynn Heinrich |
| Internal Assessment & Oversight Office | Margaret Sparrow |
| Quality Management Office | Steven Stein |
## Financial Investments OHSAS 18001 Program Resources/Cost
**Financial Investments****OHSAS 18001 Program Resources/Cost**
| OHSAS 18001 Program | Persons in this role | Person-hours
/year in FY08 | Estimated
Cost |
| --- | --- | --- | --- |
| SORD Line Organization OSH Representatives POCs | 1 | 300 | 3,000 |
| SORD Line Organization OSH POCs | 8 | | |
| Total | -- | -- | |
## Financial Investments OHSAS 18001 & EMS 14001 Programs
| | Person-hours
/year | Estimated
Cost |
| --- | --- | --- |
| ESH Directorate & BOP EMS Representative (A. Bou) | 80 | $ 8000 |
| ESH Directorate OHSAS Representative (R. Selvey) | 40 | $ 4000 |
| BOP (SORD) OHSAS Representative (N. Bernholc) | 60 | $ 6000 |
**Financial Investments****OHSAS 18001 & EMS 14001 Programs**
**Recommendations for change:**
**Decision A:** Combine the **ESH Directorate** + **BOP (SORD)** OHSAS _into one program_
**ESHD** OHSAS
**BOP** OHSAS
**ESHD** EMS
**BOP** EMS
- A
- B
**Decision B:** Combine the ESH Directorate + BOP **OSH Rep** + **EMS Rep** _to one person_
- (Suggestion: A. Bou or N. Bernholc)
## Hazard Assessment
**Hazard Assessment**
| Common Hazards | Existing JRA |
| --- | --- |
| Ergonomics | *(Manual material handling; Moving;* Office work) |
| High voltage | |
| Noise | |
| Travel * | Travel |
| Indoor Air | |
| Egress | |
| Driving *, Bicycling * | Driving; Bicycling |
| Hazards limited to CEGPA, ITD, OMC and Child Development Center
Non-ionizing Radiation (e.g. RF, microwaves)
Confined Space
Chemicals/toxic hazards
Flammable gasses/liquids/materials
Blood-borne Pathogens |
| --- |
## Review of OSH Performance Results of OHSAS 18001 Audits
**Review of OSH Performance ****Results of OHSAS 18001 ****Audits**
**Internal Audit**** **- Conducted by SHSD - February- April 2008
- Corrective action on findings and OFIs are covered in ATS 4244
**Only minor or opportunities for improvement for SORD**
**All corrected by the time of the NSF audit**
**External Audit - Site registration by NSF**** **June 2008
- Corrective Action Plan developed and tracked in ATS 4226
**No findings for SORD organizations.**
## OSH Compliance- Internal Assessments
**Industrial Hygiene Multiple Topic Self Assessment**
- Site written program and line implementation (Corrective actions are to be tracked in ATS.)
- Organizations selected those programs that were applicable to their line.
- Asbestos,
- Blood-borne Pathogens,
- Chemicals (Laboratory Standard and HazCom),
- Indoor Air Quality,
- Noise and Hearing Conservation,
- Personal Protective Equipment,
- 10 CFR 851 Compliance
- Corrections are mostly program corrections to Site-wide concerns.
- e.g.** **Site written program and line implementation (Corrective actions are to be tracked in ATS.)
** ****OSH Major Non-conformances:**** 1**
- Many locations do not have the asbestos content labeled on building material (29CFR1926.1101(k)(8)(vii).)
- Chemicals: BNL program’s policies were not modified to reflect NFPA requirements. There is a gap between the *Fire Safety* Subject Area and* WWC*
**Review of OSH Performance**
**OSH Compliance- Internal Assessments**** **
## Review of OSH Performance Nationally Recognized Testing Lab (NRTL) Electrical Equipment Inspections (EEI)
**Review of OSH Performance**** ****Nationally Recognized Testing Lab (NRTL) ****Electrical Equipment Inspections (EEI)**
**Issues: **
**Inadequate Resources** for:
**Organizing and program oversight** (Database)
- Reputable manufacturer program allows credit for acceptable equipment.
- EEI database will provide BNL-wide sharing of “Reputable manufacturer” inspections
**Completion of inspections**
- 30,000+ pieces of equipment need Authority Having Jurisdiction (AHJ) approval
- SHSD has committed to inspection all “Balance of Plant” equipment
- Inventory of Facilities & Operations, NSLS, CAD still unknown (or only estimated).
**Addressing growing number of items found not in compliance**
- In SORD only one investigation has been made.
- ITD investigation was NRTL approved.
## Review of OSH Performance Performance on Objectives for FY08
**Review of OSH Performance****Performance on Objectives for FY08**
| CEGPA | Completed |
| --- | --- |
| Computational Science Center | Completed |
| Director’s Office (including Legal, AND Office of Strategic Planning, Northeast Regional Counterintelligence Office) | Completed |
| HR | 3/5 completed |
| OMC | 4/5 completed (one to be carried over. |
| Finance Directorate (Fiscal/Business Systems/Budget) | Completed |
| Information Services | Completed |
| Information Technology Division | Mary Lynn Heinrich |
| Internal Assessment & Oversight Office
Quality Office | Completed
5 of 6 OSH completed. |
## Review of OSH Performance Leading and Trailing Indicators
**Review of OSH Performance ****Leading and Trailing Indicators**
**No injuries in :**
**Production Services (10 yrs)**
**Computational Science Center**
**Internal Audit and Oversight**
**Information Services**
**In the remaining SORD organizations: **** **
**2 ****First Aid Cases**
**5**** DART/Total Recordable Cases**
## Injury Cases By Department Fiscal Year 2008
**Injury Cases By Department****Fiscal Year 2008**
| Comm. Involve. Gvt. & Pub Aff | | | | | | | | |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Case # | Injury
Date | General
Activity | Injury
Cause | First
Aid | DOE
Recordable | DART | Lost
Days | Restricted
Days |
| | | | Fall on same level | | X | X | 48 | 99 |
| Director's Office | | | | | | | | |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Case # | Injury
Date | General
Activity | Injury
Cause | First
Aid | DOE
Recordable | DART | Lost
Days | Restricted
Days |
| | 09/25/2008 | Food Preparation | Sharp Edge - Contact with | X | | | | |
| Fiscal Division | | | | | | | | |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Case # | Injury
Date | General
Activity | Injury
Cause | First
Aid | DOE
Recordable | DART | Lost
Days | Restricted
Days |
| | 12/11/2007 | Office Work | Fall on same level | X | | | | |
| Human Resources | | | | | | | | |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Case # | Injury
Date | General
Activity | Injury
Cause | First
Aid | DOE
Recordable | DART | Lost
Days | Restricted
Days |
| | 08/06/2008 | Material Handling | Falling Object | | X | X | 31 | 11 |
## Injury Cases By Department Fiscal Year 2008
**Injury Cases By Department****Fiscal Year 2008**
| Information Technology Division | | | | | | | | |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Case # | Injury
Date | General
Activity | Injury
Cause | First
Aid | DOE
Recordable | DART | Lost
Days | Restricted
Days |
| | 11/06/2007 | Walking | Slip/Trip | | X | X | 47 | 0 |
| | 11/19/2007
| Walking
| Fall on same level | | X | | 0 | 0 |
| | 11/09/2007
| Office work | Bodily Reaction | | X | | 0 | 0 |
## Tier I’s
**Tier I’s**
**Tier I’s were done in all departments except 1 whose facilities are under construction.**
**A review of the data was done in several meetings held by S. Kane.**
**Most items were closed out within a reasonable time period.**
**Questions? **
**Are the Tier I’s effective for your organizations? **
**What help do you need? **
## Site-wide Communication OSH communications from external and internal interested parties (stakeholders)
**Site-wide Communication ****OSH communications from external and internal interested parties (stakeholders)**
**Initiatives in communication**
**Safety webinars (ASSE, NSC)**
**All hands meetings**
**Healthfest**
***Take 5***** video safety minute**
**ESSH Monthly Newsletter**
**Radiological News**
**SHSD webpage**
**BNL Bulletin / Monday Memo**
**ESH Coordinator Meetings**
**Director’s Supervisor Meetings**
## Additional SORD Department Communications
**Additional SORD Department Communications**
- Department(s) All-hands meetings
- Distribution of objective implementation process to individuals
- Training coordinators/ESH coordinators follow-up with staff to receive required training
- Special Department Training for objectives
## Effects of Foreseeable Changes to Legislation & Scope of Work
**Effects of Foreseeable Changes to Legislation & Scope of Work**
**OSH Program Areas**
***Ergonomics **** *Rules in 10 CFR 851: DOE audit in FY09. SHSD tracking.
**EEOICPA/ NIOSH** may affect workload of OMC.
**Project reviews and Safety documentation** **such as I****nformation Technology Division Sigma 7 area; new building**
**Recommendation:**
**Verify that ergonomic hazards are identified in SORD and make sure a plan for resolving these items are in place.**
- Record of Decision:
- ___No additional actions
- ___New Action: Develop Plan
## FY09 OSH Objectives
| 1. | Objective: Human Performance Improvement (HPI): Initiate/increase human performance training for work planning, design, and/or reporting (such as participation in Fisher IT, Inc. or Shane Bush human performance training).
| Org |
| --- | --- | --- |
| | Provide HPI training to 80% of line organizations involved in risk-significant activities and processes as identified by the Human Performance Steering Team.
| |
**FY09 OSH Objectives**
## FY09 OSH Objectives
| 1. | Objective: Improve DART and TRC rate performance [PEMP 5.1.1.1, 5.1.1.2] | |
| --- | --- | --- |
| 1.d.1 | Initiate awareness presentations of injuries related to overexertion, slips, falls, bodily reaction and repetitive motion. – This was started for QA last year | |
| | Review statistical data on injuries with each line organization | |
| | Conduct All-hands meeting with discussion of past injuries in line organization and other organizations | |
| 1.d.2 | Increase Webinar for ESH Professionals of Line Organizations | |
| | Help prepare for 2009 Ergo Audit - Identify ergonomic hazards | |
| 1.e.3 | Improve manual lifting and ergonomics training. | |
| 1.e.4 | Target specific groups for proactive presentation/evaluation by the new Physical Therapist | |
| 1.e.5 | Advertise the services of the new Physical Therapist for personal and work related injury therapy. | |
**FY09 OSH Objectives**
## FY09 OSH Objectives
**FY09 OSH Objectives**
| 2. | Objective: Reduce Traffic violations and accidents.
[PEMP 5.1.1.1, 5.1.1.2] |
| --- | --- |
| 2.A | Institute an appropriate organization level initiative to raise employee awareness of vehicle safely (such as use of DVD class.) | |
| --- | --- | --- |
| 2.b. | Raise awareness of the requirement for disciplinary actions for repeated violations with supervisors. As per the Disciplinary Actions Subject area. | |
| 4. | Objective: Improve Chemical Storage in Flammable Cabinets | |
| --- | --- | --- |
| | Improve storage to no violations of NFPA requirements for flammable cabinets. (Target = 0 non-compliant cabinets) | |
| 5. | Use site JRA /Eliminate redundant documents | |
| --- | --- | --- |
| | Participate on working group when formed | |
## 2009 Objectives - Finalization
**2009 Objectives - Finalization**** **** **
**Treat organizations with office functions as one. Not every small organization needs to do an objective. **
**Decide which organization will work on a goal. **
**Less is more. Don’t pick too many objectives. Do less but do it better. **
**ITD, OMC and CEGPA have the most objectives because they have the most potential hazards. **
**ITD and CEGPA should pick an additional chemical goal.**
## FY09 OSH Objectives
**FY09 OSH Objectives**
**Output: Decision & Actions Related to Possible Change:**
_**OSH Objectives**_**: **These Objectives and Improvement Initiatives were based on the proposed sitewide objectives. They may be change if the sitewide objectives are modified. They are adequate to address issues from Internal OSH Audits, NSF Audit, known weakness, and improvements.
- Record of Decision:
- ___Accept these Objectives
- ___Additional Objectives or changes:
## Issues from FY07 SORD Management Review
**Issues from FY07 SORD Management Review**
| Issue
| Resolution |
| --- | --- |
| Lack of ESH coordinator for Director’s Office Organizations | Appointed N. Bernholc to the role
|
| Question:
Does having an individual outside the organization serve the needs of the organizations? | |
## Management Review Decisions
**Management Review Decisions**
**Is the OSH Management System **_**effective**_** in**** ****achieving policy commitment?**
**Is the OSHMS **_**effective**_** in achieving the objectives, targets and performance measures?**
**Is the OSHMS **_**adequate**_** in terms of:**
**Resource allocation?**
**Information systems?**
**Organizational issues – staff expertise; procedural requirements**
## Management Review Decisions
**Management Review Decisions**
**Are the objectives, targets and performance measures **_**suitable**_**, taking into account the following factors:**
- Injuries/illnesses?
- Current and future regulatory requirements?
- Business interests, technological capability?
- Internal organizational or process changes?
**Should **_**additional**_** objectives, targets or performance measures be established?**
## Any Additional Comments or Concerns?
**Any Additional ****Comments or Concerns?**
_**Thank you for your participation**_
**This ****PowerPoint presentation**** will be posted on the Site OSH Web Page**
**Minutes of this Meeting**** and a ****Record of Decision on Issues**** will be prepared and posted on the Site OSH Web Page** | en |
markdown | 411753 | # Presentation: 411753
## Banking on Development Peter D. Cleary Director & General Counsel March 2007
- Banking on Development**Peter D. Cleary****Director & General Counsel**March 2007
## Core Mission
- To issue political risk guarantees in cross border emerging market transactions
## Four Coverages
- 1. **Transfer and inconvertibility**
- 2. **Expropriation**: government action which deprives the guarantee holder of ownership or control of the guaranteed investment or deprives the guarantee holder of a substantial benefit of the investment
- 3. **War and civil disturbance**
- 4. **Breach of contract**: failure of the host government to honor an arbitral award following a breach of contract
## Benefits of MIGA Guarantees
- Mitigate political risk
- Accessing funding and lowering borrowing costs
- Improving ratings
- Extending tenors
- Ability to resolve / mediate disputes
## Eligibility
- Must be cross border between member countries
- Cannot participate in purely local deals
- Must be “new” investment, but there is considerable flexibility here
- Expansion or modernization of old plant
- Acquisition of existing project if there is a financial restructuring etc.
## Eligibility
- Coverage of:
- Equity, including shareholder loans and various profit sharing agreements
- Loans, but only if there is an equity cover
- Loan guarantees
- could be used to cover sponsor support agreements
- Minimum term of 3 years; maximum of 20
## Miscellaneous
- Rely on rights of subrogation
- Do not require counter-guarantees
- We do obtain a host country approval
- Ability to intervene to prevent claims
- SME program for investments of $5m or less
## Infrastructure projects
Frontier markets
Conflict-affected countries
South-South investments
**Infrastructure projects**
**Frontier markets**
**Conflict-affected countries**
**South-South investments**
- $16bn of guarantees issued since 1989
- Current portfolio of $5bn
**Overview of Business**
**Four Strategic Pillars - FY06 Guarantees Issued, $ M**
** ****$469m (14 projects)**
**$481m (23)**
**$165m (10)**
**$389m (15)**
**By Region – FY06**
**By Sector – FY06**
## MIGA support to US companies
- Africa, 1%
- Asia, 17%
- ECA, 26%
- LAC, 51%
- MENA, 5%
- Guarantees Issued to US Companies, % **By Region**
- Agribusiness & Mfg, 20%
- Financial, 31%
- Oil, Gas and Mining, 18%
- Tourism & Services, 10%
- Infrastructure, 21%
- Guarantees Issued to US Companies, % **By Sector**
**MIGA has issued $2.2bn in guarantees to US investors since inception; USA represents MIGA’s 3****rd**** largest host country exposure**
## For more information
Peter D. Cleary Director & General Counsel pcleary@worldbank.org
www.miga.org
**For more information**
**Peter D. Cleary**Director & General Counselpcleary@worldbank.org
- www.miga.org | en |
log-files | 570258 | -------------------
Version: V1_10, Date: Wed Dec 3 14:38:13 PST 1997, Module: cdms, User: drach
-------------------
- In cdunifdrs.c, dimensions which are reversed or subsetted wrt a
coordinate dimension are now treated as local.
- Added cdDimGetDouble to cdmsslab.c
- Fixed wraparound, reading wraparound dimensions in cdmsslab.c
- Added cdDimGetDouble
-------------------
Version: V1_9, Date: Mon Nov 24 09:32:35 PST 1997, Module: cdms, User: drach
-------------------
- Added QL package to cdunif
- Added NdimIntersect function to CDMS slab routines
-------------------
Version: V1_8, Date: Mon Nov 10 11:26:21 PST 1997, Module: cdms, User: drach
-------------------
- Added cuvargets to cdunif, cdSlabRead to cdms
-------------------
Version: V1_7, Date: Fri Oct 24 11:26:06 PDT 1997, Module: cdms, User: drach
-------------------
- Cache netCDF unlimited dimensions
- Consistent with GrADS src170
-------------------
Version: V1_6_2, Date: Fri Sep 26 14:52:49 PDT 1997, Module: cdms, User: drach
-------------------
- Added caching for netCDF unlimited dimension
- Added cddrs double precision routines getedimD, getcdimD,
getrge2D (currently untested)
- Fixed fouled up cddrs includes
- Myriad GrADS changes
-------------------
Version: V1_6, Date: Mon Jan 6 10:54:21 PST 1997, Module: cdms, User: drach
-------------------
Added HDF driver to cdunif
-------------------
Version: V1_5_2, Date: Thu Oct 31 16:42:56 PST 1996, Module: cdms, User: drach
-------------------
- Cleaned up error returns in cw_geterr
-------------------
Version: V1_5, Date: Mon Sep 9 11:33:52 PDT 1996, Module: cdms, User: drach
-------------------
- GrADS/GRIB interface works on all platforms, supports
- platform-independent gribmap
- Recursive make
- Added autoconfiguration, removed old Makefiles
-------------------
Version: V1_4_2, Date: Wed Apr 10 12:24:35 PDT 1996, Module: cdms, User: drach
-------------------
- cleaned up Sun Makefiles
-------------------
Version: V1_4_2, Date: Thu Apr 4 10:39:37 PST 1996, Module: cdms, User: drach
-------------------
- Added FORTRAN interface for time functions
- Added CDMS API open, lookup, inquiry, and internal functions
-------------------
Version: V1_4, Date: Wed Mar 6 10:05:23 PST 1996, Module: cdms, User: drach
-------------------
- Restructured cdms.h in preparation for CDML, API development
- Moved portions of cdms.h to cdmsint.h
- Ported cdunif, cddrs to IBM, DEC Alpha, Cray
- Rewrote time routines: cdTimeConv.c overlays timeArith.c, timeConv.c
- Added seconds, Julian time to timeArith.c, timeConv.c
- Added int datatype
- Modified grads to return longitude, latitude, level instead of x,y,z
- Modified grads to return relative time units
- Translated cdunif sort routine to C (cdsort.c)
- Miscellaneous bug fixes
-------------------
Version: V1_3_3, Date: Wed Jul 12 18:59:03 PDT 1995, Module: cdms, User: drach
-------------------
- Added recursive makes on SGI
-------------------
Version: V1_3_2, Date: Wed Jul 12 17:52:12 PDT 1995, Module: cdms, User: drach
-------------------
- Added recursive Makefiles for Solaris version
-------------------
Version: V1_3, Date: Wed Jul 12 15:26:49 PDT 1995, Module: cdms, User: drach
-------------------
- Ported to SGI: no long double type on SGI platforms
- Fixed GrADS cdunif file open errors
- Added cw_get_fileid function, to get cdunif file ID
-------------------
Version: V1_2, Date: Mon Jun 26 11:04:02 PDT 1995, Module: cdms, User: drach
-------------------
Miscellaneous bug fixes.
-------------------
Version: V1_1_4, Date: Mon Jun 12 14:59:03 PDT 1995, Module: cdms, User: drach
-------------------
- cddrs: extended string lengths, extended dimension types
- cdunif: handle null return arguments in netCDF correctly
-------------------
Version: V1_1_3, Date: Thu Mar 30 22:55:43 PST 1995, Module: cdms, User: drach
-------------------
Ported to HP
-------------------
Version: V1_1_2, Date: Thu Mar 30 21:34:51 PST 1995, Module: cdms, User: drach
-------------------
Installation fixes
-------------------
Version: V1_1, Date: Thu Mar 30 17:03:53 PST 1995, Module: cdms, User: drach
-------------------
Initial version for export - netCDF and GrADS modules have not been thoroughly tested.
-----------
| en |
converted_docs | 818316 | Please go to:
<http://nepp.nasa.gov/index_nasa.cfm/1133/>
or follow this path using the links on the left navigation bar of
http://nepp.nasa.gov:
[Home](http://nepp.nasa.gov/index.cfm) »
[Photonics](http://nepp.nasa.gov/index_nasa.cfm/1128/) » [Fiber Optic
and Photonic Documents](http://nepp.nasa.gov/index_nasa.cfm/1132/) »
Reliability of Laser Diodes for Space Flight Applications
To see the following deliverable:
-----------------------------------------------------------------------
Reliability of Laser Diodes for Space Flight Applications
This page will contain information related to the reliability of laser
diodes for usage in a space flight environment. The documents that
appear here will be solely on this subject for usage by space flight
hardware engineers design, packaging and parts engineers.
-----------------------------------------------------------------------
| en |
all-txt-docs | 417969 | ;+
; NAME:
; trace_destreak
; PUPROSE:
; To remove bad pixels in streaks due to cosmic ray hits.
; The default parameters are optimized for TRACE EUV images.
; CALLING SEQUENCE:
; result = trace_destreak(image[, sens=sens, thresh=thresh])
; INPUTS:
; image = 2-dimensional image
; OPTIONAL KEYWORD INPUTS:
; sens = sensitivity to streaks and spots
; (sens = 5.0 is default)
; thresh = threshold for revised pixel map
; (not used by default)
; PROCEDURE:
; Streaks at various angles are amplified and located by
; convolution and thresholding. This information is used to generate
; a map of good (undamaged) pixels. The pixel map is then revised
; to include nearest neighbors. Bad pixels are replaced with a
; weighted average of nearby good pixels.
; SIDE-EFFECTS:
; image is converted to a float array, if it's not already.
; MODIFICATION HISTORY:
; Originally sxt_destreak by C. Kankelborg
; 1998-Jun-18 CCK Adapted for TRACE SAA/HLZ cleanup
;-
pro convol_enhance, img, ker, goodpix, sens
;Convolve img with kernel ker in all four possible orientations.
;Use this to update the good pixel map.
smoothed=smooth(img,3)
for i=0, 1 do begin ;used to go to 3, back when z was zero.
k = rotate(ker,i)/total(abs(ker))
enhanced = convol(img,k,/edge_wrap) ;/(smoothed+(5*sens))
good = float(100.0 GT (sens*enhanced))
goodpix = goodpix AND good
endfor
end
function trace_destreak, image_in, sens=sens
if keyword_set(sens) then sensitivity = sens $
else sensitivity = 5.0 ; a reasonable default
epsilon = 0.1
image=float(image_in)+epsilon
; (1) Make map of good pixels.
; Find streaks.
a = 0.05
b = 0.0
z = -a/2.0 ;formerly 0.0
good_pixmap = float(image GT 0.0) ;initialize good pixel map
kernel=[[b,b,b,b,b], $
[z,z,z,z,z], $
[a,a,a,a,a], $
[z,z,z,z,z], $
[b,b,b,b,b]]
convol_enhance, image, kernel, good_pixmap, sensitivity
kernel=[[b,b,b,b,z], $
[b,z,z,z,a], $
[z,a,a,a,z], $
[a,z,z,z,b], $
[z,b,b,b,b]]
convol_enhance, image, kernel, good_pixmap, sensitivity
kernel=transpose(kernel)
convol_enhance, image, kernel, good_pixmap, sensitivity
kernel=[[b,b,b,z,z], $
[b,b,z,a,a], $
[z,z,a,z,z], $
[a,a,z,b,b], $
[z,z,b,b,b]]
convol_enhance, image, kernel, good_pixmap, sensitivity
kernel=transpose(kernel)
convol_enhance, image, kernel, good_pixmap, sensitivity
kernel=[[b,b,b,z,a], $
[b,z,z,a,z], $
[b,z,a,z,b], $
[z,a,z,z,b], $
[a,z,b,b,b]]
convol_enhance, image, kernel, good_pixmap, sensitivity
;print, 'Displaying good pixel map....'
;xtv, good_pixmap
; (2) Revise pixel map, taking nearest neighbors
good_pixmap = float(ck_smooth(temporary(good_pixmap),1) GT 0.9)
; (3) Replace bad pixels
newpix = ck_smooth(good_pixmap*image,4)/ck_smooth(good_pixmap,4) >0 <image
;print,("Displaying newpix....")
;xtv, newpix
return, good_pixmap*image + (NOT good_pixmap)*newpix - epsilon
END
| en |
converted_docs | 743089 | **Session V -- Effective Pest (Pathogen, Insect, Weeds) Management --
Poster V-10**
Effects of Harrowing on Organically Cultivated Oat Varieties in Austria
Elisabeth Zechner
Saatzucht Edelhof, Edelhof 1, 3910 Zwettl, Austria,
<e.zechner@saatzucht.edelhof.at>
#### Introduction
Within the Austrian project "Basic principles for breeding,
multiplication and variety testing for organic agriculture" (financing
body: Ministry of Agriculture and State Governments, 2004-2008) breeders
do research for the development of new methods for the evaluation of
suitable seeds and varieties for organic agriculture, so also research
is done in "Tolerance to harrowing of spring oats". To combine the
demands on powerful and healthy varieties for organic farming with high
quality it makes sense to select lines out of the wide range in a
conventional breeding garden.
#### Material and methods
At the Austrian location Edelhof near Zwettl 12 varieties of spring oats
used in Austrian organic farming were grown to monitor their tolerance
to harrowing in the years 2005 to 2007. The drilling was done with 400
seeds/m². The monitoring consisted of two trials with three replications
each, one trial had been harrowed and one trial without harrowing.
Different criteria were noted e.g. growth rate, plant habit, plant
length, reaction to the mechanical weed control, soil covering rate, ear
emergence, and diseases. After harvesting and weighing several quality
analyses were carried out.
#### Results
- No - respectively only insignificant - differences between the same
variety in harrowed and not-harrowed model in ear emergence,
maturity, soil covering, diseases
- The not-harrowed model yielded better in three years for spring oats
- In most varieties the quality characters are going down
- Only few varieties reacted positively to harrowing
- But not in all years varieties react in the same way
#### Discussion
Although in the harrowed model less weeds emerged, the competition of
these weeds had no strong negative effects on the varieties in the
not-harrowed model. The mobilisation of nutrients through the use of the
harrow could not be realised for most of them. The harrowing could not
generate higher monetary surpluses through higher yields or better
qualities, respectively; the harrowing seems to be an unnecessary work
and expense at first glance. But as harrowing is necessary to keep under
control the weed seed bank the breeder has to look for varieties
resistant to harrowing and reacting also positively with higher yields
and better quality. So far there are no shared characters found from the
few positively reacting varieties useable as selection criteria.
**References**
Sächsische Landesanstalt für Landwirtschaft (2001).
<http://www.landwirtschaft.sachsen.de/de/wu/Landwirtschaft/lfl/inhalt/11028.htm>
(date of consultation: 19/03/07)
| en |
converted_docs | 249428 | **Air Carrier Training Research**
The FAA Office of the Chief Scientist for Human Factors (AAR-100)
directs an air carrier training research program centering methods for
effective pilot training and assessment. Semi-annual research reviews
are conducted by this office. The following report summarizes the
February 1998 review.
**Introduction**
Although basic technical and Crew Resource Management (CRM) concepts are
widely accepted, much remains to be learned regarding the appropriate
methods for effective training and valid and reliable assessment of
training programs. The general research philosophy guiding efforts to
improve training and assessment is that research must consider distinct
segments of aviation training systems. Individuals comprising the crew,
instructors who train and evaluate crews in the classroom, the simulator
and on the line as well as the management culture responsible for the
safety climate of the carriers should all be considered. Additionally,
this research must regard the variables important to Line Oriented
Flight Training (LOFT) development, implementation and evaluation. Thus
this research centers on (1) crew training and assessment, (2)
instructor training, (3) LOFT development strategies (4) and (4)
organizational and systematic influences on pilot performance.
Address questions or comments to:
Eleana Edens, Ph.D.
AAR-100
\(703\) 960-1085
Eedens@mail.FAA.GOV
**Project Title:** *Identification of Hard to Train CRM Skills*
**Performing Agency:** University of New Mexico, Albuquerque
**Background:** Traditionally, CRM training has focused on the high
level CRM components or elements of pilot performance. The training and
assessment of high-level concepts is fraught with many problems. Among
them, the validity of course content is questionable and the reliability
and validity of CRM assessment has not been established. Prior research
has shown that assessment of observable behaviors, rather than global
concepts, especially within simulator scenarios event sets, can improve
the reliability of CRM assessment. Therefore, observable behaviors have
provided a more meaningful and lower level of detail for the CRM
assessment process. However, the research and operational communities
have not yet developed a comparable level of detail for the CRM training
process. It is impractical to try to train observable behaviors. Thus,
at present, it is likely that training would be on the global level but
assessment could take place at the observable behavior level. This
training paradigm, although improved from all CRM training activities
being at the global level, still lack the training vigor employed, for
example, in technical training. An approach to solving this dilemma is
to attempt to identify the knowledge, skills and abilities underlying
CRM concepts and then to train at that level. Observable behaviors could
be identified and assessed for skills in situation specific training
events.
In addition to the need for refined skill analysis methods, reliable
data collection systems must be developed in order that carriers and the
FAA can evaluate the effectiveness of training programs.
**Project Description:** This research project has been investigating
two distinct segments of air carrier training, skill analysis and
reliable performance assessment.
Work has been conducted at major carriers to identify key CRM skills
that need to be trained in transition and recurrent training. The main
objective of the research is to provide carriers with set of steps to
identify and link CRM skills to essential elements of crew training so
that those skills can be systematically trained and assessed. This
research collected rating and agreement index data to help
representatives from different carrier departments form a consensus in
identifying CRM skills. It is significant that Advanced Qualification
Program (AQP) and Human Factors Subject Matter Experts (SMEs) as well as
check airmen participated in the process, providing the CRM skill
identification with a substantially broader base than is provided by
traditional ISD methods. Using a greater number of SMEs for each of the
steps allowed for a broader consensus and better understanding of CRM
skills across the organization while distributing the workload over a
larger number of individuals. This process reduced some of the
bottlenecks encountered in traditional carrier skill analyses where one
or two SMEs are asked to perform most of the analysis. This has resulted
in a CRM skill listing and a set of methods that carriers can use to
identify their own critical CRM skills. An effort is under way to
develop a CRM skill Identification Manual that will summarize the
process for other air carriers.
The results of this CRM skills identification will be combined with
analyses from previous research which focused on LOFT/LOE session
debriefings, decision making and situational awareness skills The sets
of CRM skills, derived from four major carriers, will be used to develop
a CRM curriculum outline applicable across air carriers. The CRM
curriculum outline will include the basic CRM skill requirements, the
advanced CRM skill requirements, the key knowledge components of those
advanced skills. This will be developed in FY 98 and distributed in FY
99.
Another component of this research project focuses on pilot assessment.
Efforts to reliably assess pilot performance, during training, have
traditionally been less than successful. During FY96 and FY 97 this
research team has been working with an air carrier to improve training
assessment by designing rater training and new data collection systems.
This work focuses on rater calibration, development of grade sheets,
development of videos used in the calibration sessions, presentations to
the instructors on the importance of quality data, collection and
analysis of the calibration data, reporting results. Several calibration
studies have been completed and additional sessions are planned. Thus
far, the results of these calibration studies show (1) how minor changes
in the wording of observed behaviors listed on gradesheets can have a
significant effect on ratings, (2) large individual differences among
raters exits, (3) higher inter-referent than inter-rater reliability and
4) a significant increase in reliability when improvements to the
calibration sessions were implemented (wording of the gradesheet,
quality of video, better briefing of the event sets). The frequency of
the higher inter-referent reliability is important to note because there
are differences among carriers in their views of whether a referent
should be established and instructors trained to the referent or whether
instructor\'s inter-rater reliability is adequate. AAR-100 is
investigating this question further by work being done by George Mason
University at several other carriers employing the inter-rater
reliability methodology.
Based on the observations of this process at the major carrier, this
team of researchers has developed a software package to be used in group
calibration sessions. This software will allow carriers to more
effectively train and asses evaluators in their ability to judge Line
Oriented Evaluations (LOE) performance. This software facilitates the
data collection, statistical data analysis, and report generation for
evaluator LOE calibration sessions. A group of evaluators individually
rate the performance of a crew shown on a video flying an LOE. After the
ratings are entered on a standard gradesheet they are collected and the
scores are entered into a PC running Access software. After entering the
evaluators ratings a complete set of statistical analyses of the data is
provided. These reports summarize each evaluators performance along with
various group performance statistics. These reports then serve as the
basis for the calibration feedback, debriefing, and further training of
the evaluators.
Although carriers conduct regular and recurrent rater calibration
sessions, using the methodologies developed by this project, it is often
necessary to recalibrate one instructor. The cost of bringing together a
group of instructors in order to conduct a group session to calibrate a
single instructor is prohibitive. This research team has developed a
prototype PC-based system that effectively presents an individual
calibration session.
This software tool is designed to allow individual evaluators to undergo
the same type of training and calibration as discussed above in the
group sessions but to self-calibrate individually at their own
convenience. The system provides the prebriefing instructions, regarding
the specific flight scenarios that would be presented and some general
instructions regarding the use of the software. An audio visual
presentation of a crew flying the LOE is presented along with the
gradesheet. The evaluator enters ratings by simply clicking the
appropriate buttons displayed. After entering all of the ratings for all
events, the data are n analyzed and the results presented in a form that
is meaningful to the evaluator (e.g., how close the ratings were to
referent grads, how the ratings compared with other evaluators, which
ratings were most deviant from a standard, etc.) This tool can be used
either as a training or evaluation tool. Its most obvious strength as a
training system is that it allows evaluators to obtain training at their
convenience, receive immediate feedback on their performance, and to
have their grades linked to fleet qualification standards. Its greatest
strength as an evaluation tool is that it allows personalized
assessment. Assuming that evaluator grading history is stored in an
Evaluator Performance Proficiency Database, it is possible to determine
whether an evaluator had specific weaknesses allowing the carrier to
address this issue.
This research team has also produced a document describing what it means
to have quality data, why quality data are necessary for training under
AQP, and the methods for achieving quality in performance assessment.
This document is intended for evaluators, and instructor/evaluator
supervisors. It is currently under AAR-100 review and will be
distributed 6/98.
Additional work being initiated by this research team will focus on
developing a Performance Proficiency Database for Instructors and
Evaluators as required in full implementation of AQP. It is necessary to
have data that reflect the effectiveness as instructors (i.e., the
performance of their former students on various measures, extending
beyond the specific classroom evaluation conducted by the instructor).
It is necessary to track calibration performance over time, as well as
any trends in LOE and first-look performance evaluations. This team will
develop the capability of linking pilot performance data to the
Instructor Proficiency Data base. It is expected that this segment of
this research will be completed early in FY99.
**Products:** Skill Analysis methods, instructor/evaluator calibration
software, performance data analysis tools.
**Title:** *Pilot training and Evaluation: Airplane Simulation Human
Factors*
**Performing agency:** Volpe Center, Cambridge
**Background:** Airplane simulators are critical for the training and
evaluation of pilots because they eliminate training accidents and
enable scenario-based training. In addition, the recently enacted
requirement that regional airlines operate under the same rules as major
airlines as well as the Advanced Qualification Program (AQP) training
approach nearly oblige operators to use simulators. However, for
regional airlines, cost continues to be an obstacle to flight simulator
access, particularly for recurrent training.
Currently, airplane FTD and simulator qualification criteria are
contained in Advisory Circulars AC 120-40B and 45B/C and related
documents. Changes both in the air carrier training environment and in
the field of simulator technology demand a reassessment of these
criteria. The shift in training philosophy from a time-based list of
specific training events to the Advanced Qualification Program (AQP)
training approach based on individual training needs requires that much
of the training formerly performed in aircraft will move to the
simulator. Considering the initiative that Part 135 carriers be held to
the same safety standards as Part 121 carriers, the success of AQP
depends on whether regional carriers will be able to afford simulators
that are appropriate for training 121 proficiency using and AQP training
approach.
In the past, the goal in simulator manufacturing was to produce
simulators that were engineered as similarly as possible to the
airplane, resulting in the highest possible physical fidelity. Today,
however, engineering capabilities have progressed in such a manner that
not always the highest technical capabilities need be applied to all
systems of the simulator, but high fidelity in one system may compensate
for lower fidelity in another. The goal, thus, has shifted from highest
possible physical fidelity to highest possible perceptual fidelity. That
is, a good simulator should feel like the airplane and most important,
elicit the same performance and behavior from pilots as the airplane.
The purpose of this project is to increase the availability and
affordability of airplane simulators by determining exactly what level
of perceptual fidelity, applied to the most costly aspects of simulator,
is required to maintain or improve the level of safety in airline pilot
recurrent training and evaluation.
**Project Description:** This project is proceeding in three directions,
(1) the collection of Subject Matter Expert opinion, (2) a literature
review and (3) new research. First, two workshops were conducted with
experts from the FAA, industry and academia. The topic of the first
workshop was the aeromodel used to program simulators. The topic of the
second workshop was the motion requirements for simulators. These
workshops led to proposed changes the regulations for Level B simulators
and gave direction to subsequent research (AC 120-40B)
The second component of this project is an extensive literature review
of simulation research. The information has been organized into a large
database, which is updated regularly to incorporate new research
results.
The third component is the implementation of new research to address the
question of the motion requirement for recurrent training. Both the
motion workshop and the literature review showed that although motion is
presently required for a level B simulator there is no scientific basis
for such a requirement despite much research in this area. Given the
advances made in simulating visual scenes subsequent to the earlier
research, it may now be possible to achieve sufficient perceptual
fidelity of motion with the vision system alone. As counterintuitive as
this may seem, one must consider that no amount of technology can erase
the fact that the simulator will not take off. Thus, the motion can not
be perfect and in fact may create false cues. In contrast, the visual
cuing can be close to perfect. Not requiring physical motion would
represent a significant cost saving both in acquisition and maintenance
of simulators used in recurrent training.
Research is underway at a regional carrier to determine if given a high
quality visual system, is a high quality motion platform necessary for
recurrent training and evaluation.
Data collection is expected to be completed in FY 98.
**Product:** Research report.
**Title:** *Rapidly Reconfigurable Event Sets*
**Performing agency:** Naval Air Warfare Center Training Systems Design
and the University of Central Florida
**Background:** Line-Oriented Evaluations (LOEs) are a methodology used
in Advanced Qualification Programs (AQPs) to evaluate pilot training
performance and establish trainee proficiency. LOEs consist of flight
simulation scenarios that are developed by the training organization and
approved by the FAA.
In the past, LOEs were developed and apprised individually . That is,
each LOE was separately conceived, developed and tested by the training
organization and individually reviewed and approved by the FAA. The
development and approval of new LOEs was costly and time-consuming. As a
result training organizations usually had only a limited number of LOEs
available for evaluation, each of which were only approved for a limited
time period. In some cases, this may have increased the risk of LOE
scenarios being compromised within a training organization, thus
reducing the validity and reliability of the scenarios.
One way to reduce the negative aspects of the previous LOE design
process is to develop a set of LOE event sets (modules) which upon FAA
approval could be assembled by the training organization into a number
of unique LOEs, without requiring additional specific approval of each
individual LOE by the FAA.
The availability of such a system will not only significantly reduce the
time and cost required by training organizations to create valid
scenarios for training and evaluation, but will increase the
diagnosticity of scenarios by directly linking the event sets with CRM
and technical training objectives. Further it will increase the validity
of the evaluative process by giving evaluators detailed guidelines and
materials for the administration of scenarios. This system will increase
the opportunities for air carriers to create valid training and
evaluation scenarios for global aviation operations.
This research team is developing the appropriate software to allow the
reconfiguration of separate event sets into entire LOEs. The
requirements document has been written and approved. Identification of a
database structure for the software system has been developed. Creation
of databases for aircraft technical data, event sets and aircraft
differences has been established.
This project is expected to be completed in FY 2000.
**Product:** Software for reconfiguring event sets.
**Project Title:** *Identifying Leadership and Followership Skills in
CRM*
**Performing Agency:** Western Michigan University
**Background:** Historically, leadership has been viewed as a linear,
one-way (i.e., downward) action with the primary aim of task
accomplishment. This perspective has dominated the cockpit of air
carriers. However, as roles in the modern cockpit change, from an
individual performance to a crew performance focus, the skills required
of the crew members change also. It is now thought that leadership is an
activity which involves both leaders and followers as they interact to
accomplish goals and that followership skills are as important as
leadership skills to the safe and efficient performance of flight crews.
It has been unclear how to train leadership/followership as the skills
underlying these concepts had not been identified.
**Project description:** This project has analyzed cockpit performance
in order to determine the behavioral components of
leadership/followership skills.
A model of cockpit leadership was developed which guided the subsequent
skill analysis. This model of effective and efficient flight operations
points out that the crew must use many skills to deal effectively with
operational variables largely out of their control. These variables
include the regulatory environment, the corporate environment, the
market environment, and the physical environment. Skill analyses were
conducted based on the assumptions that (1) a minimum amount of
leadership/followership is required to achieve a safe flight (2)
individuals constantly oscillate between leader and follower roles (3)
weak leader or follower skills will be compensated for by other crew
member. Preliminary analysis are complete and determined that in order
to deal effectively within the framework described in the model crews
must possess skills in: envisioning; modeling; receptiveness; influence;
adaptability; initiative. The analysis also showed that these skills are
common to both leadership and followership.
Data from line audits with major carriers reveal that the components
described in the model are related to overall crew effectiveness, thus
validating the skill analysis data. The line audit data showed that, in
general, the more severe an abnormal situation the less effective the
crew tends to be in exhibiting leadership/followership skills. Captains
tend to be less likely to articulate a vision for the flight, meet
company standards or obtain commitment form other crew members or be
adaptable . Both Captains and First Officers were less likely to
initiate actions in response to an operational deficiency when the
severity of abnormal was high. When handling a complex situation, but
not an abnormal, these crews displayed \"outstanding\"
leadership/followership skills. These ratings were not dependent on
position or time together as a crew. This suggests that present
leadership training may not be meeting its objectives especially when
the crews are faced with an abnormal situation.
The data also showed that Captain do in fact, set the tone in the
cockpit. When Captains articulated a vision for the flight the First
Officer would initiate a response to an operational deficiency without
further direction from the Captain. When Captains exhibited good conduct
and high standards, First Officers exhibited similar behavior. When
Captains were receptive, First Officers were likewise receptive. This
finding supports the need for appropriate pre-flight briefing.
Maintaining vigilance during the flight sees to be dependent on each
crew member at different phases. During predeparture, takeoff, climb,
and cruise, vigilance was related to the Captain\'s envisioning,
modeling and receptiveness. However, during the descent and approach
phases, vigilance was related to the First Officer\'s conduct and
standards.
Workload and task distribution was dependent on the Captain\'s conduct,
standards, and receptiveness. Establishing guidelines for automated
systems for all phases of flight was related to the Captain\'s
articulation a vision, conduct and standards (modeling), receptiveness
and use of interpersonal skills to obtain commitment from others.
Based on the skill analysis model and this line data, requirements for
leadership/followership training curriculum have been identified. This
includes the development of classroom exercises extending beyond
role-playing, the creation of event sets that address critical
leadership/followership skills and addressing company philosophy and
policy issues. A complete but preliminary training package was developed
for a major carrier. This includes instructor manual, student manual,
and training videos. This package will be distributed to industry 5/98.
The current work focuses on extending the training curriculum
development and on integrating leadership/followership training into the
second generation Model AQP which will integrate leadership training
throughout the life span of a pilot. This integration will be validated
at a major carrier in FY99.
**Products:** Leadership/Followership training guidelines, and training
systems.
**Project Title:** *Analysis of Cockpit Management System in Multiple
Carrier Environments*
**Performing Agency:** George Mason University
**Background:** Based on previous research, it is widely believed that
CRM training can result in significant improvements in flightcrew
performance and flight safety. Historically, it has been possible to
assess the effects of CRM training on pilot ***attitudes*** regarding
the general management of cockpit duties with self-report inventories
administered pre and post-CRM training. It is thought that a change in
pilot attitude will result in a change in behavior in the cockpit. It
has also been possible to subjectively evaluate the effects of CRM
training on pilot performance in LOFT and on the Line by noting the
differences in CRM performance between crews that have had CRM training
and the crews that have not. Further, performance differences between
air carriers and between fleets within one air carrier have been
investigated. While this approach to assessment has contributed to the
advancement of CRM, it is hampered by the practical constraints of self
report and global measurement.
**Project description:** This present research project will help
determine the most efficient method to train and assess CRM and whether
conceivable performance differences pre- and post- CRM training can be
empirically substantiated. This research project is being conducted with
a regional carrier and plans to transition the methodology to a major
carrier in a later phase. This project is designing and implementing a
prototype CRM training program based on a task analysis methodology. The
research will evaluate the effects of this specific CRM training on the
Line, LOFT, and LOE performance of crews. This study is also integrating
CRM performance requirements or procedures into the standard operating
procedures of the air carrier. CRM procedures are the implementation of
specific calls, checks, and/or guidance into one of more of the
following: normal checklists, Quick Reference Handbook, Abnormal
/Emergency Procedures, Flight Standards Manual, additional Job aids.
This can be viewed as translating critical CRM principles into CRM
procedures.
In developing the prototype advanced CRM course at the regional carrier,
data from line operations, instructor comments and ratings, along with
findings from the NTSB commuter safety study were used as the basis for
the CRM training design. This data was incorporated into a
proceduralized management system specifically tailored to the needs of
this regional carrier. This advanced CRM course has been given to pilots
in the research fleet. Their performance in a LOE was assessed prior to
this training and is currently being assessed after the training course
was completed with an appropriate time lapse. The central focus of this
research is to determine if a procedularized system will increase pilot
performance, not only that pilots will use the training and system but
does using this approach to CRM actually increase pilot performance and
thereby increase safety. This research has thus far proceduralized: Team
Management; Crew Communication, Decision Making, and Situation Awareness
in the operational environment of the regional carrier.
The proceduralized CRM training course is complete, and has been given
to flight crews. The Quick Reference Handbook and the normal procedures
have been rewritten to reflect proceduralized CRM.
Data analysis of the base line performance data showed some interesting
results regarding instructor/evaluator ratings. In the research process
it was necessary to train evaluators to collect data during the LOEs.
The evaluators are line pilots working in the training center. One of
the critical questions centered on whether the evaluator training was
successful and would result in reliable and valid CRM assessment. The
analysis showed that the LOE assessment process, which was taught in the
evaluator training, going from ratings of observable behaviors to
technical and CRM ratings, to overall Pilot in command (PIC), Second in
command (SIC) and Crew ratings for each event set was confirmed.
Observable behavior ratings significantly contributed to both technical
and CRM evaluations of each crew. This confirms that with appropriate
training and calibration, evaluators can use specific, observable
behaviors as the basis for judgements which should increase the
objective component of CRM evaluation in an LOE and ensure more fair,
unbiased evaluations of each pilot.
CRM ratings, across event sets, as well as technical ratings
significantly contributed to the overall evaluation of PIC and SIC .
This confirms that evaluators, when properly trained and calibrated, can
consistently integrate CRM evaluation with technical performance to
obtain overall evaluation of crew members on each event set. This is
evidence that the LOE evaluation was reliably tapping CRM as well as
technical performance. This is important because, in the past, there
were questions as to whether CRM ratings were just a reflection of
technical performance. It has been suggested that evaluators could not
or would not rate CRM behavior as a separate performance domain, but
part of the entire crew performance.
Additionally, the analysis showed that Captains and First Officers were
evaluated differently. In evaluations of the entire LOE, CRM performance
was more important than technical performance for the PIC, while
technical performance was more important than CRM performance in rating
the SIC. These differences in evaluations are congruent with holding the
PIC more responsible for CRM as part of the Captain\'s role. These
findings are also congruent with previous findings that Captains state
that the most important feature of a good first officer is technical
competence and First Officers state the most important feature of a good
Captain is CRM competence.
Further analysis showed stronger relationships of Captain evaluation to
Crew performance compared to First Officers. This provided additional
evidence that Captains are held more responsible for crew performance
particularly CRM performance. This empirically confirms that Captains
are the focal point for CRM and crew performance and suggests additional
training on establishing and maintaining CRM should be performed in
upgrade training when a First Officer transitions to Captain.
LOE data was compared with the data from traditional proficiency check
of specific maneuvers. The proficiency check evaluations could predict
about 50% of the overall evaluations of PIC and SIC on the LOE. This
confirms that the technical proficiency emphasized by the traditional
check is relevant to LOE performance. However, the remaining 50% of the
variance unique to the LOE confirms that the LOE is also tapping a
distinct type of performance in addition to technical proficiency. More
detailed evaluation of proficiency check assessments showed that only
evaluations of the SIC do not predict LOE results. Additional analyses
are required to better understand the role of rating SIC performance in
proficiency checks.
Analysis of different event sets found significant differences in the
performance of the targeted observable behaviors. For specific event
sets, the targeted behaviors (e.g. specific briefings) were observed
significantly less often. Isolation of performance problems across crews
can be used to rationally and efficiently change pilot training. The
lack of specific observable behaviors can be tied to specific
instructional objectives using an instructional database such as the
model AQP database. The database can also be used to find the specific
training components for these objectives that must be strengthened. This
analysis shows that isolating poor performance across crews can be used
to directly change relevant components of training.
The procedularized CRM concept has been extended to a major carrier
where CRM procedures were integrated into a QRC for emergency
procedures. The development and implementation of the QRC represented a
fundamental change in how the carrier addressed emergency procedures in
the past. The objectives of employing the QRC were to reduce the number
of memory items which can lead to operational errors, and to ensure that
all critical actions are taken in sequential order, eliminating errors
of commission and omission. The study was initiated to validate the
usefulness of the QRC and to identify design problems, training issues
and overall ability of the QRC to improve system safety. The study
assessed 124 crews performing checkrides with the QRC or by the
traditional memory immediate action items. The crews were assessed on
the following elements:
Timing of the crews from the beginning of the Emergency event until
the completion or the initiation of reference action items.
The timing of when each action of the checklist was initiated.
Errors in crew performance caused by omission of checklist items.
Errors in crew performance caused by omission of checklist items.
Errors in crew performance caused by addition of items to the
checklist.
Errors in crew performance caused by not following the sequential
order of the checklist.
Overall crew performance
Crew survey and feedback from on QRC philosophy
Specific timing events on critical checklist
The data indicate that the QRC checklist significantly reduced crew
error in checklist performance. This was measured in errors of omission,
commission and order. The QRC checklist received overwhelming approval
by the line crews participating in the study. Significant changes were
made to the QRC during the study improving the product based on line
input. The data also show that the QRC does increase the time for
completion of the emergency checklist. However, with the increased
accuracy crew performance is actually enhanced. Further, QRC crews
received overall higher ratings in CRM particularly in the areas of
communication and workload management.
A paper was written describing the study results and distributed to
industry, 1/98.
Work was continued with several carriers to identify appropriate
questions, data collection strategies and statistical methods to analyze
pilot performance data. This data collection system will allow carriers
to evaluate their AQP training effectiveness in many dimensions. The
overall goal of this part of the research is to determine the
appropriate data necessary to extend training intervals for AQP
programs. Extensive AQP statistical analyses activities have been
performed on data from major and regional carriers.
In order to insure that reliable and valid performance data is being
collected by carriers and being reported to the FAA this research team
found it necessary to address rater calibration issues. The overall goal
of this segment of the research is to assist carriers with incorporating
interrater reliability training strategies into existing
instructor/evaluator (I/E) indoctrination training. This project
involves: Selecting and evaluating existing videotapes or crew
performance to use as \"gold\" standards for the I/E indoctrination
class; developing behaviorally-based grading sheets for the selected
video tapes; and collecting and analyzing data from indoctrination
classes on levels of agreement and emerge as a result of training.
This rater training has continued at major and regional carriers. The
purpose of this training is to convey the importance and
knowledge/skills necessary for instructor/evaluators to provide stable,
reliable and accurate assessments of pilot performance. Continuing
refinements have been made to the inter-rater reliability software,
(developed earlier in this research) instruction materials and the
process itself. Some of the improvements include better feedback to the
instructors, a training guide for conducting inter-rater reliability
training, and a new summary report for the IRR session. This summary
report closes the loop from IRR training to fleet captains and managers
and facilitates the needed changes in flight standards operations.
This research team has developed an entire Instructor recurrent training
package for Aer Lingus in an effort to take the research results to the
international community. This training was delivered to Aer Lingus 1/98.
**Products:** A cockpit management training system. Research report on
performance differences due to proceduralized CRM training. Inter-rater
reliability training. Pilot performance analysis systems.
**Project Title:** *Crew Resource Management: Design and Evaluation of
Human Factors Training in Aviation*
**Performing Agency:** The University of Texas, Austin
**Background:** This research consists of several projects that center
on evaluating the impact of CRM and LOFT and developing methods to
optimize training and performance evaluation. This research group has
maintained an international, longitudinal, data base of pilot
performance since the late 1980\'s. Prior findings from this work
indicate that formal CRM programs combined with LOFT have a significant,
measurable positive effect on crew behavior and attitudes and by
inference on system safety. However, the data also indicate that all
human factors problems in aviation have not been solved by the current
CRM and LOFT programs. Specifically the following negative outcomes have
been documented through this research program:
\(1\) There is great variability in the impact of programs and in
observed crew performance, even after implementation of CRM training.
Incomplete acceptance of CRM concepts and practices by instructors and
evaluators has been identified as one source of problems.
\(2\) In the absence of continuing reinforcement behavior and attitudes
regress almost to pre-training levels.
\(3\) LOFT programs in several organizations show great variability in
execution and impact.
\(4\) Considerable controversy remains regarding the evaluation of
individual and team performance, as required of organizations
participating in the Advanced Qualification Program (AQP).
\(5\) There is an absence of reliable data on the human factors of
incidents occurring in the aviation system.
\(6\) Recent investigations of major accidents including air carrier
crashes have shown that organizational cultures have a profound impact
on operations and on the effectiveness of human factors programs.
\(7\) Human Factors training and awareness in Air Traffic Control (ATC)
has lagged behind programs in air carrier operations.
\(8\) Human Factors aspects of cockpit automation are not being
addressed in most CRM/LOFT programs and have been identified as critical
in a number of accidents.
**Project Description:** The research program consists of several
projects that centers on evaluating the impact of Crew Resource
Management (CRM) and Line Oriented Flight Training (LOFT) and developing
methods to optimize training and performance evaluation. Research
findings from this work indicate that formal CRM programs combined with
LOFT have a significant, measurable positive effect on crew behavior and
attitudes and by inference on system safety. However, the data also
indicate that all human factors problems in aviation have not been
solved the current CRM and LOFT programs. Specifically the following
issues have been documented through this research program:
This research program is designed to build on current knowledge and to
address the issues noted above. This research program has developed and
maintains a massive longitudinal data base on the effectiveness of CRM
in the Aviation industry. Operational line and LOFT observation data
comprise the data base. Confidential data are entered into the data base
and reports are delivered to each participating carrier. This
information is used to remedy the weaknesses apparent in the
observations or to highlight strengths. It is common practice for
carriers to use these reports to base the following year recurrent
training. This research group disseminates research findings to
scientific meetings and is widely published each year.
This project has developed an observational methodology for assessment
of crew performance in line operations. This line audit approach using
the Line/LOS Checklist (LLC) employs a team of expert observers to
collect systematic data on line operations ***without jeopardy*.** The
research team collect data in each organization giving a common
comparison point that allows comparisons of performance across
organizations. To date, line audits have been completed in five major
airlines. A large, multivariate analysis of the total data is in
progress that will form the basis of technical reports and doctoral
dissertations. The results show large differences in human factors
practices between organizations and between fleets within organizations.
A side benefit of the audit process is that organizations have used the
findings to target specific issues during recurrent training.
*Error Management.* The project has recently refocused CRM training on
error management. Curriculum issues of error management CRM are being
developed. This change in emphasis is mirrored by a revision of the LLC
to capture the dynamics of error management and the relationship with
other aspects of flight management. This should result in new training
emphasis for instructors and evaluators. Presently, this training is in
place at a major carrier.
*The Role of Cultures.* The research group is collecting data from
different national and organizational cultures to determine how culture
effects crew performance. The goal is to develop training guidance for
carriers employing cross-cultural cockpits or for carriers operating
with non-Western cockpits. One of the side benefits of the investigation
of culture has been the discovery that automation use varies
significantly as a function of culture.
*Automation.* Because flight deck automated systems can execute most
control functions performed by pilots, the flight management computer
has been likened to an \"electronic crewmember\". This view of
automation has led to speculation that the manner in which crew members
interact with the FMC may influence crew behavior and performance. The
link between interpersonal flight management attitudes and performance
in aviation suggests that attitudes regarding flight deck automation are
likely to be related to pilots\' use of automated systems and overall
performance. This research project has collected data from more than
10,000 pilots from more than 10 cultures addressing attitudes towards
automation. Analysis of this data showed significant fleet,
organizational and national differences in both general attitudes
regarding the conduct of the flight and attitudes regarding the use of
flight deck automation. Currently, this research project is
investigating these issues with an expanded methodology and will further
explore the link between national differences in attitudes toward
automation and a multi-dimensional model of national culture.
An initial finding regarding national culture and automation resulted in
a new emphasis on automation training and use within the U.S. A new
survey was developed in collaboration with pilot groups and airline
personnel. Data were collected from most US carriers regarding
automation training and use. Use of automation has also become a central
element of the line audit process using the LLC.
One of the critical elements of the project is observation of how crews
actually use automation in line operations as part of the line audit
approach. Data show, for example, that concepts taught by carriers in
philosophy or automation courses do not uniformly find their way to the
line. One of the project goals is to identify better strategies to
integrate CRM training and automation training and facilitate transfer
to line operations.
*Validating the Importance of Behavioral Markers in world wide
aviation.* This research is correlating US line audit data, that uses
the behavioral markers developed under this project, with a world wide
accident data base. This is being done to develop specific
recommendations to reduce CFIT and approach and landing accidents in
collaboration with Flight Safety Foundation. An additional goal of this
project is to validate further the role of the behaviors markers defined
in the Line/LOS CHECKLIST in safety. The results are also being analyzed
in the framework of the NTSB\'s 1994 Safety Study to determine common
casual elements worldwide and in audit data. A report with recommended
strategies to reduce accidents will be issued in FY98. This is being
done in order to determine the influence of certain cockpit behaviors
and accidents worldwide rather than just in the United States.
*Optimizing Air Safety Action Partnership Data.* This project, in
collaboration with several major airlines, is developing a self-report
human factors checklist to be used by crews to report incidents to their
parent organization. This effort is in support of the FAA\'s Aviation
Safety Action Program designed to elicit reports from crew members under
non-jeopardy conditions. the project\'s further goal is to develop a
statistical methodology to integrate data from surveys, line audits,
formal evaluations and incident reporting systems to provide the most
comprehensive and valid picture of an organization\'s operations. In
collaboration with the FAA, these de-identified data can also provide a
valid picture of elements of the aviation system.
*Cabin Safety Issues.* An extension of the research to examine issues
related to safety and CRM training for cabin crewmembers has also been
undertaken. A new survey instrument was designed and data have been
collected from more than 2,000 flight attendants at a major airline.
Results pointed to a number of safety-related issues and problems in
leadership between the cockpit and the cabin.
A large number of direct observations along with instructor and line
check airmen comments have been analyzed regarding incidents that were
successfully and safely resolved. This data can be used to develop
training scenarios and is available to air carrier training departments.
*CRM for Regional Carriers.* A segment of the work done recently by this
program was to analyze the particular CRM requirements of the regional
carriers. This research suggests that regional CRM programs should focus
on specific elements of the commuter environment. The programs must
address low experience level and high turnover of both pilots and flight
attendants. Also, pilots may be thrust into automated equipment without
extended training in non-automated equipment which may affect trust in
the automated systems. Also, these programs must address the
environmental variables: high frequency, low altitude, turbulence and
small airports.
*Performance in LOFT.* Another component of the program focused on the
effectiveness of LOFT. The goal is to determine the key components for
high quality LOFT. Scenarios were analyzed for appropriate workload,
creative problem solving required, problem realism, and simulator
mechanical condition. Briefings were analyzed for how did the instructor
integrate the crew into briefings, how was a review of CRM concepts
handled, and instructor enthusiasm. Scenario execution was also analyzed
for simulator operation, flight attendant roles, adhering to script and
radio calls. Debriefings were analyzed for crews involvement with
self-appraisal, the comprehensiveness of the debrief, and the
integration of technical and CRM. Findings showed that, overall, the
briefing and debriefing quality were the most important aspect of LOFT
quality followed by the quality of the scenario and least important was
the scenario execution. These findings were made available to the
Airline Transport Association subcommittee on LOFT development.
*Air Traffic Control Research.* This research program also investigated
team and group determinants of performance in the Air Traffic Control
system. This project was conducted with the Southwest Region to
investigate the relationships between the behavior of organizations,
work teams and individuals and three possible operational outcomes: loss
of separation, acceptable performance (absence of remarkable event) or
outstanding performance in the presence of increased challenge. Data for
each type of outcome have been collected and specific behavioral
predictors of each outcome determined. The results were reported in a
doctoral dissertation, a technical report and a forthcoming paper.
Results have also been presented at industry meetings.
**Products:** Research methodologies and data collection tools.
Technical reports and scientific papers (available on the project\'s
homepage, www.psy.utexas.edu/psy/helmreich/nasaut.htm.) Presentations of
project results have also been give at industry and scientific meetings.
Robert Helmreich serves on ICAO\'s Human Factors Team, to deliver
training in human factors to airlines around the world. During the
project\'s tenure, seven doctoral dissertations have been completed.
Most of these Ph.D.s are working in aviation positions.
**Project Title:** *An Investigation of Training Issues Concerning the
Advanced Qualification Program (AQP)*
**Performing Agency:** Battelle Memorial Institute, Columbus, Ohio
**Background:** In an attempt to encourage the use of innovative
training programs the FAA as proposed the concept of Advanced
Qualification (AQP) training. Central to AQP is proficiency based
training. Under AQP, carriers who have applied for inclusion in the
program can develop their own proficiency objectives, which must address
the range of conditions and contingencies that might be faced by pilots
working within the carrier\'s operational domain. These proficiency
objectives define the set of skills and tasks a pilot must be able to
perform to be proficient on a given aircraft type within the carriers
operational domain. The goal is to ensure that the training program
meets each carrier\'s specific requirements and does so in the most
efficient way possible. Utilization of a strong analytical frame work
for developing a carrier\'s program helps to ensure that training is
systematically oriented towards those objectives of greatest relevance
to the individual carrier and also supports meaningful crew and program
evaluation. One of the objectives of AQP is to provide seamless
integration of CRM and technical skills within the curriculum to ensure
that CRM skills are practiced together wit all other flight skills and
procedures as required by each flight situation. One goal of AQP is that
CRM skills should be utilized as normal and inherent part of aircraft
operation little different form operating the automation or performing a
proper checklist.
While AQP permits significant departures from the traditional FAR
requirements for training and checking airmen, the price of that
regulatory flexibility is a detailed front end analysis, the methodology
for which is described in Advisory Circular (AC) 120-54. Accomplishing
the analyses necessary to create AQP qualification standards has proven
to be particularly challenging for participating air carriers. Training
developers have had difficulty selecting an appropriate level of
analysis detail, efficiently executing their analyses and determining
how to incorporate cognitive and crew resource management considerations
in a manner that will generate meaningful proficiency objectives,
standards, and conditions. These difficulties stem, in part, from the
fact that as a new program, AQP lacks concrete examples for reference
purposes. The methodology was developed by the FAA on an a priori basis,
with the explicit intention that it be refined subsequently as
experience with the new programs accumulate. There was a need for a
methodology that, if faithfully followed, would produce an effective
AQP.
**Project Description:** The goals of this research project are to
assess whether the Instructional Systems Design (ISD) process can be
effectively used to develop a prototype AQP, including specification of
the process that derives learning objectives from the task analysis; (b)
determine whether the ISD methodology needs to be modified so as to best
support AQP development; and © verify the modified ISD methodology that
has been standardized through the development of a database comprised of
templates and instructional guidance for developing an AQP.
The approach to integrating CRM into technical training adopted by this
research utilizes ideas from several sources: (1) ISD methodology used
for AQP curriculum development (2) The event set approach developed in
prior AAR-100 research and (3) The situation assessment model being
developed by this research team for the Model AQP. Each of these sources
provide a useful and unique perspective. The ISD methodology, as
currently implemented, focuses of the technical skills, knowledge and
procedures required to accomplish specified tasks and subtasks. The
methodology is especially effective for activities that occur at
predictable times and in a standard order. The event set approach, in
contrast, focuses on a selected sequence of situations which attempts to
mimic real-world situations with all of the attendant complexity. The
objective is to evaluate crew performance in situations that require
pilots to utilize both technical and CRM skills. This approach is
currently used by many carriers to support line operational simulation.
This research project\'s situation assessment model attempts to provide
a cognitive perspective by focusing on those factors that influence a
flight crew\'s assessment of a situation and subsequent management of
available resources. In the past there has been little continuity
between the task-oriented front end analysis provided by the ISD
methodology and the situation-oriented event set approach. This lack of
continuity is exemplified by differences in types of CRM skills
addressed by each approach. The ISD methodology is best suited to handle
phase-specific skills, that is, those activities which are always
performed by the crew for a given task or subtask. Traditional ISD\'s
behavioral orientation supports its emphasis on the specific task and
subtasks that must be performed to complete a job.
This task orientation does not support those aspects of the pilot\'s job
which fall outside of the sequential tasks and subtasks found in a task
list. Instead, the unique dynamics of the aviation environment
necessitate a change in focus to the situation as a whole, including
conditions under which a task or subtask must be performed (e.g.
weather, aircraft system, failure and the requirement to utilize phase
-independent flight management skills either on a need basis or
continuously to ensure that the flight is properly managed. Appropriate
utilization of phase-independent skills depends upon crew judgement:
Accurate assessment of the requirements of the situation together with
effective utilization of those skills and information sources most
likely to be useful in that situation. This judgement depends upon an
understanding of the situation as awhole, not simply the task in
isolation.
This situational focus is the strength of the event set approach. An
effective training program will enable flight crews to experience these
situations so as to allow them the opportunity to practice the
phase-independent skills required to cope with these situations.
Both the ISD and event-set methodologies bring important and unique
perspective to an AQP. Merging them into a coherent approach will
support the development of a complete training program. One means by
which this integration can occur is to place the focus of flight
training on situations rather than tasks throughout the program rather
than waiting until LOFT. A situational orientation throughout training
helps to ensure that phase-specific and phase-independent technical and
CRM skills are practiced in an integrated fashion. In addition, the
situational orientation gives flight crews the opportunity to practice
those skills involved with assessing situations and utilizing available.
This transition from the task focus of the ISD methodology to situation
orientation takes place in the Model AQP by means of the concept of an
event. An event includes a specific task (i.e. a maneuver or set of
procedures) together with the conditions (weather, malfunctioning
aircraft system, etc.) under which the task is to be performed. To
handle an event successfully requires that the crew quickly and
accurately assess the situation, plan how to manage the event and
utilize the technical and CRM skills appropriate for that event. In
addition, the set of events included in curriculum can be selected to
ensure that important technical and CRM issues are addressed. Each event
has a specific topic or theme that is the point of that event. The
flight training curriculum can be designed by strategically selecting
and positioning events in accordance with these themes.
One of the strengths of the event concept is its applicability to both
ground and flight training. Continuity throughout all parts of an AQP is
a critical goal for the Model AQP project. Events can be used as the
buildingblocks for both the ground and flight training curricula. For
ground school, one of the goals of the Model AQP is to utilize
scenario-based training, where students would be required to not only
acquire new information but also learn how to apply that information to
solving problems. Events are a natural tool for designing a
scenario-based ground school curriculum. Similarly, events can serve as
the individual units for FTD and simulator training. Finally, they will
continue to serve as the building blocks for LOS scenario development.
The first generation Model AQP which has been targeted to regional
carrier training, has been completed and is in use by approximately 20
carriers. Several workshops have been conducted to train air carrier
personnel in the use of this model.
During FY 98 development will begin on an Advanced Model AQP
incorporating many features requested by the carriers and allowing each
carrier to pursue its own level of development.
**Products:** Model AQP and research report delineating process,
methodology and lessons learned. Advanced Model AQP.
**Project Title:** *LOFT Debriefing Study*
**Performing Agency:** NASA Ames
**Background:** Training effectiveness of LOFT simulations is heavily
influenced by the debriefing that occurs afterwards. The LOFT simulation
is a very busy, intense, and sometimes stressful experience. Thoughtful
discussion after the experience is necessary in order for the crew to
sort out and interpret what happened and to consolidate the lessons
learned into longterm memory in a form that can be used later in actual
line operations. The debriefing is a window on the entire CRM process.
LOFT debriefings can demonstrate how well crews are able to analyze
their performance along CRM dimensions. It is thought that in order to
implement CRM effectively in day-to-day line operations crews must have
the skill and the habit of analyzing their own performance in terms of
CRM.
**Project Description:** The purpose of this project is to determine
which techniques are actually being used by LOFT instructors, how
effective the techniques seem to be, the extent to which those
techniques are consistent with FAA Advisory circular guidelines, how
practical the guidelines are for real-world training and what obstacles
instructors encounter in trying to teach to these guidelines.
Data have been collected from five major US air carriers. At each
carrier five to eleven instructors from different fleets, made
audiotapes of the debriefings they conducted. The audiotapes are
transcribed and coded, generating a large database. Findings are as
follows:
\(1\) Typically, the debriefing is scheduled after the practice of
proficiency maneuvers, rather than immediately after the LOFT.
Interposition of the proficiency maneuver practice constitutes and
\"interference experiment\" that probably impedes the ability of the
crew to remember what happened in the LOFT.
\(2\) The similarities among carriers are greater than differences in
how they conduct LOFT and LOFT debriefings. There are large differences
among individual instructors within carriers in facilitation
effectiveness.
\(3\) Most instructors conscientiously attempt to elicit crew
participation, but some unwittingly sabotage their own efforts with
behaviors that discourage participation.
\(4\) Most instructors fail to make clear at the beginning of the
debriefing the nature of the participation that they expect of the crew
and do not explain why is important that the crew take an active role.
\(5\) Although instructors have been told to facilitate crew
self-debriefing, they have been given only very general advice on how to
do this. Training departments should provide much more explicit hands-on
training in facilitation and should mentor new instructors as they start
to facilitate.
\(6\) The content of the debriefing is strongly driven by the
instructor\'s observations and questions, rather than the crew\'s self
analysis.
\(7\) The crews are responsive to the instructors, but are more reactive
than proactive.
\(8\) Most crews would probably have difficulty in conducting a deeply
analytical debriefing on their own, however they appear to be quite
conversant with and accepting of CRM and could with practice develop
debriefing skills and apply them routinely on the line.
This data and analysis has resulted in major carriers developing a list
of do\'s and don\'ts for facilitators and is being used as the core of
annual recurrent training for instructors.
The findings from this research will be incorporated into a CBT training
system for instructors at a major and regional carrier in FY99.
**Products:** CRM Debriefing training guidelines were distributed in FY
97. A handbook for instructors was developed and distributed in FY 97.
The handbook was also incorporated into the instructors manual for
Leadership/Followership curriculum development at Alaska airlines,
distributed 5/98.
**Project Title:** *A methodology for developing Gold Standards for
Rater Training Video Tapes*
**Performing Agency:** NASA Ames and University of Central Florida
**Background:** A central issue in the Advanced Qualification Program
(AQP) is how to train check airmen to provide reliable, consistent, and
valid assessments of Crew Resource Management (CRM) skills. It has been
suggested that to enhance reliability of CRM assessment, measures should
focus on clearly defined observable behaviors. These behaviors should be
explicitly identified so that no ambiguity exists for check airmen
conducting CRM assessments. Raters should be calibrated so that check
airmen are consistent in their evaluations. Check
airmen should be trained by rating and discussing video tapes of
aircrews. The purpose of the present project was to develop and validate
a methodology for constructing gold standards video tapes for rater
training.
**Project Description:** The purpose of this present project was to
develop and validate a methodology for constructing a \"gold standard\"
for rater training video tapes. Gold standards are defined as criteria
that are assigned by experts to a training video tape. These tapes can
be used of training rater reliability and accuracy.
To meet this objective, a five step methodology was developed.
Step 1 Select Video Tapes of LOS Scenario
Step 2 Develop Gold Standards Data Collection Forms
Step 3 Conduct Gold Standards Development Meeting
Step 4 Analyze Gold Standards Data
Step 5 Establish Gold Standards
The methodology was tested at an air carrier that was interested in
developing gold standard video tapes for check airmen rater calibration
training. CRM, technical and event set gold standards were developed for
a video tape of a crew performing an LOE scenario.
**Products:** A technical report was published and distributed to
industry in 3/98.
**Project Title:** *Integrating CRM into Crew Procedures: Checklist
Standardization*
**Performing Agency:** NASA AMES
**Background:** Non-compliance with checklists has become a potentially
serious problem for air carriers and the FAA. In today\'s aviation
system, procedural changes occur frequently and are instituted for a
large variety of reasons; company mergers, changes in air traffic
procedures, changes in airport environments, introduction of new
technologies and new aircraft, etc. While one obvious goal is to
maintain compliance and standardization of crew member performance,
there must not be a sacrifice in the match between procedures and the
operational realities in which the procedures are to be used. Not only
must procedures reflect a reasonable match to technical task demands,
they must reflect consistency with company and system requirements.
Within an air carrier for example, philosophy, policies and procedures
should be made consistent both within teams (within aircraft type) and
across teams (across fleets within the company) to the extent that
standardization is feasible. Since there are legitimate aircraft and
mission differences across fleets, a means of evaluating the appropriate
level of standardization must be developed and reviewed when changes are
anticipated.
**Project Description:** The goal of this research project is to
integrate CRM principles into crew roles and procedures in order to: 1)
improve the match between current procedures and operational reality,
and 2) develop a process for adapting procedures to anticipated changes.
The basic approach is to analyze procedures from a team perspective and
to conduct a team task analysis in order to assess whether current
procedures match the task flow including team processes. The integration
of CRM principles into the task analysis provides the basis for
reviewing and re-designing procedures. The development of standard
methods and measures for evaluating procedure usage is important for
assessing both current and proposed procedures. Measures used during
research process will be refined for validation purposes as well as
eventual use in training.
The objectives of this research project are to develop a systematic
approach to checklist standardization across all fleets, to develop
guidelines for implementing and evaluating procedure changes that
optimize, 1) within company standardization, 2) compatibility with
aircraft and operational differences and 3) that the procedures are
consistent with CRM principles. This research is complete has
established company-wide philosophy and policy statements: Operations,
Automation, Training, and Checklists. Also, methods for data collection
have been identified and developed. Pilot feedback on proposed checklist
changes has been completed.
**Products:** Guidelines for standardization of procedures.
*Note:* This project led to the following project: Operating Documents
Human Factors Project
**Project Title**: *Operating Documents Human Factors Project*
**Performing Agency:** NASA Ames; George Mason University
**Background:** The original project described earlier was intended to
develop a systematic approach to checklist standardization and to
develop guidelines that would optimize within-company standardization
for eight fleets, to insure compatibility with aircraft and operational
differences and be consistent with CRM principles. This project
considered the form of the checklist with respect to content, structure,
logic, format, terminology, roles and usage. However, this approach was
inadequate as checklists are part of the whole operating document
system. It became apparent that operating documents must show internal
consistency across fleets (aircraft types, and route structures) across
departments, pilot\'s handbooks, company policies, etc.) Further, these
documents must be externally consistent with regulations and
manufacturers. Document systems must be consistent across philosophies,
policies, procedures and practices. This concept is not in place in the
air carrier industry.
**Project Description:** This research team developed surveys and held
workshops to bring together air carriers (including regionals and
cargo), manufacturers, and the FAA to work on a better, more human
centered approach to these document systems. Two workshops were held in
FY 97. The most recent workshop was attended by 78 participants,
indicating industry\'s interest in this topic.
Based on the information provided on the surveys and in the workshops,
guidelines are being written for the development of operating documents
that will include: the Organization of Documents, Standardization of
Documents, Usability of Documents, Developing and Maintaining Documents,
and Transition to Electronic Media.
Feedback from the air carriers indicate the need for additional
workshops. The structure and content has not been determined nor has it
been determined whether this process should be turned over to industry
to lead. Feedback from internal FAA sponsors indicate that the
integration of AQP documentation should be considered in future work by
the research team. This focus is presently being considered.
**Products:** Reports from the two workshops have been written and
distributed to industry, 1/98.
**Project Title:** Team Situational Awareness
**Performing Agency:** Naval Air Warfare Center, Orlando
**Background:** There is little question that situational awareness is
critical for safe flight. Much research has centered on attempts to
identify and quantify individual situational awareness. However, since
cockpit crew performance depends heavily on team processes, it is
necessary to determine exactly what aspects of individuals and the
environment either enhance or degrade team situational awareness.
**Project description:** This research project has identified a model of
team situational awareness, developed effective instructional strategies
to improve situational awareness training, developed situational
awareness assessment tools, and developed guidelines for situational
awareness scenario development.
The initial framework for team situational awareness has been completed.
This framework will serve as a basis for the team situational awareness
model. Preliminary training guidelines based on this framework, follow:
\(1\) Tailor training to the experience level of the crew in terms of
time in aircraft, time in position, and familiarity with locality. For
example: Consider a newly hired first officer or flight engineer that is
transitioning to or learning a new aircraft and flying out of a new
area. It is important to ensure that the crew member is familiar with
cockpit roles, the geographic area, and the aircraft equipment before
expecting him/her to have the awareness to handle dynamic problem
situations in that environment.
\(2\) Ensure job/task analysis provides information about the cognitive,
perceptual and behavioral demands required for situational awareness.
For example: A job analysis of a pilot who flies a highly automated or
\"glass cockpit\" aircraft should solicit information particularly
relevant to that environment, emphasizing factors such as information
seeking from different sources, collation and interpretation of
information from complicated displays, scan through the FMS, mode errors
with the FMS, manual data entry task demands, and communications
associated with the advanced technology.
\(3\) Include training which specifically focuses at the team level of
situational awareness in addition to training which focuses on
individual skill development. For example; Individual skill development
in situational awareness may include: providing information that
increases the individual\'s knowledge base(so that he/she knows what
information to seek and when) helping in the development of planning
skills, so that he/she is better prepared for completing tasks within
the flight; and providing tips that help free up time from basic tasks
in the cockpit, so that more attention may be paid to the situation.
Team skill development in situational awareness should include team
process skill training such as communication and leadership behaviors to
enhance and maintain crew awareness.
\(4\) Based on the complexity of the situation, provide training which
emphasizes adequate information, demonstration, and active practice and
feedback, all are needed to produce a behavioral change. For example: To
enhance the overall training experience provided in a realistic LOFT
scenario emphasizing situational awareness, the crew members should
receive advanced preparation about the training objectives, including
specific information on the skills to be trained and demonstrations or
examples of effective and or ineffective behaviors relevant to those
skills. Providing general information about situational awareness
concepts would be insufficient to expect the crew to obtain the full
impact of LOFT. Crew members who are a low experience level need to have
specific information on the kind and timing of information transfer that
will enhance crew situational awareness. Alerting them to the importance
of communication, if they do not know what and when to communicate,
would not prepare them to practice good communication skill in the LOFT
session.
\(5\) Design training scenarios to be realistic and to elicit the
desired cognitive, perceptual and behavioral task demands encompassing
the situational awareness construct. For example: Consider that
including an unfamiliar event, such as icing, for crews who have only
flown in Florida would require them to recognize the relevant cues,
comprehend their meaning and project a course of action. A very
different type of problem, such as a gradual change in an instrument due
to a developing condition, may require perception comprehension and
projection as well, but the cognitive and behavioral demands related to
this problem are very different from those imposed by icing conditions.
Including both types of problems within a scenario would allow the
trainee to exercise these different cognitive and behavioral skills, and
would help him/her to learn to generalize the application of these
skills across various problem situations.
\(6\) Conduct training which focuses on improving team or process skills
related to situational awareness(e.g.,planning, communication,
leadership) because this may aide the development of team situational
awareness. For example: Training focusing on communication skills
related to situational awareness can include: training that encourages
the flow of the information that needs to be transmitted in the planning
phase of the flight (e.g., what questions the Captain can ask to solicit
information, what questions the First Officer should ask, what
information should be covered with Flight Attendants.) It can also
include practice in the communications that are most effective (e.g.,
what information to provide to another crew member or when to
communicate the information to the other).
\(7\) Include training which emphasizes developing accurate and
appropriate knowledge structures for expectations related to situational
awareness. For example: Training a crew about how traffic flows around a
specific airport, prior to arriving there for the first time, helps the
pilots to understand what can be expected, thereby increasing the
readiness with which he/she can recognize that an abnormal situation is
occurring.
\(8\) Use realistic and dynamic scenarios to provide training on:
information seeking and processing; detecting anomalous information;
prioritizing attention to cues, especially when there is information
that may be related to different problems; and taking appropriate
actions based on cues. For example: Design realistic scenarios with
events that require crew members to: look for and use information;
handle multiple cues; determine when information is signaling a problem
or possible problem; and act on the information. Intermittent
fluctuations of an instrument during a scenario require crew members to
recognize the fluctuations and to diagnose the problem. This may include
cross checking instruments, discussing among themselves, and seeking
additional information. Putting this event in the scenario at the time
of moderately heavy workload or when another troubleshooting event is
occurring gives crew members practice in dividing their attention and
determining priorities.
\(9\) Design and develop performance measurement tools for the
behaviors, the knowledge and perceptions required for situational
awareness. For example: A realistic scenario provides information about
situational awareness behaviors and an observation scale can be
developed for those behaviors. Tapping into the crew member\'s knowledge
and perceptions may require asking questions, either during the scenario
or after it is completed to determine if he/she saw the problem and
understood its possible impact. For pilots with low experience levels,
questions can be either a part of the scenario (e.g., ATC can question
the crew members) or the scenario can be stopped briefly for questions
to be asked.
\(10\) Measurement tools should measure individual situational awareness
skills as well as team interactions related situational awareness. For
example; An observation scale can be designed that measures what
individual team members contributed to the team situational awareness
and what actions they performed independently that demonstrated their
situational awareness. The same scale should include opportunities to
document team interactions (e.g., planning, communications, and
leadership) that helped the crew members gain and maintain team
situational awareness.
\(11\) Situational awareness measurements of behaviors should include
both outcome and process measurements. For example: Outcome is the
action taken by the crew in response to an event (e.g., the crew
diverted to Airport A) and process is how they achieved the outcome
(e.g., the Captain gathered information from others about the decision,
crew members discussed the merits of each airport, the crew members
noticed that the runway at Airport B was not adequate for their needs).
Both are important to understanding performance.
\(12\) Include instructions and information about training objectives to
instructors about each training method or tool. Fro example: Write out
the specific objectives to be accomplished at the top or on a cover
sheet of scenario instructions. Include clear objective behaviors as
part of the scenario goals. The instructor is then informed about how to
use the measurement tool to re-enforce the training objectives.
\(13\) Link the measurement criteria to the scenario events and to the
debrief plans, for consistency in training. For example: If a generic
measurement instrument is used, prepare the raters to recognize and
document specific examples observed in the scenarios that relate to the
general behaviors on the rating form. It is likely that the raters will
need through training so they can map the scenario events and behaviors
observed to the rating form. Thus in the debrief, crew members will know
what specific actions they took and how those relate to general
requirements for situational awareness.
\(14\) Multiple measurements over time are necessary to yield a good
measurement of situational awareness; single measurements at one time
are insufficient. For example: In a single LOFT scenario, build a number
of opportunities for crew members to demonstrate situational awareness
(e.g., NOTA information, ATC calls to other aircraft, PIREPs, subtle
changes in instruments, weather, unexpected circumstances) and make sure
that observers know when, where, and how to observe and document
situational awareness actions. The same could be accomplished by using a
number of small scenarios (each with opportunities to observe
situational awareness) and then evaluating the aviator\'s situational
awareness across the scenarios.
\(15\) Use specific feedback tools along with realistic and dynamic
scenarios to provide feedback that; is specific to the trainees on their
situational awareness skill performance; reinforces the development and
maintenance of relevant knowledge; and stresses adapting knowledge to
meet situation demands. For example: Give observers feedback forms with
the specific situational awareness elements that were built into the
scenario. Observers should use there forms to document behavior they see
in the scenario. This is then used to give specific feedback on what the
crew members did, how they did it, and the context of the behaviors.
Explanation of the rationale for the feedback helps the crew members
develop and add to their existing knowledge.
\(16\) Train instructors on making ratings and giving feedback. For
example: This training can be done by providing information to the
raters on situational awareness, showing them examples of the behaviors
associated with situational awareness (so raters can be knowledgeable
about the behaviors), giving them practice in rating those behaviors,
and giving raters practice in providing feedback on specific situational
awareness behaviors.
The above guidelines have been expanded, published and distributed in
2/98. The guidelines are too lengthy to be contained in this report.
Although these guidelines have received positive comments from the air
carrier training community there remains a fundamental problem with
situational awareness training and assessment. Several carriers believe
that new instructors, and line pilots, in general, are not able to
dissect pilot performance and to identify and articulate when and what
exactly led to poor situational awareness. Thus crews and instructors
are not adequately debriefing flight scenarios, either in training or on
the line. In response to this critical requirement this research team
will design a CBT based system to provide the fundamental principals in
situational awareness cue recognition. This system will be designed at
one carrier for pilot training and at another carrier for
instructor/evaluator training. It is expected to be complete in FY 2000.
**Products:** Situational Awareness guidelines. Situational Awareness
training systems.
**Project Title:** Training Pilot Not Flying (PNF) Back-up Skills
**Performing Agency:** Naval Air Warfare Center, Orlando
**Background:** Regional airline Captains indicate that one of the
greatest difficulties they experience is working with inexperienced or
new First Officers who lack the skill to effectively provide back-up,
when serving as Pilot Not Flying (PNF), to the Captain when it is
needed. Since the complex environment of regional flying necessitates
the coordination of the two crew members it is critical that this issue
be addressed.
**Project Description:** This research project identified the knowledge,
skills and attitudes necessary for PNFs to properly perform back-up
duties. In conducting this research, (1) structured interviews with
pilots from the regional airlines were conducted to inquire about
effective and ineffective back-up behavior, (2) the 100 most recent
submissions to ASRS database were analyzed using the descriptors of
\"regional airlines\" and (3) analysis of the recent NTSB report which
reviewed flight-crew involved major accidents of U.S. air carriers that
occurred from 1978 through 1990 and which identified poor
monitoring/challenging behavior on the part of the non-flying crewmember
as a causal factor in seventy-six percent of these accidents. Combining
information from these sources, three broad problem areas requiring
additional training were identified. (1) first officer or PNF
assertiveness in ambiguous situations, (2) monitoring and challenging by
the first officer or PNF, and (3) proficiency in technical and
communication procedures.
**Products:** Training guidelines have been developed, published and
distributed 12/97.
**Project Title:** Decision Making and Judgement on the Flight Deck
**Performing Agency:** NASA Ames; the Naval Systems Warfare Center,
Orlando
**Background:** NTSB reports in a four year period 1983-1987 crew
judgement and decision making was implicated in 47% of fatal accidents.
NTSB and ASRS cites many more reports where poor decision making was
evident in many potentially serious incidents. Decision making is a
component of most CRM courses and is encouraged by the FAA Advisory
circular 120-51, 1993. However, scientific research has not been
available to support this training. Decision making in the dynamic, time
constrained cockpit environment does not mirror decision making in a
static laboratory setting. Thus, findings from generic decision making
research do not necessarily generalize to aviation settings.
**Project Description:** Decision making is an essential component of a
Captain\'s expertise. The Captain is responsible for making the hard
decision, for example, choosing where to divert after a system
malfunction, when fuel is short and weather is deteriorating;
determining how to cope with passenger\'s medical emergency; evaluating
whether to take-off with a placarded system given past experience with
the projected weather and traffic at the destination. The captain\'s
judgement is most critical when conditions are ambiguous and no clear
guidance is provided in manuals, checklists, or company policy.
This research project has been in progress for several years and has
developed a model of factors that make flight decision efforts
difficult, along with a taxonomy of decision problems. This model
incorporated the nature of the problem, the time available to solve the
problem and the risks associated with the options. This work was based
on the analyses of crews facing abnormal and emergency events in full
motion simulators and further supported by NTSB accident analyses and
ASRS reports. Fro example, analyses revealed differences in the
importance of risk and time pressure between Captains and First
Officers. For Captains, risk was the most important variable in the
decision strategy, while First Officers viewed time pressure as most
important. As might be expected, experience does affect decision
strategies. Experienced crew members are more sensitive to available
decision time. better at handling uncertainty and have better
prioritization of information needs. Based on these results it is
suggested that to encourage effective decision strategies, crews are
trained to : (1) understand and verify the problem, (2) assess time and
risk, (3) rush to judgement, (4) consider constraints and consequences
of options so as not to oversimplify the problem, (5) use \"worse case\"
instead of \" best case\" reasoning, (6) plan for contingencies, and (7)
manage the situation by setting priories, assigning tasks and using all
available resources.
Presently, this research team is developing decision making training
scenarios for major carriers to validate during recurrent training. This
research project focuses on designing and validating assessment methods
and scales for the decision making scenarios. This research team is
developing training guidelines to manage risk in ambiguous situations.
The error taxonomy data base is being incorporated into the Rapid
Reconfigurable LOE project described earlier. This research team is
working with four major carriers to develop \"challenging\" training
guidelines.
**Products:** Decision making training and assessment guidelines for air
carriers to incorporate into their CRM training or into AQP will be
published in 1998. The \"challenging\" training guidelines will be
published in 1998.
**Project Title:** Interruptions. Distractions and Lapses of Attention
in the Cockpit
**Performing Agency:** NASA Ames
**Background**: Interruptions and distractions are on of the most common
causes of pilot error incidents and have contributed to many accidents.
One of the most striking of these accidents was the Eastern L1011
accident in the Everglades. Glass cockpits, rather than attenuating this
problem, have if anything amplified it. Closely intertwined with the
issue of interruptions and distractions are problems with habit capture,
tunneling of attention and failing to remember to perform deferred
actions.
**Project Description:** This study will analyze ASRS incident data and
NTSB reports, perform field observations of LOEs and LOFTs and will
conduct experimental research to probe the cognitive mechanism pilots
use to interweave concurrent tasks and manage attention in dynamic
response to competing demands of the overall job. This study will
characterize types of interruptions, types of situations conductive to
distractions and factors that impede recovery from distractions. From
this data specific training guidelines will be developed to aid crews in
controlling interruptions, recover from distraction, avoid habit capture
and prevent tunneling of attention. Also, this study will provide
methods to design interruptions and distractions into simulator training
to realistically challenge crew\'s task management skills and ways to
modify cockpit SOP to reduce this form of crew error.
A review of the literature is underway as well as the analysis of the
ASRS and NTSB data.
**Products:** Training guidelines and scenario development methodology.
**Project Title:** Establishing Relationships Between Flight Data
Parameter Values and AQP Qualification Standards using APMS methodology.
**Performing Agency:** JIL Information Systems
**Background:** The Automated Performance Measurement System (APMS)
project has as its overall goal the development of tools and techniques
to improve the efficiency with which air carriers collect and analyze
Flight Operational Quality Assurance (FOQA) data. That overall project
is not described in this report, details can be obtained from FAA Flight
Standards, AFS-230. This present project is closely related to the
overall APMS project in that this present project will be using APMS
developed tools to analyze simulator data for flight parameters.
The goal of this project is to develop methods and techniques within the
APMS research program that will allow air carriers to determine the
extent to which daily flight operations are consistent with training
qualification standards established in an AQP program. Thus, the overall
APMS project will develop the tools necessary to analyze FOQA data and
this project will identify flight parameters and qualification standards
links. The goals of this project are: (1) To develop a \"string\" of
flight data parameters and conditions that together would identify each
AQP Qualification Standard when used in a FOQA database query. (2) To
develop a system to acquire and record simulator flight data at the same
level of fidelity and resolution as an FOQA equipped aircraft and (3) To
develop a baseline flight data parameter profile of each AQP
Qualification Standard for use in evaluating aggregate performance of
these tasks in line operations based on FOQA data.
The software to collect the simulator data has been developed and is
being used by a major carrier. The research team is presently collecting
data on the flight parameters.
**Products:** Software tools and methodology to link FOQA data and AQP
qualification standards.
| en |
all-txt-docs | 178816 | April 25, 2000
The Honorable John T. Spotila
Administrator
Office of Information and Regulatory Affairs
U.S. Office of Management and Budget
The Old Executive Office Building, Room 350
Washington, D.C. 20503
Subject: Recommendations of Representatives of Small
Business Refineries under an EPA Highway Diesel Fuel Sulfur
Control Program with a Sulfur Limit at the Lower End of the
Range Proposed during the SBREFA Panel Process (5-40 ppm)
Dear Mr. Spotila:
At your April 19 meeting with representatives of small
business refineries, Tom Kelly of EPA extended an offer to
receive comments from such representatives regarding
recommended regulatory flexibility alternatives under an EPA
Highway Diesel Fuel Sulfur Control Program with a sulfur
limit at the lower end of the range proposed during the
SBREFA panel process (5-40 ppm). Enclosed are the
recommendations of eleven representatives.
We believe that the regulatory flexibility alternatives
recommended by these small business representatives have
merit under the Regulatory Flexibility Act, as amended by
the Small Business Regulatory Enforcement Fairness Act of
1996. EPA should seriously consider these alternatives.
Sincerely,
Jere W. Glover
Chief Counsel for Advocacy
cc: Bob Perciasepe, EPA
Margo Oge, EPA
Tom Kelly, EPA
Art Fraas, OMB
Small Refiner Supplemental Comments on Diesel Sulfur Standard
April 24, 2000
Mr. Jere Glover
Chief Counsel for Advocacy
U.S. Small Business Administration
409 Third Street, S.W.
Washington, DC 20416
Dear Jere:
Small business refiners producing highway diesel fuel want to
respond to the invitation, issued by Tom Kelly of EPA in a
meeting on April 19, to comment on the prospect of a sulfur limit
significantly lower than 50 ppm. As you know, during the short
time frame of the diesel SBREFA process, we were not aware that
EPA might require a much lower sulfur limit. We appreciate this
opportunity to reconsider and modify our recommendations in light
of such a prospect.
We have tried to build on the SBREFA panel work in developing
these comments. Unfortunately, the 50-ppm sulfur limit for small
refiners-the corner stone of the alternatives we recommended
during that process-no longer appears viable in light of the
prospect of a national sulfur standard significantly lower than
50-ppm. As a result, we are now placed in the uncomfortable
position of making recommendations that may provide little, if
any, flexibility for small refiners. We are very concerned that,
even with a delay of the gasoline sulfur or "Tier 2" standards
(both interim and final standards) until 2010 and an exemption
for an unlimited time from the ultra-low sulfur diesel standards,
many small refiners will be unable to remain in the market for
highway diesel fuel for long, to take advantage of these
alternatives.
The prospect of sulfur limit for highway diesel fuel in the lower
end of the 5-40 ppm range would significantly impact our
abilities to comply with a diesel rule by potentially increasing
capital costs and dramatically escalating operational losses
(with commensurate negative impacts on company earnings and
profitability), and by adding a level of technological
uncertainty that, when combined with the financial impacts of
"Tier 2" compliance may create a situation where necessary
funding is either not available to small business refiners or the
interest rates that are offered are prohibitively high. However,
in the spirit of SBREFA, we recommend the following set of
alternatives that should be considered as a package proposal,
even though, taken together, may still be of limited assistance
to small refiners. We want to reemphasize that there is no "one
size fits all" approach to providing flexibility for small
refiners. However, once again, there is a set of alternatives
(below) that may be more likely to be of assistance (e.g., an
automatic delay of "Tier 2" standards) than others (e.g., a
hardship provision under the diesel rule).
We have reached consensus and agree on the following priorities.
1. Delay of all or part of the 2007 Heavy-Duty Engine and
Vehicle Standards at least until 2010. A 50-ppm diesel sulfur
limit with not less than a 40-ppm average is of critical
importance to small refiners. An across-the-board delay of these
engine standards would allow producers of aftertreatment
technologies to continue researching and possibly innovating to
develop devices capable of withstanding higher levels of sulfur
in diesel fuel. It would also allow small refiners that would
otherwise have to comply with the diesel and gasoline sulfur
standards in virtually the same time frame to stage those
investments.
We would prefer that EPA delay the entire diesel rule because
that would preclude any need to produce ultra-low sulfur
diesel fuel for at least three years. However, if such an
across-the-board delay were not possible, we would recommend a
phase in approach that would maximize the likelihood of
continued markets for 500-ppm highway diesel fuel in the lower-
48 states (see point 3 below regarding an Alaska-specific
phase-in). First, a significant portion of the market (not
just small refiners) would have to be allowed to continue
producing 500-ppm diesel for some period of time, subject to
sufficient availability of the ultra-low sulfur fuel. If the
main barrier to a market for vehicles requiring ultra-low
sulfur diesel fuel is that consumers won't demand them in the
early years because there is insufficient availability of the
new fuel, then EPA would only have to ensure a sufficient
supply in year one. After that, the market would work
efficiently to supply and meet the increasing demand for the
new fuel and transition from the old to new fuel, provided
there were no backsliding from the year one requirement(s).
Second, most, if not all, small businesses should be exempt
from such year-1 requirement(s). If EPA decides to require
that retailers must provide ultra-low sulfur fuel wherever
highway diesel fuel is sold and/or that a certain amount of
refinery production of highway diesel fuel must be ultra-low-
sulfur, those requirements should be limited to those
retailers and refiners that have some threshold level of
throughput.
Alternatively, EPA diesel sulfur rules could recognize the
different fuel needs of different emissions equipment by
phasing in any standards lower than 50 ppm. Specifically,
because the particulate matter (PM) trap is relatively less
sulfur sensitive, PM traps (but not NOx absorbers) could be
required on new vehicles by 2007 whereas NOx absorbers could
be added later (e.g., 2010). The diesel fuel sulfur limit
could be lowered if technology has not improved sufficiently
to allow the use of a 50 ppm sulfur fuel.
Regardless of whether the entire rule is delayed or one or
more parts of it are phased in, we recommend that EPA conduct
a technological review before small refiners are required to
meet a national standard below 50 ppm, to determine whether a
lower standard is indeed still required.
2. Delay "Tier 2" Standards at least until 2010 for qualifying
small refiners. As noted above, delaying the entire diesel rule
until 2010 would allow small refiners that would otherwise be
expected to comply with both "Tier 2" and diesel sulfur standards
virtually simultaneously to stage those investments. Without such
flexibility and with the overwhelming increase in capital and
operating costs required to meet both rules almost
simultaneously, many small refiners will not be able to continue
in operation. However, if such an across-the board delay were
not possible, we recommend that EPA modify the current hardship
extension provision under "Tier 2" to automatically delay until
2010 the final "Tier 2" standards for small refiners that commit
to desulfurizing highway diesel fuel whenever national standards
become effective. We further recommend that EPA delay the
interim "Tier 2" until 2010. Finally, we recommend that EPA
provide for an additional delay of up to two years (until 2012)
for small refiners that require additional time. In general, we
are uncomfortable with hardship provisions because EPA tends to
disapprove most, if not all, applications for such waivers.
However, if criteria could be identified that would allow for
nearly automatic waivers (e.g., must comply with Tier 2 and
diesel sulfur rules virtually simultaneously), we would be more
comfortable with such provisions.
3. Alaska's special circumstances should be considered
separately from those of other small refiners and appropriate
solutions developed for that unique market. Petro Star continues
to strongly support an exemption for small refiners from the
ultra-low sulfur requirements for an unlimited time. Petro Star
believes that small refiners should be allowed to continue
producing 500-ppm diesel fuel for as long as they have legal
buyers (and assuming labeling and separate storage requirements),
and further that retailers should have the option of offering
only non-ultra-low sulfur fuel if they so chose. Petro Star does
not believe that there is any need for a retailer availability
requirement in Alaska and supports EPA proposals that any
"availability" problem in Alaska would be best addressed through
an Alaska-specific conference among EPA, the State, and the
various stakeholder groups.
4. Access to capital, a critical issue for all small refiners,
must be enhanced. We recommend three types of assistance:
$0.03 to $0.05/gallon excise tax credit for small refiners
for a limited time. A small refiner should receive an income tax
credit of $0.03 to $0.05 per gallon of diesel produced during the
first three years to defray costs of an investment in
desulfurization technology for diesel.
Increase in SBA maximum loan guarantee on pollution control
loans from $1 million to $5 or $10 million.
Implementation of an SO2 allowance program similar to the
original diesel desulfurization allowance system but enhanced to
represent more realistically the significant costs to small
refiners of this ultra low sulfur proposal.
We greatly appreciate your interest in our small businesses and
stand ready to provide additional information if and when that
might be helpful.
Sincerely yours,
Countrymark Cooperative (John Stern)
Frontier Refining (Gerald Faudel)
Gary-Williams Energy (Sally V. Allen)
Golden Bear Oil Specialties (Jerry Davis)
Kern Oil (Chad Tuttle)
Petro Star (Richard Curtin)
Placid Refining (Ron Hurst)
San Joaquin Refining (Larry Young)
U.S. Oil and Refining (Al Cabodi)
Western Independent Refiners Association (Craig Moyer)
Wyoming Refining Company (Bob Neufeld)
Additional Comments
Western Independent Refiners Association and Kern Oil
Small refiners previously have submitted data documenting that a
15 ppm standard is unfeasible and will severely impact small
refiners. Small refiner annual operating costs increase by $0.10
per gallon and maintenance costs also increase substantially, on
the order of $1,000,000 per year. This is over $0.08 per gallon
more than costs anticipated in connection with achieving a 50 ppm
sulfur limit. Small refiners simply do not possess the broad
operating flexibility, capital and other economies of scale as a
major oil company. At these levels, all distillate streams will
be directed through the diesel hydrotreater and additional
residence time will be required. Because of limitations on
hydrotreater capacities in refineries, substantial production
loss would occur. Achieving a 15 ppm standard is calculated to
result in production losses in excess of 30%. These production
losses not only exponentially increase per gallon costs but also
threaten the viability of the entire operation. There are also
numerous other technical and logistical issues facing small
refiners that have also previously been submitted.
It is important to note that small refiners have already reduced
sulfur in diesel by over 90% from the previous 5,000 ppm standard
down to the current 500 ppm standard. Please also note that a
further reduction down to a 50 ppm standard results in a
reduction of over 99%. A 50 ppm standard would represent the
single greatest reduction of any motor fuel specification, ever.
Consistent with all control technologies, the small refiner costs
become exponential at control efficiencies greater than 99%,
i.e., below 50 ppm.
| en |
markdown | 851281 | # Presentation: 851281
## X10 Tutorial PSC Software Productivity Study May 23 – 27, 2005
**Vivek Sarkar**
**IBM T.J. Watson Research Center**
**vsarkar@us.ibm.com**
- This work has been supported in part by the Defense Advanced Research Projects Agency (DARPA) under contract No. NBCH30390004.
## Acknowledgments
**X10 core team**
- Philippe Charles
- Chris Donawa
***Kemal Ebcioglu***
- Christian Grothoff
- Allan Kielstra
- Christoph von Praun
- Vivek Sarkar
***Vijay Saraswat ***
**X10 productivity team**
***Catalina Danis***
- Christine Halverson
**Additional contributors to PSC Productivity Study**
- David Bader
- Bill Clark
- Nick Nystrom
- John Urbanic
- IBM Confidential
## Outline
**What is X10?**
**background, status**
**Basic X10 (single place)**
**async, finish, atomic**
**future, force**
**Basic X10 (arrays & loops)**
**points, rectangular regions, arrays**
**for, foreach**
**Scalable X10 (multiple places)**
**places, distributions, distributed arrays, ateach, BadPlaceException**
**Clocks**
**creation, registration, next, resume, drop, ClockUseException**
**Basic serial constructs that differ from Java**
**const, nullable, extern**
**Advanced topics**
**Value types, conditional atomic sections (when), general regions & distributions**
**Refer to language spec for details**
- IBM Confidential
## What is X10?
**X10 is a new experimental language developed in the IBM PERCS project as part of the DARPA program on High Productivity Computing Systems (HPCS)**
**X10’s goal is to provide a new parallel programming model and its embodiment in a high level language that:**
**is more productive than current models, **
**can support higher levels of abstraction better than current models, and **
**can exploit the multiple levels of parallelism and nonuniform data access that are critical for obtaining scalable performance in current and future HPC systems,**
- IBM Confidential
**Notes:**
Sun.misc.unsafe
## X10 status and schedule
- 6/2003 PERCS programming model concept (end of PERCS Phase 1)
- 7/2004 Start of PERCS Phase 2
- 2/2004 Kickoff of X10 as concrete embodiment of PERCS programming model as a new language
- 7/2004 First draft of X10 language specification
- 2/2005 First X10 implementation -- unoptimized single-VM prototype
**Emulates distributed parallelism in a single process**
**This is what you will use to run X10 programs this week**
***5/2005****** ******X10 productivity study at Pittsburgh Supercomputing Center***
- 7/2005 Results from X10 application & productivity studies
- 2H2005 Revise language based on application & productivity feedback
- 2H2005 Start participation in High Productivity Language “consortium”?
- 1/2006 Second X10 implementation – optimized multi-VM prototype
- 6/2006 Open source release of X10 reference implementation
- 6/2006 Design completed for production X10 implementation in Phase 3 (end of Phase 2)
- IBM Confidential
## Current X10 Environment: Unoptimized Single-VM Implementation
*Foo.x10*
*x10c*
- X10 compiler --- translates Foo.x10 to Foo.java,
- uses javac to generate Foo.class from Foo.java
*Foo.class*
- X10 source program --- must contain a class named Foo with a “public static void main(String[] args) method
*X10 Virtual Machine*
*(JVM + J2SE libraries + *
*X10 libraries + *
*X10 Multithreaded Runtime)*
*External DLL’s*
- X10 extern
- interface
*X10 Abstract Performance Metrics*
*(event counts, distribution efficiency)*
*X10 Program Output*
**X10 program translated into Java ---**
**// #line pseudocomment in Foo.java specifies source line mapping in Foo.x10**
***Foo.java***
**x10c Foo.x10**
**x10 Foo.x10**
***Caveat: this is a prototype implementation with many limitations. Please be patient!***
- IBM Confidential
## Examples of X10 Compiler Error Messages
**1) x10c TutError1.x10**
**TutError1.x10:8: Could not find field or local variable "evenSum".**
** ****for (int i = 2 ; i <= n ; i += 2 ) evenSum += i;**
** ****^----^**
**2) x10c TutError2.x10**
**x10c: TutError2.x10:4:27:4:27: unexpected token(s) ignored**
**3) x10c TutError3.x10**
**x10c: C:\vivek\eclipse\workspace\x10\examples\Tutorial\TutError3.java:49:**
** ****local variable n is accessed from within inner class; needs to be declared**
** ****final**
***Case 1:**** Error message identifies source file and line number*
***Case 2:**** Error message identifies source file, line number, and column range*
***Case 1:**** Carats indicate column range*
***Case 3:**** Error message reported by Java compiler – look for #line comment in .java file to identify X10 source location*
- IBM Confidential
## Future X10 Environment
*Very High Level Languages (VHLL’s),*
*Domain Specific Languages (DSL’s)*
*X10 High Level Language*
*X10 Deployment*
*HPC Runtime Environment*
*(Parallel Environment, MPI, LAPI, ...)*
*HPC Parallel System*
*Implicit parallelism,*
*Implicit data distributions*
*X10 places --- abstraction of explicit control & data distribution*
*Mapping of places to nodes in HPC Parallel Environment*
*Primitive constructs for parallelism, communication, and synchronization*
*Target system for parallel application*
*X10 Libraries*
- IBM Confidential
## Future X10 Environment: Targeting Scalable HPC Parallel Systems
- Functional Gigabit Ethernet
- I/O Node 0
- I/O Node 1023
- Console
*interconnect*
*interconnect*
*Front-end**Nodes*
*Pset 1023*
*Pset 0*
*File**Servers*
***“******Thick”***
***X10 VM***
***“******Thick” ***
***X10 VM***
**. . .**
***“******Full” X10 VM***
**. . .**
**. . .**
- IBM Confidential
## Future X10 Environment: Targeting Scalable HPC Parallel Systems
- Functional Gigabit Ethernet
- I/O Node 0
- I/O Node 1023
- Console
*interconnect*
*interconnect*
*Front-end**Nodes*
*Pset 1023*
*Pset 0*
*File**Servers*
***“******Thick”***
***X10 VM***
***“******Thick” ***
***X10 VM***
**. . .**
***“******Full X10 VM”***
**. . .**
**. . .**
| Clusters (scale-out) |
| --- |
| SMP |
| Multiple cores on a chip |
| Coprocessors (SPUs) |
| SMTs |
| SIMD |
| ILP |
**Future X10 Environment: Targeting Scalable HPC Parallel Systems**
- IBM Confidential
## X10 vs. Java
**X10 is an extended subset of Java**
**Base language = Java 1.4**
**Java 5 features (generics, metadata, etc.) are currently not supported in X10**
**Notable features removed from Java**
**Concurrency --- threads, synchronized, etc.**
**Java arrays – replaced by X10 arrays**
**Notable features added to Java**
**Concurrency – async, finish, atomic, future, force, foreach, ateach, clocks**
**Distribution --- points, distributions**
**X10 arrays --- multidimensional distributed arrays, array reductions, array initializers, **
**Serial constructs --- nullable, const, extern, value types**
**X10 supports both OO and non-OO programming paradigms**
- IBM Confidential
**Notes:**
Sun.misc.unsafe
## x10.lang standard library
- Java package with “built in” classes that provide support for selected X10 constructs
- Standard types
- boolean, byte, char, double, float, int, long, short, String
- x10.lang.Object -- root class for all instances of X10 objects
- x10.lang.clock --- clock instances & clock operations
- x10.lang.dist --- distribution instances & distribution operations
- x10.lang.place --- place instances & place operations
- x10.lang.point --- point instances & point operations
- x10.lang.region --- region instances & region operations
- All X10 programs implicitly import the x10.lang.* package, so the x10.lang prefix can be omitted when referring to members of x10.lang.* classes
- e.g., place.MAX_PLACES, dist.factory.block([0:100,0:100]), ...
- Similarly, all X10 programs also implicitly import the java.lang.* package
- e.g., X10 programs can use Math.min() and Math.max() from java.lang
- IBM Confidential
**Notes:**
NOTE: complex and String are not currently supported?
## Calling foreign functions from X10 programs
**Java methods**
**Can be called directly from X10 programs**
**Java class will be loaded automatically as part of X10 program execution**
**Basic rule: don’t call any method that can perform wait/notify or related thread operations**
**Calling synchronized methods is okay**
**C functions**
**Need to use extern declaration in X10, and perform a System.loadLibrary() call**
- IBM Confidential
**Notes:**
TODO:
Say something about classpath restrictions for X10 and Java code
## Resources available in current X10 installation
**Readme.txt --- basic information on X10 installation and usage**
**Limitations.txt --- list of known limitations in the current X10 implementation**
**etc/standard.cfg --- default configuration information**
**examples/ -- root directory for a number of working X10 example programs**
**examples/Constructs shows usage of different X10 constructs**
**examples/Tutorial contains examples used in this tutorial**
- IBM Confidential
## Outline
**What is X10?**
**background, status**
**Basic X10 (single place)**
**async, finish, atomic**
**future, force**
**Basic X10 (arrays & loops)**
**points, rectangular regions, arrays**
**for, foreach**
**Scalable X10 (multiple places)**
**places, distributions, distributed arrays, ateach, BadPlaceException**
**Clocks**
**creation, registration, next, resume, drop, ClockUseException**
**Basic serial constructs that differ from Java**
**const, nullable, extern**
**Advanced topics**
**Value types, conditional atomic sections (when), general regions & distributions**
**Refer to language spec for details**
- IBM Confidential
## X10 Programming Model (Single Place)
***Activity Stacks (S)***
***Shared Heap (H)***
*Activity *= lightweight thread
- Main program starts as single activity in Place 0
*Permitted object references (pointers);*
- I H, H I, II, HH, SH, S->I,
*Prohibited references:*
- H S, I S, S S
- No data sharing permitted between parent activity’s stack and child activity’s stack
*Single Place Memory model*
- No coherence constraints needed for I and S storage classes
- Guaranteed coherence for H storage class --- all writes to same shared location are observed in same order by all activities
- Largest deployment granularity for a single place is a single SMP
**Storage classes:**
**Immutable Data (I)**
**Shared Heap (H)**
**Activity Stacks (S)**
**Immutable Data (I) **
**-- final variables, value type instances**
***Locally***
***Synchronous***
***(coherent access to intra-place shared heap)***
**Place 0**
- IBM Confidential
## Basic X10 (Single Place)
*Core constructs used for intra-place (shared memory) parallel programming:*
*Async* = construct used to execute a statement in parallel as a new activity
*Finish* = construct used to check for global termination of statement and all the activities that it has created
*Atomic *= construct used to coordinate accesses to shared heap by multiple activities
*Future* = construct used to evaluate an expression in parallel as a new activity
*Force *= construct used to check for termination of future
- IBM Confidential
**Notes:**
NOTES:
Can we use an import statement to just type MAX_PLACES instead of x10.lang.place.MAX_PLACES
## async <stmt>
Parent activity creates a new child activity to execute <stmt> in the same place as the parent activity
An async statement returns immediately – parent execution proceeds immediately to next statement
Any access to parent’s local data must be through final variables
Similar to data access rules for inner classes in Java
Example
public class TutAsync {
const boxedInt oddSum=new boxedInt();
const boxedInt evenSum=new boxedInt();
public static void main(String[] args) {
final int n = 100;
async for (int i=1 ; i<=n ; i+=2 ) oddSum.val += i;
for (int j=2 ; j<=n ; j+=2 ) evenSum.val += j;
- async <stmt>
- Parent activity creates a new child activity to execute <stmt> in the same place as the parent activity
- An async statement returns immediately – parent execution proceeds immediately to next statement
- Any access to parent’s local data must be through final variables
- Similar to data access rules for inner classes in Java
- Example
- public class TutAsync {
- const boxedInt oddSum=new boxedInt();
- const boxedInt evenSum=new boxedInt();
- public static void main(String[] args) {
- final int n = 100;
- async for (int i=1 ; i<=n ; i+=2 ) oddSum.val += i;
- for (int j=2 ; j<=n ; j+=2 ) evenSum.val += j;
*Variable n must be declared as final --- its value is passed from parent to child activity*
**async statement**
- IBM Confidential
**Notes:**
TODO:
Check that async S is supported
Async returns immediately
Final values can be a reference
Async passes clocks to child
## finish <stmt>
Execute <stmt> as usual, but wait until all activities spawned (transitively) by <stmt> have terminated before completing the execution of finish S
finish traps all exceptions thrown by activities spawned by S, and throws a wrapping exception after S has terminated.
Example (see TutAsync.x10):
. . .
finish {
async for (int i=1 ; i<=n ; i+=2 ) oddSum.val += i;
for (int j=2 ; j<=n ; j+=2 ) evenSum.val += j;
}
// Both oddSum and evenSum have been computed now
System.out.println("oddSum = " + oddSum.val +
" ; evenSum = " + evenSum.val);
} // main()
} // TutAsync
- Execute <stmt> as usual, but wait until all activities spawned (transitively) by <stmt> have terminated before completing the execution of finish S
- finish traps all exceptions thrown by activities spawned by S, and throws a wrapping exception after S has terminated.
- Example (see TutAsync.x10):
- . . .
- **finish { **
** **** ****async for (int i=1 ; i<=n ; i+=2 ) oddSum.val += i; **
** **** ****for (int j=2 ; j<=n ; j+=2 ) evenSum.val += j;**
** ****}**
** ****// Both oddSum and evenSum have been computed now**
** ****System.out.println("oddSum = " + oddSum.val + **
** ****" ; evenSum = " + evenSum.val);**
** ****} // main()**
**} // TutAsync**
**finish statement**
*Console output:*
*oddSum = 2500 ; evenSum = 2550*
- IBM Confidential
**Notes:**
TODO:
Check that async S is supported
Async returns immediately
Final values can be a reference
Async passes clocks to child
## Atomic statements & methods
- atomic <stmt>, atomic <method-decl>
- An atomic statement/method is c*onceptually* executed in a single step, while other activities are suspended
- Note: programmer does not manage any locks explicitly
- An atomic section may not include
- Blocking operations
- Creation of activities
- Example (see TutAtomic1.x10):
** ****finish {**
** ****async for (int i=1 ; i<=n ; i+=2 ) {**
** ****double r = 1.0d / i ; atomic rSum += r; **
** ****}**
** ****for (int j=2 ; j<=n ; j+=2 ) {**
** ****double r = 1.0d / j ; atomic rSum += r; **
** ****}**
** ****}**
** ****System.out.println("rSum = " + rSum);**
*Console output:*
- rSum = 5.187377517639618
- IBM Confidential
## Another Example (TutAtomic2.x10)
- public class TutAtomic2 {
- const int a = new boxedInt(100);
- const int b = new boxedInt(100);
- public static atomic void incr_a() { a.val++ ; b.val-- ; }
- public static atomic void decr_a() { a.val-- ; b.val++ ; }
- public static void main(String args[]) {
- int sum;
- finish {
- async for (int i=1 ; i<=10 ; i++ ) incr_a();
- for (int i=1 ; i<=10 ; i++ ) decr_a();
- }
- atomic sum = a.val + b.val;
- System.out.println("a+b = " + sum);
- } // main()
- } // TutAtomic2
*Console output:*
- a+b = 200
- IBM Confidential
**Notes:**
TODO:
Support atomic in expressions e.g., int sum = atomic (a+b);
## Future & Force
- future<type> F = future { <expr> }
- Parent activity creates a new asynchronous child activity at <place> to evaluate <expr>
- <type> value = F.force()
- Caller blocks until return value is obtained from future (and all activities spawned transitively by <expr> have terminated )
- Example (see TutFuture2.x10):
- // Note that future<int> and int are different types
- future<int> Fi = future { fib(10) } ;
- int i = Fi.force();
- // Nested future types can also be created (if need be)
- future<future<int>> FFj= future { future{fib(100)} };
- future<int> Fj = FFj.force();
- int j = Fj.force();
- IBM Confidential
## Example (TutFuture1.x10)
**public class TutFuture1 {**
** ****static int fib(final int n) {**
** ****if ( n <= 0 ) return 0;**
** ****else if ( n == 1 ) return 1;**
** ****else {**
** ****future<int> fn_1 = future { fib(n-1) };**
** ****future<int> fn_2 = future { fib(n-2) };**
** ****return fn_1.force() + fn_2.force();**
** ****}**
** ****} // fib()**
** ****public static void main(String[] args) {**
** ****System.out.println("fib(10) = " + fib(10));**
** ****} // main()**
**} // TutFuture1**
*Example of recursive divide-and-conquer parallelism --- calls to fib(n-1) and fib(n-2) execute in parallel*
- IBM Confidential
## Parallel Programming Pitfalls: Deadlock
**Deadlock occurs when parallel threads/activities acquire locks or perform other blocking operations in a sequence that creates a dependence cycle**
**Java example:**
**Thread 0**
**synchronized (Foo.a) { synchronized(Foo.b) { ... } }**
**Thread 1**
**synchronized (Foo.b) { synchronized(Foo.a) { ... } }**
**MPI example:**
**Process 0: **
**MPI_Recv(recvbuf, count, MPI_REAL, 1, tag, ...)**
**Process 1: **
**MPI_Recv(recvbuf, count, MPI_REAL, 0, tag, ...)**
- IBM Confidential
## Parallel Programming Pitfalls: Deadlock (contd.)
**X10 guarantee**
**Any program written with async, finish, atomic, foreach, ateach, and clock parallel constructs will never deadlock**
**Unrestricted use of future and force may lead to deadlock (see examples/Constructs/Future/FutureDeadlock_MustFailTimeout.x10):**
**f1 = future { a1() } ; **
**f2 = future { a2() };**
**int a1() { ... f2.force(); ... }**
**Int a2() { ... f1.force(); ... }**
**Restricted use of future and force in X10 can preserve guaranteed freedom from deadlocks**
**Sufficient condition #1: ensure that activity that creates the future also performs the force() operation**
**Sufficient condition #2: . . .**
- IBM Confidential
## Parallel Programming Pitfalls: Data Races
**A data race occurs when two (or more) threads/activities can access the same shared location in parallel such that one of the accesses is a write operation**
**Java example:**
**Thread 0: **** ****a++ ; b-- ; **
**Thread 1: **** ****a++ ; b--;**
**Data race can violate invariant that (a+b) is constant **
**Data race may also prevent multiple increments from being combined correctly**
**X10 guidelines for avoiding data races**
**Use atomic methods and blocks without worrying about deadlock**
**Declare data to be read-only (i.e., final or value type instance) whenever possible**
- IBM Confidential
## Outline
**What is X10?**
**background, status**
**Basic X10 (single place)**
**async, finish, atomic**
**future, force**
**Basic X10 (arrays & loops)**
**points, rectangular regions, arrays**
**for, foreach**
**Scalable X10 (multiple places)**
**places, distributions, distributed arrays, ateach, BadPlaceException**
**Clocks**
**creation, registration, next, resume, drop, ClockUseException**
**Basic serial constructs that differ from Java**
**const, nullable, extern**
**Advanced topics**
**Value types, conditional atomic sections (when), general regions & distributions**
**Refer to language spec for details**
- IBM Confidential
## Points
- A *point* is an** **element of an n-dimensional Cartesian space (n>=1) with integer-valued coordinates e.g., [5], [1, 2], ...
- Dimensions are numbered from 0 to n-1
- n is also referred to as the *rank* of the point
- A point variable can hold values of different ranks e.g.,
- point p; p = [1]; ... p = [2,3]; ...
- The following operations are defined on a point-valued expression p1
- p1.rank --- returns rank of point p1
- p1.get(i) --- returns element i of point p1
- Returns element (i mod p1.rank) if i < 0 or i >= p1.rank
- p1.lt(p2), p1.le(p2), p1.gt(p2), p1.ge(p2)
- Returns true iff p1 is lexicographically <, <=, >, or >= p2
- Only defined when p1.rank and p1.rank are equal
- IBM Confidential
**Notes:**
TODO:
Define exceptions for point comparisons with wrong number of dimensions?
Motivation for rank analysis of points
## Example (see TutPoint.x10)
**public class TutPoint {**
** ****public static void main(String[] args) {**
** ****point p1 = [1,2,3,4,5];**
** ****point p2 = [1,2];**
** ****point p3 = [2,1];**
** ****System.out.println("p1 = " + p1 + " ; p1.rank = " + p1.rank + " ; p1.get(2) = " + p1.get(2));**
** ****System.out.println("p2 = " + p2 + " ; p3 = " + p3 + " ; p2.lt(p3) = " + p2.lt(p3));**
** ****} // main()**
**} // TutPoint**
*Console output:*
*p1 = [1,2,3,4,5] ; p1.rank = 5 ; p1.get(2) = 3*
*p2 = [1,2] ; p3 = [2,1] ; p2.lt(p3) = true*
- IBM Confidential
## Rectangular Regions
- A rectangular region is the set of points contained in a rectangular subspace
- A region variable can hold values of different ranks e.g.,
- region R; R = [0:10]; ... R = [-100:100, -100:100]; ... R = [0:-1]; ...
- The following operations are defined on a region-valued expression R
- R.rank = # dimensions in region; R.size() = # points in region
- R.contains(P) = true if region R contains point P
- R.contains(S) = true if region R contains region S
- R.equal(S) = true if region R equals region S
- R.rank(i) = projection of region R on dimension i (a one-dimensional region)
- R.rank(i).low() = lower bound of ith dimension of region R
- R.rank(i).high() = upper bound of ith dimension of region R
- R.ordinal(P) = ordinal value of point P in region R
- R.coord(N) = point in region R with ordinal value = N
- R1 && R2 = region intersection (will be rectangular if R1 and R2 are rectangular)
- R1 || R2 = union of regions R1 and R2 (may not be rectangular)
- R1 – R2 = region difference (may not be rectangular)
- IBM Confidential
**Notes:**
TODO: make all x10.lang operations method calls (no direct field accesses)
## Example (see TutRegion.x10)
**public class TutRegion {**
** ****public static void main(String[] args) {**
** ****region R1 = [1:10, -100:100]; **
** ****System.out.println("R1 = " + R1 + " ; R1.rank = " + R1.rank + " ; R1.size() = " + R1.size() + " ; R1.ordinal([10,100]) = " + R1.ordinal([10,100]));**
** ****region R2 = [1:10,90:100]; **
** ****System.out.println("R2 = " + R2 + " ; R1.contains(R2) = " + R1.contains(R2) + " ; R2.rank(1).low() = " + R2.rank(1).low() + " ; R2.coord(0) = " + R2.coord(0));**
** ****} // main()**
**} // TutRegion**
*Console output:*
*R1 = {1:10,-100:100} ; R1.rank = 2 ; R1.size() = 2010 ; R1.ordinal([10,100]) = 2009*
*R2 = {1:10,90:100} ; R1.contains(R2) = true ; R2.rank(1).low() = 90 ; R2.coord(0) = [1,90]*
- IBM Confidential
## X10 Arrays
- Java arrays are one-dimensional and local
- e.g., array args in main(String[] args)
- Multi-dimensional arrays are represented as “arrays of arrays” in Java
- X10 has true multi-dimensional arrays (as in C, Fortran) that can be distributed (as in UPC, Co-Array Fortran, ZPL, Chapel, etc.)
- Array declaration
- “T [.] A” declares an X10 array with element type T
- An array variable can hold values of different rank)
- The [.] syntax is used to avoid confusion with Java arrays
- Array creation
- “new T [ R ]” creates a local rectangular X10 array with rectangular region R as the index domain and T as the element (range) type
- e.g., int[.] A = new int[ [0:N+1, 0:N+1] ];
- Array initializers can also be specified in conjunction with creation (see TutArray1.x10)
- E.g., int[.] A = new int[ [1:10,1:10] ] (point[i,j]) { return i+j; } ;
- IBM Confidential
## X10 Array Operations
- The following operations are defined on array-valued expression s
- A.rank = # dimensions in array
- A.region = index region (domain) of array
- A[P] = element at point P, where P belongs to A.region
- A | R = restriction of array onto region R
- Useful for extracting subarrays
- A.sum(), A.max() = sum/max of elements in array
- A1 op A2 returns result of applying a pointwise op on array elements, when A1.region = A2. region
- Op can include +, -, *, and /
- A1 || A2 = disjoint union of arrays A1 and A2 (A1.region and A2.region must be disjoint)
- A1.overlay(A2)
- Returns an array with region, A1.region || A2.region, with element value A2[P] for all points P in A2.region and A1[P] otherwise.
- A.distribution = distribution of array A
- Will be discussed later when we introduce X10 places
- IBM Confidential
**Notes:**
TODO:
Add info on unary operators like abs
## Example (see TutArray1.x10)
**public class TutArray1 {**
** ****public static void main(String[] args) {**
** ****int[.] A = new int[ [1:10,1:10] ] **
** ****(point [i,j]) { return i+j;} ;**
** ****System.out.println("A.rank = " + A.rank +**
** ****" ; A.region = " + A.region);**
** ****int[.] B = A | [1:5,1:5];**
** ****System.out.println("B.max() = " + B.max());**
** ****} // main()**
**} // TutArray1**
*Console output:*
*A.rank = 2 ; A.region = {1:10,1:10}*
*B.max() = 10*
- IBM Confidential
## Pointwise for loop
- X10 extends Java’s for loop to support sequential iteration over points in region R in canonical lexicographic order
- for ( point p : R ) . . .
- Standard point operations can be used to extract individual index values from point p
- for ( point p : R ) { int i = p.get(0); int j = p.get(1); . . . }
- Or an “exploded” syntax can be used instead of explicitly declaring a point variable
- for ( point [i,j] : R ) { . . . }
- The exploded syntax declares the constituent variables (i, j, ...) as local int variables in the scope of the for loop body
- IBM Confidential
## Example (see TutFor.x10)
- public class TutFor {
- public static void main(String[] args) {
- region R = [0:1,0:2];
- System.out.print("Points in region " + R + " =");
- for ( point p : R ) System.out.print(" " + p);
- System.out.println();
- // Use exploded syntax instead
- System.out.print("(i,j) pairs in region " + R + " =");
- for ( point[i,j] : R )
- System.out.print("(" + i + "," + j + ")");
- System.out.println();
- } // main()
- } // TutFor
*Console output:*
*Points in region {0:1,0:2} = [0,0] [0,1] [0,2] [1,0] [1,1] [1,2]*
*(i,j) pairs in region {0:1,0:2} =(0,0)(0,1)(0,2)(1,0)(1,1)(1,2)*
- IBM Confidential
## foreach loop (Parallel iteration)
- The X10 foreach loop is similar to the pointwise for loop, except that each iteration executes in parallel as a new asynchronous activity i.e.,
- “foreach ( point p : R ) S” is equivalent to “for ( point p : R ) async S”
- As before, finish can be used to wait for termination of all foreach iterations
- finish foreach ( point[i,j] : [0:M-1,0:N-1] ) . . .
- Special case: use foreach to create a single-dimensional parallel loop
- foreach ( point[i] : [0 : N-1] ) S
- Allowing a single foreach construct to span multiple dimensions makes it convenient to write parallel matrix code that is independent of the underlying rank and region e.g.
- foreach ( point p : A.region ) A[p] = f(B[p], C[p], D[p]) ;
- Multiple foreach instances may accesses shared data in the same place use finish, atomic, force to avoid data races
- IBM Confidential
**Notes:**
NOTE: We expect that X10’s multi-dimensional foreach will enable efficient implementations with loop blocking/chunking schemes that span the entire region, compared to nested parallel loops
## Example (see TutForeach1.x10)
**public class TutForeach1 {**
** ****public static void main(String[] args) {**
** ****final int N = 5;**
** ****int[.] A = new int[[1:N,1:N]] (point[i,j]) {return i+j;};**
** ****// For the A[i,j] = F(A[i,j]) case, **
** ****// both loops can execute in parallel **
** ****finish foreach ( point[i,j] : A.region ) **
** ****A[i,j] = A[i,j] + 1;**
** ****// For the A[i,j] = F(A[i,j-1]) case, **
** ****// only the outer loop can execute in parallel **
** ****finish foreach ( point[i] : A.region.rank(0) ) **
** ****for (point[j]: **
** ****[(A.region.rank(1).low()+1):A.region.rank(1).high()])**
** ****A[i,j] = A[i,j-1] + 1;**
*NOTE: A.region.rank(0) is the same as [1:N]*
- IBM Confidential
## Example contd. (see TutForeach1.x10)
** ****// For the A[i,j] = F(A[i-1,j]) case, **
** ****// only the inner loop can execute in parallel **
** ****for (point[i]: **
** ****[(A.region.rank(0).low()+1):A.region.rank(0).high()] ) **
** ****finish foreach ( point[j] : A.region.rank(1) ) **
** ****A[i,j] = A[i-1,j] + 1;**
** ****// For the A[i,j] = F(A[i-1,j],A[i,j-1]) case, **
** ****// use loop skewing to execute the inner loop in parallel **
** ****for ( point[t] : [4:2*N]) {**
** ****finish foreach ( point[j] : [Math.max(2,t-N):Math.min(N,t-2)]) {**
** ****int i = t - j;**
** ****System.out.print("(" + i + "," + j + ")");**
** ****A[i,j] = A[i-1,j] + A[i,j-1] + 1;**
** ****}**
** ****System.out.println();**
*Console output:*
*(2,2)*
*(3,2)(2,3)*
*(4,2)(3,3)(2,4)*
*(5,2)(3,4)(4,3)(2,5)*
*(5,3)(4,4)(3,5)*
*(5,4)(4,5)*
*(5,5)*
- IBM Confidential
## Outline
**What is X10?**
**background, status**
**Basic X10 (single place)**
**async, finish, atomic**
**future, force**
**Basic X10 (arrays & loops)**
**points, rectangular regions, arrays**
**for, foreach**
**Scalable X10 (multiple places)**
**places, distributions, distributed arrays, ateach, BadPlaceException**
**Clocks**
**creation, registration, next, resume, drop, ClockUseException**
**Basic serial constructs that differ from Java**
**const, nullable, extern**
**Advanced topics**
**Value types, conditional atomic sections (when), general regions & distributions**
**Refer to language spec for details**
- IBM Confidential
## Limitations of using a Single Place
***Activity Stacks (S)***
***Shared Heap (H)***
- Largest deployment granularity for a single place is a single SMP
- Smallest granularity can be a single CPU or even a single hardware thread
- Single SMP is inadequate for solving problems with large memory and compute requirements
- _X10 solution:_ incorporate multiple places as a core foundation of the X10 programming model
- Enable deployment on large-scale clustered machines, with integrated support for intra-place parallelism
**Storage classes:**
**Immutable Data (I)**
**Shared Heap (H)**
**Activity Stacks (S)**
**Immutable Data (I) **
**-- final variables, value type instances**
***Locally***
***Synchronous***
***(coherent access to intra-place shared heap)***
**Place 0**
- IBM Confidential
## Scalable X10: using multiple places
*Place* = collection of activities & objects
- Activities and data objects do not move after being created
*Scalar object, O* -- maps to a single place specified by O.location
*Array object, A* – may be local to a place or distributed across multiple places, as specified by A.distribution
**Storage classes:**
**Immutable Data (I)**
**PGAS**
**Local Heap (LH)**
**Remote Heap (RH)**
**Activity Stacks (S)**
***Locally***
***Synchronous***
***(coherent access to intra-place shared heap)***
***Activity Stacks (S)***
***Local Heap (LH)***
**Immutable Data (I) **
**-- final variables, value type instances**
***Activity Stacks (S)***
***Local Heap (LH)***
***Outbound activities***
***Inbound activities***
***Outbound activity***
***replies***
***Inbound activity replies***
***. . .***
***Globally***
***Asynchronous***
*Partitioned Global Address Space (PGAS)*
**Place 0**
**Place ****(MAX_PLACES -1)**
- IBM Confidential
## Locality Rule
*Any access to a mutable (shared heap) datum must be performed by an activity located at the place as the datum*
- The prohibited references are similar as before:
- LH/RH S, I S, S S
- Local-to-remote (LH RH) and remote-to-local (RH LH) heap references are freely permitted
- However, direct access via a remote heap reference is not permitted!
- Inter-place data accesses can only be performed by creating remote activities (with weaker ordering guarantees than intra-place data accesses)
- The locality rule is currently not checked by default. Instead, the user can perform the check explicitly by inserting a place cast operator as follows:
- “(@ P) E” checks if expression E can be evaluated at place P
- If so, expression E is evaluated as usual
- If not, a BadPlaceException is thrown
- IBM Confidential
**Notes:**
TODO:
Should we restrict E to be an lval?
## Activity Execution within a Place
***Outbound activities***
***Inbound ***
***activities***
***Outbound***
***replies***
***Inbound replies***
***Place***
***Ready ***
***Activities***
***Completed***
***Activities***
***Blocked***
***Activities***
***Clock***
***Future***
***Executing***
***Activities***
***. . .***
***Atomic sections do not have blocking semantics***
***Place-local activity can only its stack (S), place-local heap (LH), or immutable data (I)***
- IBM Confidential
## Places
- place.MAX_PLACES = total number of places
- Default value is 4
- Can be changed by using the -NUMBER_OF_LOCAL_PLACES option in x10 command
- place.places = Set of all places in an X10 program(see java.lang.Set)
- place.factory.place(i) = place corresponding to index i
- here = place in which current activity is executing
- <place-expr>.toString() returns a string of the form “place(id=99)”
- <place-expr>.id returns the id of the place
*X10 Places*
*System Nodes*
*X10 language defines mapping from X10 objects to X10 places, and abstract performance metrics on places*
*X10 Data Structures*
*Future X10 deployment system will define mapping from X10 places to system nodes; not supported in current implementation*
- IBM Confidential
## Extension of async and future to places
- async (P) S
- Creates new activity to execute statement S at place P
- “async S” is equivalent to “async (here) S”
- future (P) { E }
- Create new activity to evaluate expression E at place P
- “future { E } ” is equivalent to “future (here) { E }”
- Note that “here” in a child activity for an async/future computation will refer to the place P at which the child activity is executing, not the place where the parent activity is executing
- The goal is to specify the destination place for async/future activities so as to obey the Locality Rule e.g.,
- async (O.location) O.x = 1;
- future<int> F = future (A.distribution[i]) { A[i] } ;
- IBM Confidential
## Distribution = mapping from region to places
- Creating distributions (x10.lang.dist):
- dist D1 = R-> here; // local distribution – maps region R to here
- dist D2 = dist.factory.block(R); // blocked distribution* *
- dist D3 = dist.factory.cyclic(R); // cyclic distribution
- dist D4 = dist.factory.unique(); // identity map on [0:MAX_PLACES-1]
- Using distributions
- D[P] = place to which point P is mapped by distribution D (assuming that P is in D.region)
- Allocate a distributed array e.g., T[.] A = new T[ D ];
- Allocates an array with index set = D.region, such that element A[P] is located at place D[P] for each point P in D.region
- NOTE: “new T[R]” for region R is equivalent to “new T[R->here]”
- Iterating over a distribution – generalization of “foreach” to “ateach”
- ateach is discussed in more detail later
- IBM Confidential
**Notes:**
TODO:
1) Say that we can write D[P] instead of D.get(P)
2) Add figures for block, cyclic, unique
## Operations defined on distributions
- D.region = source region of distribution
- D.rank = rank of D.region
- D | R = region restriction for distribution D and region R (returns a restricted distribution)
- D | P = place restriction for distribution D and place P (returns region mapped by D to place P)
- D1 || D2 = union of distributions D1 and D2 (assumes that D1.region and D2.region are disjoint)
- D1.overlay(D2); // Overlay of D2 over D1 – asymmetric union
- D.contains(p) = true iff D.region contains point p
- D = R -> P, constant distribution which maps entire region R to place P
- D1 – D2 = distribution difference = D1 | (D1.region – D2.region)
- D.distributionEfficiency() = load balance efficiency of distribution D
- IBM Confidential
## Inter-place communication using async and future
- Question: how to assign A[i] = B[j], when A[i] and and B[j] may be in different places?
- Answer #1 --- use nested async’s!
- finish async ( B.distribution[j] ) {
- final int bb = B[j];
- async ( A.distribution[i] ) A[i] = bb;
- }
- Answer #2 --- use future-force and an async!
- final int b = future (B.distribution[j]) { B[j] }.force();
- finish async ( A.distribution[i] ) A[i] = b;
- IBM Confidential
## Load Balance Efficiency
- Consider a parallel application that is executed on P places
- Let T(i) = computation load mapped to place i
- For distribution D, T(i) = (D | place.factory.place(i)).size()
- Let Tmax = max { T(i) | 1 <= i <= P }
- Let E = SUM { T(i) | 1 <= i <= P } / (Tmax * P)
- E is the *load balance efficiency*, 1/P <= E <= 1
- E = 1 is the best case computation load is perfectly balanced
- E = 1/P is the worst case computation load is placed on a single processor/place
- Load balance efficiency is one of the key factors that limit speedup on a parallel machine
- there are several other factors e.g., comm. & synchronization overhead
- ignoring other factors, we expect speedup to be <= E * P
- NOTE: also try “x10 –DUMP_STATS_ON_EXIT=true ...” to see activity and atomic counts
- IBM Confidential
**Notes:**
TODO: add a picture
## ateach loop (distributed parallel iteration)
- The X10 ateach loop is similar to the foreach loop, except that each iteration executes in parallel at a place specified by a distribution
- “ateach ( point p : D ) S ” is equivalent to “for ( point p : D.region ) async (D[p]) S”
- As before, finish can be used to wait for termination of all ateach iterations
- “finish ateach( point[i] : dist.factory.unique() ) S” creates one activity per place, as in an SPMD computation
- ateach is a convenient construct for writing parallel matrix code that is independent of the underlying distribution e.g.,
- ateach ( point p : A.distribution ) A[p] = f(B[p], C[p], D[p]) ;
- IBM Confidential
**Notes:**
NOTE: We expect that X10’s multi-dimensional foreach will enable efficient implementations with loop blocking/chunking schemes that span the entire region, compared to nested parallel loops
## Example (see TutAteach1.x10)
- public class TutAteach1 {
- public static void main(String args[]) {
- finish ateach( point[i] : dist.factory.unique() ) {
- System.out.println("Hello from " + i);
- }
- } // main()
- } // TutAteach1
*Console output:*
*Hello from 1*
*Hello from 0*
*Hello from 3*
*Hello from 2*
- dist.factory.unique() maps point i in the region, [0 : place.MAX_PLACES-1], to place place.factory.place(i)
- IBM Confidential
## Example: converting foreach to ateach (see TutAteach2.x10)
_**foreach version:**_
** ****// For the A[i,j] = F(A[i,j]) case, **
** ****// both loops can execute in parallel **
** ****finish foreach ( point[i,j] : A.region ) **
** ****A[i,j] = A[i,j] + 1;**
_**ateach version #1:**_
** ****finish ateach ( point[i,j] : A.distribution) **
** ****A[i,j] = A[i,j] + 1;**
_**ateach version #2 (create only one activity per place):**_
** ****finish ateach ( point p : dist.factory.unique() ) **
** ****for ( point[i,j] : A.distribution | here ) **
** ****A[i,j] = A[i,j] + 1;**
- IBM Confidential
## Example: converting foreach to ateach, contd. (see TutAteach2.x10)
_**foreach version:**_
** ****// For the A[i,j] = F(A[i,j-1]) case, **
** ****// only the outer loop can execute in parallel **
** ****finish foreach ( point[i] : [1:N] ) **
** ****for ( point[j]: [2:N] )**
** ****A[i,j] = A[i,j-1] + 1;**
_**ateach version:**_
** ****// Assume that N is a multiple of place.MAX_PLACES**
** ****finish ateach ( point[i] : dist.factory.block([1:N]) ) **
** ****for ( point[j]: [2:N] ) **
** ****A[i,j] = A[i,j-1] + 1;**
- IBM Confidential
## Outline
**What is X10?**
**background, status**
**Basic X10 (single place)**
**async, finish, atomic**
**future, force**
**Basic X10 (arrays & loops)**
**points, rectangular regions, arrays**
**for, foreach**
**Scalable X10 (multiple places)**
**places, distributions, distributed arrays, ateach, BadPlaceException**
**Clocks**
**creation, registration, next, resume, drop, ClockUseException**
**Basic serial constructs that differ from Java**
**const, nullable, extern**
**Advanced topics**
**Value types, conditional atomic sections (when), general regions & distributions**
**Refer to language spec for details**
- IBM Confidential
## X10 clocks: Motivation
- Activity coordination using finish and force() is accomplished by checking for activity termination
- However, there are many cases in which a producer-consumer relationship exists among the activities, and a “barrier”-like coordination is needed without waiting for activity termination
- The activities involved may be in the same place or in different places
*Activity 0*
*Activity 1*
*Activity 2*
*. . .*
*Phase 0*
*Phase 1*
*. . .*
- IBM Confidential
## X10 Clocks
**cl****oc****k c = clock.factory.clock();**
- Allocate a clock, register current activity with it. Phase 0 of c starts.
**async(...) clocked (c1,c2,...) S**
**ateach(...) clocked (c1,c2,...) S**
**foreach(...) clocked (c1,c2,...) S**
- Create async activities registered on clocks c1, c2, ...
**c.resume();**
- Nonblocking operation that signals completion of work by current activity for this phase of clock c
**next;**
- Barrier --- suspend until all clocks that the current activity is registered with can advance. c.resume() is first performed for each such clock, if needed.
- Next can be viewed like a “finish” of all computations under way in the current phase of the clock
- IBM Confidential
## X10 Clocks (contd.)
** ****c.drop();**
- Unregister with c. A terminating activity will implicitly drop all clocks that it is registered on.
** ****c.registered()**
- Return true iff current activity is registered on clock c
**c.dropped() **returns the opposite of **c.registered()**
- ClockUseException
- Thrown if an activity attempts to transmit or operate on a clock that it is not registered on
- IBM Confidential
## Example (see TutClock1.x10)
** ****finish async {**
** ****final clock c = clock.factory.clock();**
** ****foreach (point[i]: [1:N]) clocked (c) {**
** ****while ( true ) {**
** ****int old_A_i = A[i]; int new_A_i = Math.min(A[i],B[i]);**
** ****if ( i > 1 ) new_A_i = Math.min(new_A_i,B[i-1]);**
** ****if ( i < N ) new_A_i = Math.min(new_A_i,B[i+1]);**
** ****A[i] = new_A_i;**
** ****next;**
** ****int old_B_i = B[i]; int new_B_i = Math.min(B[i],A[i]);**
** ****if ( i > 1 ) new_B_i = Math.min(new_B_i,A[i-1]);**
** ****if ( i < N ) new_B_i = Math.min(new_B_i,A[i+1]);**
** **** **** ****B[i] = new_B_i;**
** ****next;**
** ****if ( old_A_i == new_A_i && old_B_i == new_B_i ) break;**
** ****} // while**
** ****} // foreach **
** ****} // finish async**
*NOTE: exiting from while loop terminates activity for iteration i, and automatically deregisters activity from clock*
*Example of transmitting clock from parent to child*
- IBM Confidential
## Outline
**What is X10?**
**background, status**
**Basic X10 (single place)**
**async, finish, atomic**
**future, force**
**Basic X10 (arrays & loops)**
**points, rectangular regions, arrays**
**for, foreach**
**Scalable X10 (multiple places)**
**places, distributions, distributed arrays, ateach, BadPlaceException**
**Clocks**
**creation, registration, next, resume, drop, ClockUseException**
**Basic serial constructs that differ from Java**
**const, nullable, extern**
**Advanced topics**
**Value types, conditional atomic sections (when), general regions & distributions**
**Refer to language spec for details**
- IBM Confidential
## nullable
- By default, object references in X10 are not allowed to take on the null value
- However, the nullable type constructor can be used to enable certain object references to be set to null, or to compare them with null e.g.,
- T1 a;
- nullable T2 b;
- a = null; // Not allowed
- b = null; // Allowed
- NOTE: “const” is simply a shorthand for “static final”
- IBM Confidential
## extern
- X10 provides a simple mechanism for invoking external functions written in C
- Currently, the C function is restricted to arguments with primitive types or references to “unsafe” X10 arrays
- The X10 program must contain an external declaration of the C function as follows ...
- static extern char doit(int a, float b)
- ... and also a statement to ensure that the native DLL, <dll>.dll is loaded
- static { System.loadLibrary(“<dll>");}
- The X10 compiler then generates a file called <class>_x10stub.c
- To generate the DLL, the C programmer must compile the C function by including the file jni.h in tehir C function, and must link with the object file obtained from <class>_x10stub.c
- IBM Confidential
## Outline
**What is X10?**
**background, status**
**Basic X10 (single place)**
**async, finish, atomic**
**future, force**
**Basic X10 (arrays & loops)**
**points, rectangular regions, arrays**
**for, foreach**
**Scalable X10 (multiple places)**
**places, distributions, distributed arrays, ateach, BadPlaceException**
**Clocks**
**creation, registration, next, resume, drop, ClockUseException**
**Basic serial constructs that differ from Java**
**const, nullable, extern**
**Advanced topics**
**Value types, conditional atomic sections (when), general regions & distributions**
**Refer to language spec for details**
- IBM Confidential | en |
converted_docs | 064072 | {width="5.96875in" height="0.41944444444444445in"}
Top of Form
## Complete Summary
#### GUIDELINE TITLE
Treatment of primary headache: episodic tension-type headache. Standards
of care for headache diagnosis and treatment.
#### BIBLIOGRAPHIC SOURCE(S)
Ruoff G, Urban G. Treatment of primary headache: episodic tension-type
headache. In: Standards of care for headache diagnosis and treatment.
Chicago (IL): National Headache Foundation; 2004. p. 53-8. \[6
references\]
#### GUIDELINE STATUS
This is the current release of the guideline.
### \*\* REGULATORY ALERT \*\*
#### FDA WARNING/REGULATORY ALERT
**Note from the National Guideline Clearinghouse**: This guideline
references a drug(s) for which important revised regulatory information
has been released.
- [June 15, 2005, COX-2 Selective (includes Bextra, Celebrex, and
Vioxx) and Non-Selective Non-Steroidal Anti-Inflammatory Drugs
(NSAIDs)](http://www.fda.gov/medwatch/SAFETY/2005/safety05.htm#NSAID):
Labeling revised to include a boxed warning and a Medication Guide,
highlighting the potential for increased risk of cardiovascular (CV)
events and life-threatening gastrointestinal (GI) bleeding.
- [April 7, 2005, Bextra (valdecoxib), Cox-2 inhibitors, Celebrex
(celecoxib), Non-steroidal anti-inflammatory drugs (NSAIDS)
(prescription and OTC, including ibuprofen and
naproxen](http://www.fda.gov/medwatch/SAFETY/2005/safety05.htm#BEXTRA):
Bextra (valdecoxib) withdrawn from the market and labels for other
Cox-2 inhibitors and NSAIDS revised to include a boxed warning and a
Medication Guide, highlighting the potential for increased risk of
cardiovascular (CV) events and life-threatening gastrointestinal
(GI) bleeding.
**Additional Notice**
- [April 11, 2007, Zanaflex (tizanidine
hydrochloride)](http://www.fda.gov/medwatch/safety/2007/safety07.htm#Zanaflex):
Changes to the product labeling for Zanaflex, a drug used to treat
spasticity, to warn against its hypotensive and sedative effects
when administered with fluvoxamine or ciprofloxacin (CYP1A2
inhibitors).
### COMPLETE SUMMARY CONTENT
\*\* REGULATORY ALERT \*\*\
SCOPE\
METHODOLOGY - including Rating Scheme and Cost Analysis\
RECOMMENDATIONS\
EVIDENCE SUPPORTING THE RECOMMENDATIONS\
BENEFITS/HARMS OF IMPLEMENTING THE GUIDELINE RECOMMENDATIONS\
QUALIFYING STATEMENTS\
IMPLEMENTATION OF THE GUIDELINE\
INSTITUTE OF MEDICINE (IOM) NATIONAL HEALTHCARE QUALITY REPORT
CATEGORIES\
IDENTIFYING INFORMATION AND AVAILABILITY\
DISCLAIMER
### SCOPE
#### DISEASE/CONDITION(S)
Episodic tension-type headache (TTH)
#### GUIDELINE CATEGORY
Treatment
#### CLINICAL SPECIALTY
Family Practice\
Internal Medicine\
Neurology
#### INTENDED USERS
Health Care Providers\
Physicians
#### GUIDELINE OBJECTIVE(S)
- To improve the medical treatment of headache
- To help physicians and other health care professionals to design a
treatment plan, combining nonpharmacologic with pharmacologic
approaches as necessary to:
- Minimize symptomatology
- Reduce disability
- Improve quality of life
- To make practicing physicians aware of the existence of tension-type
headache (TTH), as well as general treatment strategies for it,
including both drug and nondrug approaches
#### TARGET POPULATION
Patients with episodic tension-type headache (TTH)
#### INTERVENTIONS AND PRACTICES CONSIDERED
**Drug Treatment**
**Simple Over-the-Counter Analgesics**
1. Aspirin
2. Acetaminophen
3. Nonsteroidal anti-inflammatory drugs (NSAIDs)
- Acetylsalicylic acid
- Ibuprofen
- Naproxen sodium
**Over-the-Counter Combination Analgesics**
1. Aspirin/caffeine
2. Acetaminophen/caffeine
3. Aspirin/acetaminophen/caffeine
**Prescription Medications**
1. NSAIDs
- Celecoxib
- Diclofenac
- Diflunisal
- Etodolac
- Fenoprofen
- Flurbiprofen
- Ibuprofen
- Indomethacin
- Ketoprofen
- Ketorolac
- Meclofenamate
- Mefenamic acid
- Meloxicam
- Nabumetone
- Naproxen
- Naproxen sodium
- Rofecoxib
- Salsalate
- Tolmetin
- Valdecoxib
2. Muscle relaxants, alone or combination
- Baclofen
- Carisoprodol
- Carisoprodol/aspirin
- Chlorzoxazone
- Cyclobenzaprine
- Metaxalone
- Methocarbamol
- Orphenadrine citrate
- Orphenadrine citrate/aspirin/caffeine
- Tizanidine
3. Barbiturate-containing analgesics
- Butalbital/aspirin/caffeine
- Butalbital/acetaminophen/caffeine
- Butalbital/acetaminophen
4. Other
- Isometheptene mucate/dichloralphenazone/acetaminophen
**Nondrug Treatments**
1. Relaxation techniques
2. Proper sleep and diet habits
3. Exercise
4. Avoidance of behaviors or situations that may trigger an attack
5. Biofeedback
6. Physical interventions
- Acupuncture and acupressure
- Heat or cold applications
#### MAJOR OUTCOMES CONSIDERED
Not stated
### METHODOLOGY
#### METHODS USED TO COLLECT/SELECT EVIDENCE
Searches of Electronic Databases
#### DESCRIPTION OF METHODS USED TO COLLECT/SELECT THE EVIDENCE
Not stated
#### NUMBER OF SOURCE DOCUMENTS
Not stated
#### METHODS USED TO ASSESS THE QUALITY AND STRENGTH OF THE EVIDENCE
Expert Consensus
#### RATING SCHEME FOR THE STRENGTH OF THE EVIDENCE
Not applicable
#### METHODS USED TO ANALYZE THE EVIDENCE
Review
#### DESCRIPTION OF THE METHODS USED TO ANALYZE THE EVIDENCE
Not stated
#### METHODS USED TO FORMULATE THE RECOMMENDATIONS
Expert Consensus
#### DESCRIPTION OF METHODS USED TO FORMULATE THE RECOMMENDATIONS
The guidelines presented in this monograph represent the consensus of an
advisory panel of practitioners chosen by the National Headache
Foundation (NHF) for their expertise. In addition to incorporating the
US Headache Consortium\'s recommendations, their conclusions reflect
clinical experience and the most recent medical literature.
#### RATING SCHEME FOR THE STRENGTH OF THE RECOMMENDATIONS
Not applicable
#### COST ANALYSIS
A formal cost analysis was not performed and published cost analyses
were not reviewed.
#### METHOD OF GUIDELINE VALIDATION
Not stated
#### DESCRIPTION OF METHOD OF GUIDELINE VALIDATION
Not applicable
### RECOMMENDATIONS
#### MAJOR RECOMMENDATIONS
**Episodic Tension-Type Headache (TTH)**
**Drug Treatment**
Once a more serious underlying condition has been ruled out, the goal of
TTH therapy is acute intervention with the simplest, most effective, and
best-tolerated agent (see figure 5.1 of the original guideline
document). Selection of an appropriate therapeutic approach is based on
a thorough history, including the patient\'s response to previous
treatments and an assessment of the impact of the attacks on the
patient\'s quality of life. Physicians should specifically inquire about
over-the-counter (OTC) medications, as few patients recognize how
differences in this class of analgesics can affect subsequent treatment
(see table 5.1 of the original guideline document for guidelines for use
of selected abortive therapies in the treatment of TTH).
**Simple OTC Analgesics**
Unless the patient has already tried simple analgesics without success,
treatment of TTH should begin with a nonprescription aspirin,
acetaminophen, or nonsteroidal anti-inflammatory drug (NSAID) such as
ibuprofen, naproxen sodium, or ketoprofen. In general, recommend a
relatively high dose and stress the importance of early intervention to
maximize effectiveness.
**OTC Combination Analgesics**
If simple analgesics fail, consider recommending a nonprescription
medication that contains aspirin and/or acetaminophen with the addition
of caffeine. Caffeine is an adjunct that provides mild vasoconstrictive,
psychomimetic, and pain-enhancing action as well as a gastrokinetic
effect.
**Prescription Medications**
If OTC analgesics are unsuccessful, prescription medications are the
next appropriate step, including NSAIDs and barbiturate-containing
medications (see table below). Keep in mind that the response to NSAIDs
is highly individual, and failure of one agent should not preclude the
use of another for future attacks. Further, prescribe
barbiturate-containing products only with extreme caution, as they have
a strong tendency to induce analgesic rebound, which often leads to
their overuse.
+--------------------------+-------------------------------------------+
| **Prescription NSAIDs | |
| and | |
| Barbiturate-Containing | |
| Analgesics** | |
+==========================+===========================================+
| **NSAIDs** | **Barbiturate-Containing Analgesics** |
+--------------------------+-------------------------------------------+
| - Celecoxib | - Butalbital/aspirin/caffeine |
| | |
| - Diclofenac | - Butalbital/acetaminophen/caffeine |
| | |
| - Etodolac | - Butalbital/acetaminophen |
| | |
| - Fenoprofen | |
| | |
| - Flurbiprofen | |
| | |
| - Indomethacin | |
| | |
| - Ibuprofen | |
| | |
| - Ketoprofen | |
| | |
| - Ketorolac | |
| | |
| - Mefenamic acid | |
| | |
| - Meloxicam | |
| | |
| - Nabumetone | |
| | |
| - Naproxen | |
| | |
| - Naproxen sodium | |
| | |
| - Rofecoxib\* | |
| | |
| - Salsalate | |
| | |
| - Valdecoxib\*\* | |
+--------------------------+-------------------------------------------+
\*On September 30, 2004, Vioxx (rofecoxib) was withdrawn from the U.S.
and worldwide market due to safety concerns of an increased risk of
cardiovascular events. See the [U.S. Food and Drug Administration (FDA)
Web site](http://www.fda.gov/medwatch/SAFETY/2004/safety04.htm#vioxx)
for more information.
\*\*Subsequently, on April 7, 2005, after concluding that the overall
risk versus benefit profile is unfavorable, the FDA requested that
Pfizer, Inc voluntarily withdraw Bextra (valdecoxib) from the market.
The FDA also asked manufacturers of all marketed prescription
nonsteroidal anti-inflammatory drugs (NSAIDs), including Celebrex
(celecoxib), a COX-2 selective NSAID, to revise the labeling (package
insert) for their products to include a boxed warning and a Medication
Guide. Finally, FDA asked manufacturers of non-prescription (over the
counter \[OTC\]) NSAIDs to revise their labeling to include more
specific information about the potential gastrointestinal (GI) and
cardiovascular (CV) risks, and information to assist consumers in the
safe use of the drug. See the [FDA Web
site](http://www.fda.gov/medwatch/SAFETY/2005/safety05.htm#Bextra) for
more information.
**Additional Prescribing Considerations**
Preventive therapy is not required unless the number of TTH attacks
exceeds 15 per month. Muscle relaxants with or without analgesics may be
used effectively, if the attacks are associated with the pericranial
muscles (see table below). In rare cases, depression, anxiety, or both
may be associated with TTH and should be treated as appropriate.
+-----------------------------------------------------------------------+
| **Muscle Relaxants with/without Analgesics** |
+=======================================================================+
| - Baclofen |
| |
| - Carisoprodol |
| |
| - Carisoprodol/aspirin |
| |
| - Chlorzoxazone |
| |
| - Cyclobenzaprine |
| |
| - Metaxalone |
| |
| - Methocarbamol |
| |
| - Orphenadrine |
| |
| - Orphenadrine/aspirin/caffeine |
| |
| - Tizanidine |
| |
| - Isometheptene/dichloralphenazone/acetaminophen |
+-----------------------------------------------------------------------+
**Safety Issues**
Physicians should be aware of, and should thoroughly explain to the
patient, any potential side effects associated with treatments for TTH.
For example, prolonged use or abuse of analgesics may lead to
gastrointestinal irritation, impair platelet function, and cause renal
or hepatic complications. Barbiturate-containing analgesics may cause
drowsiness, analgesic rebound headache, and habituation.
Patients should always be reminded to follow precisely the recommended
usage for any acute headache medication. For example, patients who
medicate their attacks on a daily or near-daily basis may be susceptible
to the rebound phenomenon. Although the medication initially relieves
the pain, response may gradually decrease over time, prompting the
gradual use of additional medication. As this cycle continues - and
worsens - the patient may ultimately develop chronic TTH or daily
headache. Reminding patients to limit their use of acute medications to
a single dose (with one repeat dose if pain persists) may help to avoid
a serious problem before it begins.
**Nondrug Treatments**
Nondrug treatments can be an effective approach to TTH treatment,
especially when used in conjunction with medication. Strategies include
relaxation techniques, proper sleep and diet habits, exercise, and
avoidance of behaviors or situations that may trigger an attack.
Biofeedback has been used successfully in practice, but clinical studies
on its effectiveness have been inconclusive. Physical interventions,
such as acupuncture and acupressure, as well as simple heat or cold
applications may also be useful.
#### CLINICAL ALGORITHM(S)
A clinical algorithm is provided for the pharmacologic approach to
tension-type headache (TTH)
### EVIDENCE SUPPORTING THE RECOMMENDATIONS
#### TYPE OF EVIDENCE SUPPORTING THE RECOMMENDATIONS
The type of evidence supporting the recommendations is not specifically
stated.
In addition to incorporating the US Headache Consortium\'s
recommendations, the conclusions reflect clinical experience and the
most recent medical literature.
### BENEFITS/HARMS OF IMPLEMENTING THE GUIDELINE RECOMMENDATIONS
#### POTENTIAL BENEFITS
Appropriate treatment of episodic tension-type headache (TTH)
#### POTENTIAL HARMS
- Prolonged use or abuse of analgesics may lead to gastrointestinal
irritation, impair platelet function, and cause renal or hepatic
complications.
- Barbiturate-containing analgesics may cause drowsiness, analgesic
rebound headache, and habituation.
- Patients who medicate their attacks on a daily or near-daily basis
may be susceptible to the rebound phenomenon. Although the
medication initially relieves the pain, response may gradually
decrease over time, prompting the gradual use of additional
medication. As this cycle continues - and worsens - the patient may
ultimately develop chronic TTH or daily headache.
### QUALIFYING STATEMENTS
#### QUALIFYING STATEMENTS
Drug therapy is constantly evolving as new research, clinical trials,
case reports, and opinions are published. Many of the drugs recommended
in these guidelines are not approved by the US Food and Drug
Administration (FDA) for treatment of headache, nor are they necessarily
the same as those therapies recommended by the manufacturer for labeled
indications. Their use in headache, however, may be supported by the
scientific literature and by the authors\' clinical experiences. While
efforts have been made to ensure accuracy, the authors and publisher do
not assume responsibility for the consistent updating of available
information for these guidelines, nor for any errors or omissions, nor
for any consequences thereof. The onus is on the practitioner to
evaluate recommendations in light of the clinical condition of the
patient and recent medical literature. The authors advise the
practitioner to consult other sources, especially the manufacturers\'
warnings and precautions, before prescribing any drug with which they
are unfamiliar. Practitioners are also advised that while these
guidelines will address the needs of many patients, there will be
circumstances calling for exceptions to these recommendations.
### IMPLEMENTATION OF THE GUIDELINE
#### DESCRIPTION OF IMPLEMENTATION STRATEGY
An implementation strategy was not provided.
#### IMPLEMENTATION TOOLS
Chart Documentation/Checklists/Forms\
Clinical Algorithm\
Foreign Language Translations\
Patient Resources\
Slide Presentation
For information about
[availability](#identifying-information-and-availability), see the
\"Availability of Companion Documents\" and \"Patient Resources\" fields
below.
### INSTITUTE OF MEDICINE (IOM) NATIONAL HEALTHCARE QUALITY REPORT CATEGORIES
#### IOM CARE NEED
Getting Better
#### IOM DOMAIN
Effectiveness
### IDENTIFYING INFORMATION AND AVAILABILITY
#### BIBLIOGRAPHIC SOURCE(S)
Ruoff G, Urban G. Treatment of primary headache: episodic tension-type
headache. In: Standards of care for headache diagnosis and treatment.
Chicago (IL): National Headache Foundation; 2004. p. 53-8. \[6
references\]
#### ADAPTATION
Not applicable: The guideline was not adapted from another source.
#### DATE RELEASED
2004
#### GUIDELINE DEVELOPER(S)
National Headache Foundation - Private Nonprofit Organization
#### SOURCE(S) OF FUNDING
National Headache Foundation
#### GUIDELINE COMMITTEE
Not stated
#### COMPOSITION OF GROUP THAT AUTHORED THE GUIDELINE
*Authors*: Gary Ruoff, MD, and George Urban, MD
#### FINANCIAL DISCLOSURES/CONFLICTS OF INTEREST
Not stated
#### GUIDELINE STATUS
This is the current release of the guideline.
#### GUIDELINE AVAILABILITY
Electronic copies: None available
Print copies: Available from the National Headache Foundation, 820 N.
Orleans, Suite 218, Chicago, IL 60610; Phone: (888) NHF-5552; Web
address: [www.headaches.org](http://www.headaches.org/)
#### AVAILABILITY OF COMPANION DOCUMENTS
The following are available:
- The complete headache chart. Chicago (IL): National Headache
Foundation (NHF); 2 p. Electronic copies available in Portable
Document Format (PDF) from the [National Headache Foundation Web
site](http://www.headaches.org/consumer/presskit/hachart.pdf)
- National Headache Foundation fact sheet. Chicago (IL): National
Headache Foundation (NHF); 2004 Oct. 2 p. Electronic copies
available in Portable Document Format (PDF) from the [National
Headache Foundation Web
site](http://www.headaches.org/consumer/presskit/factsheet.pdf).
Print copies: Available from the National Headache Foundation, 820 N.
Orleans, Suite 218, Chicago, IL 60610; Phone: (888) NHF-5552; Web
address: [www.headaches.org](http://www.headaches.org/)
#### PATIENT RESOURCES
The National Headache Foundation (NHF) has created a variety of
educational resources for patients, including informative brochures, a
patient diary for migraines, Power Point presentations, and patient
guides; many of these resources are available in both Spanish and
English. Some of these items are available as print copies for purchase
through the [NHF online
store](http://www.headaches.org/consumer/storeindex.jsp). Electronic
versions of other resources are available through the consumer education
section of the [NHF Web
site](http://www.headaches.org/consumer/educationindex.html).
Print copies: Available from the National Headache Foundation, 820 N.
Orleans, Suite 218, Chicago, IL 60610; Phone: (888) NHF-5552; Web
address: [www.headaches.org](http://www.headaches.org/).
Please note: This patient information is intended to provide health
professionals with information to share with their patients to help them
better understand their health and their diagnosed disorders. By
providing access to this patient information, it is not the intention of
NGC to provide specific medical advice for particular patients. Rather
we urge patients and their representatives to review this material and
then to consult with a licensed health professional for evaluation of
treatment options suitable for them as well as for diagnosis and answers
to their personal medical questions. This patient information has been
derived and prepared from a guideline for health care professionals
included on NGC by the authors or publishers of that original guideline.
The patient information is not reviewed by NGC to establish whether or
not it accurately reflects the original guideline\'s content.
#### NGC STATUS
This NGC summary was completed by ECRI on April 11, 2005. The
information was verified by the guideline developer on April 26, 2005.
This summary was updated by ECRI on June 16, 2005, following the U.S.
Food and Drug Administration advisory on COX-2 selective and
non-selective non-steroidal anti-inflammatory drugs (NSAIDs). This
summary was updated by ECRI Institute on May 8, 2007, following the U.S.
Food and Drug Administration advisory on Zanaflex (tizanidine
hydrochloride).
#### COPYRIGHT STATEMENT
These guidelines are for reference purposes only and are not to be mass
produced. This information is copyrighted by the National Headache
Foundation, 2005.
### DISCLAIMER
#### NGC DISCLAIMER
The National Guideline Clearinghouse™ (NGC) does not develop, produce,
approve, or endorse the guidelines represented on this site.
All guidelines summarized by NGC and hosted on our site are produced
under the auspices of medical specialty societies, relevant professional
associations, public or private organizations, other government
agencies, health care organizations or plans, and similar entities.
Guidelines represented on the NGC Web site are submitted by guideline
developers, and are screened solely to determine that they meet the NGC
Inclusion Criteria which may be found at
<http://www.guideline.gov/about/inclusion.aspx> .
NGC, AHRQ, and its contractor ECRI Institute make no warranties
concerning the content or clinical efficacy or effectiveness of the
clinical practice guidelines and related materials represented on this
site. Moreover, the views and opinions of developers or authors of
guidelines represented on this site do not necessarily state or reflect
those of NGC, AHRQ, or its contractor ECRI Institute, and inclusion or
hosting of guidelines in NGC may not be used for advertising or
commercial endorsement purposes.
Readers with questions regarding guideline content are directed to
contact the guideline developer.
Bottom of Form
© 1998-2008 National Guideline Clearinghouse
Date Modified: 11/3/2008
| en |
converted_docs | 417578 | <table>
<colgroup>
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 17%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 16%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="6"><strong>COMMENTS FROM PUBLIC REVIEWERS</strong></td>
<td colspan="7"><strong>AUTHOR'S RESPONSE</strong></td>
</tr>
<tr class="even">
<td><blockquote>
<p><strong>Comment</strong></p>
<p><strong>Number</strong></p>
</blockquote></td>
<td><blockquote>
<p><strong>Reviewer</strong></p>
<p><strong>ID</strong></p>
</blockquote></td>
<td><strong>Chapter</strong></td>
<td><strong>Page</strong></td>
<td><strong>Line</strong></td>
<td><strong>Comment Text</strong></td>
<td><blockquote>
<p><strong>Acknowledged,</strong></p>
<p><strong>but no further</strong></p>
<p><strong>response or revisions</strong></p>
<p><strong>are required</strong></p>
</blockquote></td>
<td><blockquote>
<p><strong>Revisions have</strong></p>
<p><strong>been incorporated</strong></p>
<p><strong>as suggested in the</strong></p>
<p><strong>comment</strong></p>
</blockquote></td>
<td><blockquote>
<p><strong>Agree, but see</strong></p>
<p><strong>"Notes on</strong></p>
<p><strong>Response"</strong></p>
</blockquote></td>
<td><blockquote>
<p><strong>Agree, but</strong></p>
<p><strong>elaboration is</strong></p>
<p><strong>precluded by length</strong></p>
<p><strong>limitations</strong></p>
</blockquote></td>
<td><blockquote>
<p><strong>Disagree; see</strong></p>
<p><strong>"Notes on</strong></p>
<p><strong>Response"</strong></p>
</blockquote></td>
<td><blockquote>
<p><strong>Beyond scope of</strong></p>
<p><strong>report/chapter</strong></p>
</blockquote></td>
<td><strong>Notes on Response</strong></td>
</tr>
<tr class="odd">
<td><p>W-1</p>
<p>Ref: G-11</p></td>
<td>Amy Kaminsky</td>
<td><p>General</p>
<p>Chapter 5</p></td>
<td></td>
<td></td>
<td>“in press” or “submitted” references. If the articles or books have
already undergone peer review and are in their final form, these
references should be assumed to be published peer-reviewed literature.
If the articles or books are not in final peer-reviewed form, the
authors should fully comply with the Guidelines for approval and
materials availability</td>
<td></td>
<td>XX</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><mark></mark></td>
</tr>
<tr class="even">
<td><p>W-2</p>
<p>Ref G-2</p></td>
<td>Amy Kaminsky</td>
<td><p>General</p>
<p>Chapter 5</p></td>
<td></td>
<td></td>
<td><p>Grey literature sources - newspapers, the trade press, websites,
advocacy documents, position papers or research plans for the
government’s conservation partners– which may not have been
peer-reviewed,</p>
<p>The authors should fully comply with the Guidelines for approval and
materials availability.</p>
<p>To ensure clarity on the part of readers, we request that the authors
carefully differentiate in the text or in the list of references their
use of non-peer-reviewed sources.</p></td>
<td>XX</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><p>I think my materials comply with the guidelines. In the reference
section, I used an asterisk to denote non-peer reviewed material.</p>
<p><mark></mark></p>
<p>It would be helpful for the report to include a statement about
non-peer reviewed literature, especially that, when used as examples of
research activities (rather than research outcomes) or agency practice,
the use of non-peer reviewed literature is useful. Those comments are
not appropriate within my specific chapter.</p></td>
</tr>
<tr class="odd">
<td><p>W-3</p>
<p>Ref: G-11</p></td>
<td>Amy Kaminsky</td>
<td><p>General</p>
<p>Chapter 5</p></td>
<td>141</td>
<td>3179</td>
<td>“in press” or “submitted” references. If the articles or books have
already undergone peer review and are in their final form, these
references should be assumed to be published peer-reviewed literature.
If the articles or books are not in final peer-reviewed form, the
authors should fully comply with the Guidelines for approval and
materials availability</td>
<td></td>
<td>XX</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><p>Updated (Schaake, in press)</p>
<p>All URLs updated.</p>
<p>The one date-sensitive URL citation has been modified to include a
specific date for which Internet Archive access is available (e.g.,
through the Wayback Machine).</p></td>
</tr>
<tr class="even">
<td>W-4</td>
<td>Williamson</td>
<td>Chapter 5</td>
<td>100</td>
<td>2171-2173</td>
<td>The text on these lines reads: “Meteorological prospects are
mediated by those placing the water orders or through short-term weather
forecasts that may affect operations when the system is near some
constraint…” I’m not sure I understand the expression, “Meteorological
prospects,” and I question the use of the word “mediate” in this
sentence. Please consider rewriting the sentence to clearly convey the
author’s point.</td>
<td></td>
<td>XX</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Sentence reworded.</td>
</tr>
<tr class="odd">
<td>W-5</td>
<td>Williamson</td>
<td>Chapter 5</td>
<td>100</td>
<td>2184-2186</td>
<td>The text on these lines reads: “For long-term planning and design
applications, observations are less important because the effects of
recent conditions have less impact on long-term outcomes than future
meteorological uncertainty, or even institutions at multidecadal time
scales.” The use of the word “institutions” is confusing along with the
entire sentence. Please consider rewriting the sentence to clearly
convey the author’s point.</td>
<td></td>
<td>XX</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>“institutions” changed to “institutional change” and entire sentence
recast.</td>
</tr>
<tr class="even">
<td>W-6</td>
<td>Williamson</td>
<td>Chapter 5</td>
<td>99</td>
<td>2149</td>
<td>The CloudSat mission [misspelled CloudSAT in draft] was launched in
April 2006 and has been successfully providing data since June 2006, so
it is not a future or planned satellite.</td>
<td></td>
<td>XX</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
| en |
all-txt-docs | 041939 | ARPANET Mailing Lists and Usenet Newsgroups
Creating an Open and Scientific Process
for Technology Development and Diffusion
by Ronda Hauben
rh120@columbia.edu
Introduction
In an article in the journal "The Information Society",
Luciano Floridi from Wolfson College at Oxford, notes the
importance of the Internet and how it has generated an excitement
and promise for the future. Floridi writes:
[L]ast year the Internet finally appeared to the general
public as the most revolutionary phenomenon since the
invention of telephones, though in this case Time missed the
opportunity to elect the Internet Man of the Year.(1)
Floridi, contrasts the significance of the new development
represented by the Internet with the relative lack of scholarly
study and knowledge about its development:
A whole population of several million people interacts
by means of the global network. It is the most educated
intellectual community that ever appeared on earth, a global
academy that, like a unique Leibnizian mind, thinks always.
The Internet is a completely new world, about which we seem
to know very little....its appearance has found most of us,
and especially the intellectual community, thoroughly
unprepared.
However, to "know" something it is helpful to look at its
early development, as that is when its form and principles are
most clearly articulated.
The foundation for the Internet was set by the development
of the ARPANET(b. 1969) and Usenet(b. 1979), which were connected
to each other in the early 1980s. This paper will examine some of
the early computer conferencing research work to link those on
different computers or using different operating systems on
the ARPANET and then on Usenet. It will explore how the foundation
was set to promote computer facilitated communication, which was some
of the scientific and collaborative work which made the Internet
possible. There will be an effort to quote early pioneers when
possible to give an indication of the process as well as the
result of their work.
Part I
Support for a Scientific Methodology
Writing in the 1960s, the German philosopher Jurgen Habermas
described a scientific methodology developed by the U.S. Air
Force to solve difficult technological problems. He outlines the
process of communication established between those contractors
who would work on a problem and the Air Force personnel
involved, the importance placed on communication to identify the
precise nature of the problem, and then the combining of practice
and theory to develop a methodology to solve the problem.(2)
A similar kind of collaborative communication process was developed
via the early mailing list MsgGroup on the ARPANET and this process
helped to make it possible to develop and expand the ARPANET into
the Internet.
ARPA and the ARPANET
When the Soviet Union lauched Sputnik I, the world's first
man man satellite on October 4, 1957, they took the world by
surprise. In the U.S., President Eisenhower summoned scientists
to provide advice to the White House on how to advance U.S.
science and technical developments. Believing that the
competition within the U.S. Department of Defense (DoD) was a
problem that had to be solved if the U.S. was to advance in its
ability to do forefront scientific and technological development,
Secretary of Defense Neil McElroy created a new agency, apart
from the three existing branches of the services. This new
agency, the Advanced Research and Projects Agency (ARPA) was to
provide support for advanced space research. By the early 1960's,
ARPA recognized the need to expand its scope, and J.C.R.
Licklider was brought in to head a new office that would take on
research in computer science. Licklider served as the first head
of the Information Processing Techniques Office (IPTO) at ARPA
from 1962 to 1964. The earliest work of the IPTO was to fund
research in the time-sharing of computers, to make interactive
computing available in a way not possible with the batch operated
computers common at the time.(3)
By the late 1960's however, time sharing of computers had
developed and there were different computer time sharing systems
around the U.S. Those at ARPA began to envision a linking up of
these different systems so that the resources could be shared
and so those using different computer hardware and software would
be able to communicate with each other.(4) Also, the work of
pioneers like Paul Baran at RAND in the U.S. and Donald W. Davies
working in the United Kingdom, indicated that a more economical
form of data transmission, i.e. packet switching, would provide
an appropriate technology for data transmission. Recognizing the
need to do research in creating a computer data network that
would make it possible to share resources among researchers doing
work on different hardware and software platforms, a contract was
awarded to BBN to begin the construction of a subnetwork that would
connect various ARPA contractors at universities and other sites
with ARPA contracts. The new network became known as the ARPANET.
Those connected to the ARPANET grew rapidly and by the mid 1970's
there was the recognition that a new form of communication
had developed on the ARPANET called electronic mail or more
commonly, email.
MsgGroup Begins
In a message submitted to the Msggroup mailing list dated June
7 1975, Steve Walker, of ARPA (IPTO) and Net Manager of the
ARPANET(5) describes a proposal for communication research on the
early ARPANET. He writes that he is "seeking to establish a group
of people concerned with message processing" in order to "develop
a sense of what is mandatory, what is nice, and what is not
desirable." He notes, "We have a lot of experience with lots of
services and should be able to collect our thoughts on the
matter."
The methodology he proposes, however, is of particular
importance. He is encouraging the creation of a new form of
computer conferencing to be developed on the early ARPANET. "My
goal," he writes, "at present is not to establish 'another
committee' but to see if dialogue can develop over the net." He
notes that there is probably something less formal already
occurring, but he wants to broaden it to be able to include more
of those who could make a contribution. Participation will be
encouraged, but it is voluntary. "I do not wish to force anyone to
participate," he explains, "but I strongly urge anyone with
comments (positive or negative) to toss them in."
Also, the form of participation was to be open ended, rather
than requiring particular kinds of contribution. "While
supporting philosophical discussions," he writes, "I like very
much the specifics of...evaluation....Can we try to do this," he
asks, promising that "the results may surprise many of us."
He requests that the participants "encourage a FORUM-type
set up if it's not too difficult to set up, realizing that many
(myself included) will have little time to contribute." Though
he recognizes that such sporatic participation may be thought
to fragment the group, he proposed they should be made and
will prove to be a contribution.
"I've asked Dave Farber to maintain a list of Message Group
participants," he continues, noting that Dave Farber, then on the
faculty at the University of California Irvine, a participant
on the ARPANET, would help facilitate participation in the online
forum Walker was proposing. Extending his invitation to newcomers
to be full participants without feeling they have to gather any
particular background, he explains, "those who don't wish to have
their message files filled with possible `junk mail' should feel
free to withdraw." But he expresses the hope that it will be possible
"from all this to develop a long term strategy for where message services
should go on the ARPAnet and indeed in the DoD." And Walker ends his
message by encouraging participation, "Let's have at it."
The mid 1970's was a period of change in developing the
usefulness of computer mail on the ARPANET. Previous to 1975, the
creation of programs making email possible on the ARPANET was
more of an informal undertaking, according to a study of ARPANET
email posted to MsgGroup by Raymond R. Panko(6). Panko notes the
earliest work in developing email capabilities grew up on the
earliest time sharing systems funded by ARPA in the early 1960s.
"But the value of computer mail had become obvious to ARPA by the
beginning of 1975," he writes how ARPA had, like a number of
other...organizations, had begun to use computer mail for its
bread and butter communication and had become aware that a
relatively mature communication medium was becoming available.
It was against this background of increasing interest by ARPA in
email that Steve Walker issued the invitation to take part
in an online conference to develop a computer conferencing system.
Farber responded to Walker's invitation, "I too second the motion
of Steve to Let's have at it."(7) Farber promises to maintain a file
of correspondence for those who participate in case they miss any of
the messages or do "not feel like making like a file clerk."
Those involved agree to accept the challenge of exploring
how to create a network conferencing system using ARPAnet
communication. In considering the difficulties of using such
technology during this period in the mid 1970s, David Crocker, at
the University of Southern California presented his evaluation of
three possible programs that those on MsgGroup could use to form
their online conference. One of the programs was FORUM, a
conferencing system developed under DoD funding. Crocker explains
that this conferencing system "has a long start-up curve and requires
that all paticipants have access to the same machine."(7) Another
proposed conferencing program TCTalk, Crocker notes, "requires
that all have operating access to the operating system Tenex,"
which was one of the operating systems used by some of those on
the ARPANET.(8)
Since those on the ARPAnet were using a variety of different
computers and several different operating systems, Crocker
believed that neither a program dependent upon a single type of
computer nor one requiring a particular operating system would be
appropriate. Instead he explained that there was a program being
used to send email on the ARPANET (i.e. Net Mail) that was
already being used by those on the ARPAnet and it made
communication between users with diverse computer systems and
operating systems possible. Crocker also noted some of the other
advantages of Net Mail. He wrote(9):
Use of Net Mail a) is extrememly convenient for most, if not
all, of us, since we already exercise it for other
activities; b) allows passive observation of the dialogue,
rather than forcing everyone to explicitly catch up on
recent comments....; c) mail is easily deleted and so "junk"
mail is not really a serious problem. Most, if not all of us,
have mail reading systems which allow a "menu" review of mail,
prior to reading the contents.
Proposing that Net Mail will best satisfy the aims of the
research, he writes: "I have spent the better part of this spring
looking at our teleconferencing capabilities (as part of a
seminar...) and as a result, suggest we continue to use Network
mail as our communication tool, rather than using TCTALK or
FORUM."
Listing the participants in MsgGroup at this early period
and the sites where they have their computer accounts(10), Farber
identifies Burchfiel, Myer and Gilbert from Bolt Beranek and
Newman, the Cambridge, MA contractor who created the IMP subnetwork
for the ARPANET. He lists Tasker, McLinden, Walker, Farber, Stefferud,
Ellis, Kirstein, Iseli, Dave Crocker, and Paul Baran at ISI at the
University of Southern California. At Office-1, he lists Uhlig and Watson,
at MIT-DMS, Vezza, and at Harvard-10, Mealy.
In a message noting the promising potential of this
new form of computer networking communication, another early
MsgGroup participant(11), Tasker writes, "Sitting here in the
offices of a potential military user...I am extremely gratified
and excited to see the msg group interacting and that those
interactions appear to be converging around real capabilities
that I think can be sold to the operational military guy. A scant
three or four months ago I never would have even hoped for the
current state of affairs and the direction it indicates."
In a similar vein, Ron Uhlig at Office 1 expressed his
enthusiastic support for MsgGroup. Describing the informal
project he was working on for the Army Materiel Command
(AMC), he wrote(12):
For those of you unfamiliar with our "experiment"
in Army Materiel Command, we have been using OFFICE 1 for
communication among seven of the key managers in data
processing in Army Materiel Command (AMC)....In general, we
have had the same kind of experience in improved
communication that ARPA had when they began using a
message system on the network. Continuing major cuts in the
Army Materiel Command work force plus some fairly major
reorganizations which are now being planned are
leading us to give serious consideration to adopting
an on-line computer based message system for key managers
throughout the command. We are in the early stages of
trying to define what such a system needs to look like....
Since we are aiming more at the informal communications
we are not terribly concerned with the DOD traditions...
Our primary concern is that the message system be
easily usable by noncomputer science people, some of whom
are actively hostile to computers in general. The
demonstrations that we have given to various
noncomputer science, non technical personnel around AMC
have generally been well received. But one must know
far too much "computerese" to use any of the existing
systems."
Elaborating on the need for online conferencing, he writes:
We have a strong need for teleconferencing because
our key managers are greatly dispersed geographically. The
message system that we eventually adopt needs a
teleconference capability. We don't want message handling
and teleconferencing to be in two separate systems.
Because of this we also want to make it easy in the middle
of a message based teleconference to link to a data bank
somewhere in AMC to pick up information which is needed at
that point in time. An FTP type capability, simple to use
for the novice, would meet the need very nicely.
Concluding his comments, he promises continued feedback:
As we get better definition on our requirements
during the next few months I will put additional messages
into the network to keep you all current on our
thinking. This message is only intended to be introductory.(10)
A subsequent message by Crocker suggested they ignore authentication
issues, whcih like other security issues, were considered secondary and
were avoided for the time being.(13).
Given the current state of network/system/mail security, I
suggest we ignore authentication issues.
Summarizing the progress made in the first month since the
beginnings of the new form of network communication, Steve Walker
writes(14):
The MsgGroup...was formed...by a group of interested people
commenting on how message services should appear to users
(as opposed to how they should function internally.) I'm
pleased with the progress of this `conference'. I am trying
to arrange for Stefferud to serve as a `paid' organizer so
that the groups ramblings can come out in a coherent form. I
would encourage your continued participation here and in
groups such as Dave Farber's Compcom get together.
Part II
Vision of New Form of Computer Communication
Documenting the success of the work done by those on
MsgGroup and subsequent ARPANET mailing lists, a report prepared
for a technical conference in 1979 by several MsgGroup
participants, observed that there had been important advances in
email and conferencing capabilities. (15) The report explained how
these achievements are not only a natural outgrowth of technological
advances, but also the result of the convergence of communication
and computers. "In various current networks of computers," they
write, "large numbers (thousands) of individuals and agencies are
able to communicate among themselves via message exchange using
many different computers and terminals in the process." This was
not an easy feat to achieve.
Their report notes the value to people who have access to
these computer message services (CMS). They write(16):
Those who have access will be able to communicate through
the CMS facilites with others who have access as the number
of connected individuals and agencies grows, the value of
being connected will grow....The key source of value lies in
the range of easily addressable potential communication.
In the development of MsgGroup conferencing efforts, several
describe the unique capabilities that a mailing list like
MsgGroup has made available to those participating. For example,
in a post, Pickers(17) describes how a mailing list creates a
participatory process that is superior to what traditional meetings
could make possible. He writes:
Unlike normal conferences, where there are limited
microphones, a chairperson and where audience energy tends
to wear down, MSGGROUP style conferencing never resolve issues
much less adjourns. This effect follows naturally from the
observation that every participant reenters the discussion
by choice, perhaps following a recuperative and regenerative
period of rest.
Others on MsgGroup consider the problem of emotional
messages (also known as flaming). However, Gaines, in a post(18),
proposes that such problems are secondary and should be
recognized as "the price we have to pay for an open discussion
group where people are free to voice their ideas....We must
expect that this whole process produces a fair amount of
nonsense...."
Most importantly, however, he points out:
We are feeling our way in a murky area, and have to expect
to make mistakes. Let us judge the msggroup by the good
ideas that surface which by the nature of the area have to
be expected to be few and far between but worth the overhead
of the other traffic when they arrive.
Emphasizing the unique nature of the contributions to
MsgGroup, Charles Frankston with a login at MIT, warned that
analogies between electronic mail and telephone and paper
communications must be made very carefully. Electronic mail, he
writes(19), "is a new medium and it may not necessarily make
sense to use it in the same fashion as existing medium, any more
than it would have made sense to use telephones in precisely the
same fashion as telegraphs that preceeded them."
Observing that "electronic mail is currently used
extensively for communications which today does go to many
recipients," he cites interoffice memos as an example. "As a new
medium I also claim electronic mail has generated new uses not
heretofore possible, he continues, "For example, most of my use
of the medium consists of back and forth technical discussions,
often among persons widely dispersed geographically....In fact,
the great advantage of electronic mail for this sort of use, is
that it is easy to simply cc anyone I think might be interested
or have information to provide on the current topic."
Another report, titled "The Convergence of Computing and
Telecommunications System," by Dave Farber and packet switching
pioneer Paul Baran, was posted to MsgGroup(20). Farber and Baran
were able to collaborate to write the report via the ARPANET
despite the fact they lived in geographically different regions
of the U.S. In the report, they wrote that "A major change in
computer communication is taking place....Tomorrow, computer
communication systems will be the rule for remote collaboration."
Problems and Benefits
In their report, Farber and Baran observed that the falling
costs of computing would lead to a situation where certain
industries and institutions would feel threatened by the
"prospect of obsolescence of their present justification." One
such industry they predicted would be publishing.
In his study of email, Panko, too, noted a similar barrier
to technological development of email and email conferencing. He
observed the inability of commercial users to recognize the
advantage of email and of the increased communication that email
and online conferencing made possible. However, both Panko's
study and the report by Farber and Baran emphasized that many
others would welcome the new forms of communication that this
convergence of computers and communication technology would make
possible. Panko pointed to the promising development represented
by the 15 million people involved with CB radio in the U.S., out
of a possible 70 million households. This promised that a warm
welcome would greet the increased ability for communication to be
made available via email and email conferencing.
Social Issues Become Important
Panko documented how government funding of computer science
researchers to solve the problem of computer conferencing
communication across different computers and different operating
systems had yielded great social and technical benefits. He
wrote(21):
"Historically, computer media were first extensively
developed on the ARPANET. Anyone familiar with the Advanced
Research Projects Agency (after whom the ARPANET is named)
realizes that ARPA was the dominant funder of leading-edge
computing during the 1960's. Essentially, ARPA was funding
the community of hobby computerists par excellence. Funding
was fat and creativity was given free reign during business
hours. Moreover, ARPA contractors found their staffs working
long overtime, developing space war games, stock market
information services, and -- as noted above, computer mail
systems. In other words, hobby computering at a grand scale
was the original source of many advanced mail systems today.
Computer mail had a strong hobbiest flavor in its use as
well as in its origins. Colleagues in artificial
intelligence, data base design, and other exotic fields used
computer mail to build and maintain their community."
"Furthermore," he added, "in applications where computer
teleconferencing has been successful, discussion has often been
free-wheeling and chatty. The longest conferences tend to be
breezy and rambling, yet very successful in exchanging ideas and
viewpoints...."
Thus he noted the great stimulus given to these email
developments by the support of government financed programs.
In their report, Farber and Baran recognize that social
questions would arise as a result of these important new
communications developments. And they realized that too little
emphasis would be given to examining the social consequences that
had to be considered to determine what the future should be for
these social developments. For example, the issue of how
decisions over the new medium would be made wasn't being given
adequate consideration.(22) "Little attention," they wrote, "is
paid to the `public interest.' In part, the term defies
definition. Is the public interest the interest of the cross-
subsidized residential telephone user? Is it the interest of a
business which faces a reduced communications bill? Is the public
interest to be viewed primarily in the short term irrespective of
long term damage to existing institutions in achieving immediate
savings."
Summarizing the promise for the future that enhanced
communication would hold, Lauren Weinstein wrote(23):
The whole point of Msggroup to me is that we are free to
communicate without undue worry about costs, and to borrow a
line from the closing episode of the `Connections' program
from PBS, "the easier it is to communicate, the faster
change occurs." It is this very change that is creating the
systems, concepts and most importantly, the EXPECTATIONS of
people for message systems of the future.
Part III
Government Use at the FCC
While the ARPANET was helping to research how ARPA would use
online communication, other government entities found it helpful
in broadening the mechanism of input into their work.
Stephen Lukasik had been a director of ARPA from 1970 until 1975.
After he left ARPA (then called DARPA), he spent some time at
government contractors Xerox and RAND. By September 1979, he
posts on MsgGroup(24):
I recently assumed the position of Chief Scientist at the
Federal Communications Commission in Washington.
He notes that he is looking to fill the position of Deputy
Chief Scientist/Engineer who will assist him in directing
technical, scientific and engineering activities of his office at
the FCC. He also announces that there will be positions in a new
Technical Planning Staff within the agency. And he requests input
from those on MsgGroup.
In October, 1979, Lukasik announced that he was to give the
keynote at the December Computer Networking Workshop at the
National Bureau of Standards (NBS).(25) "The topic will be regulation
of computer communication," he wrote. And he asks for both
questions and input into his talk. "I would be interested to know
what questions and concerns you have in this area. Your
viewpoints would also be welcome." He signed his message Steve
Lukasik, Chief Scientist, FCC, and his message included "reply
to: LUKASIK@usc-isi" so that replies could be sent to him by
email.
In February 1981, Stefferud posted an unofficial copy of an
FCC Notice of Inquiry (NOI) to MsgGroup, though those interested
in receiving an official copy were instructed to write
MJMarcus@ISI(26). "This copy is being circulated," the message
explained, "via MsgGroup to allow individuals with ARPANET access
to comment informally on the NOI. Interested parties may file
comments on or before March 16, 1981," Stefferud noted. "You may
file informal comments by sending messages to MJMarcus@ISI. To be
considered by the FCC, your informal comment should include your
full name and U.S. Postal Service Address."
Stefferud described how it was even possible to file
informal comments via email, "All such messages will be forwarded
to the Secretary for filing in the Docket as stated in paragraph
23 of the NOI where informal comments are solicited from
DEAF-NET users." DEAF NET was a demonstration telecommunications
network project for the deaf funded by Department of Health,
Education and Welfare funds. Questions about procedure could be
sent by email to Mike Marcus or "with MsgGroup distribution so we
may share your questions and answers."
"Any discussion of this NOI in the regular manner of group
discussion via MsgGroup distribution," Stefferud noted, "will
also be made available to the FCC as informal public comments in
response to the NOI, and as such will be forwarded to the
Secretary for filing in the Docket."
"This is a new kind of activity for MsgGroup," Stefferud
wrote, "and we hope that it might afford some progress in the use
of network facilties for the type of inquiry." He went on to note
that the FCC was not sponsoring his actions, but that the FCC
staff was aware of what he was doing to facilitate online input
into an FCC process.
"The use of MsgGroup is not sponsored by the FCC, though it
is understood that FCC staff members are aware of our
undertaking."
The text of the Notice of Inquiry in FCC 80-702 General
Docket 80-756 followed as a message to MsgGroup. The issue
involved Digital Communications protocol conversions between
different networks.
Email comments to the U.S. Postal Service
Another example of government officials seeking input from
MsgGroup participants involved United States Postal Service
interface specifications for Electronic Computer-Originated Mail
(ECOM). Richard Shuford posting from MIT-AI (27) in a message
dated July 8, 1981, noted that there had been an announcement in
the Federal Register on June 19, 1981 (page 32111) of a public
meeting for questions and comments on the proposed system. That
meeting was then held at the Postal Services headquarters in
Washington, D.C. However, as there seemed to be no press coverage
that the meeting would happen, only "professional Federal
Register readers" knew of the meeting to attend it. Shuford
described how the result of this situation was that "the meeting
was therefore attended only by representatives of large
corporations that have some economic interest in what the Postal
Service does with electronic mail." However, a few days before
this post on MsgGroup Shuford had received a call from a Postal
Service consultant who worked at SRI International. The
consultant said that he wasn't on the ARPANET but wanted Shuford
to send a message to those on the ARPANET for him. "He feels very
strongly," wrote Shuford, "that comments on the proposed system
should come from a wider variety of `stake-holders' (as he calls
them) in the future of electronic mail. In particular, he would
like to hear comments from personal computer users and others who
are not interested in electronic mail from a purely commercial
point of view." He related how the deadline was in 2 weeks on
July 23, 1981 and that comments could be sent by regular mail to
Charles Shaw, Director of Electronic-Mail Systems Development at
the Postal Service Research and Development Laboratory in Maryland.
Shuford explained that the consultant was making his request
in an unofficial capacity and that therefore comments sent to
Harris should not mention his request.
In response, Pickers at SRI-UNIX observed(28):
"In a message which is sent to 100+ institutions, 200+
individuals and spanning both North America and Europe (5
million square miles), the suggestion to keep an individual's name in
confidence seems a bit incongruous."
Steve Kudlak, at MIT-MC disagreed. He wrote(29):
"ACTUALLY THATS NOT TOO UNREASONABLE TO BELIEVE. We all know
the Arpanet is another world and I assume a very high
percentage of us are nice enuff to hold someone's name in
confidence if they requested it."
Several messages later, on July 18, Shuford explains that
Ron Newman at Parc-Maxc had located an email address for the
consultant and that it was possible to send him one's comments
directly by email.(30) "He will then have them printed and will
pass them along to the proper people at the Postal Services.
Please keep in mind," Shuford emphasized, "that any comments
passed along in such a manner are officially regarded as
`informal' comments. And that to register `official' opinion,
traditional procedures had to be followed." Thus a way to make
input directly into a government proceeding was available via
email.
Many different issues were discussed on MsgGroup and when
some on the list suggested limiting what could be discussed,
others on the list would invariably complain and encourage a
broadness of subjects.
Debating the Focus of MsgGroup
For example, Brian Reid at Carnegie Mellon University,
objected to efforts to limit the discussion on MsgGroup. He
wrote(31):
MsgGroup is the closest that we have to a nationwide Computer
science community forum. MsgGroup is supposedly devoted to
topics involving electronic mail. One of the many virtues
of computer-based mail systems is their astounding ability
to support conferencing. All of us are still learning a lot
about the ways in which people communicate over these
marvelous mail systems, and about the kinds of discussions
that can and cannot be made to work over computer-based mail
networks.
Despite the large amount of supposed chitchat that passes
over MsgGroup... I believe that such conferencing schemes
are still very much at the research stage, and that
ARPA and the public will ultimately benefit from our
experiences using MsgGroup as a nationwide community forum,
no matter what the topic at hand.
Until such time as people start suggesting the overthrow of
our government over MsgGroup, I don't think any sensible
topic should be off limits unless you decide that said topic
falls outside the scope of MsgGroup. If you decide to
restrict the topics that ought to be discussed in MsgGroup,
then I submit that there ought to be a "Network-Forum"
mailing list which could be a general-purpose forum.
The crucial issue for the MsgGroup, however, was seen to be
the discussion of message systems and eventually of office
automation. In May of 1980, Stefferud announced that office
automation should be a significant focus of the MsgGroup mailing
list. He wrote(32):
As the "Coodinator in Chief" of MsgGroup, I would like to
take this opportunity to ask whether we should shift our
focus to office automation in general, as a natural
expansion from the message systems orientation that we have
had for the last five years? (Yes! Count them, five whole
years!)
It is my opinion that the ARPANET provides the best
available prototypical office automation environment, one
that contains all the required facilities, elements,
functions, and features somewhere or other around the net.
I use a wide variety of systems on different hosts to get my
work done. I truly use the network as my electronic office,
which is somewhat remarkable because I am working as a
management consultant, rather than as a computer or network
technician.
Unless we hear some serious dissent, we should consider this
change of focus to be a fait accompli.
Cheers - Stef
His proposal was greeted with support(33):
I agree wholeheartedly with Stef that we should accept our
destiny and let all office automation be within the Msggroup
purview. I, too, conduct large amounts of my work via
various network facilities, and often describe the "office
of the future" to groups as already existing within the net
framework. So by all means let's continue discussions such
as the recent one on the Prime OA stuff.
[Howard]
But it was also greeted with an opposing view from Gaines at
Rand (34). He wrote:
I think the term "office automation" is at once too broad
and too narrow for the charter of MsgGroup. The MsgGroup
ought to broadly focus on issues relevant to computer
generation, manipulation, and transmission of messages....
But, there are nevertheless aspects of office automation
that are pretty distant from issues related to messages.
Taste and judgment rather than any sort of strict rules
should be the determinant of whether something is
appropriate for the MsgGroup, and we ought to take kindly to
rather far removed discussions if somebody considers that
they are worth presenting to the MsgGroup. However, I think
we ought to still say that our focus is on issues related to
computers and messages. The field of office automation is
too narrow. Messages are used in other context than what
people normally associate with the office environment....
Men communicate for a large variety of reasons in a wide
variety of circumstances and we should not narrowly
constrain ourselves to any one subset of that universe of
communications.
"So here's a vote against a change of focus and a vote for a
very wide latitude in interpreting what falls within the purview
of MsgGroup," concluded Gaines.
Stefferud responded that his view of office automation was
not a narrow one, but a broad one encompassing the broad scope
that was being proposed by others. He wrote(35):
Thanks...for your careful comments. I concur with
your assessment and suggestion. I see the new focus as
being wider as you propose it, but your clarification is
very helpful.
From my ARPANET experience, I find that office automation
should mean the application of computer networking and
computer mail facilities to all kinds of work in all
possible locations.
Office Automation does not belong exclusively to the Word
Processing Industry any more than to the TWX Switching
Industry or the ADP Systems Industry. It belongs to the
integration of all these, which to this date has only been
demonstrated in these hallowed ARPANET halls.
And, to me, COMPUTER NETWORK MAIL is THE KEY ADDED INGREDIENT.
So to further set our new context - Onward! Stef
While new and exploratory uses of the Net were tried out on
MsgGroup, there was also discussion of the kinds of uses that had
to be prevented. In a post by Leonard Foner(36) explains that
as a "tourist" on the ARPANET he was able to get an account at
MIT but had to sign and return an application form which detailed
"good uses of MIT's computer resources, as well as caveats about
things that a tourist should not do. It is fairly simple at
least to warn them about abusing the network," he wrote,
especially against using it for commercial purposes, which were
forbidden. He recommended, "That all users of the net...should be
informed as to its intended uses, and what is strictly forbidden
(such as profit-making from the Net)....Discussion of funded
research on the net seems fine," he continued, noting that that
was what the ARPANET was created to support."
In 1977, a message from IPTO's Steve Walker indicated that
he would no longer be following MsgGroup in his old status, but
that he had found the work done by those participating in
MsgGroup very valuable. He wrote(37):
It has been a long time since I have sent a message to this
group but I have certainly enjoyed the dialog which has
taken place here for the past two and a half years.
In remembering all the things that have happened during that
time, it is with a good bit of reluctance that I announce my
departure from ARPA in late January for a position with the
Undersecretary of Defense for Research and Engineering. In
my new position I hope to be able to influence the
acceptance by the Defense Dept of secure computer systems,
interactive message systems and general networking
capabilities. I plan to remain active on the ARPAnet and to
maintain close contact with groups such as yours.
I am personally proud to have been associated with the
collection of people on the ARPA network who got this whole
message handling, electronic mail thing started. Keep up
your excellent work.
"Have a good holiday season," his message ended.
The Need for Interneting
By 1979, Crocker noted that he and others were working on
a project to create a new distributed mail program MMDF, Multi-
channel Memo Distribution Facility(38), "to allow mail
transmission between machines which have access to a variety of
communication lines." In particular, he wrote, "We want to allow
interneting and to eliminate the need for being attached to the
ArpaNet."
A report by the DCA (Defence Communications Agency) in July
1980 documented how the ARPANET had grown to over 66 nodes and
included 4000-5000 users(39). The report explained how even though
the ARPANET was successful, there were problems. "The basic
hardware and software are becoming obsolete," it noted. It
described how the nodes used minicomputers developed in the 1960s
which no longer had sufficient memory and other capabilities to
support technical components to the network. The ultimate goal,
"of our planning," the report explained, "is to provide for an
ARPANET II which will be a virtual network and will make use of
several different networks."
The report described how in the next 3 years the ARPANET
Host Protocols Network Control Program (NCP)would be replaced
with a new DOD Standard Protocol Set. The new protocols were DOD
Standard Transmission Control Protocol (TCP) and the Internet
Protocol (IP). Also, new computers would replace the IMPs and
TIPs that formed the IMP subnetwork administered by BBN. All
Honeywell equipment was to be replaced with the BBN C/30 costing
$20,000 - $35,000 (depending on the configuration) if funding
could be obtained, and the software would run in a virtual mode.
Unix and the Transition to TCP/IP
Other messages noted that there were many sites that wanted
network connections, but that the ARPANET couldn't accommodate
them. It was during this 1979-80 period that Usenet was being
introduced at Duke and the University of North Carolina to
provide an online network for those in the Unix community.(40)
In a post on July 4, 1981, Mike Muuss at the Ballistic Research
Laboratory noted that it was possible to run Unix on many of
the computers being used by those who wanted network
connectivity. He wrote(41):
"Unix runs on everything these days"
This would help facilitate the transition from the IMP with
NCP subnetwork to TCP/IP protocols that was being planned for
January. 1 1983. "There exists AT LEAST one choice of software for
UNIX systems," writes Muuss in a post on the fa.digest-p on
January 14, 1982,(42) "(all machines), T(w)enexes,
Multics, and IBMs, so the majority of the "ordinary" systems will
at least be able to talk, even if non conveniently." However, he
noted that there was not a TCP/IP implementation for the ITS
machines at MIT that archived and carried many of the ARPANET
Mailing lists.
By May 3, 1982, a post by Steve Hartwell noted, "Let's not
forget, there are more unix sites than arpanet sites." And Usenet
was helping to meet the goal of providing "interoperabilty among
our differently hosted mesage systems." (43).
Also, the problem of large mailing lists had become clear on
the ARPANET. Lists that had several hundred participants like
Msggroup and others were a heavy load on the host machines that
were used to send them out.
Horton noted the superiority of Usenet to ARPANET for
mailing lists as it made it possible to send one copy to each
site, rather than having to send out a copy to each person
subscribing(44), "Note that one of the big points of USENET is that
only one copy of each digest or article is sent to each site...."
Those sites using Unix as their operating system could
connect to Usenet and thus have access to some of the ARPANET
mailing lists. Mark Horton, posting on MsgGroup in 1983 wrote(45):
I'll repeat my invitation to any sites, ARPANET or
otherwise, who want to join Usenet - drop me a line and I'll
point you at a nearby contact. If you run UNIX, the code is
all written; if you run something else, you'll have some
work to do....
Also, by this period several of those who had participated in
MsgGroup and the ARPANET were participants on the discussion on
Usenet. And the MsgGroup themes of supporting and exploring the
development of communication using an online network were
continued via Usenet and the ARPANET mailing lists which were
ported to Usenet by Horton at the University of California at
Berkeley.
Part IV
The Early Days of Usenet
Usenet was created in 1979 by graduate students at the
Duke University and the University of North Carolina who were
trying to create a network to connect those who had access to the
Unix operating system.(46) By the summer of 1980, Mark Horton, at
the University of California at Berkeley had joined Usenet.
Berkeley was also a site on the ARPANET and Horton soon began to
port the discussion from several ARPANET mailing lists onto
Usenet. At first those on Usenet could only read the discussion
on the ARPANET mailing lists, but by Fall 1980, contributions
from Usenet participants began to be a part of the ARPANET lists
carried on Usenet.
Among the earliest ARPANET mailing lists carried on Usenet were
Sf-lovers and Human Nets. By Spring of 1981, however, a new
mailing list was started to deal with office automation. That
mailing list was made available on Usenet as FA.apollo. It was
named after one of the workstations. In an early post to the mailing
list, Roger Duffy wrote(47):
Hello,
Welcome to the APOLLO mailing list. APOLLO discusses
personal work station computers, such as the APOLLO work
station computer, the Three Rivers Corporation PERC, or the
recently announced Xerox STAR. APOLLO provides a way for
interested members of the ARPAnet community to discuss what
is wrong with these machines, compare notes on work in
progress, and share useful insights about these kinds of
systems. The list is managed by Hank Dreifus <Dreifus at
WHARTON>.
He explained that "APOLLO is currently discussing initial
reactions to the Xerox Star Workstation." And he ended his
message, "Lastly, welcome to APOLLO. I trust you will enjoy
being part of these discussions."
A flurry of discussion followed, and it soon began to center
on the pros and cons of having a programming language available
with the Xerox Star Workstation.
Summarizing responses from those on the mailing list and
participating on the Usenet newsgroup, Hank Dreifus at the Wharton
School in PA noted several generalizations he felt applied to the
subject area(48).
o Everyone's view of Personal Workstations is different.
o The machine(s) selected are wide ranged and apparently
well suited for each application chosen.
o There is no wrong Personal Workstation machine.
o The technology of Personal Workstations is not well
established as of yet.
o There is a demonstrated need for this technology,
it appears to be one year away from general use.
The summary listed the common characteristics of
workstations and described the parts not yet available. "The
intention is to educate ourselves about personal workstations,"
explained the post, "They sound neat, but what they are under the
surface is still a hot topic."
Particular discussion in the list focused on the Xerox
machines -- the Xerox Star, their high end machine and the 820, a
less expensive product.
Questions were raised as to whether the 820 could be
networked to the Star. Others asked what software would be
available with the Star (49) and particularly if there would be a
programming system available. One response noted that the Star
would come with a low power programming language, but that a more
powerful programming environment called the Mesa development
system had been developed at Xerox would not be made
available(50).
Apparently, the poster noted, "the reasoning behind this
involves consistency in system software." The post explained that
Xerox felt it would keep users from doing harm to the system by
restricting access to the Mesa programming environment. Those who
wanted new applications would have to ask Xerox to create them.
Another post explained that if Xerox wanted to succeed in
selling the Star (51) "it is essential that they provide a decent
programming language with it. Otherwise," the post continued, "it
will be just a word processor or maybe a little more." He went on
to explain that those using the Star would need specific
specialized applications and only if there was a programming
language would it be possible to have those written.
A subsequent post noted that though the initial purchase of
the Star was expensive, that would end up being a minimal cost
compared to the cost of renting software. He wrote (52):
You people seem to be concentrating on the hardware costs of
STAR, which, from my reading of the information available is
just the start-up. I think this is like worrying about
Gillette's pricing of the razor-blade holder. Most people
will be renting software (...blades) forever. This could get
very expensive.
Soon the moderator of the Apollo mailing list announced that
the name of this office automation system mailing list would
changed and on Usenet would become FA.works for personal
workstations, as it wasn't appropriate to name the list
after one particular product(53).
The economics of buying a workstation was the subject of
discussion. One post noted (54) that because workstations like
the Star appeared expensive ($10,000 per person) they would
probably be attractive to managers rather than office peons.
Another poster (55) responded pointing out that for an engineer
earning $30,000 a year, his or her time might cost the company
$60,000, when the cost of the technology being used was added
to the salary paid. If having such a personal workstation like the
Star made work more productive, it would save the company money and
thus be worth the investment. He wrote (56) "so if I do my work 10%
faster, the company in some way, "saves" 6,000 (the savings could
be in hiring less engineers or by getting more work done per unit
time or by getting the job done more effectively."
Another post cautioned that there was an interest cost to
borrowing for capital investment (57). "At today's rates, $10K
capital investment costs the economy 20% interest, either directly
because they had to borrow it, or indirectly because they don't
have it to invest elsewhere. So your increase in productivity,"
he noted, "would have to be at least 20% to break even. He went
on to discuss the difficulty of proving such "increases in
productivity."
One of the participants on the FA.apollo newsgroup, and
on the successor newsgroup that followed it, FA.works, was Randy
Ivanciw. He had also posted on the MsgGroup list. He became a
regular contributor to the FA.Apollo and FA.works.(58)
In his introduction, he wrote:
I am Randy Ivanciw, a computer specialist with the US Army
Development and Readiness Command (DARCOM). My major duties
include long range and short range planning for office
automation. I work at DARCOM headquarters (I am a civilian)
as a member of a 7 person staff dealing with the use,
planning, implementation and other nasties of office
automation.
He explains how the installation at DARCOM benefitted from
the discussion on the list, which helped to make possible a broad
view of what they were trying to do. He wrote:
In reading the debates pro and con on big systems and little
systems, where big systems are large mainframes and little
systems are personal workstations....Let me illustrate how
we have attempted to incorporate both worlds in our OA
plans.
Describing the system he helped create, he writes:
DARCOM has a DEC 10 (DARCOM-KA) on the ARPANET which it uses
to provide electronic mail and other OA services to a broad
community of users throughout the command (the command is
all over this country). Access is via ARPANET. Advantages here
are that for a relatively inexpensive yearly charge a
remotely located single user can obtain OA service with a
communications capability as powerful as the ARPANET. This
service is in such demand that we cannot supply services in
large enough quantities (thus the DEC 10 will soon be
replaced with a couple of 11/780s to provide more services).
Outlining a 3 level office automation system, he explains
how it is used to encourage participation.
For example, let me paint a typical scenario of one of
DARCOM's subordinate commands or activities just entering
into the world of office automation:
The Commander or somebody at the command wants to try office
automation. Now they are unsure of its benefits so they
don't want to spend mucho money. The buy a mailbox on our
DARCOM-KA (LARGE MAINFRAME). With this mailbox they can
experiment with all the OA tools.
After a short while they want 5 or 10 other people at their
command or activity to get mailboxes so that they can
communicate via electronic mail. They buy more mailboxes on
the large mainframe.
Then it is determined that office automation is good for the
command. They make large scale plans to provide OA services
to 100, or 200, or 300, or how-ever-many prople. At this
point the economies of scale move towards the LARGE CLUSTER
machine. With a large cluster installed locally, the
command is essentially running their own OA.
But soon they find that more and more users are demanding
service. Enter the small cluster. As one division goes from
one or two users (who were getting OA services on the large
cluster) to a demand to provide services to 8 or 10 people
in that particular division, a micro computer is installed
in the division to provide those services (and offset the
demand on the large cluster).(59)
His post indicates a process within ARPA encouraging office
automation. The discussion on FA.apollo and then FA.works mailing
proved helpful to those like Ivanciw who were charged with such a
task, but who didn't find their questions were answered by the
vendors. For example, Ivanciw, describes the difficulty he
encountered during a sales event trying to get information about
how successfully the Xerox 820 and Star Workstations could be
connected to the Ethernet. He writes (60), "So what it breaks down
to is this: there are not too many folks at Xerox that know how
these things connect to the ethernet. The literature is written
so that one can assume a lot."
A response to his post described how the two different Xerox
workstations had been developed and how there was ethernet
capabilility really functioning on only one of them. Paul Karger,
who had worked at Xerox, wrote (61):
The key to getting through the Xerox propaganda is to
realize that there is NOT one, but TWO office automation
product lines which have been forcefully "merged." These
lines were developed by two competing groups and don't
really have much in common....
The two product lines evolved and were designed separately....
I hear that the Xerox sales force is claiming that they have
an integrated product line for office automation. Low cost
820's up to the Star. Ah . . . I don't think I can agree
with that. I believe they are undermining their credibility
when they try to convince people of this.
Karger's post included a diagram with two columns describing
the origins of the two sets of products designs(62). In a postscript
to his message, he wrote:
P.S. Randy -- to answer your specific message, the products
in column one all have the Ethernet designed and built in
from the start. The products in column two have had the
Ethernet added with chewing gum and bailing wire (if at all).
Part V
Questioning What Should Be Discussed
Not surprisingly there were managers at Xerox who were not
happy about the kind of frank discussion ongoing on the ARPANET
mailing lists. A post by David Liddle, Vice President of the
Office Products Division at Xerox explained his reluctance to
have Xerox products discussed by Xerox employees on the ARPANET
(63):
Many of you in Xerox are aware of a newly created Arpanet
distribution list named Apollo. It was established to
promote discussion of personal workstation computers. As you
might expect, much of the recent discussion has involved the
Xerox 8010 Star information system. Because many of the
messages ask for information about this product and its
associated development software, you may feel tempted to
reply to some of them.
It is ARPA policy that the Arpanet be used only for
government supported research and development. It is against
Xerox policy to use the Arpanet to discuss products....
Xerox employees use the Arpanet for ARPA related research
purposes only, not for answering questions or distributing
information about our products.
Questions from potential customers about the Xerox 8010 and
other OPD products should be referred to Arnold Palmer,
Field Sales Manager, Xerox Corporation, 1341 West
Mockingbird Lane, Dallas, Texas 75247, phone (214) 689-6689.
David E. Liddle
Vice President
Office Products Division
A response to Liddle's post challenged the reasons he had given
for limiting discussion. Lars Ericson at CMU wrote(64):
The use of the ARPANET for informal discussion of computer
science -- related issues is a primary win. It is clear that
such discussion is beneficial to ongoing government research
projects -- DARCOM and Office Automation for example, are
well represented on the Work Station.
Ericson continued:
Mr Liddle also seems to forget that the reason PARC efforts
are so immensely saleable these days is precisely BECAUSE of
their participation and open-ness (as opposed to IBM, say)
in the ARPA/university research community, and not in spite
of it.
"Mr. Liddle's Xerox policy announcement," Ericson wrote,
"represents the sort of irrelevant (to ARPANET interests)
administrative miserlyness that we may come to expect from Xerox
now that the 13-piece suits have brought PARC to market."
Also responding Little's post, Joe Newcomer emphasized ARPA's
policy forbidding commercial use of the ARPANET(65).
Joining the controversy, Crocker explained (66):
It is my understanding that the purpose of this discussion is
to consider the technical aspects of personal work-stations.
Arpa and the rest of the military are investing quite a bit
of money in this area, so that this discussion would seem to
be extremely appropriate to the Arpanet mission.
He added:
I do not believe that conformance with the Arpanet
proscriptions necessarily requires commercial participants
to be prohibited from voicing opinions about the technology
in general or from answering specific questions about their
product. Touting their product is another matter.
Crocker's proposal was that, "I suggest that each company
assign one technical (not marketing) person to respond to
queries. This will permit direct information, while making
"tone-control" easier."
Part VI
Limited Distribution?
Not only was there reluctance on the part of representatives
of some commercial entities to have open conversation of all
issues on ARPANET mailing lists ported to Usenet, but also there
was a sense among ARPANET participants that their contributions
should be considered privileged private publications and their
distribution strictly limited. A conversation describing this
issue developed on FA.digest-p carried on the ARPANET and on
Usenet. In January 1982 a post noted that Computer World magazine
had gotten copies of the TCP digest from someone and published
verbatim quotes from the digest(67). Though the source of the
leak acknowledged what had been done and agreed to stop, "it gave
everybody a real scare," the post noted. "My temporary solution
to this issue," the poster proposed, "is to add the following
notice to the Masthead:
"TCP/IP Digest Thursday, 8 Oct 1981 Volume 1 : Issue 1
----------------------------------------------------------------------
LIMITED DISTRIBUTION
For Research Use Only --- Not for Public Distribution
---------------------------------------------------------------------
At least this ensures that anybody who gets fed a copy knows that
it is not supposed to be shouted to the treetops. Comments?"
Christopher C Stacy at MIT disagreed with such a publication
identifier. He wrote (68):
I think that the explicit banner on the masthead of the
Digest is a bad idea, because this will cause many people to
think that if such a banner is NOT present (ie., on any
other Digests or on future TCP Digests) that it is alright
to redistribute the material.
In another post, Stacy described his understanding of why
ARPANET mailing lists had to have limited distribution. (69) He
pointed to an incident that had occurred when MIT had to fight
for its continued existence on the ARPANET after an article in
the journal Datamation about the WINE-TASTERS mailing list
appeared. He also cautioned of the possible liability problems
when evaluating and discussing various commercial products, as
with the INFO-TERMS mailing list which evaluated terminals.
"But laying down the law," he wrote, "is a fairly useless
way of solving this sort of problem. The problem is one of
awareness, cooperation and trust. Only if people understand and
care, will they take steps to protect a fragile institution like
the ARPANET," he wrote.
Another post noted that the mailing list digests "do not
exist as authorized publications." (70) He felt that they should
be considered "internal communications between research project
members authorized to use the net."
A post asking about the implications of the Daniel Ellsberg
case to this issue by Mike Muuss was answered by Paul Karger.
Karger wrote (71):
While putting a restricted distribution statement on a
digest may be a psychological limitation on distribution,
there are a couple of problems. First, since ARPA and DCA
are part of the DoD, there are specific regulations on what
may or may not be marked as FOR OFFICIAL USE ONLY.
The regulations are in part designed to not let people
invent other kinds of markings. This dates back to the
Ellsberg case and the desire to limit the ability of
government people to conceal information from the "public"
(whoever that is).
Though Karger said his familiarity with the regulations was
a little stale, "I would be very careful about developing new
ways to restrict distribution of government information," he
cautioned.
Through this discussion, concerns for limiting the ARPANET
discussions were raised, and answered with the limitations that
the current state of relevant law allowed US government officials
to impose on the ARPANET mailing list discussions.
Thus the way was cleared for broader distribution of the
posts on ARPANET mailing lists, making the transition from the
limited circulation available on the ARPANET to the broader
participation Usenet made possible.
Part VII
Usenet Welcomes All
While access to the ARPANET was limited, Usenet welcomed all
who were willing to connect in a public way (72). "Usenet is a
public network," wrote Mark Horton, "and those on it should
announce themselves."
"It seems to be a common thing," he wrote, "for a new site
to come upon USENET without telling anyone they exist." What
happens," he explained, "is that someone hears about USENET from
someone already on the net, who sends them their copy of whatever
code they are running." He asked, "When you start getting network
news, you should announce your existence to the net by filling
out the enclosed form and posting it to the newsgroup net.general....
This form will be used as your entry in the USENET directory.
Note," he continued, that is the policy of USENET that all sites
receiving public newsgroups (such as net.all and fa.all) are
public in the sense that the fact they are on USENET is public.
The name and phone number of a contact person, as well as the
name and location of the site, is important. If you are doing
some kind of secret work there is certainly no need to divulge
the nature of your work. If you feel that you must keep your
existence a secret, you should not be joining USENET," Horton
clarified.
A form was provided for a new site to fill in. Horton asked
that those joining Usenet post their announcement and basic
configuration information in NET.general. NET.general was the one
newsgroup that all were on Usenet during this period were
encouraged to read (73). "net general," wrote Horton, "is for
stuff that everybody is supposed to at least consider reading.
"It's useful for INITIAL QUERIES and ANNOUNCEMENTS." However, he
noted that "It is NOT there for discussions." He explained, "If
you see something in net.general you want to comment on, you
should almost always just REPLY to the author, not follow up to
the world. If a continuing discussion is needed, start a new
newsgroup." He also suggested replying to initial queries from
NET.general in NET.misc. "NET.misc," he wrote, "is a good way to
keep net.general free of trivia without starting new newsgroups
for short lived topics." He urged those on Usenet to realize that
not all might be interested in a particular topic but "feel
obligated to read things in net.general because of their possible
importance."
Matt Glickman, who with Mark Horton wrote the code for B
News, supported Horton's request for maintaining NET.general as a
newsgroup that would concern all. He wrote (74):
Just reminding everybody (It feel it is my duty...) that
net.general is no run-of-the-mill newsgorup. No sir. It's
not net.misc and it's not net.news. net.general should only
contain GENERAL interest information of interest to the
ENTIRE network. Especially, no dreaded newsgroup discussions
whatsoever! Please behave yourselves.
Therefore, while the posts on NET.general don't document the
interesting discussion carried on on early Usenet, they do convey
some of the general concerns and views of the pioneering Usenet
participants.
Many of those on early Usenet were programmers or system
administrators. As such, they are particularly sensitive to
misspellings and other textual and writing errors. In a post on
NET.general, one user gathered comments from all interested about
concerns about what they considered poor writing that appeared on
Usenet. In response, Rob Glaser from Yale wrote (75):
It is true that many technical people use the English
language sloppily. In an informal setting such as USENET,
however, content ought to be valued over form, timelines
over lengthy deliberation. I'd rather see a timely article
with a few grammatical mistakes (as long as it is basically
coherent) than the same piece, impeccably written but
appearing days later."
He also observed that the software (inews) for posting
sometimes was problemmatic and helped create the grammatical or
other errors one saw online. He wrote:
Another factor to keep in mind is that, judging from some of
the submissions we receive over the net, the inews
submission interface is not always conducive to perfection
(not a slap at the news designers, just the imcompetents,
myself included, who make dumb mistakes.)
He then went on to describe how he had had to redo even this
post twice before getting it right. "For instance," he wrote, "I
messed up two earlier versions of this flame (one of which may
have been sent, my apologies if it was) before (*pray*) finally
getting things right."
Other posts on NET.general included requests for
recommendations for buying something worthwhile or complaints
about problems users were having with commercial entities to see
if others had similar problems or could help.
For example, a post by Larry Piovano (76) described how he
was planning to buy a color tv with a 13" screen. He asked for
recommendations and experiences of others to help him decide
which brand to get. "I wish to buy one," he wrote, "that will not
die in short order." Bill Shannon from Digitial Equipment
answered (77), "My 12 inch Sony has been going strong for 10
years with no repairs, no adjustments, no problems! And I'm sure
they've gotten better (and more expensive)." A response on Usenet
responded (78):
Suggest SONY. I have two trinitrons and they work
wonderfully...."
The post continued:
I have had my SONY for a couple of years now and have had no
problem. I suggest you get one with an electronic tuner (no
moving parts to wear out). Try the wireless remote control.
Its a great toy if your lazy."
A similar question about recommendations regarding the Hayes
Smart modem was posed by John L. McAlpine in Canada at the
Saskatchewan Linear Accelerator. He wrote (79):
Use of HAYES Smart Modem
1) I would appreciate receiving comments on the reliability
of above modem.
2) If anyone has available the appropriate patches to use
this modem with uucp for auto-dialling I would appreciate
receiving same.
A post by Ron Gordon at Bell Labs (Murray Hill) warned other
Volkswagon Rabbit owners of a potential radiator tank leak. He
wrote (80):
Attention VW Rabbit owners, you may have a problem! The
radiator overlow tank on my vehicle developed several cracks
which permitted coolant to escape. Because the overflow tank
is directly connected to the radiator system without a
valve, a leak in the overflow tank is just as bad as a leak
in the radiator!
He went on to ask if other VW Rabbit owners were having a
similar problem. "My tank failed after 16 months at 15,000
miles," he wrote, "Should enough evidence become available, a
formal complaint may be filed with VW and the Consumer Protection
Agency."
Another Usenet poster asked if there could be a consumer
forum newsgroup to monitor companies that ripoff consumers. In
his post, Randy King wrote (81):
What provisions, if any, have been made to provide a sharing
of gripes about national "ripoff" companies and the like? I
would like to hear some comment on this, as well as see the
establishment of a newsgroup (as if any more were needed).
It might be very interesting to see what goes [on-ed] out
there and to provide readers with some insight to companies
so that they may not be smitten by these "invisible
stalkers!
"What's the feeling out there," his post asked.
Responding to an answer by Andy Tanenbaum from Bell Labs
about the intent of his post, King wrote that he had had in mind
an insurance company, but that the forum could discuss both
problemmatic and beneficial companies. (82)
Several of the posts on NET.general suggested creating new
newsgroups, such as a post by Linda Seltzer at Bell Labs (83):
I would like to start a newsgroup called net.music
`for communication among composers, news of concerts
and conferences, news about computer music, news of
good new records, etc. Anyone interested in
subscribing to this group please send mail to
research.lin or alice.seltzer
- Linda Seltzer
Another post noted that her email was inaccurate in her
post, and that it should be alice!seltzer (84).
Other posts concerned general questions or problems. For
example, Andy Tanenbaum posted about a piece of junk mail he had
received from a head hunter who seemed to have gotten his name
from the list of conference attendees who attended the previous
USENIX winter conference (85). "I DON'T want junk mail from
employment agencies," he wrote. "If you want to put up a
recruiting note at a USENIX, fine. But as long as I have a means
here to express my dissatisfaction, I want it to be known that I
look with bad feelings toward companies that badger me by abusing
a valuable resource." His post ended, "I wouldn't want a future
list of conferees to not have addresses just because some losers
bother some of the good folks on the list with junk mail. Don't
call us, we'll call you."
A post by Jay Lepreau asked if there were any archive of
bugs for software that had been posted on Usenet so he wouldn't
have to do work others had already done. He wrote (86):
Has anyone out there been archiving any of the "net.*bugs"
newsgroups or just have old stuff still kicking around? We
just joined Usenet around the beginning of November; if
anyone has stuff from before that I'd appreciate hearing
from you. I'm TIRED of fixing bugs i know have been found &
fixed before. I can send you a shell script to pull stuff
out of your .nindex if you've got A news; I don't know how B
news works.
A post from Scott Baden announced (87) that he was in the
process of creating an annotated bibliography on two topics:
"Functional Programming languages" and about "Applicative
architectures." He asked those with any references or comments to
email them to him, promising, "I'll make a copy of the
bibliography available to all interested parties. If you have
already started a bibliography I'd be interested in collaborating
with you."
News items were posted as was one on the AT&T settlement
with the U.S. government posted on January 8, 1982 by Steve
Bellovin. The post explained (88):
AT&T and the U.S. government have settled their seven-year-
old anti-trust suit out of court. Under the terms of the
settlement, AT&T will divest itself of the local operating
companies; it will retain AT&T Long Lines (the long distance
service), Western Electric, and Bell Labs. The
reorganization will be completed within 18 months.
Questions about Usenet were posted, as in a post by Randy
King asking how long it took a post to get to the majority on
Usenet. He wrote (89):
This may have been answered long before my emergence onto
NETNEWS, but I will ask it anyway! Does anybody have a feel
for how long it takes a posted article to reach the majority
of the NETNEWS community? I realize that there are N!
variables here, but a general ordinary run-of-the mill
answer would suffice. Two Days? Three Days? A month? Fifteen
minutes? (HA). How 'bout it.
A response from Horton described the process of distribution
of Netnews during this period. He wrote (90):
It depends on the newsgroup and where you are. If you are
somewhere inside Bell Labs or on a key machine with a dialer
(decvax, duke) it will probably get out to 70 - 80% of the
net within a few hours. If not, you probably have to wait
for an overnight poll, but it will get most places ( >90% )
overnight. There are some far reaches that won't get it for
2-3 days (more if something is down) and it may take another
2-3 days for a reply or followup to get back to you.
Horton went on to describe how distribution of the Mailing
Lists carried on Usenet occurred. He wrote:
The fa newsgroups are different. They are fed in at Berkeley
which then waits for ihnss [at Bell Labs-ed] and decvax [at
Digital Equipment Corp-ed] to poll. ihnss only polls once a
day (in the early morning). decvax calls often. So Bell Labs
(which gets most stuff from ihnss) tends to have fa stuff
each morning from the previous day. Those getting news from
duke or decvax get it randomly, faster depending on when
decvax happens to call ucbvax (at Berkeley-ed) usually
several time a day.
Horton also described other delays affecting how users got
news from Usenet. He wrote:
And of course there are the delays from the time the news
shows up on a system to when any given person actually reads
it - often once a day, but some people log in on neighboring
machines to get news and don't get it that often. I have
gotten replies to queries as much as 3 weeks later, not
counting the famous unix-wizards drought where it took 2
months to reach the masses before it even got into USENET!
In summary, he wrote, "But a rough rule of thumb is that by
overnight, most of the net will have at least had the chance to
read your article."
Along with the advantages of being on Netnews were the
problems that users were confronted with. One such problem
concerned discussion over what was appropriate discussion or in
bad taste. Others claimed it was censorship to bar certain
discussions. Describing this problem, Horton wrote:
Also, PLEASE restrict your "questionable taste" stuff to
net.jokes.q for the time being until this whole thing is
settled. I am seeing stuff in net.general about dead babies
that certainly offends me (and no, I'm neither dead nor a
baby) and probably half the rest of the net. I'm still
seeing poor taste jokes in net.jokes. There are people out
there that are trying not to get this stuff, and they are
being barraged with it anyway! This includes limericks -
most of them belong in net.jokes.q. If you would be
unwilling to get on your local TV station and recite what
you're posting (with your mother and your boss in the
audience) you shouldn't be broadcasting it to an equally
wide audience of random people. Remember, also, that a
record is kept on every machine of everything you say.
He also asked for input from those who found such posts
offensive toward trying to determine an appropriate policy with
regard to such posts. He wrote (91):
I haven't been hearing from many people who actually ARE
OFFENDED by the net.jokes.q stuff. I'd like to get input
from them (either privately by electronic mail or publicly
in net.news) in regards to the policy that needs to be
formed. How you feel about various proposed solutions is
important. Anyone who further understands the Affirmative
Action issues should speak up -- I don't claim to understand
them very well.
Another concern involved what were appropriate posts on
Usenet. J.C. Winterton asked that users not post articles from
the wire services but instead that people subscribe to newspapers
for such information rather than trying to send it around on
Usenet. He wrote (92):
Notwithstanding the fact that some persons do work for Bell,
it STILL costs a bundle to send this stuff around the
continent on this network when it is being shipped by the
wire services anyway. Why not just subscribe to a large
daily newspaper or two. If you really are interested in the
entertainment world you can subscribe to Variety. The New
York Times and the Times of London probably carry everything
else. And where these are unavailable, there are other major
papers. I don't believe that usenet should become an arm of
AP, Reuters, etc. I am reasonably sure that they would be
somewhat upset with the infringing of their copyright as
well. That a thing can be done is not a reason to do it!
Besides, by distributing wire service stuff this way (with
or without authorization) is probably helping to unemploy
some poor newspaper carrier, etc. etc."
Commenting on the proliferation of new newsgroups and
newsgroup names, Horton promised to issue a list of the
newsgroups "officially blessed" to help resolve the problems of
multiple names for similar groups. But he also encouraged those
with various views on the issue to speak up. He wrote (93):
I am coming to realized that people are waiting for me to
say something. We are discussing what to do about the
proliferation of newsgroups - if you want to be involved in
this discussion please send me mail. (We might even, ahem,
start a newsgroup.) I hope to have a list of active
newsgroups, "officially blessed" (whatever that means), in a
few days.
Chain letters also posed a problem on early Usenet. Henry
Spencer from the University of Toronto posted asking users to
recognize the problem and keep it from harming the Net. He wrote
(94):
Some turkeys evidently have decided it's funny, funny, funny
to start sending chain letters around Usenet. With all the
mail headers on them, these messages are many Kbytes. For
some strange reason, when we're paying phone bills for 300-
baud long distance calls, this does not seem amusing. This
is EXACTLY the sort of thing that could lead to humorless
administrators closing down people's network connections on
the grounds that the money is being wasted. For heaven's
sake people, STOP IT!!! Your thoughtless empty-headed
practical joke is endangering the network that many people
worked long and hard to set up!
Noting the kinds of problems those on Usenet had to deal
with, Horton observed the obligation to those on Usenet to
consider its best interest. He urged that those with different
views of the issues involved be active and participate in the
discussions over what to do (95). "I propose that anyone with
opinions on this issue discuss it on net.news. I want to hear
from both sides. This is YOUR NETWORK, remember!
Others on Usenet had hoped that it would make it possible to
form a new form of media or to influence the political process in
a way not formerly available. "Not to belittle any new
newsgroup," George Otto wrote (96), "but it strikes me that we
are developing a real electronic newspaper here."
In a similar way, rdg at allegra wrote (97), "Wouldn't it be
great to use this electronic medium to send notes to our
government officials. i never seem to write postal letters or
telegrams, but we all seem to find these electric notes enough to
use often. Can you image net.reagan with a few authentic
replies."
Scott Baden added (98), "Or what if we could lobby our
favorite senator? (net.lobby, net.senator?)"
The dilemma of funding Usenet posed a problem to some sites
as described in the post by Chris Kent at the University of
Cincinnati. He wrote (99):
We at the University of Cincinnati are on a budget crunch.
Therefore, I have been told to cut down on outgoing calls or
lose the ability to place them. I ask you all to cooperate,
please; try to avoid routing program sources through us
whenever possible. We will continue to transship news, so
that won't be a problem, but will probably poll only every
other day....I am sorry it has to come to this -- but some
people higher up seem to see this as just wasted money. I
will keep you all posted as to our situation.
Chris Kent (cincy!chris)
Others like Mel Haas at Bell Labs (houxm) reported that the
funding of various sites could be jeopardized by an irresponsible
activity on the net and that all users should be aware of the
problems that might be caused. He wrote (100):
This is a plea to clean up the net. Please ! There are
whole sections of the net that are being watched by the
payers of the bills, and what shows now is not good. The
flame and flash content of the past few weeks has far
outweighed the useful. Don't revive the "db" stuff in
net.cooks! Don't send everything to net.general! and,
certainly, don't send anything to both net.general and
another! Put net.news stuff in net.news, net.records stuff
in net.records, etc. Show some consideration for others in
the wording and content of your submittals.
He pointed out that responsible use would help establish how
the Net was a money saver for the sites paticipating and thus
support continued use. He wrote:
Try to make the net a useful exchange of useful nformation
and ideas, that will pay for the service and help people. In
other words, make the net a useful tool, not a place to
expose yourself, our ego and your bad manners. Thank you.
Mel Haas, houxm!mel
Explaining his need for access to Usenet even though he was
would no longer have Net access through the University of
California Berkeley, Michael Shilol wrote (101):
I recently graduated from Berkeley where I enjoyed this
network very much, both for entertainment and for receiving
the latest news on many subjects.
I am now starting a job and will soon be loosing my account
on the Berkeley Vax. My question is:
Is it possible for me to get access to this network in any
way?
Can my company get access to it?
Is there a way to pay for this privilege?
He noted that the useful technical information available on
Usenet was so valuable that a company could benefit financially
from being connected, "This network has been so useful to me for
finding information that I think it is worth money and/or
equipment to get it."
And he concluded his post:
"Any answers, comments, suggestions appreciated."
He then had a form of signature giving both UUCP and ARPANET
address forms.
Michael Shiloh
CSVAX.shiloh@berkekey
UCBVAX!shiloh
In another post, George Otto at Indian Hill Bell Labs noted
the technical superiority of Usenet newsgroups to mailing lists.
He described the problem of keeping mailing lists on different
computers in sync. He wrote (102):
Is anyone working on making mailing lists just as efficient
as newsgroups? One problem with using mailing lists for
maintaining communications among those in a small group of
people is the difficulty of keeping the lists on many
machines in sync. I tried looking into setting up a
program under my ID that would allow others to mail to me
for automatic redistribution to a list I maintained, but
never found a good way to do it.
He noted that Usenet solved the problem in a superior way by
making it possible for people connected to different computers to
participate in a common newsgroup. He wrote:
The beauty of using USENET it that members of affected
groups can be on different machines and need do one or two
simple things to be attached to the common group.
Conclusion
These posts on NET.general show how those using different
computers at a wide variety of different academic and research
sites, many of which were not officially sponsored by any funding
agency, were able to participate in the kind of collaborative
communication and some of the mailing lists formerly only
available to those with access to the ARPANET. More importantly,
Usenet made the process of posing a problem and collaborating
with others to try to determine how to solve it more widely
available. Such a process is needed to solve the difficult
technical and social problems which computers and networking
technology present for our times. Habermas writes that there is a
need to understand such a scientific approach to technical issues
and challenges. What he doesn't recognize is that the technology
itself is needed to help in the process. The early ARPANET as
demonstrated through posts on the MsgGroup mailing list and early
Usenet provide beginning insight into how people using and
directing technology can be part of the important scientific and
regenerative process that contributing to the online community
makes possible.
Footnotes
(1)Floridi, Luciano, "Internet: Which Future for Organized
Knowledge, Frankenstein or Pygmalion?" The Information Society,
Vol. 12, No. 1, p 6.
(2) Writing in 1968, the German philosopher Jurgen Habermas
noted the scientific methodology employed by the U.S. airforce
to solve difficult technological problems. He writes:
The headquarters of the U.S. Air Force using experienced
contact men presents a roughly outlined problem of military
technology or organization to the program department of a
research and consulting organization. The starting point is
a vaguely formulated need. A more rigorous version of the
problem first arises during the course of protracted
communication between officers, themselves scientifically
trained, and the project director. But contact is not broken
off once the real problem is identified and successfully
defined, for this suffices only to conclude a detailed
contract. During the research itself, information is
exchanged at all levels, from the president of the research
organization down to the technician, with the
corresponding personnel at the contracting institution.
Communication may not end until the solution can be foreseen
in principle is the goal of the project. The
preunderstanding of the problem -- the practical need for the
contracting agency -- is articulated in the measure that
theoretical solutions, and consequently techniques of
execution, crystallize in rigorously constructed model. The
communication between the two partners is like a net of
rational discussion stretching between practice and science.
It must not break if during the development of
specific technologies or strategies the originally vague,
preunderstood interest in the elimination of a problematic
situation is not to be frustrated -- if instead its intention
is to be preserved in formalized scientific models.
Toward A Rational Society, Jurgen Habermas, p.71
(3) James R. Killian, Jr., Sputnik, Scientists, and Eisenhower,
The MIT Press, Cambridge, 1977, xv, 129.
(4) Michael Hauben, "The Untold Story of the ARPANET", in Netizens:
On the History and Impact of Usenet and the Internet, by Hauben,
Michael and Ronda Hauben, in press, 1997, URL
http://www.columbia.edu/~hauben/netbook/
(5) The post also has the date of 1978, and so it seems it was
retransmitted in 1978
10-MAY-78 22:09:57-PDT,2463;000000000001
Mail-from: USC-ISI rcvd at 7-JUN-75 2024-PDT
Date: 7 JUN 1975 2024-PDT
From: WALKER at USC-ISI
Subject: MSGGROUP# 002 Message Group Status
To: MessageGroup:
(6) Msg. #456
-------
10-MAY-78 22:13:37-PDT,13009;000000000001
Mail from OFFICE-1 rcvd at 16-FEB-77 1617-PST
Date: 16 FEB 1977 1609-PST
From: PANKO at OFFICE-1
Subject: MSGGROUP# 456 CB Computer Mail Draft
To: msggroup at USC-ISI, farber at RAND-UNIX,
To: schlesinger at PARC-MAXC
(7) Msg.#004
10-MAY-78 22:09:57-PDT,1645;000000000001
Mail-from: USC-ISI rcvd at 8-JUN-75 1636-PDT
Date: 8 JUN 1975 1629-PDT
From: DCROCKER at USC-ISI
Subject: MSGGROUP# 004 Use of a Teleconferencing system, in place of Net Mail
To: MessageGroup:
(8) Ibid.
(9) Ibid.
(10) Msg #013
-------
10-MAY-78 22:09:58-PDT,594;000000000001
Date: 12 JUN 1975 1043-PDT
Sender: FARBER at USC-ISI
Subject: MSGGROUP# 013 Current Message Group Mailing List
From: FARBER at USC-ISI
To: MessageGroup:
Message-ID: <[USC-ISI]12-JUN-75 10:43:25-PDT.FARBER>
(11) Msg #049
-------
10-MAY-78 22:10:04-PDT,2283;000000000001
Mail-from: USC-ISI rcvd at 23-JUN-75 1433-PDT
Date: 23 JUN 1975 1420-PDT
From: TASKER at USC-ISI
Subject: MSGGROUP# 049 MAILSYS; creation prompting
To: [ISI]<Farber>MessageGroup.List:
(12) Msg. #053
(10-MAY-78 22:10:05-PDT,4443;000000000001
Date: 24 JUN 1975 1110-PDT
Sender: AMC at USC-ISI
Subject: MSGGROUP# 053 Army Materiel Command Interests in Message Systems
From: AMC at USC-ISI
To: [ISI]<Farber>MessageGroup.List:
Cc: Gilbert at OFFICE-1, Arntson at OFFICE-1, Cianflone at OFFICE-1, Mitchell a
t OFFICE-1, Dsmith at OFFICE-1, Gunn at OFFICE-1, Uhlig at OFFICE-1
Message-ID: <[USC-ISI]24-JUN-75 11:10:24-PDT.AMC>
(13) Msg# 067
-------
10-MAY-78 22:10:07-PDT,1619;000000000001
Mail-from: USC-ISI rcvd at 26-JUN-75 1108-PDT
Date: 26 JUN 1975 1051-PDT
From: DCROCKER at USC-ISI
Subject: MSGGROUP# 067 Secretaries Answering Boss' mail
To: [ISI]<Farber>MessageGroup.List:
(14) Msg# 097
(15) Msg #1184 IFIP 6.5
(16) Ibid., page 12.
(17) Msg #1429
(18) Msg #1411
(19) Msg. #1365
(20) Farber and Baran Report
(21) Msg #455
(22) Farber and Baran Report
(23) Msg #1427
(24) Msg #1285
(25) Msg. #1326
(26) Msg. #1239
(27) Msg. 1620
(28) Msg. 1622
(29) Msg #1623
(30) Msg. #1631
(31) Msg #680
(32) Msg #1549
(33) Msg #1550
(34) Msg #1552
(35) Msg #1553
(36) Msg. #1605
(37) Msg #624
(38) Msg #1192
(39) Msg #1565
(40) See "The Evolution of Usenet: The Poor Man's ARPANET" by R.
Hauben in Netizens. Also during this period CSNET was being
started by Farber, Landweber and others under a grant from the
NSF to provide online access to members of the computer science
community that didn't have access to the ARPANET. However, there
was a fee for participating in CSNET.
(41) NET.works.0066
(42) NET.works digest.033
(43) Msg. #1721
(44) digest.047
Aucbvax.5828
fa.digest-p
utcsrgv!utzoo!decvax!ucbvax!digest-people
Sun Jan 17 14:30:17 1982
USENET on a PDP-10?
(45) Msg# 2011
(46) See "Evolution of Usenet" in Netizens
(47)Aucbvax.1531
fa.apollo
utzoo!duke!mhtsa!eagle!ucbvax!halbert
Fri Jun 5 11:14:18 1981
Introduction to Apollo
>From DUFFEY@MIT-AI Fri Jun 5 06:19:43 1981
Date: 5 June 1981 09:19-EDT
From: "Roger D. Duffey, II" <DUFFEY at MIT-AI>
Subject: Welcome to APOLLO
To: New APOLLO Subscribers
(48) fa.apollo.0006
Aucbvax.1620
fa.apollo
utzoo!duke!decvax!ucbvax!DREIFU@WHARTON-10
Thu Jun 11 06:48:30 1981
(49) fa.works.0017
Aucbvax.1972
fa.works
utzoo!duke!decvax!ucbvax!Rivanciw.DHQ@UDel
Sat Jun 27 12:41:06 1981
Personal Workstations
(49a) fa.apollo.0017
(50) fa.apollo.0021
(51) fa.apollo.0029
(52) fa.apollo.0028
(53) to check
(54) fa.apollo.0007
(55) fa.apollo.0012
(56) Ibid.
(57) fa.apollo.0013
(58) to check
(59) to check
(60) FA.works.2080
(61) FA.works.069
(62) FA.works.069
Aucbvax.2112
fa.works
utzoo!duke!decvax!ucbvax!works@mit-ai
Sun Jul 5 08:40:37 1981
Re: Ethernet capabilities of 820 and STAR
>From guyton@RAND-UNIX Sun Jul 5 08:31:49 1981
"SDD" "OPD"
+-------------------------+-------------------------+
Location | California | Texas |
+-------------------------+-------------------------+
Programming | MESA | Assembler |
Environment | | |
+-------------------------+-------------------------+
Processor | Custom Bit-Slice | Standard u-processors |
+-------------------------+-------------------------+
Background | PARC/Research | Electronic Typewriters |
+-------------------------+-------------------------+
Product Lines | Star | 820 |
(Partial list | File Server | 850 |
due to failing | Communication Server| 860 |
memory) | Ethernet | |
| Laser printers | |
+-------------------------+-------------------------+
(63) to check
(64) FA.works.0007
(65) FA.works.0008
(66) FA.works.0017
Aucbvax.1912
fa.works
utzoo!duke!decvax!ucbvax!dcrocker@udel
Wed Jun 24 07:22:21 1981
Vendor participation
(67) FA.works.0014
jan 12, digest 114
Aucbvax.5744
fa.digest-p
utcsrgv!utzoo!decvax!ucbvax!digest-people
Tue Jan 12 18:54:24 1982
TCP-IP Digest Frolic
>From tcp-ip@brl Tue Jan 12 18:51:37 1982
-Mike
(68) FA.digest.030
Date: 14 January 1982 00:48-EST
From: Christopher C. Stacy <CStacy at MIT-AI>
Subject: For Research Use Only --- Not for Public Distribution
To: Tcp-IP at BRL, Mike at BRL
cc: DIGEST-PEOPLE at MIT-AI
(69) FA.digest.035
(70) FA.digest.043
(71) FA.digest.0044
(72) NET.general.0341
(73) Dec. 19 647
(74) NET.general.0423
(75) NET.general.0976
(76) NET.general.279
(77) NET.general.0278
(78) NET.general.315
(79) NET.general.0337
(80) NET.general.0088
(81) NET.general.0041
(82) NET.general.0418
(83) Aalice.268
net.general
utzoo!decvax!ucbvax!mhtsa!alice!seltzer
Fri Dec 18 16:57:09 1981
Newsgroup net.music
(84) to check
(85) Afloyd.73
(86) NET.general.0243
(87) NET.general.0357
(88) NET.general. Aunc.1672
(89) NET.general.0417
(90) NET.general.0419
(91) NET.general. Acbosgd.647
(92) NET.general.0323
(93) NET.general Acbosg.285
net.general
utzoo!decvax!ucbvax!ARPAVAX:mhtsa!harpo!cbosg!mark
Wed Dec 16 10:29:01 1981
Re: more mess!
(94) Net.general.0629
Autzoo.1447
net.general
utcsrgv!utzoo!henry
Sun Feb 28 02:42:44 1982
chain letters on the net
(95) NET.general.0229
(96) NET.general.0490
(97) NET.general.0202
(98) NET.general.0204
(99) NET.general.0114
Acincy.169
net.general,NET.general
utzoo!decvax!duke!cincy!chris
Tue Aug 18 15:24:58 1981
Cincy goes on an austerity program
(100) NET.general.0663
Ahouxm.156
net.general
utcsrgv!utzoo!decvax!duke!chico!harpo!floyd!houxi!houxm!mel
Fri Mar 5 08:53:16 1982
Please clean up the net
Thanks to several for offering comments on this draft including Peter
Capek.
Last corrected: 8/5/97
| en |
converted_docs | 759003 | ## U.S. Department of Education November 2002
**2002-2003 *No Child Left Behind---Blue Ribbon Schools Program***
# Cover Sheet
Name of Principal \_\_ [\_\_Mr. Jeffrey
Ratner]{.underline}\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> (Specify: Ms., Miss, Mrs., Dr., Mr., Other) (As it should appear in
> the official records)
Official School Name \_\_[Robert Seaman Elementary
School\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_]{.underline}
> (As it should appear in the official records)
School Mailing Address [137 Leahy
Street]{.underline}\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> (If address is P.O. Box, also include street address)
### \_\_\_\_Jericho \_\_\_\_\_\_New York 11753-1697\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
City State Zip Code+4 (9 digits total)
Tel. [(516)
681-9419\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_]{.underline} Fax [(516)
681-9493\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_]{.underline}
Website/URL [www.bestschools.org\_\_\_\_\_\_\_\_\_\_\_\_\_]{.underline}
Email
[jratner@jericho.k12.ny.us\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_]{.underline}
I have reviewed the information in this application, including the
eligibility requirements on page 2, and certify that to the best of my
knowledge all information is accurate.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date [3/24/03\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_]{.underline}
(Principal's Signature)
Name of Superintendent \_\_[Mr. Henry L.
Grishman]{.underline}\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> (Specify: Ms., Miss, Mrs., Dr., Mr., Other) (As it should appear in
> the official records)
District Name [Jericho Union Free School District\_\_\_]{.underline}
Tel. [(516) 681-4100 ext.
201]{.underline}\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
I have reviewed the information in this application, including the
eligibility requirements on page 2, and certify that to the best of my
knowledge all information is accurate.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date \_[3/25/03\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_]{.underline}
(Superintendent's Signature)
Name of School Board
President/Chairperson \_\_\_\_[Mrs. Hilari
Cohen]{.underline}\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
(Specify: Ms., Miss, Mrs., Dr., Mr., Other)
I have reviewed the information in this application, including the
eligibility requirements on page 2, and certify that to the best of my
knowledge all information is accurate.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Date
\_[3/25/03]{.underline}\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
(School Board President's/Chairperson's Signature)
**[PART II - DEMOGRAPHIC DATA]{.underline}**
**JERICHO SCHOOL DISTRICT**
1\. Number of schools in the Jericho \_\_\_[3]{.underline}\_ Elementary
schools
School District: \_\_\_[1]{.underline}\_ Middle schools
> \_\_\_\_\_ Junior high schools
>
> \_\_\_[1]{.underline}\_ High schools
>
> \_\_\_[5]{.underline}\_ TOTAL
2\. Jericho School District Per Pupil [\$19,978.00]{.underline}
Expenditure:
Average New York State Per Pupil [\$11,871.00]{.underline}
Expenditure:
**ROBERT SEAMAN SCHOOL**
3\. Category that best describes the area where the school is located:
> ( ) Urban or large central city
>
> ( ) Suburban school with characteristics typical of an urban area
>
> \(X\) Suburban
>
> ( ) Small city or town in a rural area
>
> ( ) Rural
4\. \_\_[7]{.underline}\_\_\_ Number of years the principal has been in
his position at this school.
5\. Number of students enrolled at each grade level or its equivalent in
applying school:
+------+------+----------+-------+---+--------+-------+-------+-------+
| * | **\# | **\# | **Gr | | **G | **\# | **\# | **Gr |
| *Gra | of** | of** | ade** | | rade** | of** | of** | ade** |
| de** | | | | | | | | |
| | * | **F | **To | | | **Ma | * | **To |
| | *Mal | emales** | tal** | | | les** | *Fema | tal** |
| | es** | | | | | | les** | |
+------+------+----------+-------+---+--------+-------+-------+-------+
| # K | 20 | 30 | 50 | | | | | |
+------+------+----------+-------+---+--------+-------+-------+-------+
| * | 45 | 32 | 77 | | | | | |
| *1** | | | | | | | | |
+------+------+----------+-------+---+--------+-------+-------+-------+
| * | 40 | 30 | 70 | | | | | |
| *2** | | | | | | | | |
+------+------+----------+-------+---+--------+-------+-------+-------+
| * | 37 | 45 | 82 | | | | | |
| *3** | | | | | | | | |
+------+------+----------+-------+---+--------+-------+-------+-------+
| * | 33 | 30 | 63 | | | | | |
| *4** | | | | | | | | |
+------+------+----------+-------+---+--------+-------+-------+-------+
| * | 40 | 50 | 90 | | | | | |
| *5** | | | | | | | | |
+------+------+----------+-------+---+--------+-------+-------+-------+
| * | | | | | | | | |
| *6** | | | | | | | | |
+------+------+----------+-------+---+--------+-------+-------+-------+
| | | # TO | | | | | | ** |
| | | TAL STUD | | | | | | 432** |
| | | ENTS IN | | | | | | |
| | | THE ROBE | | | | | | |
| | | RT SEAMA | | | | | | |
| | | N SCHOOL | | | | | | |
+------+------+----------+-------+---+--------+-------+-------+-------+
6\. Racial/ethnic composition of \_\_\_[89]{.underline}\_\_% White
the students in the school: \_\_\_\_[1]{.underline}\_\_% Black or
African American
> \_\_\_\_[1]{.underline}\_\_% Hispanic or Latino
>
> \_\_\_\_[9]{.underline}\_\_% Asian/Pacific Islander
>
> \_\_\_\_[0]{.underline}\_\_% American Indian/Alaskan Native
>
> **100% Total**
7\. Student turnover, or mobility rate, during the past year:
\_\_[8.7]{.underline}\_\_%
(This rate includes the total number of students who transferred to or
from different schools between October 1 and the end of the school year,
divided by the total number of students in the school as of October 1,
multiplied by 100.)
+------------+---------------------------+-----------------------------+
| **(1)** | Number of students who | 22 |
| | | |
| | transferred ***to*** the | |
| | school | |
| | | |
| | after October 1 until the | |
| | | |
| | end of the year. | |
+------------+---------------------------+-----------------------------+
| **(2)** | Number of students who | 16 |
| | | |
| | transferred ***from*** | |
| | the | |
| | | |
| | school after October 1 | |
| | | |
| | until the end of the | |
| | year. | |
+------------+---------------------------+-----------------------------+
| **(3)** | Subtotal of all | 38 |
| | | |
| | transferred students | |
| | \[sum | |
| | | |
| | of rows (1) and (2)\] | |
+------------+---------------------------+-----------------------------+
| **(4)** | Total number of students | 436 |
| | | |
| | in the school as of | |
| | | |
| | October 1 | |
+------------+---------------------------+-----------------------------+
| **(5)** | Subtotal in row (3) | .087 |
| | | |
| | divided by total in row | |
| | | |
| | \(4\) | |
+------------+---------------------------+-----------------------------+
| **(6)** | Amount in row (5) | 8.7% |
| | | |
| | multiplied by 100 | |
+------------+---------------------------+-----------------------------+
8\. Limited English Proficient students in the school:
\_\_[1]{.underline}\_%
> \_\_ [4\_]{.underline}\_Total Number Limited English Proficient
Number of languages represented: \_\_\_[7]{.underline}\_\_\_\_
Specify languages: Spanish, Japanese, Chinese, Korean, Italian, Hebrew,
and Russian
9\. Students eligible for free/reduced-priced meals: \_\_[.
025]{.underline} %
> \_\_\_[1]{.underline}\_\_\_Total Number Students Who Qualify
10\. Students receiving special education services:
\_\_[9.5]{.underline}\_\_%
> \_ [41]{.underline}\_\_Total Number of Students Served
Indicate below the number of students with disabilities according to
conditions designated in the
Individuals with Disabilities Education Act.
> \_\_[1]{.underline}\_Autism \_\_\_\_Orthopedic Impairment
>
> \_\_[1]{.underline}\_Deafness \_\_[9]{.underline}\_Other Health
> Impaired
>
> \_\_\_\_Deaf-Blindness \_\_[6]{.underline}\_Specific Learning
> Disability
>
> \_\_\_\_Hearing Impairment \_[17]{.underline}\_Speech or Language
> Impairment
>
> \_\_\_\_Mental Retardation \_\_\_\_Traumatic Brain Injury
>
> \_\_[7]{.underline}\_Multiple Disabilities \_\_\_\_Visual Impairment
> Including Blindness
11\. Indicate number of full-time and part-time staff members in each of
the categories below:
> **Number of Staff**
# [Full-time]{.underline} [Part-Time]{.underline}
Administrator(s) \_\_\_[1\_]{.underline}\_\_\_ \_\_\_\_\_\_\_\_
> Classroom teachers \_\_[21]{.underline}\_\_\_\_ \_\_\_\_\_\_\_\_
>
> Special resource teachers/specialists \_\_[18\_]{.underline}\_\_\_
> \_\_\_[5]{.underline}\_\_\_\_
Paraprofessionals \_\_[16]{.underline}\_\_\_\_
\_\_\_\_[\_\_\_\_]{.underline}
Support staff \_\_ [9]{.underline}\_\_\_\_ \_\_\_[7]{.underline}\_\_\_\_
Total number \_\_[65]{.underline}\_\_\_\_ \_\_[12]{.underline}\_\_\_\_
12\. Student-"classroom teacher" ratio: \_[22:1]{.underline}\_\_\_
13\. Show the attendance patterns of teachers and students.
-------------------- ----------- ----------- ----------- ----------- -----------
2001-2002 2000-2001 1999-2000 1998-1999 1997-1998
Daily student 96.0 95.6 96.0 96.0 96.9
attendance
Daily teacher 96.9 97.2 97.1 97.3 97.4
attendance
Teacher turnover 0.3 0 .03 .03 .03
rate
-------------------- ----------- ----------- ----------- ----------- -----------
**[PART III -- SUMMARY]{.underline}**
*Provide a brief, coherent narrative snapshot of the school in one page
(approximately 475 words). Include at least a summary of the school's
mission or vision in the statement and begin the first sentence with the
school's name, city, and state.*
The Robert Seaman Elementary School is located in Jericho, New York, a
community of about 20,000, located 30 miles east of New York City on
Long Island. The mission of the Robert Seaman School is to promote a
community of students, family, and staff who address the changing
physical, social, emotional and intellectual needs of elementary-aged
youngsters and direct their energy and vitality toward realization of
mastery level performance.
In 1996, the school was reopened as a response to an increasing student
population by a committed and dedicated Board of Education and a
nurturing and highly competent Superintendent of Schools. Since then, we
have developed a rigorous academic program with high expectations for
all and an emphasis on critical thinking, problem solving, curiosity, an
appreciation of the natural world, and the ability to adapt to our
ever-changing global society. We have embraced the diversity brought to
us by a growing number of students who are Korean, Japanese, Chinese,
Columbian, Israeli, and Russian, and have developed a World Language
Program for all our students. Our school has made a strong commitment to
the personal and social development of our students, including character
education and community service. Enrichment activities are open to all
students during recess and after school with club programs like \"Stock
Market,\" Just Think,\" \"Movement and Music,\" \"School Newspaper,\"
and \"Math Olympiads.\"
The Student Council supports a code of conduct based on four principles:
respect, responsibility, integrity, and compassion. Students receive
training to help them support the code through the training in peer
mediation, bullying prevention, and the recently adopted \"Peaceful
Playgrounds\" program. The school's heart and spirit are reflected in
the school song, \"The Robert Seaman School is a Caring Place.\" We have
a committed PTA, which sponsors \"Seamans Cares,\" offering monthly
community service events. The PTA is also active in leading food and
coat drives, scheduling assembly programs, providing parent education,
and playing a key role in school hiring committees.
Our instructional programs are aligned with the New Yok State Standards.
Reading and Language Arts are built around a balanced literacy approach
using authentic literature with a strong emphasis on phonemic awareness
and comprehension strategies. Mathematics and language are interrelated
in that our youngsters are asked to think mathematically as well as talk
and write about their approaches to solving problems or using
computation. They are just as likely to create a graph from gathered
data as they are to analyze data from an existing graph in a textbook.
Our Science program is inquiry-based with a balance between earth,
physical, and life sciences. Science programming includes materials and
resources from the Lawrence Hall of Science and the New York State
Department of Conservation.
Social Studies is activity and project based and includes experiences
with nonfiction and authentic documents. We strongly support physical
education, and cultivate time for art and music. Technology is a part of
almost everything we do, with the computer and library teachers working
closely with classroom teachers. The computer lab, television studio,
and library are in a connected suite visited often by our students,
where we teach them to use computers, projection systems and the
school's web page to present their work. We know that some youngsters
need alternate kinds of support. For about ten percent of our children,
we have individually planned safety nets that include support from a
resource room teacher during the school day and special help after
school from math and reading teachers and teacher aides. Open access
enrichment activities include special interest group instruction, clubs,
and small group activities in reading, science, and mathematics.
**[PART IV -- INDICATORS OF ACADEMIC SUCCESS]{.underline}**
*1. Assessment results in reading (language arts or English) and
mathematics using the criteria determined by the CSSO for the state
accountability system are appended on pp.15-18.*
*2. Show in one-half page (approximately 200 words) how the school uses
assessment data to understand and improve student and school
performance.*
A variety of assessment data are used to understand and improve
instruction and identify students who need special assistance. Beginning
in kindergarten and first grade, students are individually assessed with
the Early Literacy Profile including an informal reading inventory. Any
student in kindergarten through grade three not performing at the
appropriate literacy level is scheduled for in-school support based on
the data we collect.
For grades two through five, assessments are given in English Language
Arts, Math, and Social Studies based on benchmarks that have been
locally developed. The benchmark assessments provide specific data about
the strengths and weaknesses of students in each subject area.
Benchmarks are aligned with skills and knowledge measured by New York
State Assessments. In grade three, students take their first
criterion-referenced state assessment, the Test of New York State
Standards (TONYSS). Results are analyzed to identify students with
literacy deficits, who are then invited to join the after school reading
program at the beginning of fourth grade. During fourth grade, students
take State criterion-referenced exams in ELA, math, science, and these
results are analyzed by our staff.
Reading and math specialists work in classrooms as co-teachers,
targeting their assistance to struggling learners. Lessons are modeled
on prototypes of the New York State exams to assure that required skills
are being developed. Each child's profile, which includes benchmarks,
state, and local assessment data, is updated regularly. This profile is
stored in the district\'s computer data warehouse, where it can be
accessed by classroom teachers, reading and math support staff, and
administrators to monitor progress and adjust interventions.
*3. Describe in one-half page how the school communicates student
performance, including assessment data, to parents, students, and the
community.*
The staff at the Robert Seaman Elementary School communicates student
performance in a variety of ways to our parents, students, and the
community.
Our district has recently adopted a standards-based report card aligned
with New York State Standards and assessments. The new report card is
designed to communicate student proficiency levels in the following
areas: personal development; reading; writing; listening/speaking; math;
science; and social studies. Numbers from 1-4 indicate proficiency
levels along a continuum ranging from \"experiences difficulty in
demonstration of the skills (1)\" to \"exhibits mastery (4).\" Skills
described by each indicator on the report card are specific, such as
\"knows basic sight words,\" or \"uses a range of strategies to
construct meaning from text.\"
Families receive report cards three times each school year, and
parent-teacher conferences are held in December and April to thoroughly
discuss student performance. Besides examining the report cards, these
conferences share results of the Early Literacy Profile and for third
and fourth graders, the results of the district benchmark tests, and the
Test of New York State Standards (TONYSS) and State ELA, math, and
science assessments. During the conferences, teachers also share student
portfolios, offering samples of student work and progress over time.
Each April, the aggregated school assessment data is presented at an
annual PTA meeting by the principal, sharing with parents school-wide
progress and overall strengths and weaknesses in student performance. A
school newsletter is also sent to all parents, which includes the data
reported to the PTA. In addition, phone conversations, IEP meetings, and
progress reports are used to maintain communication between our school
and families.
*4. Describe in one-half page how the school will share its successes
with other schools.*
Our staff welcomes visits from other schools as a vehicle for sharing
success. Teachers and administrators have recently visited us from other
Long Island school districts located in Seaford, Hauppauge, Port
Washington, and Merrick, to observe our approaches to inclusion, math
instruction, and physical education. Open discussion leads to new ideas
and successful practices through replication. At weekly faculty
meetings, building professionals describe positive events that occur in
our classrooms. Examples include novel use of technology, the
incorporation of new units of study, and innovative ways of presenting
curriculum. Networking with pen-pal classes in other school districts,
buddy classes, and curricula projects with other districts allow our
staff members to discuss unique academic successes.
We expect to continue to encourage such visits, as well as to share our
successes through presentations at various professional conferences.
These may include state and national subject area associations, the New
York State Reading Association, and the School Administrators
Association of New York State. As a Blue Ribbon School, we would take
full advantage of dissemination opportunities offered during the Fall
2003 ceremony. In addition, our school will continue to share its
successes district wide through combined faculty meetings with other
elementary schools. And we will explore use of our district web site and
the web site of our county Board of Cooperative Educational Services
(Nassau County BOCES).
**[PART V -- CURRICULUM AND INSTRUCTION]{.underline}**
*1. Describe in one page the school's curriculum, including foreign
languages (foreign language instruction is an eligibility requirement
for middle, junior high, and high schools), and show how all students
are engaged with significant content, based on high standards**. ***
Our curriculum is rich in high-level, interdisciplinary learning
experiences. Our students acquire important knowledge, develop
meta-cognitive skills of inquiry and critical thinking, and display high
levels of interest, motivation and creativity as they approach their
studies. Our balanced literacy program uses the Readers and Writers
Workshop approaches to enable students to read, write, listen and speak
for information and understanding, for literary response and expression,
for critical analysis and evaluation, and for social interaction. For
phonemic awareness and word study, we use the Glass Analysis, Wilson
Program, and \"Explode the Code.\" The social studies content area
learnings for students begin with themselves, their family, and their
neighborhood. Interrelationships between geography, economics and
government are explored. Our social studies program uses the Geography
Terrain Model, \"History Alive,\" original sources, and leveled texts of
historical fiction.
Students in all grades develop the relationships and use commons themes
that connect mathematics, science and technology. Knowledge and the
application of critical thinking skills in math, science and technology
are applied to address real-life problems and help students make
informed decisions. Students use mathematical analysis and scientific
inquiry as appropriate to pose questions, seek answers and develop
solutions. Students become mathematically confident by communicating,
reasoning, and by applying mathematics in real world settings and by
solving problems through the integrated study of numbers. Students
understand and apply scientific concepts, principles and theories
pertaining to the physical setting and living environment. As a
foundation for our math program, we use the McGraw-Hill Math Series
supplemented with \"Soaring Scores,\" a problem-solving workbook. For
science, we call on the \"Windows on Science Laser Disc Series; \"Design
& Make" Folio Series by DJK Technology, Bank Street College; the Voyage
of the Mimi (for fifth grade oceanography); Exemplars TM (for MST K-5),
AIMS; GEMS (from the Lawrence Hall of Science), and from the New York
State Department of Conservation, Project WET and Project WILD.
Students actively engage in the process that constitutes creation and
performance in the arts (dance, music, visual arts), and take part in
individual and group productions, exhibitions and performances. Physical
and Health Education play an essential role, which heightens our
students' awareness of their own physical fitness and promotes a healthy
life style and informed decisions. Students at every grade level are
exposed to the study of world languages which includes Spanish, Italian,
Chinese, French and Latin. The program has a language and content-based
curriculum with a strong emphasis on cultures. Visual aids, songs, and
real-life situations provide the context for lessons with listening and
speaking skills stressed. Our school's annual literary magazine provides
every child with an opportunity to publish his/her own writing. Our
student newspaper, *The Seaman Scoop*, opens a window on the activities
in our school community through the eyes of student reporters. "Eye on
Seaman", a student videography project records the events throughout the
year with students acting as anchors, roving reporters and technicians.
The annual \"Parents As Reading Partners (PARP)\" program culminates a
week of reading activities with a Community Read-In. Judges, doctors,
farmers, chefs, authors, publishers, sports figures, and television
journalists read to our classes and discuss their fields of study. At
our Consumer Science Fair, classes design and perform experiments to
measure and compare the quality of similar household products. Graphing,
percentages, and data charts were well used as class decisions were
made. Fifth graders close out the school year in a week long training
camp with the National Circus Project to develop unique physical and
performing skills that are then presented to the entire school and
parent community.
*2. Describe in one-half page the school's reading curriculum, including
a description of why the school chose this particular approach to
reading.*
The Robert Seaman Elementary School is dedicated to helping all students
develop into confident, active, and successful readers, writers and
thinkers through its balanced literacy program using a Readers and
Writers Workshop approach. This approach was chosen by our teachers
after they examined approaches used in other schools and conducted trial
literacy lessons.
Based on data collected during through the individually administered
Early Literacy Profile, students are placed in a flexible guided reading
group. Students also participate in whole class shared reading
activities, independent reading activities and also listen to stories
read aloud. Reading activities include literature discussion groups,
author studies, reading buddies (e.g., fifth graders reading to first
graders), and note-taking research projects using reference materials,
documents, and other primary sources.
Classroom teachers have a rich collection of materials for reading
instruction including leveled literature anthologies, workbooks, trade
books, and books on tape or CD. Corresponding skills development guides
have been written by teachers through the district's Research and
Development program. The Seaman WEB Room (Wonderfully Exciting Books!)
offers an array of leveled literature including realistic fiction,
fantasy fiction, folk tales and fables, as well as nonfiction such as
biographies, poetry, and content-related literature. Classroom teachers
work in a co-teaching model with the reading specialist in order to
teach the three cueing systems. Students develop phonemic awareness,
begin to self-monitor and self-correct for fluency, and learn to use the
context for understanding meanings of new words. Students are also
learning comprehension skills and strategies such as visualizing, "think
aloud," critical analysis and synthesis, and inferential thinking.
Students who require academic intervention are often seen in small
groups in the Reading Room, where skills and strategies such as
pre-teaching, repetition, and review are used, supported by Wilson
Reading, Glass Analysis, Orton-Gillingham strategies, and \"Explode the
Code.\"
*3. Describe in one-half page one other curriculum area of the school's
choice and show how it relates to essential skills and knowledge based
on the school's mission.*
At Robert Seaman Elementary School, we build connections between Math,
Science and Technology. A visit to the science lab will reveal a glimpse
into Harry Potter's world, as the fourth grade students measure and
observe different chemicals while investigating the chemistry of potion
making. First graders play marble games, make data tables to find
patterns as they explore Newton's laws of motion, and then design and
construct marble roller coasters. Another visit will reveal third
graders investigating electrical circuits as they construct lighthouses.
Our young scientists are actively engaged in inquiry as they discover
important concepts and skills described in the New York State Learning
Standards for Mathematics, Science and Technology. Their science
journals reflect this hands-on investigative process as well as the
integration of math, science, writing and critical thinking. Their New
York State Science Assessment scores reflect the success of a motivating
program that is enhanced by a variety of resources, methodologies and
field trips. The MST program is a very exciting endeavor, which is
especially significant to the school's mission because it revolves
around the basic nature of the child's curiosity and appreciation of the
natural world, while fostering critical thinking and problem solving. In
a unique partnership with the DNA Learning Center located in Cold Spring
Harbor, New York, fifth graders are immersed in genetics, a key element
of the Standards. The students construct models of the DNA to understand
its chemical composition and use jellybean "genes" to simulate the
transfer of genetic information. They share ideas based on current
events in the field of genetics and apply mathematics in real world
settings as they determine offspring probability by analyzing Punnett
squares. During a field trip to the DNA Learning Center, the students
actually extract DNA from onion cells and during the in-school
visitations, they used stereomicroscopes to observe fruit fly mutations.
As a culminating project, the students are encouraged apply their
knowledge of how species change over time and invent mutant organisms,
which are adapted to a specific environment. Our MST program is dynamic
and constantly evolving.
4. *Describe in one-half page the different instructional methods the
school uses to improve student learning.*
To improve student learning through different instructional methods, we
start with individual assessment, which forms the basis for enrichment
and reinforcement activities. Cooperative learning strategies are
employed across all grades in all content areas, enabling students to
learn from peers as well as teachers.
Flexible grouping is evident in each classroom. Teachers use a variety
of instructional strategies to target instruction and compact or
re-teach as needed. Assessment techniques can include portfolios,
rubrics, performance- based assessment, and graphic organizers. Learning
activities and materials may be varied by difficulty to challenge
students at different levels, and by student's preferred way of learning
and expressing themselves.
Examples of differentiating content include using materials at varying
readability levels; putting text materials on tape; using spelling or
vocabulary lists at individual student levels; presenting ideas through
auditory, visual or tactile means, and meeting with small groups or one
to one to re-teach a concept or skill. Differentiated instructional
activities include using scaffolded activities through which all
learners work, and providing support where necessary. It also includes
interest centers which encourage subject exploration and higher order
thinking skills for students; developing personal student work agendas;
technology integration; offering manipulatives or other hands-on
supports for students who need them; varying the length of time a
student may take to complete a task, and allowing students to work alone
or in small groups.
*5. Describe in one-half page the school's professional development
program and its impact on improving student achievement.*
The professional development program is multi-faceted. District
curriculum specialists (called \"curriculum associates\") support
professional development through observation, workshops, curriculum
writing, and demonstration lessons. New teachers attend orientation
programs, are assigned mentor teachers, and attend ongoing workshops.
The Jericho School District offers a variety of workshops, courses and
conferences onsite, in which Seaman teachers readily participate.
Teachers are surveyed regarding course offerings. Teachers have the
flexibility to choose courses which will best benefit themselves and
their students. For example, the completion of an in-service course on
the Early Literacy Profile enabled twelve K-3 teachers to successfully
administer and interpret student data obtained from this individual
reading assessment. Recent \"best practices\" workshops offered include
\"The Michigan Model Health Program,\" and \"Inclusion Strategies for
Children with Autism.\"
The district also partners with Brooklyn College of the City University
of New York to offer graduate level courses onsite. These include
courses in technology, social/emotional development, new trends in
curriculum and instructional, special education, and State Standards and
Assessments. In addition, staff is encouraged to attend professional
conferences on relevant topics. They bring back ideas and strategies
that have significant impact on school programs. For example, computer
teachers returning from a technology conference one year provided the
impetus for the school to replace its Macintosh computers with PCs.
**[NEW YORK STATE ENGLISH LANGUAGE ARTS GRADE FOUR]{.underline}**
CRITERION-REFERENCED TESTS
The Data Display Table is illustrated on the following page.
Grade[\_\_\_4\_\_\_\_\_]{.underline} Test [New York State English
Language Arts (Grade Four)]{.underline}
Edition/publication year [1998-2002]{.underline} Publisher
[CTB/McGraw-Hill]{.underline}
What groups were excluded from testing? Why, and how were they assessed?
[None]{.underline} \_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Number excluded [0\_\_\_\_]{.underline} Percent
excluded[\_\_0%\_\_\_\_]{.underline}
Explain the standards for basic, proficient, and advanced, and make
clear what the test results mean in a way that someone unfamiliar with
the test can interpret the results.
The English Language Arts Assessment given by the New York State Testing
Program groups students into four performance levels. Students in a
given performance level can perform the majority of what is described
for that level, as well as what is described for the levels below.
Students who attain a Level 1 (*Below Basic*) performance level on the
New York State English Language Arts Fourth Grade assessment demonstrate
a minimal understanding of written text. They can locate and recall some
stated information and attempt to construct short and extended
responses. Their writing consists of brief, general, or repetitive
statements, and reveals difficulty in organizing thoughts.
Students who attain a Level 2 (*Basic*) performance level on the New
York State English Language Arts Fourth Grade assessment demonstrate
partial understanding of written and oral text at a literal level. They
can recognize basic story elements, make some inferences, and identify
some similarities and differences in two related texts, providing
limited supporting information. Their writing shows some focus and basic
organization and uses simple sentence structure and vocabulary.
Students who attain a Level 3 (*Proficient*) performance level on the
New York State English Language Arts Fourth Grade assessment demonstrate
understanding of written and oral text with some attention to meaning
beyond the literal level. They can gather information, make inferences,
identify theme or main idea, understand character actions and make
connections between two related texts, providing some supporting
information. Their writing is generally focused and organized.
Students who attain a Level 4 (*Advanced*) performance level on the New
York State English Language Arts Fourth Grade assessment consistently
demonstrate understanding of written and oral text beyond the literal
level. They can analyze and interpret a variety of texts, identify
significant story elements, compare and synthesize information from
related text, and form insightful opinions, using extensive supporting
details. Their writing is well organized, thoroughly developed, and uses
sophisticated and effective language.
DATA DISPLAY TABLE FOR NEW YORK STATE ENGLISH LANGUAGE ARTS
GRADE FOUR
(Criterion-Referenced Tests)
> 
NEW YORK STATE MATHEMATICS GRADE FOUR
CRITERION-REFERENCED TESTS
The Data Display Table is illustrated on the following page.
Grade[\_\_\_4\_\_\_\_\_]{.underline} Test [New York State Mathematics
(Grade Four)]{.underline}
Edition/publication year [1998-2002]{.underline} Publisher
[CTB/McGraw-Hill]{.underline}
What groups were excluded from testing? Why, and how were they assessed?
[None]{.underline} \_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Number excluded [0\_\_\_\_]{.underline} Percent
excluded[\_\_0%\_\_\_\_]{.underline}
Explain the standards for basic, proficient, and advanced, and make
clear what the test results mean in a way that someone unfamiliar with
the test can interpret the results.
The Mathematics Assessment given by the New York State Testing Program
groups students into four performance levels. Students in a given
performance level can perform the majority of what is described for that
level, as well as what is described for the levels below.
Students who attain a Level 1 (*Below Basic*) performance level on the
New York State Fourth Grade Mathematics assessment may use basic
addition and subtraction; identify first and last numbers; count groups
of objects; use manipulatives to model whole-number relationships;
recognize simple data; use counting to determine perimeter and area of
simple figures; understand that some events are more likely than others;
and use manipulatives to explore patterns.
Students who attain a Level 2 (*Basic*) performance level on the New
York State Fourth Grade Mathematics assessment for the most part use
basic facts for all operations; add/subtract with regrouping; use
ordinals; order whole numbers; use whole-number place value; model
operations and simple fractional relationships with manipulatives;
read/interpret data; identify appropriate units of measure; identify
polygons; identify lines of symmetry; extend and describe simple
patterns; solve for an unknown with manipulatives.
Students who attain a Level 3 (*Proficient*) performance level on the
New York State Fourth Grade Mathematics assessment consistently solve
multi-step problems; identify odds/evens; order fractions; use
manipulatives to model decimal relationships; identify percent; collect,
organize, display and interpret real-world data; use appropriate units
of measure; identify points, lines, rays, planes, polygons; identify
faces of solid figures; express probability; extend a numerical pattern,
and justify a reasonable solution.
Students who attain a Level 4 (*Advanced*) performance level on the New
York State Fourth Grade Mathematics assessment order decimals; identify
decimal values; use percent; use estimation; apply graphical data;
predict effect of a biased sample; identify equivalents within a
measuring system; fine linear, square, and cubic measure; model solid
figures; predict probability; identify arrangements and combinations;
create and describe patterns; explain reasoning; draw conclusions, and
analyze situations.
DATA DISPLAY TABLE FOR NEW YORK STATE MATHEMATICS GRADE FOUR
(CRITERION-REFERNECED TESTS)
> 
| en |
markdown | 212371 | # Presentation: 212371
## Liability: The Oklahoma Experience
- Before Legislation =Patchwork coverage
- Partner agencies
- Volunteers are covered when working for specific agencies: Public Health Department, American Red Cross volunteers
- National coverage
- United States Code
- Title 42, Chapter 139
- Section 14503.- Limitation on liability for volunteers
- Individual Malpractice Insurance
## May, 2004
- House Bill 2661 is introduced which primarily addresses tort reform and involves lengthy negotiations and active lobbying from the medical community
- Dr. John Sacra, the Medical Director of EMSA is instrumental in including language providing liability immunity for Medical Reserve Corps Volunteers
## May 28th, 2004
- State legislature passes and the Governor signs the “Volunteer Medical Professional Services Immunity Act”
## Section 34 G. “Any person participating in a Medical Reserve Corps and assisting with emergency management, emergency operations, or hazard mitigation in response to any emergency, man-made disaster, or natural disaster, or participating in public health initiatives endorsed by a city, county, or state health department in the State of Oklahoma, shall not be liable for civil damages on the basis of any act or omission, if:
1. The person was acting in good faith and within the scope of the official duties and functions of the Medical Reserve Corps; and
2. The acts or omissions were not caused from gross, willful, or wanton acts of negligence.”
This section shall apply to all civil actions filed on or after November 1, 2004.
- 1. The person was acting in good faith and within the scope of the official duties and functions of the Medical Reserve Corps; and
- 2. The acts or omissions were not caused from gross, willful, or wanton acts of negligence.”
- This section shall apply to all civil actions filed on or after November 1, 2004.
## Advantages
- The Medical Reserve Corps is now the identified entity for medical volunteers with protection from civil liability damages.
- We anticipate this will help our recruiting efforts.
## Disadvantage
- Does not provide the full coverage that a state employee would have, such as Workers Compensation
- This protection has not been tested in the courts. | en |
converted_docs | 267405 | +-------------------------+--------------+----+-------+-------------+
| Employee's Name (Last, | Soc. Sec. | Ra | | To: |
| First, MI) | No. | ti | | |
| | | ng | | |
| | | Pe | | |
| | | ri | | |
| | | od | | |
| | | F | | |
| | | ro | | |
| | | m: | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| ## FOREIGN SERVICE SK | | | | |
| ILLS FEEDBACK WORKSHEET | | | | |
+-------------------------+--------------+----+-------+-------------+
| **QUALITY OF WORK** - | | | | |
| *Effectively | | | | |
| interprets, applies, | | | | |
| implements, and | | | | |
| communicates USAID's | | | | |
| strategies, goals, | | | | |
| objectives, policies | | | | |
| and procedures. Adapts | | | | |
| the knowledge of | | | | |
| respective discipline | | | | |
| to the particular | | | | |
| setting and translates | | | | |
| this knowledge, using | | | | |
| his/her technical, | | | | |
| program and/or | | | | |
| administrative skills | | | | |
| into results that | | | | |
| support program and | | | | |
| organizational | | | | |
| objectives. Remains | | | | |
| abreast of developments | | | | |
| in the discipline. | | | | |
| Utilizes understanding | | | | |
| of U.S. foreign policy | | | | |
| and major global issues | | | | |
| to promote sustainable | | | | |
| development.* | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| DEVELOPMENT ASSISTANCE | | | | |
| KNOWLEDGE | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - understands USAID's | | | | |
| objectives and | | | C | |
| approach to | | | ommen | |
| development | | | dable | |
| assistance | | | | |
+-------------------------+--------------+----+-------+-------------+
| - understands | | | | |
| theories and | | | Profi | |
| strategies of | | | cient | |
| sustainable | | | | |
| development | | | | |
+-------------------------+--------------+----+-------+-------------+
| - understands major | | | Area | |
| global development | | | for | |
| issues | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| KNOWLEDGE OF USAID | | | | |
| VALUES AND SYSTEMS | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - demonstrates | | | | |
| understanding of | | | C | |
| USAID values | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
| | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| DATA GATHERING, | | | | |
| ANALYSIS AND EVALUATION | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - problem solving | | | | |
| skills developed | | | C | |
| | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - gathers and uses | | | | |
| data effectively | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| WRITTEN COMMUNICATION | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - expresses facts and | | | | |
| ideas | | | C | |
| clearly/succinctly | | | ommen | |
| and in an organized | | | dable | |
| manner | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
| | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| TECHNICAL SKILLS | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - uses tools of | | | | |
| professional | | | C | |
| discipline to | | | ommen | |
| achieve objectives | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
| | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| # Comments | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| **LEADERSHIP** - | | | | |
| *Inspires, motivates, | | | | |
| and guides others | | | | |
| toward the achievement | | | | |
| of USAID goals. | | | | |
| Demonstrates ability to | | | | |
| objectively evaluate | | | | |
| and analyze new | | | | |
| concepts; to understand | | | | |
| the complexities and | | | | |
| intricacies of the | | | | |
| political, economic and | | | | |
| cultural setting; and | | | | |
| to develop effective | | | | |
| and innovative | | | | |
| operational and/or | | | | |
| program strategies | | | | |
| appropriate to the | | | | |
| setting. Makes sound | | | | |
| and well-informed | | | | |
| decisions, with | | | | |
| knowledge of impact and | | | | |
| implications. Leads by | | | | |
| example. Acknowledges | | | | |
| and rewards superior | | | | |
| performance.* | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| DIRECTION AND VISION | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - defines and/or | | | | |
| assists with | | | C | |
| implementation of | | | ommen | |
| USAID or sub-unit's | | | dable | |
| vision and | | | | |
| strategic goals | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
| | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| INITIATIVE, CREATIVITY | | | | |
| AND RISKTAKING | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - pursues goals | | | | |
| actively | | | C | |
| | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - takes calculated | | | | |
| risks | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| MOTIVATING | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - directs/energizes | | | | |
| others to | | | C | |
| accomplish goals | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - serves as mentor | | | | |
| | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| - delegates | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| PROBLEM SOLVING AND | | | | |
| DECISION -- MAKING | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - problem solving | | | | |
| skills includes | | | C | |
| consideration of | | | ommen | |
| relevant factors | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - decisions are | | | | |
| reasoned, effective | | | Profi | |
| and timely | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| # Comments | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
AID 400-3 (2/2000) Page 1 of 3
+-------------------------+--------------+----+-------+-------------+
| Employee's Name (Last, | Soc. Sec. | Ra | | To: |
| First, MI) | No. | ti | | |
| | | ng | | |
| | | Pe | | |
| | | ri | | |
| | | od | | |
| | | F | | |
| | | ro | | |
| | | m: | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| **RESOURCE MANAGEMENT | | | | |
| -** *Understands and | | | | |
| effectively implements | | | | |
| USAID business | | | | |
| processes. Exercises | | | | |
| good judgment while | | | | |
| insuring that resources | | | | |
| are used effectively to | | | | |
| produce results. | | | | |
| Allocates and monitors | | | | |
| usage of financial and | | | | |
| physical resources | | | | |
| within actual span of | | | | |
| control. Anticipates | | | | |
| future requirements, | | | | |
| develops plans and | | | | |
| establishes priorities. | | | | |
| Manages resources | | | | |
| within a well-planned | | | | |
| approach and considers | | | | |
| immediate and long term | | | | |
| needs to make good use | | | | |
| of resource allocation. | | | | |
| Uses resources within | | | | |
| framework that includes | | | | |
| clear goals and | | | | |
| objectives to assure | | | | |
| that available | | | | |
| resources are | | | | |
| efficiently devoted to | | | | |
| priority and critical | | | | |
| issues. Develops sound | | | | |
| management controls and | | | | |
| takes personal | | | | |
| responsibility for | | | | |
| reducing agency | | | | |
| vulnerability.* | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| STRATEGY DEVELOPMENT | | | | |
| AND IMPLEMENTATION | | | O | |
| | | | utsta | |
| | | | nding | |
| | | | N/A | |
+-------------------------+--------------+----+-------+-------------+
| - reviews and | | | | |
| assisses | | | C | |
| prog | | | ommen | |
| ram/project/operational | | | dable | |
| goals | | | | |
+-------------------------+--------------+----+-------+-------------+
| - develops strategies | | | | |
| and priorities | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| RESULTS ACHIEVEMENT, | | | | |
| PROGRAM MONITORING AND | | | O | |
| EVALUATION | | | utsta | |
| | | | nding | |
| | | | N/A | |
+-------------------------+--------------+----+-------+-------------+
| - defines measurable | | | | |
| results | | | C | |
| | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - focuses on results | | | | |
| | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| - assesses | | | Area | |
| prog | | | for | |
| ram/project/operational | | | I | |
| effectiveness | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| BUDGET AND FINANCIAL | | | | |
| MANAGEMENT | | | O | |
| | | | utsta | |
| | | | nding | |
| | | | N/A | |
+-------------------------+--------------+----+-------+-------------+
| - develops, justifies | | | | |
| and/or administers | | | C | |
| budget | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
| | | | Profi | |
| | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| # Comments | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| **STAFF DEVELOPMENT -** | | | | |
| *Takes action to | | | | |
| develop and strengthen | | | | |
| employee skills, | | | | |
| abilities, and | | | | |
| professional knowledge. | | | | |
| Utilizes formal and | | | | |
| informal techniques of | | | | |
| staff development, | | | | |
| making good use of | | | | |
| special assignments, | | | | |
| team participation, | | | | |
| formal short and | | | | |
| long-term training, | | | | |
| personal-career | | | | |
| counseling through | | | | |
| mentoring, and | | | | |
| on-the-job training to | | | | |
| develop staff. | | | | |
| Establishes and | | | | |
| communicates work | | | | |
| objectives. Provides | | | | |
| and receives effective, | | | | |
| constructive, and | | | | |
| ongoing performance | | | | |
| feedback. Prepares | | | | |
| accurate and timely | | | | |
| performance | | | | |
| evaluations.* | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| ENHANCEMENT OF | | | | |
| SUBORDINATE GROWTH | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - supports employees' | | | | |
| professional | | | C | |
| development | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - provides | | | | |
| development | | | Profi | |
| opportunities to | | | cient | |
| subordinates | | | | |
+-------------------------+--------------+----+-------+-------------+
| - mentors | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| DIVERSITY, EQUAL | | | | |
| EMPLOYMENT OPPORTUNITY | | | O | |
| KNOWLEDGE AND | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| IMPLEMENTATION | | | | |
| | | | C | |
| | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - | | | | |
| understands/implements | | | Profi | |
| USAID's EEO and | | | cient | |
| diversity programs | | | | |
+-------------------------+--------------+----+-------+-------------+
| - identifies and | | | Area | |
| removes barriers to | | | for | |
| equal employment | | | I | |
| opportunity | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| PERFORMANCE MANAGEMENT | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - provides | | | | |
| t | | | C | |
| horough/accurate/timely | | | ommen | |
| feedback on | | | dable | |
| performance of | | | | |
| subordinates | | | | |
+-------------------------+--------------+----+-------+-------------+
| - conducts progress | | | | |
| reviews for all | | | Profi | |
| subordinates | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| - provides ongoing | | | Area | |
| feedback about | | | for | |
| performance to | | | I | |
| employees | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| # Comments | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| **PROFESSIONALISM -** | | | | |
| *Exhibits | | | | |
| responsibility for | | | | |
| achieving results, not | | | | |
| just performing tasks. | | | | |
| Demonstrates knowledge | | | | |
| of USAID vision and | | | | |
| core values in | | | | |
| representing the U.S. | | | | |
| Government, Operating | | | | |
| Unit, and/or team. | | | | |
| Demonstrates | | | | |
| reliability, accepts | | | | |
| responsibility and acts | | | | |
| ethically. Anticipates, | | | | |
| appreciates, and | | | | |
| responds to the | | | | |
| challenges of serving | | | | |
| internal and external | | | | |
| customers, clients and | | | | |
| stakeholders. Is | | | | |
| responsive to pressing | | | | |
| and changing customer | | | | |
| needs. Is committed to | | | | |
| improving customer | | | | |
| service.* | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| CUSTOMER SERVICE | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - identifies customer | | | | |
| needs | | | C | |
| | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - meets customers' | | | | |
| expectations in a | | | Profi | |
| satisfactory manner | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| PROFESSIONAL CONDUCT | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
+-------------------------+--------------+----+-------+-------------+
| - represents US | | | | |
| government | | | C | |
| appropriately and | | | ommen | |
| responsibly | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - maintains poise in | | | | |
| stressful | | | Profi | |
| situations | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| - upholds Agency | | | Area | |
| ethical standards | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| # Comments | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
AID 400-3 (2/2000) Page 2 of 3
+-------------------------+--------------+----+-------+-------------+
| Employee's Name (Last, | Soc. Sec. | Ra | | To: |
| First, MI) | No. | ti | | |
| | | ng | | |
| | | Pe | | |
| | | ri | | |
| | | od | | |
| | | F | | |
| | | ro | | |
| | | m: | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| * | | | | |
| *TEAMWORK/INTERPERSONAL | | | | |
| SKILLS** - *Works in a | | | | |
| collaborative, | | | | |
| inclusive, | | | | |
| team-oriented manner, | | | | |
| valuing diversity and | | | | |
| equal opportunity. | | | | |
| Fosters a climate of | | | | |
| trust and respect. | | | | |
| Demonstrates | | | | |
| sensitivity to | | | | |
| individual and cultural | | | | |
| differences and ensures | | | | |
| that all views are | | | | |
| taken into | | | | |
| consideration. Is open | | | | |
| to change and new | | | | |
| information, adapting | | | | |
| work behavior and | | | | |
| methods accordingly. | | | | |
| Demonstrates capacity | | | | |
| to effectively interact | | | | |
| with other people. | | | | |
| Creates and maintains | | | | |
| effective working | | | | |
| relations with team | | | | |
| members, other USAID | | | | |
| staff, host country | | | | |
| citizens, other U.S. | | | | |
| and foreign government | | | | |
| organizations, and | | | | |
| representatives of | | | | |
| donor institutions and | | | | |
| non-governmental | | | | |
| organizations. | | | | |
| Communicates | | | | |
| effectively utilizing | | | | |
| foreign language | | | | |
| ability as | | | | |
| appropriate.* | | | | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| SENSITIVITY AND RESPECT | | | | |
| FOR DIVERSITY | | | O | |
| | | | utsta | |
| | | | nding | |
| | | | N/A | |
+-------------------------+--------------+----+-------+-------------+
| - shows sensitivity | | | | |
| to individual | | | C | |
| customs, mores and | | | ommen | |
| beliefs | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - demonstrates | | | | |
| ability to work in | | | Profi | |
| new cultural | | | cient | |
| contexts as | | | | |
| required | | | | |
+-------------------------+--------------+----+-------+-------------+
| - promotes diversity | | | Area | |
| in the workplace | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| CONSENSUS BUILDING | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
| | | | N/A | |
+-------------------------+--------------+----+-------+-------------+
| - consensus built | | | | |
| through discussion | | | C | |
| of divergent views | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - resolves connflicts | | | | |
| sensibly and | | | Profi | |
| persuasively | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| ADAPTABILITY AND | | | | |
| FLEXIBILITY | | | O | |
| | | | utsta | |
| | | | nding | |
| | | | N/A | |
+-------------------------+--------------+----+-------+-------------+
| - adjusts | | | | |
| appropriately to | | | C | |
| meet changing | | | ommen | |
| conditions | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - allocates time and | | | | |
| effort as needed to | | | Profi | |
| multiple teams | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| COLLABORATION AND | | | | |
| EMPOWERMENT | | | O | |
| | | | utsta | |
| | | | nding | |
| | | | N/A | |
+-------------------------+--------------+----+-------+-------------+
| - adjusts | | | | |
| appropriately to | | | C | |
| meet changing | | | ommen | |
| conditions | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - realizes impact | | | | |
| that behavior has | | | Profi | |
| on others | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| | | | Area | |
| | | | for | |
| | | | I | |
| | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| ORAL COMMUNICATION | | | | |
| | | | O | |
| | | | utsta | |
| | | | nding | |
| | | | N/A | |
+-------------------------+--------------+----+-------+-------------+
| - relay information | | | | |
| clearly and | | | C | |
| concisely | | | ommen | |
| | | | dable | |
+-------------------------+--------------+----+-------+-------------+
| - demonstrates | | | | |
| effective listening | | | Profi | |
| skills | | | cient | |
+-------------------------+--------------+----+-------+-------------+
| - communications | | | Area | |
| effectively in host | | | for | |
| country language, | | | I | |
| if appropriate | | | mprov | |
| | | | ement | |
+-------------------------+--------------+----+-------+-------------+
| | | | | |
+-------------------------+--------------+----+-------+-------------+
| # Comments | | | | |
| | | | | |
| | | | | |
+-------------------------+--------------+----+-------+-------------+
AID 400-3 (2/2000) Page 3 of 3
| en |
converted_docs | 167333 | National PBM Drug Monograph
Ibandronate Sodium Tablets and Injection (Boniva®)
January 2008
VHA Pharmacy Benefits Management Services and the Medical Advisory Panel
*The purpose of VACO PBM Services drug monographs is to provide a
comprehensive drug review for making formulary decisions. These
documents will be updated when new clinical data warrant additional
formulary discussion. Documents will be placed in the Archive section
when the information is deemed to be no longer current.*
# Executive Summary:
- Ibandronate is a nitrogen-containing bisphosphonate agent that
inhibits bone resorption and turnover.
- Oral daily (2.5 mg) and monthly (150 mg) and intravenous (IV)
quarterly (3 mg) formulations of ibandronate are available and FDA
approved in the prevention (oral) and treatment (IV and oral) of
osteoporosis in postmenopausal women.
- In the pivotal BONE trial, ibandronate 2.5 mg oral daily was shown
to be more effective than placebo in decreasing morphometric
vertebral fractures and increasing lumbar spine and hip bone mineral
density (BMD) in a total of 2929 postmenopausal women with
osteoporosis and baseline vertebral fractures. No significant
reduction in nonvertebral fractures was observed.
- Ibandronate 150 mg oral monthly was shown to be noninferior to the
established 2.5 mg daily regimen in increasing lumbar spine and hip
BMD in women with osteoporosis in the MOBILE trial. In addition, the
150 mg monthly regimen was associated with statistically superior
increases in lumbar spine and hip BMD. No significant differences in
adverse events between groups were observed.
- The ibandronate 3 mg quarterly IV formulation was shown to be
noninferior to the oral daily 2.5 mg dose in increasing lumbar spine
and hip BMD in the DIVA trial in postmenopausal women with
osteoporosis. A similar incidence of side effects between groups was
noted in the 1-year interim results.
- In the Prevention study, 2.5 mg oral ibandronate daily was shown to
be effective in improving and normalizing BMD in postmenopausal
osteopenic women.
- Ibandronate is not approved for the treatment of osteoporosis in
men, and evidence in this patient population is very limited.
- Ibandronate appears well tolerated and similar to other
bisphosphonates in its side effect profile. Common side effects
include upper gastrointestinal (GI) upset and musculoskeletal
symptoms.
# Introduction {#introduction .Style-Heading-1-+-Black}
The purposes of this monograph are to (1) evaluate the available
evidence of safety, tolerability, efficacy, cost, and other
pharmaceutical issues that would be relevant to evaluating ibandronate
for possible addition to the VA National Formulary; (2) define its role
in therapy; and (3) identify parameters for its rational use in the VA.
# Pharmacology/Pharmacokinetics^1-3^ {#pharmacologypharmacokinetics1-3 .Style-Heading-1-+-Black}
Ibandronate sodium is a nitrogen-containing bisphosphonate agent that
decreases bone resorption and turnover through the inhibition of
osteoclast activity.
Bioavailability and pharmacokinetics of ibandronate sodium are
comparable in men and women. Similar to other bisphosphonates (i.e.,
alendronate and risedronate), oral absorption of ibandronate sodium is
low and is further reduced by ingestion of food and beverages (other
than plain water).
Table 1. Pharmacokinetic Parameters of Ibandronate^2^\*
----------------------------------- -----------------------------------
**Parameter** **Ibandronate**
Bioavailability (Fasting) 0.6%
Protein Binding 85.7 -- 99.5%
Metabolism Not Metabolized
Elimination Renal
Terminal Half-life 37-157 hrs\*
----------------------------------- -----------------------------------
\*Observed apparent half-life based on 150 mg oral dose. The true
terminal elimination half-life is dependent on dose and sensitivity of
assay used and is likely to be longer and similar to other
bisphosphonates.
# FDA Approved Indication(s) and Off-label Uses ^1-3^
Ibandronate sodium tablets are indicated for the prevention and
treatment of osteoporosis in postmenopausal women; ibandronate sodium
injection is indicated for the treatment of osteoporosis in
postmenopausal women.
Off-label uses of ibandronate include the treatment of osteoporosis in
men, corticosteroid-induced osteoporosis, and Paget's disease.
# Current VA National Formulary Alternatives
The bisphosphonates alendronate and risedronate are therapeutic
alternatives currently listed on the VA National Formulary.
# Dosage and Administration ^1-3^
**Oral**
Ibandronate is available in 2.5 mg and 150 mg tablets. The recommended
dose of ibandronate for the treatment of postmenopausal osteoporosis
(PMO) is 2.5 mg once daily or 150 mg once monthly, given on the same
date each month. For prevention of PMO, the recommended dose of
ibandronate is 2.5 mg daily; 150 mg monthly may be considered as an
alternative.
For maximal drug absorption, ibandronate should be taken with plain
water at least 60 minutes prior to the first food or drink of the day
and prior to taking any oral medications (including supplements). To
minimize the risk for esophageal irritation, ibandronate tablets should
be swallowed whole with 6-8 oz of water, and patients should remain in
an upright position (either standing or sitting) for 60 minutes
following administration.
**Injection**
Ibandronate is available in a 3 mg/3ml solution for injection in a
prefilled syringe. The recommended dose of ibandronate injection is 3 mg
given every 3 months, administered by a healthcare professional as an
intravenous bolus over 15-30 seconds.
All patients should have adequate intake of calcium (at least 1200
mg/day) and vitamin D (400-800 IU/day).
**Special Populations**
*Elderly*
No dosage adjustments are recommended in the elderly. Patients \>65
years of age comprised greater than 50% of the population in the major
clinical trials with ibandronate tablets and injection. No overall
difference in safety and effectiveness was noted between patients \>65
years old and younger patients, although the manufacturer states that
greater sensitivity in certain elderly individuals cannot be ruled out.
Age-related decline in renal function may alter the elimination of
ibandronate in this population (see Renal Impairment below).
*Hepatic Impairment*
No dosage adjustments are recommended in patients with hepatic
impairment, as the drug is not metabolized by the liver.
*Renal Impairment*
No dosage adjustments are recommended in patients with mild to moderate
renal impairment (creatinine clearance ≥30 ml/min). Ibandronate is not
recommended for use in patients with severe renal impairment (i.e.,
creatinine clearance \<30 ml/min or serum creatinine \>2.3 mg/dL).
Compared to those with normal renal function, exposure was 55% higher in
patients with a creatinine clearance between 40 and 70 ml/min and
greater than 2-fold higher in patients with a creatinine clearance \<30
ml/min following a single IV dose of ibandronate.
# Storage
The tablets and prefilled syringe should be stored at room temperature
(25°C) with excursions between 15-30°C (59-86°F) permitted.
# Efficacy
## Efficacy Measures^4,5^
Although fracture reduction is the preferred outcome measure in
osteoporosis investigation, the surrogate marker of change in bone
mineral density (BMD) is often used in clinical trials. Studies that
evaluate fracture reduction require a large patient population and long
duration of study to detect significant differences between treatments.
Although measuring BMD is the gold standard in diagnosing osteoporosis,
the ability to predict fracture risk using BMD is imperfect. BMD is
accurately and commonly measured at the lumbar spine and hip by dual
energy x-ray absorptiometry (DXA).
Primary Efficacy Endpoints
- Morphometric vertebral fracture
- Changes in BMD at lumbar spine and hip
Secondary and Other Efficacy Endpoints
- Clinical vertebral and non-vertebral fractures (often reported as
adverse events)
- Biochemical markers of bone turnover
- Height loss
- Safety and tolerability
## Summary of efficacy findings (See Appendix for additional information on clinical trials)
*Treatment of Osteoporosis in Postmenopausal Women*
The efficacy of ibandronate in the treatment of women with PMO has been
demonstrated in four pivotal clinical trials; two evaluating oral
regimens and two evaluating the injectable formulation. The BONE and
fracture prevention trials were superiority studies that measured
fracture incidence as the primary endpoint. The MOBILE and DIVA studies
were comparative noninferiority trials that investigated changes in BMD
as the primary outcome measure.
BONE was a randomized, double-blind, placebo-controlled study that
compared oral ibandronate given in a daily regimen (2.5 mg/day), an
intermittent regimen (20 mg every other day x12 doses every 3 months),
and placebo in a total of 2946 women with osteoporosis and baseline
vertebral fracture.^6^ Following 3 years of treatment, both ibandronate
regimens were associated with a significantly lower incidence of new
morphometric vertebral fractures compared to placebo: 4.7% (95% CI
3.2-6.2) with the daily regimen; 4.9% (95% CI 3.4-6.4) with the
intermittent regimen; 9.6% (95% CI 7.5-11.7) with placebo. Similar and
significant improvements in spine and hip BMD were observed with both
ibandronate regimens vs. placebo as shown below (see Table 2). Although
lower rates of clinical vertebral fractures occurred in the ibandronate
groups, no difference in the incidence of non-vertebral fractures vs.
placebo was shown. Ibandronate treatment was associated with sustained
and significant improvements in markers of bone turnover (in a
predefined subpopulation of 20%) and decreased loss of height.
MOBILE was a randomized, double-blind, noninferiority trial of two years
duration that compared three monthly oral ibandronate regimens (50 mg
daily x2 days once monthly; 100 mg once monthly; and 150 mg once
monthly) to the established daily regimen (2.5 mg daily) in a total of
1609 women with PMO.^7,8^ Efficacy measures were analyzed based on the
per-protocol population (n=1277) due to the noninferiority design. For
the primary endpoint of change in lumbar spine BMD, all monthly regimens
were found to be at least as effective as the daily regimen (see Table 2
below). Additionally, in a prospectively defined analysis, the 150 mg
monthly regimen was statistically superior to the daily regimen in the
primary measure. All regimens were associated with significant
improvements in hip BMD (total hip, femoral neck, and trochanter), and
the 100 mg and 150 mg dose statistically superior to the daily dose.
Significant decreases in the bone resorption marker C-telopeptide of the
alpha-chain of type I collagen (sCTX) were also observed with all
regimens. Analysis performed on the ITT population produced consistent
results regarding BMD outcomes.
Based on results from previous IV dose ranging studies, the IV fracture
prevention study, a phase III randomized, placebo-controlled trial of 3
years duration was conducted in 2862 postmenopausal women with
osteoporosis and baseline fracture.^1,10^ This study failed to reach its
primary endpoint, and the cumulative incidence of new morphometric
vertebral fractures was not significantly different between ibandronate
treatment groups (ibandronate 0.5 mg or 1 mg IV given every 3 months)
and placebo. Dose dependent increases in lumbar spine and hip BMD were
reported in both ibandronate groups, but the statistical significance
was not stated. Recker et al. concluded that larger doses may be needed
to produce more substantial increases in BMD and potentially reducing
fracture risk.
DIVA was a two year, randomized, double-blind, double-dummy
noninferiority trial that compared two higher dose regimens of
ibandronate injection (2 mg IV every 2 months and 3 mg IV every 3
months) to the established daily regimen (2.5 mg/day). One year results
are published at this time.^9^ In the per-protocol population of 1104
women with PMO, the primary efficacy endpoint of mean change in lumbar
spine BMD was shown to be noninferior in both ibandronate injection
groups compared to oral treatment at one year (see Table 2 below).
Further, both injection groups were found to be statistically superior
to the oral ibandronate group with respect to lumbar spine BMD
improvements in a prospectively defined analysis. Both ibandronate
injection regimens were at least as effective as oral treatment in
increasing hip BMD. In a similar preplanned analysis, injectable
ibandronate was shown to be more effective than oral treatment.
Significant and sustained decreases of sCTX were observed in all
treatment arms. Analysis of the ITT population produced consistent
results.
In a recent meta-analysis of pooled individual patient data from a total
of 8710 patients from BONE, MOBILE, DIVA, and the IV fracture prevention
study, Harris et al. evaluated comparisons of annual cumulative exposure
(ACE) of ibandronate on non-vertebral fracture risk.^11^ The high dose
group (ACE of ≥10.8 mg) included 150 mg oral monthly, 2 mg IV every 2
months, and 3 mg IV quarterly dosing regimens. A significant reduction
in non-vertebral fracture risk was noted in the high dose group compared
to placebo (35% relative risk reduction). Individual clinical trials
were not powered to detect significant differences in non-vertebral
fractures. Limitations of this meta-analysis include that fracture rates
were determined from the two placebo-controlled studies; different
dosing regimens were pooled together; and potential differences in study
populations may exist.
*Prevention of Osteoporosis in Postmenopausal Women*
In a randomized, double-blind, multicenter, placebo-controlled trial,
the efficacy of oral daily ibandronate (0.5 mg, 1 mg, or 2.5 mg daily)
was evaluated for the prevention of bone loss in 653 postmenopausal
women with osteopenia and no history of fracture.^12^ After 2 years of
treatment, statistically significant increases in and normalization of
mean lumbar spine and hip BMD from baseline versus placebo were observed
in the 2.5 mg group (see Table 2 below). In a subanalysis, bone loss was
greater in women who were recently menopausal (within the past 1-3
years) compared with those \>3 years postmenopause.
Table 2. Mean BMD changes from baseline in major clinical trials
------------------------------ --------------------- -------------------
**Study/Intervention** **Lumbar Spine BMD** **Total Hip BMD**
**BONE** (3 yr)
2.5 mg PO daily +6.5%\* +3.4%\*
20 mg PO intermittent +5.7%\* +2.9%\*
Placebo +1.3% -0.7%
**MOBILE** (2 yr
non-inferiority)
2.5 mg PO daily +5% +2.5%
50+50 mg PO monthly +5.3% +2.8%
100 mg PO monthly +5.6% +3.5%\*\*
150 mg PO monthly +6.6%\*\* +4.2%\*\*
**DIVA** (1 yr results --
non-inferiority)
2.5 mg PO daily +3.8% +1.8%
2 mg IV q2 months +5.1%\*\* +2.6%\*\*
3 mg IV q3 months +4.8%\*\* +2.4%\*\*
**Prevention** (2 yr)
0.5 mg PO daily -0.5% -0.5%
1 mg PO daily +0.3%\* 0
2.5 mg PO daily +1.9%\* +1.2%\*
Placebo -1.2% -0.6%
------------------------------ --------------------- -------------------
\*significant vs. placebo
\*\*significant vs. active control (daily regimen)
*Osteoporosis in Men*
Evidence for the effectiveness of ibandronate in males is limited to a
prospective, open-label pilot study that evaluated change in lumbar
spine BMD in 14 men with a baseline osteoporotic fracture.^1,13^
Patients received 2 mg IV ibandronate every 3 months. After two years,
significant increases in mean lumbar spine and trochanter BMD (6.7% and
3.2% respectively) were observed.
A Phase IV trial sponsored by Roche is planned to evaluate oral
ibandronate monthly in male osteoporosis and is currently recruiting
subjects (Clinical trial identifier NCT00397839).
*Treatment of Glucocorticoid-Induced Osteoporosis*
In an open label, parallel group clinical trial, 2 mg IV ibandronate was
compared to alfacalcidol in 115 patients (53 men and 62 women) with
corticosteroid-induced osteoporosis.^1,14^ After 3 years of treatment,
lumbar spine BMD in ibandronate-treated patients increased by a mean of
13.3% (±7.2) compared with 2.6% (±2.3) increase in alfacalcidol group.
Although not powered to detect a difference, a decreased frequency of
vertebral fractures was noted in the ibandronate group (8.6% vs. 22.8%
in alfacalcidol group).
*Paget's Disease*
Evidence for the effectiveness of ibandronate in the treatment of
Paget's disease is limited. In one study of 20 patients (12 males; 8
females) evaluating the usefulness of novel bone turnover markers,
ibandronate 2 mg IV was given either by injection or by 24 hour
infusion.^15^ As measured by the established marker, serum total
alkaline phosphatase (TAP), 11 of 20 patients achieved normalization of
levels with treatment (\<170 U/L). All patients relapsed (≥25% increase
over nadir) by 12 months. No differences in response were observed
between infusion and injection groups. The authors concluded that 2 mg
IV ibandronate is insufficient to normalize disease activity in most
patients in the treatment of Paget's disease.
A separate report described 2 additional studies: 1) retreatment of 13
patients from the above study with 2 mg IV ibandronate injection and 2)
treatment of 14 patients with high dose ibandronate (4 or 6 mg IV
infusion).^16^ Patients were recruited to the high dose group based on
high levels of TAP and/or failure to normalize with previous treatment
of 2 mg IV ibandronate. In the retreatment study, 6 of 13 patients
achieved normalization of TAP levels, which is similar to the response
observed with the first dose (5 of 13). In the high dose study, 6 of 10
and 2 of 4 patients achieved normalization of TAP levels in the 4 mg and
6 mg groups, respectively. The authors concluded that further study is
needed to determine the optimal dosing regimen for ibandronate.
**Adherence**
Patient adherence to medications including bisphosphonates in the
treatment of osteoporosis is generally poor.^17-19^ Factors that may
negatively influence adherence include absence of symptoms prior to
fracture (and unclear benefit of the medication), inconvenient dosing
instructions, cost, and side effects.^1,20^ Low adherence to
osteoporosis treatment has been linked to higher risk of fracture in
several evaluations utilizing patient populations from large healthcare
database systems.^21-24^ Reduction in overall fracture risk in the range
of approximately 16-30% (although this may vary) has been observed in
patients with high rates of compliance and persistence (approximately
80% or greater) compared to noncompliant patients.
In efforts to improve compliance, extended interval bisphosphonate
dosing regimens have become available including weekly, monthly,
quarterly, and yearly formulations. In evaluations comparing weekly and
daily oral bisphosphonates, weekly bisphosphonates were generally
associated with higher rates of compliance; however, compliance with all
regimens remained suboptimal.^17-19^
Direct comparisons of ibandronate regimens that evaluated preference and
persistence include BALTO, PERSIST, and a study by Gold et al.^25-27^ In
the BALTO trial (n=342), a randomized, 6 month, open-label cross over
trial, 66% of patients cited a preference for monthly ibandronate over
weekly alendronate, most commonly for reasons of convenience. In the
PERSIST trial (n=1103), more patients persisted on monthly ibandronate
along with a patient support program than on weekly alendronate at 6
months of therapy (56.6% vs 38.6%; p \<0.05). Gold et al. showed that
patients are influenced by knowledge of anti-fracture efficacy of
bisphosphonates and preferred weekly risedronate over monthly
ibandronate when informed of the proven non-vertebral anti-fracture
efficacy of risedronate. Limitations with these evaluations include the
short duration and some methodological issues. None investigated the
effects of adherence on outcomes. However, taken as a whole, patients
seem to prefer more convenient regimens, which may lead to improved
adherence and persistence. Additionally, increased knowledge about
medications can influence patient preference and adherence.
# Adverse Events (Safety Data)
Both oral and IV formulations of ibandronate were generally well
tolerated in clinical trials, with adverse events occurring with similar
frequency overall in the treatment and placebo groups. Oral ibandronate
has been studied in \>3900 women with PMO for durations of up to 3
years. Intravenous ibandronate has been studied in \>5000 women with PMO
for durations of up to 3 years.^1-3^
## Serious Adverse Events
Serious adverse events were reported in similar frequencies in all
placebo and treatment groups in the four major clinical trials (BONE,
Prevention, MOBILE, DIVA). Serious adverse events related to drug
therapy occurred rarely (≤1.1% of patients). Eight total serious adverse
events were reported among the safety population of 1583 patients in the
MOBILE trial: gastric ulcer (two patients), duodenal ulcer, erosive
duodenitis, gastric ulcer hemorrhage, hemorrhagic gastritis, melena, and
liver disorder.^8^
^Table\ 3.\ Tolerability\ of\ ibandronate6,8-10^
+--------+------+------+------+------+------+------+------+------+
| | **BO | | ** | | ** | | ** | |
| | NE** | | Prev | | MOBI | | DIVA | |
| | | | enti | | LE** | | (at | |
| | | | on** | | | | 1 | |
| | | | | | | | y | |
| | | | | | | | r)** | |
+--------+------+------+------+------+------+------+------+------+
| | **I | **P | **I | **P | **I | **I | **I | **I |
| | band | lace | band | lace | band | band | band | band |
| | 2.5 | bo** | 2.5 | bo** | 150 | 2.5 | 3 mg | 2.5 |
| | mg | | mg | | mg | mg | IV | mg |
| | PO | **( | PO | **( | PO | PO | q3 | PO |
| | dai | n=97 | dai | n=15 | dai | dai | mont | dai |
| | ly** | 5)** | ly** | 9)** | ly** | ly** | hs** | ly** |
| | | | | | | | | |
| | **( | | **( | | **( | **( | **( | **( |
| | n=97 | | n=16 | | n=39 | n=39 | n=46 | n=46 |
| | 7)** | | 3)** | | 6)** | 5)** | 9)** | 5)** |
+--------+------+------+------+------+------+------+------+------+
| All | 329 | 347 | 30 | 27 | 74( | 70 | 75 | 56 |
| withd | ( | ( | ( | ( | 19%) | ( | ( | ( |
| rawals | 34%) | 36%) | 18%) | 17%) | | 18%) | 16%) | 12%) |
+--------+------+------+------+------+------+------+------+------+
| Due to | 175 | 180 | 12 | 14 | 37 | 41 | 41 | 31 |
| AE | ( | ( | (7%) | (9%) | (9%) | ( | (9%) | (7%) |
| | 18%) | 19%) | | | | 10%) | | |
+--------+------+------+------+------+------+------+------+------+
| Other | 154 | 167 | 18 | 13 | 37 | 29 | 34 | 25 |
| | ( | ( | ( | (8%) | (9%) | (7%) | (7%) | (5%) |
| | 15%) | 17%) | 11%) | | | | | |
+--------+------+------+------+------+------+------+------+------+
^Table\ 4.\ Adverse\ events\ (%)\ reported\ in\ ≥2%\ of\ patients\ in\ the\ pivotal\ clinical\ trials1-3^
+--------------+--------+--------+--------+--------+--------+--------+
| | **BONE | | **MO | | ** | |
| | and | | BILE** | | DIVA** | |
| | Prev | | | | | |
| | ention | | | | | |
| | (poo | | | | | |
| | led)** | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| **Adverse | * | **Pla | * | * | * | * |
| Event** | *Iband | cebo** | *Iband | *Iband | *Iband | *Iband |
| | 2.5 mg | | 150 mg | 2.5 mg | 3 mg | 2.5 mg |
| | PO | **(n=1 | PO | PO | IV q3 | PO |
| | d | 134)** | d | d | mo | d |
| | aily** | | aily** | aily** | nths** | aily** |
| | | | | | | |
| | **(n=1 | | **(n= | **(n= | **(n= | **(n= |
| | 140)** | | 396)** | 395)** | 469)** | 465)** |
+--------------+--------+--------+--------+--------+--------+--------+
| Abdominal | | | 7.8 | 5.3 | 5.1 | 5.6 |
| pain | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Allergic | 2.5 | 1.9 | | | | |
| reaction | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Arthralgia | | | 5.6 | 3.5 | 9.6 | 8.6 |
+--------------+--------+--------+--------+--------+--------+--------+
| Arthritis | 3.2 | 2.7 | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Asthenia | 3.5 | 2.3 | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Back pain | 13.5 | 12.2 | 4.5 | 4.3 | 7 | 7.5 |
+--------------+--------+--------+--------+--------+--------+--------+
| Bronchitis | 10 | 6.8 | 2.5 | 3.5 | 2.1 | 2.8 |
+--------------+--------+--------+--------+--------+--------+--------+
| Constipation | | | 4 | 2.5 | 3.4 | 4.1 |
+--------------+--------+--------+--------+--------+--------+--------+
| Cystitis | | | | | 1.9 | 3.4 |
+--------------+--------+--------+--------+--------+--------+--------+
| Depression | | | | | 1.3 | 2.2 |
+--------------+--------+--------+--------+--------+--------+--------+
| Diarrhea | 6.8 | 5 | 5.1 | 4.1 | 2.8 | 2.4 |
+--------------+--------+--------+--------+--------+--------+--------+
| Dizziness | 3.7 | 2.6 | 2.3 | 1 | 1.9 | 2.8 |
+--------------+--------+--------+--------+--------+--------+--------+
| Dyspepsia | 11.9 | 9.8 | 5.6 | 7.1 | 3.6 | 4.3 |
+--------------+--------+--------+--------+--------+--------+--------+
| Fatigue | | | | | 2.8 | 1.1 |
+--------------+--------+--------+--------+--------+--------+--------+
| Gas | | | | | 1.5 | 3.4 |
| troenteritis | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Gastritis | 2.2 | 1.9 | | | 1.9 | 2.2 |
+--------------+--------+--------+--------+--------+--------+--------+
| Headache | 6.5 | 5.8 | 3.3 | 4.1 | 3.6 | 2.6 |
+--------------+--------+--------+--------+--------+--------+--------+
| Hypercho | 4.8 | 4.2 | | | 1.5 | 4.3 |
| lesterolemia | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Hypertension | | | 6.3 | 7.3 | 5.3 | 7.1 |
+--------------+--------+--------+--------+--------+--------+--------+
| Infection | 4.3 | 3.4 | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Influenza | | | 4 | 3.8 | 4.7 | 8 |
+--------------+--------+--------+--------+--------+--------+--------+
| In | | | 3.3 | 0.8 | 4.9 | 1.1 |
| fluenza-like | | | | | | |
| illness | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Insomnia | | | 2 | 0.8 | 1.1 | 2.6 |
+--------------+--------+--------+--------+--------+--------+--------+
| Joint | 3.6 | 3.3 | | | | |
| disorder | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Localized | | | 3 | 1.3 | 1.5 | 2.4 |
| os | | | | | | |
| teoarthritis | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Muscle cramp | | | 1.8 | 2 | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Myalgia | 5.7 | 5.1 | 2 | 0.8 | 2.8 | 0.9 |
+--------------+--------+--------+--------+--------+--------+--------+
| Nas | | | 3.5 | 4.3 | 3.4 | 6 |
| opharyngitis | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Nausea | | | 5.1 | 4.8 | 2.1 | 4.3 |
+--------------+--------+--------+--------+--------+--------+--------+
| Nerve root | 2.2 | 1.9 | | | | |
| lesion | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Pain in | 7.8 | 6.4 | 4 | 1.3 | 2.8 | 2.2 |
| extremity | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Pharyngitis | 2.5 | 1.5 | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Pneumonia | 5.9 | 4.3 | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Rash | | | 2.3 | 1.3 | 2.3 | 2.8 |
+--------------+--------+--------+--------+--------+--------+--------+
| Tooth | 3.5 | 2.3 | | | | |
| disorder | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Upper | 33.7 | 33.2 | 2 | 2 | 1.1 | 2.8 |
| respiratory | | | | | | |
| infection | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Urinary | 5.5 | 4.2 | | | 2.6 | 3.2 |
| tract | | | | | | |
| infection | | | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
| Vertigo | 3 | 2.5 | | | | |
+--------------+--------+--------+--------+--------+--------+--------+
# Precautions/Contraindications^1-3^
## Contraindications
- Hypersensitivity to ingredients
- Inability to sit upright or stand for 60 minutes following
administration of oral tablets
- Uncorrected hypocalcemia
## Precautions
*Mineral Metabolism*
Small reductions in serum calcium may occur with bisphosphonate therapy,
which are generally not clinically significant unless underlying
deficiencies are present.^28^ Hypocalcemia, vitamin D deficiency, and
other bone and mineral metabolic abnormalities should be corrected prior
to initiating therapy with ibandronate. Transient hypocalcemia may occur
with IV administration of the drug. Patients receiving ibandronate must
have adequate intake of calcium and vitamin D.
*Gastrointestinal Effects*
Oral administration of bisphosphonates as a class is associated with
adverse upper GI events including dysphagia, esophagitis, and esophageal
and gastric ulcers. To minimize the risk of these adverse effects,
patients should adhere to the special dosing administration instructions
(see Dosage and Administration section).
Major clinical trials evaluating ibandronate (BONE, MOBILE, Prevention)
did not specifically exclude patients with GI disorders or those taking
medications with the potential for additive GI irritation (i.e., NSAIDs,
aspirin).^6,8,12,29^ A significant and similar proportion of patients
across treatment groups were taking concomitant NSAIDs (35-37%) and had
pre-existing GI disorders (25-28%) in the BONE trial. Upper GI adverse
events occurred with similar frequency among ibandronate and placebo
groups as well as in the subpopulations on NSAIDs or with pre-existing
GI disorder. In the Prevention study, comparable upper GI events
occurred in ibandronate and placebo groups. Although no differences in
overall reports of adverse GI events were observed, an evenly
distributed but higher proportion of patients with a history of GI
disorders or on concomitant NSAIDs reported adverse events in the MOBILE
trial. In summary, unique safety concerns with ibandronate regarding GI
effects have not been identified. No apparent differences in GI
tolerance in daily versus monthly oral ibandronate regimens have been
observed. Caution should be exercised with ibandronate as with other
bisphosphonates, as upper GI disorders may occur with treatment.
*Osteonecrosis of the Jaw (ONJ)*
ONJ has been reported rarely in patients treated with bisphosphonates.
The majority of cases reported have been in patients with cancer treated
with IV bisphosphonates and undergoing dental procedures, although cases
in patients with osteoporosis on oral bisphosphonates have occurred.
Certain pre-existing conditions including cancer, anemia, coagulopathy,
infection, and pre-existing dental disease and concomitant therapy with
chemo, radiation, or corticosteroids are known risk factors. In a recent
review of ONJ in patients with osteoporosis treated with oral
bisphosphonates, 26 total cases in the literature were reported.^30^
Characteristics of these patients included age ≥60 years, female, and
history of invasive dental treatment. Whether discontinuing
bisphosphonate therapy and for how long prior to an invasive dental
procedure reduces the risk of ONJ is unknown.
*Musculoskeletal Pain*
Severe and sometimes incapacitating musculoskeletal pain has been
reported in patients taking bisphosphonates, including ibandronate. The
FDA recently issued a letter for healthcare professionals to aid in
recognition of bisphosphonates as a possible cause in patients
presenting with these symptoms.^31^ According to a postmarketing review,
symptoms may occur within days to years of initiating therapy. Symptoms
resolve quickly and completely in many patients after discontinuing the
bisphosphonate, although recovery may be slow and partial in others.
Risk factors and incidence are unknown.
*Pregnancy/Lactation*
Ibandronate belongs to FDA Pregnancy Category C. There are no well
controlled studies of ibandronate in pregnant women, although fetal harm
has been demonstrated in animal studies. Ibandronate should only be used
during pregnancy when the benefits justify the potential risks. It is
not known whether ibandronate is excreted in human milk. Caution should
be exercised if ibandronate is prescribed to a breastfeeding mother.
*Renal Impairment*
Intravenous administration of bisphosphonates has been associated with
renal impairment and rarely, acute renal failure. No cases of renal
failure were reported in the clinical development program with
ibandronate. Monitoring of serum creatinine prior to each dose of IV
ibandronate therapy is recommended. Therapy should be withheld in the
presence of worsening renal function. Close monitoring is recommended in
patients with pre-existing conditions or on medications that may
predispose them to renal impairment.
*Atrial Fibrillation*
Recent findings from a clinical efficacy trial with zoledronic acid as
well as a retrospective review of a previously completed trial with
alendronate have identified a potential association of bisphosphonates
and atrial fibrillation.^32-34^ At this time, it is unclear whether
there is a true association and whether it may be a class effect.
#
# Look-alike / Sound-alike (LA / SA) Error Risk Potential
The VA PBM and Center for Medication Safety is conducting a pilot
program which queries a multi-attribute drug product search engine for
similar sounding and appearing drug names based on orthographic and
phonologic similarities, as well as similarities in dosage form,
strength and route of administration. Based on similarity scores as well
as clinical judgment, the following drug names [may]{.underline} be
potential sources of drug name confusion:
+-----------------+----------------------------------------------------+
| **Drug Name** | **LA/SA Drug Name** |
+-----------------+----------------------------------------------------+
| **Ibandronate | Alendronate 10 mg tablets |
| (generic)** | |
| | |
| **2.5 mg | |
| tablets, 150 mg | |
| tablets, 1 | |
| mg/ml 3 ml | |
| injection** | |
+-----------------+----------------------------------------------------+
| | Etidronate 50 mg/ml injection |
+-----------------+----------------------------------------------------+
| | Nilandron\* 150 mg tablet |
+-----------------+----------------------------------------------------+
| | Pamidronate 3 mg/ml injection |
+-----------------+----------------------------------------------------+
| | Risedronate 30 mg tablets |
+-----------------+----------------------------------------------------+
| **Boniva | Januvia 25 mg tablets |
| (brand)** | |
| | |
| **2.5 mg | |
| tablets, 150 mg | |
| tablets, 1 | |
| mg/ml 3 ml | |
| injection** | |
+-----------------+----------------------------------------------------+
| | Kariva 0.15 mg tablets |
+-----------------+----------------------------------------------------+
| | Levitra 2.5 mg tablets |
+-----------------+----------------------------------------------------+
| | Tarceva 150 mg tablets |
+-----------------+----------------------------------------------------+
| | Univasc 15 mg tablets |
+-----------------+----------------------------------------------------+
\*Identified as a High Alert Medication per ISMP (i.e., special
precautions must be taken in the receipt, storage, distribution and
administration of these drugs)
# Drug Interactions^1-3^
## Drug Interactions
Ibandronate is not metabolized by the liver and is not an inhibitor of
the cytochrome P450 system. Renally eliminated, ibandronate does not
interfere with known acidic or basic transport systems involved in the
excretion of other drugs based on animal studies.
*Calcium and Multivalent Cations*
Concomitant oral administration of medications or supplements containing
multivalent cations (i.e., calcium, aluminum, magnesium, and iron) is
likely to interfere with oral ibandronate absorption. Oral medications
or supplements containing multivalent cations should be taken at least
60 minutes following oral ibandronate.
*Food and Beverages*
Food and beverages other than plain water are known to decrease the
bioavailability of oral ibandronate and should not be consumed less than
60 minutes following oral ibandronate administration.
*Aspirin and Non-Steroidal Anti-inflammatory Drugs (NSAIDs)*
A significant proportion of patients in the major clinical trials with
ibandronate were taking aspirin and/or NSAIDs. The incidence of upper GI
adverse events reported in clinical trials was similar between study
groups (i.e., placebo, daily, and monthly ibandronate). Caution should
be exercised when ibandronate is administered concomitantly with
aspirin/NSAIDs, as all are known to cause GI irritation.
*Other Medications*
No clinically relevant interactions with ibandronate were observed
during pharmacokinetic studies with ranitidine, tamoxifen, melphalan,
and prednisolone.
# Acquisition Costs
Table 5. Ibandronate Acquisition Costs
---------------------------- --------------- ------------------------ -----------------------
**Dose/Regimen** **Cost/Dose** **Cost/Patient/Month** **Cost/Patient/Year**
Ibandronate 2.5 mg tablets \$1.58 \$47.25 \$567.00
(daily)
Ibandronate 150 mg tablets \$45.41 \$45.41 \$544.92
(monthly)
Ibandronate 3 mg/3 ml IV \$299.80 \~\$99.93 \$1199.20
injection (q3 months)
---------------------------- --------------- ------------------------ -----------------------
Table 6. Comparator Acquisition Costs
---------------------------- --------------- ------------------------ -----------------------
**Drug/Regimen** **Cost/Dose** **Cost/Patient/Month** **Cost/Patient/Year**
Alendronate 10 mg tablets \$0.74 \$22.20 \$266.40
(daily)
Alendronate 70 mg tablets \$5.15 - \$5.30 \$20.60 - \$21.12 \$247.20 - \$254.40
(weekly)
Risedronate 5 mg tablets \$1.16 \$34.80 \$417.60
(daily)
Risedronate 35 mg tablets \$8.11 \$32.44 \$389.28
(weekly)
Zoledronic acid 5 mg/100 ml \$774.90 \$64.58 \$774.90
IV infusion (yearly)
---------------------------- --------------- ------------------------ -----------------------
# Conclusions
Ibandronate is a bisphosphonate agent available in oral daily, oral
monthly, and injectable quarterly regimens. Daily oral ibandronate (2.5
mg) has been shown to be superior to placebo in improving vertebral
fracture risk and spine and hip BMD in PMO. No difference in
nonvertebral fracture risk has been proven in individual clinical
trials, although pooled data suggests a benefit with higher doses of
ibandronate (150 mg oral monthly, 3 mg IV quarterly). Extended regimens
(150 mg PO monthly and 3 mg IV quarterly) have been shown to be at least
as effective as the daily regimen in improving spine and hip BMD.
However, decrease in fracture risk (vertebral or non-vertebral) has not
been directly demonstrated with ibandronate extended interval regimens.
Ibandronate is generally well tolerated, and its side effect profile,
including upper GI effects and musculoskeletal symptoms appears similar
to other bisphosphonates. No unique safety concerns with ibandronate
have been identified. Little is known about the safety and effectiveness
of ibandronate in the male population.
Extended interval bisphosphonate regimens including monthly oral and
quarterly injectable ibandronate have become available in attempts to
increase convenience and tolerability, improve adherence and
persistence, and optimally improve outcomes in osteoporosis treatment.
Preliminary study suggests that patients may prefer monthly oral
ibandronate over a weekly oral bisphosphonate regimen; however, it is
not known whether patient preference will translate into improved
outcomes with ibandronate.
**[Recommendations/Place in Therapy]{.underline}**
Potential advantages of ibandronate over other bisphosphonate agents
include the convenience of a monthly or quarterly regimen and the
ability to administer the IV formulation as a bolus rather than
infusion. Potential disadvantages include the lack of efficacy and
safety in males and in other indications (i.e., corticosteroid induced
osteoporosis, Paget's disease). Additionally, the monthly and IV
regimens have not been directly shown to reduce vertebral fractures.
There is no comparative efficacy or safety data available with
ibandronate vs. other bisphosphonates. The cost of ibandronate is higher
than that of alternatives.
# References:
1\. Boniva® Formulary Dossier. Final Version 3.0. Roche Pharmaceuticals.
Nutley NJ. February 2006.
2\. Boniva® Tablets Product Information. Roche Pharmaceuticals. Nutley
NJ. Aug 2006.
3\. Boniva® Injection Product Information. Roche Pharmaceuticals. Nutley
NJ. Feb 2007.
4\. Rosen HN, Drezner MK. Diagnosis and evaluation of osteoporosis in
postmenopausal women. UpToDate.Version 15.3;August 2007.
5\. Small RE. Uses and limitations of bone mineral density measurements
in the management of osteoporosis. Medscape General
Medicine;2005:7(2):3.
6\. Chesnut CH, Skag A, Christiansen C, et al. Effects of oral
ibandronate administered daily or intermittently on fracture risk in
postmenopausal osteoporosis. (BONE) J Bone Miner Res. 2004;19:1241-1249.
7\. Miller PD, McClung MR, MAcovei L, et al. Monthly oral ibandronate
therapy in postmenopausal osteoporosis: 1-year results from the MOBILE
study. J Bone Miner Res. 2005;20:1315-22.
8\. Reginster JY, Adami S, Lakatos P, et al. Efficacy and tolerability
of once-monthly oral ibandronate in postmenopausal osteoporosis: 2 year
results from the MOBILE study. Ann Rheum Dis. 2006;65:654-61.
9\. Delmas PD, Adami S, Strugala C, et al. Intravenous ibandronate
injections in postmenopausal women with osteoporosis: one-year results
from the Dosing Intravenous Administration Study (DIVA). Arthritis
Rheum. 2006;54(6):1838-46.
10\. Recker R, Stakkestad JA, Chesnut CH, et al. Insufficiently dosed
intravenous ibandronate injections are associated with suboptimal
antifracture efficacy in postmenopausal osteoporosis. Bone.
2004;34:890-99.
11\. Harris ST, Blumentals WA, Miller PD. Inbandronate and the risk of
non-vertebral and clinical fractures in women with postmenopausal
osteoporosis: results of a meta-analysis of phase III studies. Curr Med
Res Opin. 2008;24(1):237-45.
12\. McClung MR, Wasnich RD, Recker R, et al. Oral daily ibandronate
prevents bone loss in early postmenopausal women without osteoporosis. J
Bone Min Res. 2004;29(1):11-18.
13\. Lamy O, Sandini L, Pache I, et al. Intravenous ibandronate in men
with osteoporosis: an open pilot study over 2 years. J Endocrinol
Invest. 2003;26(8):728-32.
14\. Ringe JD, Dorst A, Faber H, et al. Intermittent intravenous
ibandronate injections reduce vertebral fracture risk in
corticosteroid-induced osteoporosis: results from a long term
comparative study. Osteoporos Int. 2003;14:801-7.
15\. Woitge HW, Oberwittler H, Heichel S, et al. Short and long term
effects of ibandronate treatment on bone turnover in Paget disease of
the bone. Clin Chem. 2000;46(5):684-90.
16\. Grauer A, Heichel S, Knaus J, et al. Ibandronate treatment in
Paget's disease of the bone. Bone. 1999;24(5 Suppl):87S-89S.
17\. Cramer JA, Amonkar MM, Hebborn A, et al. Compliance and persistence
with bisphosphonate dosing regimens among women with postmenopausal
osteoporosis. Curr Med Res Opin. 2005;21(9):1453-60.
18\. Cramer JA, Gold DT, Silverman SL, et al. A systematic review of
persistence and compliance with bisphosphonates for osteoporosis.
Osteoporos Int. 2007;18:1023-31.
19\. Recker RR, Gallagher R, MacCosbe PE. Effect of dosing frequency on
bisphosphonate medication adherence in a large longitudinal cohort of
women. Mayo Clin Proc. 2005;80(7):856-61.
20\. Osterberg L and Blaschke T. Adherence to medication. N Engl J Med.
2005;353:487-97.
21\. Caro JJ, Ishak KJ, Huybrechts KF, et al. The impact of compliance
with osteoporosis therapy on fracture rates in actual practice.
Osteoporos Int. 2004;15:1003-8.
22\. Rabenda V, Mertens R, Fabri V, et al. Adherence to bisphosphonates
therapy and hip fracture risk in osteoporotic women. Osteoporos Int.
2007; (epub Nov 13).
23\. Siris ES, Harris ST, Rosen CJ, et al. Adherence to bisphosphonate
therapy and fracture rates in osteoporotic women: relationship to
vertebral and nonvertebral fractures from 2 US claims databases. Mayo
Clin Proc. 2006;81(8):1013-1022.
24\. Weycker D, Macarios D, Edelsberg J, et al. Compliance with
osteoporosis drug therapy and risk of fracture. Osteoporos Int.
2007;18:271-7.
25\. Emkey R, Koltun W, Beusterien K, et al. Patient preference for
once-monthly ibandronate versus once-weekly alendronate in a randomized,
open-label, cross-over trial: the Boniva Alendronate Trial in
Osteoporosis (BALTO). Curr Med Res Opin. 2005;21(12):1895-1903.
26\. Cooper A, Drake J, Brankin E. Treatment persistence with
once-monthly ibandronate and patient support vs. once-weekly
alendronate: results from the PERSIST study. Int J Clin Pract.
2006;896-905.
27\. Gold et al. Patient preference and adherence: comparative US
studies between two bisphosphonates, weekly risedronate and monthly
ibandronate. Curr Med Res Opin. 2006;22(12):2383-91.
28\. Rosen HN. Pharmacology of bisphosphonates. UpToDate.Version
15.3;August 2007.
29\. Epstein S, Delmas PD, Emkey R, et al. Oral ibandronate in the
management of postmenopausal osteoporosis: review of upper
gastrointestinal safety. Maturitas.2006;54:1-10.
30\. Pazianas M, Miller P, Blumentals W, et al. A review of the
literature on osteonecrosis of the jaw in patients with osteoporosis
treated with oral bisphosphonates: prevalence, risk factors, and
clinical characteristics. Clin Ther. 2007;29:1548-58.
31\. FDA MedWatch. Bisphosphonates. Information for Healthcare
Professionals. Issued Jan 7, 2008. Available at:
www.fda.gov/cder/drug/InfoSheets/HCP/bisphosphonatesHCP.htm. Accessed
January 7, 2008.
32\. FDA MedWatch. Bisphosphonates. Early communication of an ongoing
safety review. Issued on October 1, 2007, updated January 7, 2008.
Available at: www.fda.gov/cder/drug/early_comm/bisphosphonates.htm.
Accessed January 15, 2008.
33\. Black DM, Delmas PD, Eastel R, et al. Once-yearly zoledronic acid
for treatment of postmenopausal osteoporosis. N Engl J Med.
2007;356:1809-22.
34\. Cummings SR, Schwartz AV, Black DM. Alendronate and atrial
fibrillation. N Engl J Med. 2007;356:18:1895-6. Letter.
**Prepared January 2008. Contact person: Lisa Longo, PharmD, BCPS**
Appendix 1. Ibandronate Clinical Trials
+------+----------+-----------+----------------------------------------+
| * | **Eli | **Interv | **Results** |
| *Stu | gibility | entions** | |
| dy** | Cr | | |
| | iteria** | | |
+======+==========+===========+========================================+
| BONE | **[I | Ib | **[Baseline |
| S | nclusion | andronate | demographics]{.underline}** (mean): |
| tudy | ]{.under | 2.5 mg PO | age 69yrs; ht 160cm; wt 67kg; yrs |
| | line}:** | daily | since menopause 21; patients with 1 |
| Che | | | fracture 93-94%; patients with 2 |
| snut | Female | Ib | fractures 42-44%; LS BMD T score -2.7 |
| 2004 | | andronate | to -2.8; TH BMD T score -1.7; all |
| | 55-80 | 20 mg PO | similar between groups. |
| R, | yrs old | int | |
| MC, | | ermittent | --------------- ----------- |
| DB, | ≥5 yrs | (20 mg | ---- ------------------ -------------- |
| PC, | postme | QOD x12 | **DAILY* |
| PG | nopause; | doses q3 | * **INTERMITTENT** **PLACEBO** |
| | | mos) | |
| n | 1-4 | | ITT (n=2929) |
| ~R~= | baseline | Placebo | 977 977 975 |
| 2946 | v | | |
| | ertebral | | Completed 66% (n=6 |
| ITT= | f | | 48) 68% (n=662) 64% (n=628) |
| 2929 | ractures | | treatment |
| | | | |
| PP= | LS BMD | | |
| 2125 | T-score | | Primary |
| | -2 to -5 | | |
| 3 | in ≥1 | | Endpoint |
| yrs | vertebra | | |
| dura | | | |
| tion | **[E | | Morphometric 4 |
| | xclusion | | .7%\* 4.9%\* \[3.4-6.4\] 9.6% |
| Si | ]{.under | | vertebral \[3.2-6.2 |
| tes: | line}:** | | \] \[7.5-11.7\] |
| N | | | fracture rate |
| orth | LS BMD | | |
| Ame | T-score | | |
| rica | \< -5 | | RRR |
| and | | | 62%\* \[41-75\] 50%\* \[26-66\] |
| Eu | \>2 | | |
| rope | baseline | | Secondary |
| | LS | | |
| | f | | Endpoints |
| | ractures | | |
| | | | |
| | Disorder | | Clinical 2 |
| | or | | .8%\* 2.8%\* \[1.6-3.9\] 5.3% |
| | therapy | | vertebral \[1.6-3. |
| | (within | | 9\] \[3.7-6.9\] |
| | the last | | fracture rate |
| | 6 mos) | | |
| | known to | | |
| | affect | | Clinical 9 |
| | bone | | .1% 8.9% 8.2% |
| | me | | osteoporotic |
| | tabolism | | |
| | | | non-vertebral |
| | Previous | | |
| | t | | fracture rate |
| | reatment | | |
| | with | | |
| | bisphos | | LS BMD changes 6 |
| | phonates | | .5%\* 5.7%\* 1.3% |
| | | | (mean) |
| | Fluoride | | |
| | t | | |
| | reatment | | TH BMD changes 3. |
| | in past | | 4%\* 2.9%\* -0.7% |
| | 12 mos | | (mean) |
| | or \>2 | | |
| | yrs | | |
| | duration | | Height loss |
| | | | 3.9 4.7 5.6 |
| | Renal | | (mm) |
| | im | | |
| | pairment | | |
| | (Cr | | Bone turnover |
| | \>2.4 | | Significant, |
| | mg/dL) | | biomarkers |
| | | | sustained |
| | Hy | | |
| | per/hypo | | reductions in |
| | calcemia | | |
| | | | markers in |
| | | | |
| | | | subpopulation |
| | | | |
| | | | studied |
| | | | --------------- ----------- |
| | | | ---- ------------------ -------------- |
| | | | |
| | | | \*significant vs. placebo; \[95% CI\] |
| | | | |
| | | | **AE Withdrawals:** 18.5%/18.5%/18.8% |
| | | | (daily/intermittent/placebo) |
| | | | |
| | | | **AEs/Safety:** No significant |
| | | | differences in AEs between groups |
| | | | including GI events, serious events or |
| | | | deaths |
| | | | |
| | | | **AEs reported in ≥10% patients in any |
| | | | group:** upper respiratory infection, |
| | | | accidental injury, back pain, |
| | | | arthralgia, dyspepsia, bronchitis, |
| | | | osteoporosis fracture |
+------+----------+-----------+----------------------------------------+
| MO | **[I | Ib | **[Baseline |
| BILE | nclusion | andronate | demographics]{.underline}** (mean): |
| S | ]{.under | 2.5 mg PO | age 66 yrs; ht 157-158 cm; wt 64 kg; |
| tudy | line}:** | daily | BMI 26 kg/m^2^; yrs since menopause |
| | | | 18-19; history of fracture 46-49%; LS |
| Mi | Female | Ib | BMD T score -3.3; all similar between |
| ller | | andronate | groups |
| PD | 55-80 | 50 mg PO | |
| 2 | yrs old | daily x2 | ----------- -------------- --------- |
| 005; | | monthly | ---- ------------- ------------------- |
| | ≥5 yrs | | **DAILY** **50/ |
| R | postm | Ib | 50 **100 **150 MONTHLY** |
| egin | enopause | andronate | |
| ster | | 100 mg PO | MONTHLY** MONTHLY** |
| JY | Oste | once | |
| 2 | oporosis | monthly | PP (n=1277) 292 |
| 006; | dx: LS | | 291 277 289 |
| Iba | BMD T | Ib | |
| ndro | score | andronate | Completed 82% (n=325) 8 |
| nate | (mean) | 150 mg PO | 3% (n=328) 80% (n=316) 81% (n=322) |
| Dos | -2 to -5 | once | treatment |
| sier | | monthly | |
| 2006 | **[E | | |
| | xclusion | (all | Primary |
| R, | ]{.under | patients | |
| MC, | line}:** | received | Endpoint |
| DB, | | calcium | |
| PG | PUD | and | |
| | (unco | vitamin D | LS BMD 5% \[4.4-5.5\] 5.3%\* |
| no | ntrolled | supplem | 5.6%\* 6.6%\*\^\[6-7.1\] |
| ninf | active | entation) | changes |
| erio | or | | \[4.8-5.9\] \[5.1-6.1\] |
| rity | re | | (mean) |
| | current) | | |
| n | | | |
| ~R~= | Disorder | | Secondary |
| 1609 | or | | |
| | therapy | | Endpoints |
| PP= | (within | | |
| 1277 | the last | | |
| | 6 mos) | | TH BMD 2.5% |
| ITT= | known to | | 2.8%\* 3.5%\*\^ 4.2%\*\^ |
| 1572 | affect | | changes |
| | bone | | |
| 2 | me | | (mean) |
| yrs | tabolism | | |
| dura | | | |
| tion | Previous | | Serum CTx Signi |
| | t | | ficant, |
| Si | reatment | | susta |
| tes: | with | | ined |
| N | bisphos | | reduc |
| orth | phonates | | tions in |
| Amer | | | all g |
| ica, | Fluoride | | roups |
| Eur | t | | ----------- -------------- --------- |
| ope, | reatment | | ---- ------------- ------------------- |
| Au | in past | | |
| stra | 12 mos | | \*noninferior to daily regimen; \^p |
| lia, | or \>2 | | \<0.05 vs. daily regimen; \[95% CI\]; |
| S | yrs | | sCTx= C-telopeptide of the alpha-chain |
| outh | duration | | of type I collagen |
| Af | | | |
| rica | Renal | | **AE Withdrawals:** 10%/8%/11%/9% |
| | im | | (daily/50-50/100/150) |
| | pairment | | |
| | (Cr | | **Clinical Osteoporotic Fractures:** |
| | \>2.4 | | 6.1%/7.3%/6.1%/6.8% |
| | mg/dL) | | (daily/50-50/100/150) |
| | | | |
| | CI to | | **AEs occurring more frequently in |
| | calcium | | monthly groups than daily group:** |
| | or | | arthralgia, dizziness, myalgia, |
| | vitamin | | flu-like illness |
| | D | | |
+------+----------+-----------+----------------------------------------+
| DIVA | **[I | Ib | **[Baseline |
| S | nclusion | andronate | Demographics]{.underline}** (mean): |
| tudy | ]{.under | 2.5 mg PO | age 66 yrs; ht 158 cm; wt 63-64 kg; |
| | line}:** | daily | BMI 25-26 kg/m^2^; yrs since menopause |
| De | | | 18-19; LS BMD T score -3.3; baseline |
| lmas | Female | Ib | fracture 42-44%; all similar between |
| PD | | andronate | groups |
| 2 | 55-80 | 2 mg IV | |
| 006; | yrs old | q2 mos | ------------ ------------- - |
| | | | -------------------- ----------------- |
| Iba | ≥5 yrs | Ib | **2.5 MG PO * |
| ndro | postm | andronate | *2MG IV Q2 MOS** **3MG IV Q3 MOS** |
| nate | enopause | 3 mg IV | |
| Dos | | q3 mos | DAILY** |
| sier | Oste | | |
| 2006 | oporosis | (all | PP (n=1104) 3 |
| | dx: LS | patients | 81 355 368 |
| R, | BMD T | received | |
| MC, | score | 500 mg | Completed 1 87% (n=40 |
| DB, | (mean) | oral | 9) 84% (n=382) 84% (n=394) |
| PG, | -2 to -5 | calcium | yr of |
| no | | and 400 | |
| ninf | **[E | iu oral | treatment |
| erio | xclusion | vitamin D | |
| rity | ]{.under | daily | |
| | line}:** | supplem | Primary |
| n | | entation) | |
| ~R~= | Previous | | Endpoint |
| 1395 | IV | | |
| | bispho | | |
| PP= | sphonate | | LS BMD 3. |
| 1104 | therapy | | 8% 5.1%\*\^\[4.7-5.5\] 4.8% |
| | | | changes \[3.4-4.2\] |
| 2 | Therapy | | \*\^\[4.5-5.2\] |
| yrs | within | | (mean)^†^ |
| dura | the last | | |
| tion | 6 mos | | |
| (1 | known to | | Secondary |
| yr | affect | | |
| data | bone | | Endpoints |
| av | me | | |
| aila | tabolism | | |
| ble) | (i | | TH BMD 1.8% |
| | ncluding | | 2.6%\*\^ 2.4%\*\^ |
| Si | bisphosp | | changes |
| tes: | honates) | | |
| N | | | (mean) |
| orth | Renal | | |
| Amer | im | | |
| ica, | pairment | | Serum CTx |
| Eur | (Cr | | Significant |
| ope, | \>2.4 | | |
| Au | mg/dL) | | reductions in |
| stra | | | |
| lia, | History | | all groups |
| S | of major | | ------------ ------------- - |
| outh | upper GI | | -------------------- ----------------- |
| Af | disease | | |
| rica | | | ^†^n=377/353/365 for LS BMD at 1 yr |
| | Allergy | | (daily/2mgIV /3mgIV); \*noninferior to |
| | to | | daily regimen; \^p \<0.05 vs. daily |
| | bisphos | | regimen; \[95% CI\]; sCTx= |
| | phonates | | C-telopeptide of the alpha-chain of |
| | | | type I collagen |
| | | | |
| | | | **AE Withdrawals:** 4.5%/5.4%/6.6% |
| | | | (2.5PO/2IV/3IV) |
| | | | |
| | | | **Clinical fractures:** 17/13/13 |
| | | | (2.5PO/2IV/3IV) |
| | | | |
| | | | **Renal AEs:** 2%/3%/2% |
| | | | (2.5PO/2IV/3IV) |
| | | | |
| | | | **Flu-like symptoms:** 1.1%/5.1%/4.9% |
| | | | (2.5PO/2IV/3IV) |
| | | | |
| | | | **Common AEs:** dyspepsia, upper |
| | | | abdominal pain, arthralgia, and |
| | | | flu-like illness |
+------+----------+-----------+----------------------------------------+
| Re | **[I | Ib | **[Baseline |
| cker | nclusion | andronate | demographics]{.underline}** (mean): |
| R | ]{.under | 0.5 mg IV | age 67 yrs; LS BMD T score -2.7 to |
| 2 | line}:** | q3 mos | -2.79; TH BMD T score -1.8 to -1.9; 1 |
| 004; | | | baseline vertebral fracture 48-51%; |
| Dos | Female | Ib | \>1 baseline vertebral fracture 47-50% |
| sier | | andronate | ; all similar between groups |
| 2006 | 55-76 | 1 mg IV | |
| | yrs old | q3 mos | -------------- --- |
| R, | | | ---------- ------------- ------------- |
| DB, | ≥5 yrs | Placebo | * |
| PG | postme | | *0.5MG IV q3 **1MG IV q3 **PLACEBO** |
| | nopause; | (all | |
| n | | patients | MOS** MOS** |
| ~R~= | 1-4 | received | |
| 2862 | baseline | 500 mg | ITT (n=2 |
| | v | oral | 860) 950 961 949 |
| ITT= | ertebral | calcium | |
| 2860 | f | and 400 | Completed 8 |
| | ractures | iu oral | 4% (n=798) 80% (n=774) 83% (n=787) |
| 3 | | vitamin D | treat |
| yrs | LS BMD | daily | ment |
| dura | T-score | supplem | |
| tion | -2 to -5 | entation) | Prima |
| | in ≥1 | | ry |
| | vertebra | | Endpo |
| | | | int |
| | **[E | | |
| | xclusion | | Morphometr |
| | ]{.under | | ic 8.7% 9.2% 10.7% |
| | line}:** | | verte |
| | | | bral |
| | Disorder | | fract |
| | or | | ure rate |
| | therapy | | |
| | (within | | Secon |
| | the last | | dary |
| | 6 mos) | | Endpo |
| | known to | | ints |
| | affect | | |
| | bone | | Clinical |
| | me | | 10.2% 10.8% 12.6% |
| | tabolism | | osteo |
| | | | porotic |
| | Previous | | fract |
| | t | | ures |
| | reatment | | |
| | with | | LS BMD changes |
| | bisphos | | 3.9% 4.9% not given |
| | phonates | | (mean |
| | | | ) \[3.6-4.3\] \[4.6-5.3\] |
| | T | | |
| | reatment | | TH BMD changes |
| | with | | 1.1% 2.3% not given |
| | investi | | (mean |
| | gational | | ) \[0.8-1.3\] \[2-2.6\] |
| | drug in | | -------------- --- |
| | past 30 | | ---------- ------------- ------------- |
| | days | | |
| | | | \*significant vs. placebo; \[95% CI\] |
| | Fluoride | | |
| | t | | **AE Withdrawals:** 8%/11%/8% |
| | reatment | | (0.5/1/placebo) |
| | in past | | |
| | 12 mos | | **AEs reported in ≥1% higher incidence |
| | or \>2 | | in active treatment arms:** myalgia, |
| | yrs | | sinusitis, headache, joint disorder, |
| | duration | | asthenia, injection site reaction |
| | | | |
| | Renal | | |
| | im | | |
| | pairment | | |
| | (Cr | | |
| | \>2.4 | | |
| | mg/dL) | | |
| | | | |
| | CI to | | |
| | calcium | | |
| | therapy | | |
| | | | |
| | Hy | | |
| | per/hypo | | |
| | calcemia | | |
+------+----------+-----------+----------------------------------------+
| Pr | **[I | Ib | **[Baseline |
| even | nclusion | andronate | demographics]{.underline}** (mean): |
| tion | ]{.under | 0.5 mg PO | 58-59; yrs since menopause 8-9; wt |
| | line}:** | daily | 71-75 kg; LS BMD T score -1 to -1.1; |
| McC | | | all similar between groups |
| lung | Female | Ib | |
| 2 | | andronate | ----------- ----- |
| 004; | ≥5 yrs | 1 mg PO | ---- --------- --------- ------------- |
| | postme | daily | **0 |
| Dos | nopause; | | .5MG **1MG **2.5MG **PLACEBO** |
| sier | | Ib | |
| 2006 | No | andronate | DAILY** DAILY** DAILY** |
| | history | 2.5 mg PO | |
| R, | of | daily | Completed 86% |
| DB, | oste | | 87% 82% 83% (n=132) |
| MC, | oporotic | Placebo | trea |
| PG | f | | tment (n=138) (n=144) (n=133) |
| | ractures | (all | |
| n~R~ | | patients | LS BMD |
| =653 | LS BMD | received | -0.5% 0.3%\* 1.9%\* -1.2% |
| | T-score | 500 mg | chan |
| ITT | \>-2.5 | oral | ges |
| =620 | | calcium | (mea |
| | **[E | supple | n) |
| 2 | xclusion | mentation | |
| yrs | ]{.under | daily) | TH BMD |
| dura | line}:** | | -0.5% 0 1.2%\* -0.6% |
| tion | | | chan |
| | B | | ges |
| | ilateral | | (mea |
| | ooph | | n) |
| | orectomy | | ----------- ----- |
| | | | ---- --------- --------- ------------- |
| | Renal | | |
| | im | | \*significant vs. placebo; \[95% CI\] |
| | pairment | | |
| | | | **AE Withdrawals:** 5%/5%/7%/9% |
| | Severe | | (0.5/1/2.5/placebo) |
| | vitamin | | |
| | D | | **Commonly reported AEs:** dyspepsia, |
| | de | | gastroenteritis, nausea, GI pain, GI |
| | ficiency | | disorder (similar between all groups) |
| | | | |
| | Abnormal | | |
| | calcium | | |
| | levels | | |
| | | | |
| | CI to | | |
| | calcium | | |
| | therapy | | |
| | | | |
| | Delayed | | |
| | es | | |
| | ophageal | | |
| | emptying | | |
| | | | |
| | Disorder | | |
| | or | | |
| | therapy | | |
| | (within | | |
| | the last | | |
| | 6 mos) | | |
| | known to | | |
| | affect | | |
| | bone | | |
| | me | | |
| | tabolism | | |
| | | | |
| | Previous | | |
| | t | | |
| | reatment | | |
| | with | | |
| | bisphos | | |
| | phonates | | |
| | | | |
| | T | | |
| | reatment | | |
| | with | | |
| | investi | | |
| | gational | | |
| | drug in | | |
| | past 30 | | |
| | days | | |
| | | | |
| | Fluoride | | |
| | t | | |
| | reatment | | |
| | in past | | |
| | 12 mos | | |
| | or \>2 | | |
| | yrs | | |
| | duration | | |
+------+----------+-----------+----------------------------------------+
AE=adverse event; BMD=bone mineral density; BMI=body mass index;
CI=contraindication; DB=double-blind; ITT=intention to treat;
GI=gastrointestinal; LS=lumbar spine; MC=multicenter;
PC=placebo-controlled; PG=parallel group; PP=per-protocol; PUD=peptic
ulcer disease; RRR=relative risk reduction; TH=total hip
| en |
converted_docs | 930887 | SECTION D - PACKAGING AND MARKING
D.1 PACKAGING AND MARKING (NASA 18-52.210-75) (SEP 1990) (ALTERNATE II)
(SEP 1990)
\(a\) -The Contractor shall pack and mark all hardware deliverable under
this contract in accordance with the provisions of NASA Handbook (NHB)
6000.1, Requirements for Packaging, Handling, and Transportation, and/or
MIL-STD-2073-1 and MIL-STD-2073-2, as applicable, except as noted below:
None
\(b\) The Contractor shall pack potentially hazardous items in
accordance with paragraph 204 of NHB 6000.1.
\(c\) The Contractor shall develop packaging, handling, and
transportation records, if required, from engineering and packaging
data. The Contracting Officer\'s technical representative is the
approving official of the records and special packaging data under
paragraph 302 of NHB 6000.1.
\(d\) The Contractor\'s packaging specifications or procedures may be
utilized if they are (i) not in conflict with cited NASA specifications
and (ii) approved in writing by the Contracting Officer. In any conflict
between NASA and the Contractor specifications or procedures, the NASA
documents cited in this clause shall take precedence.
\(e\) The Contractor shall place identical requirements on all
subcontracts.
\(f\) The following items to be furnished under this contract are for
space flight use:
To be determined by task order.
\(g\) All markings for space flight items shall be blue in color. All
shipping containers, shipping documents, and purchasing documents for
these items shall be marked \"ITEMS FOR SPACE FLIGHT USE.\"
\(h\) The Contractor shall prominently display a NASA Critical Space
Item Label on the exterior of all Class I, Class II, and Class III
interim packages and exterior shipping containers to alert all shipping
and handling personnel to the criticality of the item in accordance with
paragraph 303 of NHB 6000.1.
(End of clause)
\[END OF SECTION\]
| en |
converted_docs | 985984 | ### Expand Your Business and Boost Your International Sales
The U.S. Commercial Service's Gold Key Matchmaking Service (GKS) enables
you to spend your time doing what you do best --- managing your company.
Our commercial specialists in **INDONESIA, MALAYSIA, PHILIPPINES,
SINGAPORE, THAILAND** and **VIETNAM** will arrange one-on-one business
meetings for you with pre-screened buyers, distributors, professional
associations, government contacts, and/or licensing or joint venture
partners in markets around the world, including the Southeast Asia
region. We'll do all the legwork so you're prepared to hit the ground
running once you're in country, saving you time and money. Just choose
which markets your firm is targeting, and the Commercial Service will
facilitate each stop in your Southeast Asian strategy!
{width="0.6188976377952756in"
height="0.5098425196850394in"}{width="0.6862204724409449in"
height="0.5161417322834646in"}{width="0.6929133858267716in"
height="0.5866141732283464in"}{width="0.6665354330708662in"
height="0.5019685039370079in"}{width="0.6862204724409449in"
height="0.5192913385826772in"}{width="0.6862204724409449in"
height="0.5192913385826772in"}
#
# **The Southeast Asia GKS:**
# **More Bang for Your Buck**
The Southeast Asia region includes the markets of Indonesia, Malaysia,
Philippines, Singapore, Thailand, and Vietnam. The strong consumer
demand of these individual markets---as well as their close proximity to
one another---make the Southeast Asia Region ideal for the coordinated
matchmaking efforts of our GKS. Our dedicated Commercial Specialists
will work with you to:
- Identify qualified and suitable prospects matching your criteria
```{=html}
<!-- -->
```
- Schedule appointments with up to five pre-qualified buyers per
market
- Provide brief profiles of the pre-qualified buyers
- Ensure you have a thorough understanding of the market, including
counseling from our local experts and up-to-date relevant market
research
- Coordinate logistical support, e.g., transfers, discounted lodging
reservations, etc.
- Arrange for Interpreter services
**Let Us Help You Sell in the Southeast Asia Market and Worldwide**
With its network of offices across the United States and in more than 80
countries, the U.S. Commercial Service of the U.S. Department of
Commerce utilizes its global presence and international marketing
expertise to help U.S. companies sell their products and services
worldwide.
| en |
converted_docs | 050213 | PAIN MANAGEMENT
*Prepared by Kathy Kessel, Library Service \~ VAMC Northport, NY*
#
## August 2002
This bibliography on PAIN MANAGEMENT was prepared by Kathy Kessel,
Library Service, VAMC, Northport, NY, as part of a VA Library Network
(VALNET) effort to identify useful published information relating to
trends in health care. This bibliography will be updated monthly. Please
check with your Library Service if you are interested in this resource
or would like to identify other materials specific to your information
needs.
Other bibliographies prepared for this project are as follows:
CHEMICAL/BIOLOGICAL TERRORISM
Prepared by Stephen Perlman, Library Service, VAMC, Durham, NC
CUSTOMER FOCUSED HEALTHCARE DELIVERY AND SATISFACTION
Prepared by Sandra Brayson, Library Service, VAMC, Portland, OR
END OF LIFE CARE
Prepared by Stephen Perlman, Library Service, VAMC, Durham, NC
HEPATITIS C
Prepared by Stephen Perlman, Library Service, VAMC, Durham, NC
HIGH PERFORMANCE DEVELOPMENT MODEL
Prepared by Joyce Zarrinnahad, Central Office Library, Washington DC
PAIN MANAGEMENT
Prepared by Kathy Kessel, Library Service, VAMC, Northport, NY
PATIENT EDUCATION
Prepared by Stephen Perlman, Library Service, VAMC, Durham, NC
PATIENT SAFETY
Prepared by Stephen Perlman, Library Service, VAMC, Durham, NC
POST-TRAUMATIC STRESS DISORDER
Prepared by Stephen Perlman, Library Service, VAMC, Durham, NC
VETERAN'S HEALTHCARE
Prepared by Stephen Perlman, Library Service, VAMC, Durham, NC
WOMEN\'S HEALTH
Prepared by Stephen Perlman, Library Service, VAMC, Durham, NC
# **AUGUST 2002**
Alvarez, R. \"Preliminary results on the safety and efficacy of the
OssaTron for treatment of plantar fasciitis.\" *Foot & Ankle
International.* 23, no. 3(2002): 197-203 UI 11934060.
American College of Critical Care Medicine of the Society of Critical
Care Medicine, A. S. o. H.-S. P. A. C. o. C. P. \"Clinical practice
guidelines for the sustained use of sedatives and analgesics in the
critically ill adult.\" *American Journal of Health-System Pharmacy.*
59, no. 2(2002): 150-78 UI 11826570.
Amsterdam, E. A., et al. \"Immediate exercise testing to evaluate
low-risk patients presenting to the emergency department with chest
pain.\" *Journal of the American College of Cardiology.* 40, no.
2(2002): 251-6 UI 12106928.
Amsterdam, E. A., et al. \"Acute ischemic syndromes. Chest pain center
concept.\" *Cardiology Clinics.* 20, no. 1(2002): 117-36 UI 11845539.
Anonymous. \"Antibiotics for heart health?\" *Health News.* 8, no.
5(2002): 9 UI 12132417.
Anonymous. \"JCAHO partners to develop pain management measures.\"
*Joint Commission Perspectives.* 22, no. 4(2002): 2, 4 UI 11957864.
Anonymous. \"New, non-NSAID alternative.\" *Nurse Practitioner.* 27, no.
2(2002): 57 UI 11858591.
Anonymous. \"Pain management is high priority for surveyors.\" *Hospital
Peer Review.* 27, no. 2(2002): 20-3 UI 11924067.
Anonymous. \"SAM-e on par with NSAIDs for osteoarthritis?\" *Health
News.* 8, no. 7(2002): 8-9 UI 12132510.
Anonymous. \"Steps taken to ensure narcotics\' availability for
legitimate use.\" *Clinical Journal of Oncology Nursing.* 6, no.
3(2002): 124 UI 11998600.
Asano, H., T. Muneta, and K. Shinomiya. \"Evaluation of clinical factors
affecting knee pain after anterior cruciate ligament reconstruction.\"
*American Journal of Knee Surgery.* 15, no. 1(2002): 23-8 UI 11829330.
Ashley, K. F. \"Paracetamol pain relief.\" *British Dental Journal.*
192, no. 5(2002): 243; discussion 243 UI 11924950.
Baltic, T. E., et al. \"Improving pain relief in a rural cancer
center.\" *Cancer Practice.* 10, no. Suppl 1(2002): S39-44 UI 12027968.
Banks, C. \"Spinal cord stimulation for patients with chronic pain
conditions.\" *Professional Nurse.* 17, no. 7(2002): 425-7 UI 11917433.
Basaranoglu, G., V. Erden, and H. Delatioglu. \"Reduction of pain on
injection of propofol: a comparison of fentanyl with remifentanil.\"
*Anesthesia & Analgesia.* 94, no. 4(2002): 1040-1 UI 11916821.
Bell, A., and R. Wheeler. \"Improving the pain management standard of
care in a community hospital.\" *Cancer Practice.* 10, no. Suppl
1(2002): S45-51 UI 12027969.
Bharani, A., et al. \"Efficacy of Terminalia arjuna in chronic stable
angina: a double-blind, placebo-controlled, crossover study comparing
Terminalia arjuna with isosorbide mononitrate.\" *Indian Heart Journal.*
54, no. 2(2002): 170-5 UI 12086380.
Biddle, C. \"Meta-analysis of the effectiveness of nonsteroidal
anti-inflammatory drugs in a standardized pain model.\" *AANA Journal.*
70, no. 2(2002): 111-4 UI 11969061.
Blum, C. L. \"Chiropractic and pilates therapy for the treatment of
adult scoliosis.\" *Journal of Manipulative & Physiological
Therapeutics.* 25, no. 4(2002): E3 UI 12021749.
Boersma, E., et al. \"Platelet glycoprotein IIb/IIIa inhibitors in acute
coronary syndromes: a meta-analysis of all major randomised clinical
trials.\" *Lancet.* 359, no. 9302(2002): 189-98 UI 11812552.
Bornhovd, K., et al. \"Painful stimuli evoke different stimulus-response
functions in the amygdala, prefrontal, insula and somatosensory cortex:
a single-trial fMRI study.\" *Brain.* 125, no. Pt 6(2002): 1326-36 UI
12023321.
Brodmerkel, G. J., Jr. \"Patient-maintained sedation for ERCP with a
target-controlled infusion of propofol: a pilot study.\"
*Gastrointestinal Endoscopy.* 55, no. 7(2002): 966; discussion 966 UI
12024171.
Carnie, J., J. Boden, and F. Gao Smith. \"Prediction by computerised
tomography of distance from skin to epidural space during thoracic
epidural insertion.\" *Anaesthesia.* 57, no. 7(2002): 701-4 UI 12059829.
Chang, B. J. \"Ergonomic benefits of surgical telescope systems:
selection guidelines.\" *Journal of the California Dental Association.*
30, no. 2(2002): 161-9 UI 11881960.
Chen, J. L., et al. \"Infections associated with intra-spinal
catheter-pump systems for severe pain management.\" *Journal of Hospital
Infection.* 50, no. 4(2002): 322-3 UI 12014911.
Chow, R. \"EBM in action: is laser treatment effective and safe for
musculoskeletal pain? \[letter; comment.\].\" *Medical Journal of
Australia.* 176, no. 4(2002): 194-5 UI 11913929.
Cullinane, C. A., D. Z. Chu, and A. N. Mamelak. \"Current surgical
options in the control of cancer pain.\" *Cancer Practice.* 10, no.
Suppl 1(2002): S21-6 UI 12027965.
Dahl, J. L., et al. \"Success of the state pain initiatives: moving pain
management forward.\" *Cancer Practice.* 10, no. Suppl 1(2002): S9-S13
UI 12027963.
Daniell, H. W. \"Inhibition of opioid analgesia by selective serotonin
reuptake inhibitors.\" *Journal of Clinical Oncology.* 20, no. 9(2002):
2409; discussion 2409-10 UI 11981019.
De Cordoba, J. L., et al. \"Combined lumbar and sacral plexus block for
the management of long-standing hip pain.\" *Regional Anesthesia & Pain
Medicine.* 27, no. 2(2002): 226-7; discussion 227 UI 11915077.
de Feyter, P. J., et al. \"Bypass surgery versus stenting for the
treatment of multivessel disease in patients with unstable angina
compared with stable angina.\" *Circulation.* 105, no. 20(2002): 2367-72
UI 12021222.
Desmeules, J. A., et al. \"Advances with analgesics and NSAIDs for the
treatment of spinal disorders.\" *Best Practice & Research in Clinical
Rheumatology.* 16, no. 1(2002): 105-21 UI 11987934.
Desmond, R. A., et al. \"Clinical applications for change-point analysis
of herpes zoster pain.\" *Journal of Pain & Symptom Management.* 23, no.
6(2002): 510-6 UI 12067775.
Dhillon, S., et al. \"The therapeutic impact of abdominal ultrasound in
patients with acute abdominal symptoms.\" *Clinical Radiology.* 57, no.
4(2002): 268-71 UI 12014871.
Digre, K. B. \"Idiopathic intracranial hypertension headache.\" *Current
Pain & Headache Reports.* 6, no. 3(2002): 217-25 UI 12003693.
Dodick, D. W. \"Thunderclap headache.\" *Current Pain & Headache
Reports.* 6, no. 3(2002): 226-32 UI 12003694.
Drewes, A. M., et al. \"Multimodal assessment of pain in the esophagus:
a new experimental model.\" *American Journal of Physiology -
Gastrointestinal & Liver Physiology.* 283, no. 1(2002): G95-103 UI
12065296.
Dudler, J., and F. Balague. \"What is the rational diagnostic approach
to spinal disorders?\" *Best Practice & Research in Clinical
Rheumatology.* 16, no. 1(2002): 43-57 UI 11987931.
Duncan, M. A., et al. \"Periosteal infusion of bupivacaine/morphine post
sternal fracture: a new analgesic technique.\" *Regional Anesthesia &
Pain Medicine.* 27, no. 3(2002): 316-8 UI 12016608.
Edelen, C., and M. Perlow. \"A comparison of the effectiveness of an
opioid analgesic and a nonpharmacologic intervention to improve
incentive spirometry volumes.\" *Pain Management Nursing.* 3, no.
1(2002): 36-42 UI 11894000.
Etlin, D. \"Neck pain.\" *CMAJ: Canadian Medical Association Journal.*
166, no. 1(2002): 16 UI 11800242.
Evans, D. \"The effectiveness of music as an intervention for hospital
patients: a systematic review.\" *Journal of Advanced Nursing.* 37, no.
1(2002): 8-18 UI 11784393.
Evans, D. W. \"Mechanisms and effects of spinal high-velocity,
low-amplitude thrust manipulation: previous theories.\" *Journal of
Manipulative & Physiological Therapeutics.* 25, no. 4(2002): 251-62 UI
12021744.
Evrard, S. \"Surgical lesioning of splanchnic nerves using wet needle
radiofrequency thermoablation.\" *Journal of Surgical Oncology -
Supplement.* 80, no. 3(2002): 171-2 UI 12115800.
Field, J. M. \"The reperfusion era. Strategies for establishing or
maintaining coronary patency.\" *Cardiology Clinics.* 20, no. 1(2002):
137-57, ix UI 11845541.
Fisher, S. E., et al. \"Pain assessment and management in cognitively
impaired nursing home residents: association of certified nursing
assistant pain report, Minimum Data Set pain report, and analgesic
medication use.\" *Journal of the American Geriatrics Society.* 50, no.
1(2002): 152-6 UI 12028260.
Fishman, S. M., et al. \"Radiation safety in pain medicine.\" *Regional
Anesthesia & Pain Medicine.* 27, no. 3(2002): 296-305 UI 12016604.
Furlow, L., and J. L. O\'Quinn. \"Does prayer really help?\" *Journal of
Christian Nursing.* 19, no. 2(2002): 31-4 UI 11908050.
Gallagher, E. J., et al. \"Reliability and validity of a visual analog
scale for acute abdominal pain in the ED.\" *American Journal of
Emergency Medicine.* 20, no. 4(2002): 287-90 UI 12098173.
Gebhardt, R., and M. A. Kinney. \"Conversion from intrathecal morphine
to oral methadone.\" *Regional Anesthesia & Pain Medicine.* 27, no.
3(2002): 319-21 UI 12016609.
Goadsby, P. J. \"Headache.\" *Current Opinion in Neurology.* 15, no.
3(2002): 285-6 UI 12045726.
Gori, A. M., et al. \"Tissue factor and tissue factor pathway inhibitor
levels in unstable angina patients during short-term
low-molecular-weight heparin administration.\" *British Journal of
Haematology.* 117, no. 3(2002): 693-8 UI 12028043.
Gracely, R. H., et al. \"Functional magnetic resonance imaging evidence
of augmented pain processing in fibromyalgia.\" *Arthritis &
Rheumatism.* 46, no. 5(2002): 1333-43 UI 12115241.
Greenwald, I. B., and D. H. Newman. \"Acute abdominal emergencies.
Assessing & treating patients with severe abdominal pain.\" *Journal of
Emergency Medical Services.* 27, no. 6(2002): 88-94, 96-9; quiz 100-1 UI
12068714.
Guignard, B., et al. \"Supplementing desflurane-remifentanil anesthesia
with small-dose ketamine reduces perioperative opioid analgesic
requirements.\" *Anesthesia & Analgesia.* 95, no. 1(2002): 103-8, table
of contents UI 12088951.
Hagg, O., et al. \"Simplifying outcome measurement: evaluation of
instruments for measuring outcome after fusion surgery for chronic low
back pain.\" *Spine.* 27, no. 11(2002): 1213-22 UI 12045520.
Hazelett, S., C. Powell, and V. Androulakakis. \"Patients\' behavior at
the time of injury: effect on nurses\' perception of pain level and
subsequent treatment.\" *Pain Management Nursing.* 3, no. 1(2002): 28-35
UI 11893999.
Helvig, E. I. \"Managing thermal injuries within WOCN practice.\"
*Journal of Wocn.* 29, no. 2(2002): 76-82 UI 11901415.
Hesselmann, S., et al. \"Systemic mast cell disease (SMCD) and bone
pain. A case treated with radiotherapy.\" *Strahlentherapie und
Onkologie.* 178, no. 5(2002): 275-9 UI 12082688.
Hoffmann, D. \"Undertreating pain in women: a risky practice.\" *Journal
of Gender-Specific Medicine.* 5, no. 1(2002): 10-3 UI 11859681.
Hogue, J. H., and T. L. Mersfelder. \"Pathophysiology and first-line
treatment of osteoarthritis.\" *Annals of Pharmacotherapy.* 36, no.
4(2002): 679-86 UI 11918520.
Holmes, D. R., Jr., and B. J. Gersh. \"And the answer is, it doesn\'t
much matter.\" *Circulation.* 106, no. 1(2002): 11-3 UI 12093761.
Holroyd, K. A. \"Assessment and psychological management of recurrent
headache disorders.\" *Journal of Consulting & Clinical Psychology.* 70,
no. 3(2002): 656-77 UI 12090375.
Holthusen, H., et al. \"Preemptive analgesia: no relevant advantage of
preoperative compared with postoperative intravenous administration of
morphine, ketamine, and clonidine in patients undergoing transperitoneal
tumor nephrectomy.\" *Regional Anesthesia & Pain Medicine.* 27, no.
3(2002): 249-53 UI 12016597.
Humphreys, S. C., J. C. Eck, and S. D. Hodges. \"Neuroimaging in low
back pain.\" *American Family Physician.* 65, no. 11(2002): 2299-306 UI
12074530.
Idvall, E., E. Hamrin, and M. Unosson. \"Development of an instrument to
measure strategic and clinical quality indicators in postoperative pain
management.\" *Journal of Advanced Nursing.* 37, no. 6(2002): 532-40 UI
11879417.
Jackson, K., M. Ashby, and J. Keech. \"Pilot dose finding study of
intranasal sufentanil for breakthrough and incident cancer-associated
pain.\" *Journal of Pain & Symptom Management.* 23, no. 6(2002): 450-2
UI 12067765.
Jalal, S., K. Habib, and M. A. Rauoof. \"Prognostic significance of
rapid bedside cardiac troponin T testing in unstable angina.\" *Indian
Heart Journal.* 54, no. 2(2002): 220 UI 12086394.
Janken, J. K., and M. A. Dufault. \"Improving the quality of pain
assessment through research utilization.\" *Online Journal of Knowledge
Synthesis for Nursing.* 9(2002): 2C UI 12089637.
Katz, W. A. \"Cyclooxygenase-2-selective inhibitors in the management of
acute and perioperative pain.\" *Cleveland Clinic Journal of Medicine.*
69, no. Suppl 1(2002): SI65-75 UI 12086297.
Keller, R. B., and M. G. Fehlings. \"Editorial.\" *Spine.* 27, no.
12(2002): 1373 UI 12065988.
Khot, U. N., and S. E. Nissen. \"Is CURE a cure for acute coronary
syndromes? Statistical versus clinical significance.\" *Journal of the
American College of Cardiology.* 40, no. 2(2002): 218-9 UI 12106922.
Kianifard, B., S. Price, and M. S. Whiteley. \"Clipping perforators
without dividing them could reduce postoperative pain and swelling
following subfascial endoscopic perforator surgery.\" *Annals of the
Royal College of Surgeons of England.* 84, no. 3(2002): 210-1 UI
12092881.
Kidd, B. L., and P. M. Richardson. \"How does neuropathophysiology
affect the signs and symptoms of spinal disease?\" *Best Practice &
Research in Clinical Rheumatology.* 16, no. 1(2002): 31-42 UI 11987930.
Kissin, I. \"Study design to demonstrate clinical value of preemptive
analgesia: is the commonly used approach valid? \[letter; comment.\].\"
*Regional Anesthesia & Pain Medicine.* 27, no. 3(2002): 242-4 UI
12016595.
Koenig, H. G. \"An 83-year-old woman with chronic illness and strong
religious beliefs.\" *Jama.* 288, no. 4(2002): 487-93 UI 12132980.
Kovach, C. R., et al. \"The assessment of discomfort in dementia
protocol.\" *Pain Management Nursing.* 3, no. 1(2002): 16-27 UI
11893998.
Lee, D. S., et al. \"Randomized comparison of T-type versus L-type
calcium-channel blockade on exercise duration in stable angina: results
of the Posicor Reduction of Ischemia During Exercise (PRIDE) trial.\"
*American Heart Journal.* 144, no. 1(2002): 60-7 UI 12094189.
Leffler, A. S., P. Hansson, and E. Kosek. \"Somatosensory perception in
a remote pain-free area and function of diffuse noxious inhibitory
controls (DNIC) in patients suffering from long-term trapezius
myalgia.\" *European Journal of Pain:Ejp.* 6, no. 2(2002): 149-59 UI
11900475.
Leffler, A. S., et al. \"Somatosensory perception and function of
diffuse noxious inhibitory controls (DNIC) in patients suffering from
rheumatoid arthritis.\" *European Journal of Pain:Ejp.* 6, no. 2(2002):
161-76 UI 11900476.
Lema, M. J. \"Emerging options with coxib therapy.\" *Cleveland Clinic
Journal of Medicine.* 69, no. Suppl 1(2002): SI76-84 UI 12086298.
Lentz, G. M., et al. \"Hormonal manipulation in women with chronic,
cyclic irritable bladder symptoms and pelvic pain.\" *American Journal
of Obstetrics & Gynecology.* 186, no. 6(2002): 1268-71; discussion
1271-3 UI 12066108.
Lipley, N. \"Painful lessons.\" *Emergency Nurse.* 10, no. 1(2002): 5 UI
12001524.
Littrell, K. A., and K. B. Kern. \"Acute ischemic syndromes. Adjunctive
therapy.\" *Cardiology Clinics.* 20, no. 1(2002): 159-75, ix-x UI
11845542.
Lively, M. W. \"Sports medicine approach to low back pain.\" *Southern
Medical Journal.* 95, no. 6(2002): 642-6 UI 12081221.
Lordon, S. P. \"Interventional approach to cancer pain.\" *Current Pain
& Headache Reports.* 6, no. 3(2002): 202-6 UI 12003691.
Lucas, L. K., and A. G. Lipman. \"Recent advances in pharmacotherapy for
cancer pain management.\" *Cancer Practice.* 10, no. Suppl 1(2002):
S14-20 UI 12027964.
Lynch, M., and J. Abrahm. \"Ensuring a good death.\" *Cancer Practice.*
10, no. Suppl 1(2002): S33-8 UI 12027967.
Lyne, M. E., P. J. Coyne, and A. C. Watson. \"Pain management issues for
cancer survivors.\" *Cancer Practice.* 10, no. Suppl 1(2002): S27-32 UI
12027966.
Mackool, R. J. \"Bandage contact lens after LASIK.\" *Journal of
Cataract & Refractive Surgery.* 28, no. 6(2002): 911-2 UI 12036614.
Mannix, L. K., M. Diamond, and E. Loder. \"Women and headache: a
treatment approach based on life stages.\" *Cleveland Clinic Journal of
Medicine.* 69, no. 6(2002): 488-500 UI 12061464.
Mantyselka, P. T., et al. \"Direct and indirect costs of managing
patients with musculoskeletal pain-challenge for health care.\"
*European Journal of Pain:Ejp.* 6, no. 2(2002): 141-8 UI 11900474.
Martin, R. M., et al. \"Mortality and morbidity surrounding coronary
artery bypass surgery and the public presentation of risk.\" *Journal of
Epidemiology & Community Health.* 56, no. 6(2002): 430-1 UI 12011197.
Mazanec, P., and J. Bartel. \"Family caregiver perspectives of pain
management.\" *Cancer Practice.* 10, no. Suppl 1(2002): S66-9 UI
12027972.
McCrory, C. R., and S. G. Lindahl. \"Cyclooxygenase inhibition for
postoperative analgesia.\" *Anesthesia & Analgesia.* 95, no. 1(2002):
169-76 UI 12088963.
McPartland, J. M. \"Use of capsaicin cream for abdominal wall scar
pain.\" *American Family Physician.* 65, no. 11(2002): 2211; discussion
2212 UI 12074521.
Mercadante, S., et al. \"Rapid titration with intravenous morphine for
severe cancer pain and immediate oral conversion.\" *Cancer.* 95, no.
1(2002): 203-8 UI 12115334.
Miaskowski, C. \"Two landmark achievements.\" *Pain Management Nursing.*
3, no. 1(2002): 1 UI 11893996.
Michalek, P., and D. Kautznerova. \"Combined use of ultrasonography and
neurostimulation for therapeutic phrenic nerve block.\" *Regional
Anesthesia & Pain Medicine.* 27, no. 3(2002): 306-8 UI 12016605.
Mitka, M. \"Colon and rectal surgeons are trying Botox treatment, too.\"
*Jama.* 288, no. 4(2002): 439-40 UI 12132956.
Montgomery, J., and A. D. Donovan. \"Postoperative pain relief in the
day surgery unit.\" *Anaesthesia.* 57, no. 7(2002): 727-8 UI 12109433.
Moss, A. H. \"Update on pain management in West Virginia: new
legislation encourages control of dying patients\' pain.\" *West
Virginia Medical Journal.* 98, no. 3(2002): 100-3 UI 12099094.
Myers, J., et al. \"Do transmyocardial and percutaneous laser
revascularization induce silent ischemia? An assessment by exercise
testing.\" *American Heart Journal.* 143, no. 6(2002): 1052-7 UI
12075263.
Ness, T. J., L. Jones, and H. Smith. \"Use of compounded topical
analgesics\--results of an Internet survey.\" *Regional Anesthesia &
Pain Medicine.* 27, no. 3(2002): 309-12 UI 12016606.
Nordin, M., et al. \"Self-care techniques for acute episodes of low back
pain.\" *Best Practice & Research in Clinical Rheumatology.* 16, no.
1(2002): 89-104 UI 11987933.
O\'Kane, C., and T. E. Kilmartin. \"The surgical management of central
metatarsalgia.\" *Foot & Ankle International.* 23, no. 5(2002): 415-9 UI
12043986.
Orgill, R., G. A. Krempl, and J. E. Medina. \"Acute pain management
following laryngectomy.\" *Archives of Otolaryngology \-- Head & Neck
Surgery.* 128, no. 7(2002): 829-32 UI 12117345.
Otis-Green, S., et al. \"An integrated psychosocial-spiritual model for
cancer pain management.\" *Cancer Practice.* 10, no. Suppl 1(2002):
S58-65 UI 12027971.
Palangio, M., et al. \"Combination hydrocodone and ibuprofen versus
combination oxycodone and acetaminophen in the treatment of moderate or
severe acute low back pain.\" *Clinical Therapeutics.* 24, no. 1(2002):
87-99 UI 11833838.
Patberg, W. R. \"Beneficial effect of being outdoors in rheumatoid
arthritis.\" *Journal of Rheumatology.* 29, no. 1(2002): 202-4 UI
11824963.
Pattany, P. M., et al. \"Proton magnetic resonance spectroscopy of the
thalamus in patients with chronic neuropathic pain after spinal cord
injury.\" *Ajnr: American Journal of Neuroradiology.* 23, no. 6(2002):
901-5 UI 12063213.
Patterson, C. H. \"Unravel pain standards for higher compliance.\"
*Nursing Management (Springhouse).* 33, no. 3(2002): 20-1 UI 11923976.
Pelham, A., M. A. Lee, and C. B. Regnard. \"Gabapentin for coeliac
plexus pain.\" *Palliative Medicine.* 16, no. 4(2002): 355-6 UI
12132549.
Pellino, T. A., et al. \"The American Society of Pain Management Nurses
practice analysis: role delineation study.\" *Pain Management Nursing.*
3, no. 1(2002): 2-15 UI 11893997.
Persons, A. G. S. P. o. P. P. i. O. \"The management of persistent pain
in older persons.\" *Journal of the American Geriatrics Society.* 50,
no. 6 Suppl(2002): S205-24 UI 12067390.
Phillips, B. B., J. D. Joss, and P. L. Mulhausen. \"Blood pressure
elevation in a patient treated with salsalate.\" *Annals of
Pharmacotherapy.* 36, no. 4(2002): 624-7 UI 11918510.
Pinnock, D. \"Effective services for the care of patients with back
pain.\" *Professional Nurse.* 17, no. 7(2002): 422-4 UI 11917432.
Potter, P. J. \"Neck pain.\" *CMAJ: Canadian Medical Association
Journal.* 166, no. 1(2002): 16 UI 11800240.
Pulec, J. L. \"Geniculate neuralgia: long-term results of surgical
treatment.\" *Ear, Nose, & Throat Journal.* 81, no. 1(2002): 30-3 UI
11816385.
Raff, G. L., and W. W. O\'Neill. \"Interventional therapy of the acute
coronary syndromes.\" *Progress in Cardiovascular Diseases.* 44, no.
6(2002): 455-68 UI 12077719.
Rasmussen, S., et al. \"Combined intra-articular glucocorticoid,
bupivacaine and morphine reduces pain and convalescence after diagnostic
knee arthroscopy.\" *Acta Orthopaedica Scandinavica.* 73, no. 2(2002):
175-8 UI 12079015.
Raspe, H. \"How epidemiology contributes to the management of spinal
disorders.\" *Best Practice & Research in Clinical Rheumatology.* 16,
no. 1(2002): 9-21 UI 11987928.
Ratka, A. \"The role of a pharmacist in ambulatory cancer pain
management.\" *Current Pain & Headache Reports.* 6, no. 3(2002): 191-6
UI 12003689.
Reuben, S. S., and J. Sklar. \"Preemptive multimodal analgesia for
anterior cruciate ligament surgery.\" *Regional Anesthesia & Pain
Medicine.* 27, no. 2(2002): 225; discussion 225-6 UI 11915075.
Rocca, P. V. \"From physician to inmate.\" *Delaware Medical Journal.*
74, no. 5(2002): 245-6 UI 12063835.
Rokos, I. \"Indications for appropriate platelet glycoprotein IIb/IIIa
inhibitor therapy.\" *Annals of Emergency Medicine.* 39, no. 4(2002):
457-8; discussion 458-9 UI 11919540.
Ronner, E., et al. \"Early angioplasty in acute coronary syndromes
without persistent ST-segment elevation improves outcome but increases
the need for six-month repeat revascularization: an analysis of the
PURSUIT Trial. Platelet glycoprotein IIB/IIIA in Unstable angina:
Receptor Suppression Using Integrilin Therapy.\" *Journal of the
American College of Cardiology.* 39, no. 12(2002): 1924-9 UI 12084589.
Rosenow, D. E. \"Does neural blockade and other neurosurgical modalities
offer a durable pain relief for spinal disorders?\" *Best Practice &
Research in Clinical Rheumatology.* 16, no. 1(2002): 155-64 UI 11987937.
Rosenquist, R. W. \"Gabapentin.\" *Journal of the American Academy of
Orthopaedic Surgeons.* 10, no. 3(2002): 153-6 UI 12041936.
Sabatier, R., et al. \"Could direct stenting reduce no-reflow in acute
coronary syndromes? A randomized pilot study.\" *American Heart
Journal.* 143, no. 6(2002): 1027-32 UI 12075259.
Scheel, A. K., et al. \"Assessment of proximal finger joint inflammation
in patients with rheumatoid arthritis, using a novel laser-based imaging
technique.\" *Arthritis & Rheumatism.* 46, no. 5(2002): 1177-84 UI
12115221.
Schumacher, K. L., et al. \"Pain management autobiographies and
reluctance to use opioids for cancer pain management.\" *Cancer
Nursing.* 25, no. 2(2002): 125-33 UI 11984100.
Selim, N. A., and H. T. Hmouda. \"A pilot study of cardiac troponin I in
patients with acute myocardial infarction and unstable angina.\" *Saudi
Medical Journal.* 23, no. 5(2002): 526-8 UI 12070573.
Shah, S. G., et al. \"Effect of magnetic endoscope imaging on patient
tolerance and sedation requirements during colonoscopy: a randomized
controlled trial.\" *Gastrointestinal Endoscopy.* 55, no. 7(2002): 832-7
UI 12024136.
Smith, L. \"Chronic pain and its management in primary care.\" *Southern
Medical Journal.* 95, no. 1(2002): 108 UI 11827242.
Snook, S. H., B. S. Webster, and R. W. McGorry. \"The reduction of
chronic, nonspecific low back pain through the control of early morning
lumbar flexion: 3-year follow-up.\" *Journal of Occupational
Rehabilitation.* 12, no. 1(2002): 13-9 UI 11837055.
Stamou, S. C., et al. \"One-year outcome after combined coronary artery
bypass grafting and transmyocardial laser revascularization for
refractory angina pectoris.\" *American Journal of Cardiology.* 89, no.
12(2002): 1365-8 UI 12062729.
Stryer, D. B. \"The development and role of predictive instruments in
acute coronary events: improving diagnosis and management.\" *Journal of
Cardiovascular Nursing.* 16, no. 3(2002): 1-8 UI 11958440.
Susman, J. \"The care of low back problems: less is more.\" *American
Family Physician.* 65, no. 11(2002): 2217-8 UI 12074523.
Thadani, U. \"Selective L-type, T-type, and nonspecific calcium-channel
blockers for stable angina pectoris.\" *American Heart Journal.* 144,
no. 1(2002): 8-10 UI 12094182.
Thomas, P. W., et al. \"In defence of paravertebral blockade.\" *BJA:
British Journal of Anaesthesia.* 88, no. 5(2002): 743; discussion 744 UI
12067025.
Thompson, C., and A. Tsiperfal. \"How may we evaluate and treat a
wide-complex tachycardia in a patient presenting with chest pain in the
emergency department?\" *Progress in Cardiovascular Nursing.* 17, no.
1(2002): 49-50 UI 11872982.
Thuile, C., and M. Walzl. \"Evaluation of electromagnetic fields in the
treatment of pain in patients with lumbar radiculopathy or the whiplash
syndrome.\" *Neurorehabilitation.* 17, no. 1(2002): 63-7 UI 12016348.
Viel, E. J., P. Cuvillon, and J. J. Eledjam. \"Opioid and local
anesthetic combination for brachial plexus block to provide
postoperative analgesia.\" *Regional Anesthesia & Pain Medicine.* 27,
no. 3(2002): 336 UI 12016621.
Walker, C. P., A. Gaunt, and N. C. Wall. \"In defence of paravertebral
blockade.\" *BJA: British Journal of Anaesthesia.* 88, no. 5(2002):
743-4; discussion 744 UI 12067024.
Warren, S. C., et al. \"Dying in a West Virginia acute care hospital:
what is it like?\" *West Virginia Medical Journal.* 98, no. 3(2002):
110-3 UI 12099097.
Watanabe, S., et al. \"Opioid rotation to methadone: proceed with
caution.\" *Journal of Clinical Oncology.* 20, no. 9(2002): 2409-10 UI
11981018.
Wenzel, R. G., and M. R. Neidich. \"Headache education in colleges of
pharmacy.\" *Annals of Pharmacotherapy.* 36, no. 4(2002): 612-6 UI
11918507.
Werner, M. U., B. Lassen, and H. Kehlet. \"Analgesic effects of
dexamethasone in burn injury.\" *Regional Anesthesia & Pain Medicine.*
27, no. 3(2002): 254-60 UI 12016598.
Wheeler, A. H., and D. B. Murrey. \"Chronic lumbar spine and radicular
pain: pathophysiology and treatment.\" *Current Pain & Headache
Reports.* 6, no. 2(2002): 97-105 UI 11872180.
Wu, L. A., et al. \"Prognostic value of the erythrocyte sedimentation
rate in patients with unstable angina.\" *Archives of Pathology &
Laboratory Medicine.* 126, no. 7(2002): 772 UI 12125644.
Wyatt, G. \"Complementary therapies.\" *Cancer Practice.* 10, no. Suppl
1(2002): S70-3 UI 12027973.
Yang, W., A. Wragg, and A. Timmis. \"Casebook: chest pain.\"
*Practitioner.* 246, no. 1635(2002): 385-9, 392, 395 passim UI 12073697.
Yoser, A. J., and R. S. Mito. \"Injury prevention for the practice of
dentistry.\" *Journal of the California Dental Association.* 30, no.
2(2002): 170-6 UI 11881961.
| en |
log-files | 773852 |
gnt_infrm: **********************************************
gnt_infrm: Running procedure do_proc on sequence 74033000
gnt_infrm: **********************************************
Fri Apr 28 04:42:33 EDT 2000
gnt_infrm: (do_proc) Root directory is /tproc/nandra/processing/
gnt_infrm: (do_proc) Deleting sequence 74033000...
gnt_infrm: (do_proc) Creating sequence 74033000...
gnt_infrm: *************************
gnt_infrm: Running procedure do_getf
gnt_infrm: *************************
Fri Apr 28 04:42:34 EDT 2000
gnt_infrm: Using rcp to copy aux/ files...
fa951216_0434.0250.gz
ft951216_0434_0250.mkf.gz
ft951216_0434_0250_mkfc.ps.gz
ft951216_0434_0250_mkfm.ps.gz
ft951216_0434_0250_mkfs.ps.gz
gnt_infrm: Copying screened/ files...
ad74033000g200170m.evt.gz
ad74033000g200270l.evt.gz
ad74033000g200370h.evt.gz
ad74033000g300170m.evt.gz
ad74033000g300270l.evt.gz
ad74033000g300370h.evt.gz
ad74033000s000102m.evt.gz
ad74033000s000112m.evt.gz
ad74033000s000202h.evt.gz
ad74033000s000212h.evt.gz
ad74033000s100102m.evt.gz
ad74033000s100112m.evt.gz
ad74033000s100202h.evt.gz
ad74033000s100212h.evt.gz
gnt_infrm: Copying unscreened/ files...
ad74033000g200170m.unf.gz
ad74033000g200270l.unf.gz
ad74033000g200370h.unf.gz
ad74033000g300170m.unf.gz
ad74033000g300270l.unf.gz
ad74033000g300370h.unf.gz
ad74033000s000101m.unf.gz
ad74033000s000102m.unf.gz
ad74033000s000112m.unf.gz
ad74033000s000201h.unf.gz
ad74033000s000202h.unf.gz
ad74033000s000212h.unf.gz
ad74033000s000301l.unf.gz
ad74033000s000302l.unf.gz
ad74033000s000312l.unf.gz
ad74033000s100101m.unf.gz
ad74033000s100102m.unf.gz
ad74033000s100112m.unf.gz
ad74033000s100201h.unf.gz
ad74033000s100202h.unf.gz
ad74033000s100212h.unf.gz
ad74033000s100301l.unf.gz
ad74033000s100302l.unf.gz
ad74033000s100312l.unf.gz
gnt_infrm: Unzipping all files...
gnt_infrm: Unzipped all files in /tproc/nandra/processing/74033000/unscreened.
gnt_infrm: Unzipped all files in /tproc/nandra/processing/74033000/screened.
gnt_infrm: Unzipped all files in /tproc/nandra/processing/74033000/aux.
gnt_infrm: Getting object name from attitude file...
gnt_infrm: ========================
gnt_infrm: End of procedure do_getf
gnt_infrm: ========================
Fri Apr 28 04:43:27 EDT 2000
gnt_infrm: (do_proc) Sequence directory is /tproc/nandra/processing/74033000.
gnt_infrm: *************************
gnt_infrm: Running procedure do_cats
gnt_infrm: *************************
Fri Apr 28 04:43:27 EDT 2000
** XSELECT V2.0 **
!> Enter session name >[xsel] cat
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!cat:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!cat > set datadir ../unscreened
Setting data directory to /tproc/nandra/processing/74033000/unscreened/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!cat > set DUMPCAT
Obscat listing off
!cat > set inst sis0
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
!cat:ASCA-SIS0 > set datamode BRIGHT
!cat:ASCA-SIS0-BRIGHT > make obscat cat_filt=DEF lststr='ad*s0*.unf'
''Using default selection expression: ONTIME>100&&NEVENTS>0&&COORDPRO!='ERROR'&&INSTRUME=='SIS0'&&DATAMODE=='BRIGHT'
!cat:ASCA-SIS0-BRIGHT > save obscat s0_bright.cat clobber=yes
!cat:ASCA-SIS0-BRIGHT > set datamode BRIGHT2
!cat:ASCA-SIS0-BRIGHT2 > make obscat cat_filt=DEF lststr='ad*s0*.unf'
''Using default selection expression: ONTIME>100&&NEVENTS>0&&COORDPRO!='ERROR'&&INSTRUME=='SIS0'&&DATAMODE=='BRIGHT2'
!cat:ASCA-SIS0-BRIGHT2 > save obscat s0_bright2.cat clobber=yes
!cat:ASCA-SIS0-BRIGHT2 > set inst sis1
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
!cat:ASCA-SIS1 > set datamode BRIGHT
!cat:ASCA-SIS1-BRIGHT > make obscat cat_filt=DEF lststr='ad*s1*.unf'
''Using default selection expression: ONTIME>100&&NEVENTS>0&&COORDPRO!='ERROR'&&INSTRUME=='SIS1'&&DATAMODE=='BRIGHT'
!cat:ASCA-SIS1-BRIGHT > save obscat s1_bright.cat clobber=yes
!cat:ASCA-SIS1-BRIGHT > set datamode BRIGHT2
!cat:ASCA-SIS1-BRIGHT2 > make obscat cat_filt=DEF lststr='ad*s1*.unf'
''Using default selection expression: ONTIME>100&&NEVENTS>0&&COORDPRO!='ERROR'&&INSTRUME=='SIS1'&&DATAMODE=='BRIGHT2'
!cat:ASCA-SIS1-BRIGHT2 > save obscat s1_bright2.cat clobber=yes
!cat:ASCA-SIS1-BRIGHT2 > set inst gis2
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
!cat:ASCA-GIS2 > make obscat cat_filt=DEF lststr='ad*g2*.unf'
''Using default selection expression: ONTIME>100&&NEVENTS>0&&HV_RED=='OFF'&&HVH_LVL==3&&HVL_LVL==4&&COORDPRO!='ERROR'&&INSTRUME=='GIS2'
!cat:ASCA-GIS2 > save obscat g2.cat clobber=yes
!cat:ASCA-GIS2 > set inst gis3
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
!cat:ASCA-GIS3 > make obscat cat_filt=DEF lststr='ad*g3*.unf'
''Using default selection expression: ONTIME>100&&NEVENTS>0&&HV_RED=='OFF'&&HVH_LVL==3&&HVL_LVL==4&&COORDPRO!='ERROR'&&INSTRUME=='GIS3'
!cat:ASCA-GIS3 > save obscat g3.cat clobber=yes
!cat:ASCA-GIS3 > exit save=no
gnt_infrm: Makefilter file is: /tproc/nandra/processing/74033000/aux/ft951216_0434_0250.mkf
gnt_infrm: Determining datamode...
gnt_infrm: Determining BR_EARTH angle...
rm: No match.
rm: No match.
gnt_infrm: ========================
gnt_infrm: End of procedure do_cats
gnt_infrm: ========================
Fri Apr 28 04:43:54 EDT 2000
gnt_infrm: (do_proc) The dominant datamode is: BRIGHT2.
gnt_infrm: (do_proc) The BR_EARTH angle is: 20.
gnt_infrm: *************************
gnt_infrm: Running procedure do_scrn
gnt_infrm: *************************
Fri Apr 28 04:43:54 EDT 2000
gnt_infrm: The datamode is BRIGHT2.
gnt_infrm: Determining the CCD mode...
CCD EXP_TIME
--------------------------
2 1.274496372342110E+02
2 4.645532351419330E+03
-------------------------------------
Exposure time in 1-CCD mode: 0
Exposure time in 2-CCD mode: 4772
Exposure time in 4-CCD mode: 0
-------------------------------------
gnt_infrm: Using 2-CCD mode.
****** ASCASCREEN V.0.51 ******
Applies standard clean criteria to all modes of ASCA data.
Output:
-- A single cleaned events file (.evt) except in MPC mode
-- An image for the entire detector (.img) except in FAST and MPC modes
-- The timing filters (.gti) in MPC mode
-- A lightcurve (.lc) and spectrum (.pha) in MPC mode.
-- The Dark Frame Error history file (.dfe) for FAINT mode.
-- A reduced obscat (.cat)
Try ascascreen -h for help.
Report problems to ascahelp@athena.gsfc.nasa.gov
A return will accept the default.
For character replies, the default is in upper case.
Okay, I'll only write the xco file
To use it, say:
xselect @output_root.xco
I will choose all the minor modes.
Okay, I will use the defaults.
Got data directory: /local/data/tproc/nandra/processing/74033000/unscreened
Got instrument SIS0
Got datamode BRIGHT2
Using HIGH bit rate data.
Using MEDIUM bit rate data.
Using LOW bit rate data.
Analysing files for your chosen mode, please wait.
Using 0.01 for Maximum allowed angular deviation
Using 30 for Bright Earth Angle
Using 10 for minimum elevation
Using 6 for minimum cutoff rigidity
Using 275 for Radiation Belt Monitor upper-threshold
Using 75 for SIS Pixel rejection upper-threshold for chips 01 .
I will start up SAOImage, and leave you in Xselect at the end
Writing command file 74033000_sis0.xco
Index NEVENTS ONTIME S0CCDMOD S0CCDLST S0_ARENA
0 261610 53787.4 2 0101 0
Removing Hot and Flickering Pixels.
Performing Grade selection ( keeping 0,2,3, and 4 ).
Command file written, goodbye
****** ASCASCREEN V.0.51 ******
Applies standard clean criteria to all modes of ASCA data.
Output:
-- A single cleaned events file (.evt) except in MPC mode
-- An image for the entire detector (.img) except in FAST and MPC modes
-- The timing filters (.gti) in MPC mode
-- A lightcurve (.lc) and spectrum (.pha) in MPC mode.
-- The Dark Frame Error history file (.dfe) for FAINT mode.
-- A reduced obscat (.cat)
Try ascascreen -h for help.
Report problems to ascahelp@athena.gsfc.nasa.gov
A return will accept the default.
For character replies, the default is in upper case.
Okay, I'll only write the xco file
To use it, say:
xselect @output_root.xco
I will choose all the minor modes.
Okay, I will use the defaults.
Got data directory: /local/data/tproc/nandra/processing/74033000/unscreened
Got instrument SIS1
Got datamode BRIGHT2
Using HIGH bit rate data.
Using MEDIUM bit rate data.
Using LOW bit rate data.
Analysing files for your chosen mode, please wait.
Using 0.01 for Maximum allowed angular deviation
Using 20 for Bright Earth Angle
Using 10 for minimum elevation
Using 6 for minimum cutoff rigidity
Using 275 for Radiation Belt Monitor upper-threshold
Using 75 for SIS Pixel rejection upper-threshold for chips 23 .
I will start up SAOImage, and leave you in Xselect at the end
Writing command file 74033000_sis1.xco
Index NEVENTS ONTIME S1CCDMOD S1CCDLST S1_ARENA
0 260106 53992 2 2323 0
Removing Hot and Flickering Pixels.
Performing Grade selection ( keeping 0,2,3, and 4 ).
Command file written, goodbye
****** ASCASCREEN V.0.51 ******
Applies standard clean criteria to all modes of ASCA data.
Output:
-- A single cleaned events file (.evt) except in MPC mode
-- An image for the entire detector (.img) except in FAST and MPC modes
-- The timing filters (.gti) in MPC mode
-- A lightcurve (.lc) and spectrum (.pha) in MPC mode.
-- The Dark Frame Error history file (.dfe) for FAINT mode.
-- A reduced obscat (.cat)
Try ascascreen -h for help.
Report problems to ascahelp@athena.gsfc.nasa.gov
A return will accept the default.
For character replies, the default is in upper case.
Okay, I'll only write the xco file
To use it, say:
xselect @output_root.xco
I will choose all the minor modes.
Okay, I will use the defaults.
Got data directory: /local/data/tproc/nandra/processing/74033000/unscreened
Got instrument GIS2
Got datamode PH
Using HIGH bit rate data.
Using MEDIUM bit rate data.
Using LOW bit rate data.
Analysing files for your chosen mode, please wait.
Using 0.01 for Maximum allowed angular deviation
Using 5 for minimum elevation
Using standard GIS particle BGD rejection criterion
I will start up SAOImage, and leave you in Xselect at the end
Removing ring and calibration sources
Using the region:
CIRCLE(128.50,128.50,88.00)
-ELLIPSE(167.50,220.00,24.66,28.95,245.298)
Writing command file 74033000_gis2.xco
Index NEVENTS ONTIME RAWXBINS RISEBINS TIMEBINS PHA_BINS POS_DET
0 44270 49901.9 256 32 1 1024 FLF
Using Rise Time window bkgd. rejection
Command file written, goodbye
****** ASCASCREEN V.0.51 ******
Applies standard clean criteria to all modes of ASCA data.
Output:
-- A single cleaned events file (.evt) except in MPC mode
-- An image for the entire detector (.img) except in FAST and MPC modes
-- The timing filters (.gti) in MPC mode
-- A lightcurve (.lc) and spectrum (.pha) in MPC mode.
-- The Dark Frame Error history file (.dfe) for FAINT mode.
-- A reduced obscat (.cat)
Try ascascreen -h for help.
Report problems to ascahelp@athena.gsfc.nasa.gov
A return will accept the default.
For character replies, the default is in upper case.
Okay, I'll only write the xco file
To use it, say:
xselect @output_root.xco
I will choose all the minor modes.
Okay, I will use the defaults.
Got data directory: /local/data/tproc/nandra/processing/74033000/unscreened
Got instrument GIS3
Got datamode PH
Using HIGH bit rate data.
Using MEDIUM bit rate data.
Using LOW bit rate data.
Analysing files for your chosen mode, please wait.
Using 0.01 for Maximum allowed angular deviation
Using 5 for minimum elevation
Using standard GIS particle BGD rejection criterion
I will start up SAOImage, and leave you in Xselect at the end
Removing ring and calibration sources
CIRCLE(128.50,128.50,88.00)
-ELLIPSE(217,95,21.56,25.92,169.216)
Writing command file 74033000_gis3.xco
Index NEVENTS ONTIME RAWXBINS RISEBINS TIMEBINS PHA_BINS POS_DET
0 43462 51579.8 256 32 1 1024 FLF
Using Rise Time window bkgd. rejection
Using the region:
Command file written, goodbye
Running extractions
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000s000112m.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
189582 146264 0 43318 0 0
Writing events file
146264 events written to the output file
No events selected from file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000s000312l.unf
Writing events file
146264 events written to the output file
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000s000212h.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
57196 34388 0 22808 0 0
Writing events file
180652 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
246778 180652 0 66126 0 0
in 32032. seconds
CLEANSIS_V1.6
allocating image arrays...
PROGRAM TO MAKE AN SIS SCIENCE FILE CLEANED OF ANOMALOUS PIXELS.
* Anomalous pixels may consist of at least two populations.
1. Persistent HOT pixels are removed by comparing to the chip mean.
2. Flickering WARM pixels are removed by comparing to the cell mean.
3. In faint areas (zero bgd), flickering pixels are removed with a
cutoff threshold.
Hints:
Choose cell size and thresholds based on the expected background and the PSF.
Use the DIRTYSIS option to examine the anomalous pixel spectra.
Try a multiple pass clean:
Choose a PHA cut to optimize the S/N of the flickering pixels,
then a broad band clean.
Be suspicious of extended source cleans.
For very bright sources you may need to turn off the iteration option.
See the help page for further info (fhelp cleansis)
Poisson clean cell size : 5
Poisson probability threshold : 0.631E-05
Zero Bgd Cutoff threshold (>) : 3
Iterate : T
Dirtysis : F
Minimum PHA value (inclusive) : 0
Maximum PHA value (inclusive) : 4095
open output file: /local/data/tproc/nandra/processing/74033000/work/ascascr
reading data file: /local/data/tproc/nandra/processing/74033000/work/ascascr
copying primary header to output file...
making chip image...
Total counts in chip images : 180652
copy bad pix array...
cleaning chip # 0
Hot pixels & counts : 50 111988
Flickering pixels iter, pixels & cnts : 1 36 1674
cleaning chip # 1
Hot pixels & counts : 28 60872
Flickering pixels iter, pixels & cnts : 1 15 415
cleaning chip # 2
cleaning chip # 3
Number of pixels rejected : 129
Number of (internal) image counts : 180652
Number of image cts rejected (N, %) : 17494996.84
By chip : 0 1 2 3
Pixels rejected : 86 43 0 0
Image counts : 116670 63982 0 0
Image cts rejected: 113662 61287 0 0
Image cts rej (%) : 97.42 95.79 0.00 0.00
filtering data...
Total counts : 116670 63982 0 0
Total cts rejected: 113662 61287 0 0
Total cts rej (%) : 97.42 95.79 0.00 0.00
Number of clean counts accepted : 5703
writing history cards...
copying extensions...
writing out hot pixs...
Number of rejected pixels : 129
updating NEVENTS keywords...
closing data file...
closing clean file...
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: ascascreen_sis0_in_event.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
4049 4049 0 0 0 0
Writing events file
4049 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
4049 4049 0 0 0 0
in 32032. seconds
Image has 4049 counts for 0.1264 counts/sec
** XSELECT V2.0 **
!> Enter session name >[xsel] ascascreen_sis0
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!ascascreen_sis0:ASCA > set mission ASCA
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
!ascascreen_sis0:ASCA > set instru SIS0
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
!ascascreen_sis0:ASCA-SIS0 > set datadir /local/data/tproc/nandra/processing/74033000/unscreened
Setting data directory to /local/data/tproc/nandra/processing/74033000/unscreened/
Setting mkf directory to /local/data/tproc/nandra/processing/74033000/aux/
!ascascreen_sis0:ASCA-SIS0 > set dumpcat
Obscat listing off
!ascascreen_sis0:ASCA-SIS0 > set datamode BRIGHT2
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > make obscat cat_filt=@74033000_sis0_obscat.sel lststr = '[af][dt]*[Ss]0*[HhMmLl].unf'
''!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > choose 1-** switch=yes
Setting datamode to BRIGHT2
Got the minimum time resolution of the chosen data: 0.80000E+01,
Getting Min and Max for Energy Column...
Got min and max for PI: 0 4095
Number of files read in: 3
Files currently in use:
1 ad74033000s000112m.unf
2 ad74033000s000312l.unf
3 ad74033000s000212h.unf
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > set image detector
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > select mkf @74033000_sis0_mkf.sel
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > extract events
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > sisclean clean=2 cellsize=5 log_prob=-5.24 bkg_thr=3 clean_phalow=0 clean_phahi =4095 sis_plot2=no saoimage2=no
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > select events "grade==0||(grade>=2&&grade<=4)" save_file=no
The select output will overwrite the cleaned event list
if you have not saved it already.
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > extract "event image"
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > save obscat 74033000_sis0 clobberit = yes
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > $rm -f ascascreen_sis0*.cat 74033000_sis0_list.tmp 74033000_sis0_obscat.lis
Spawning...
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > save all 74033000_sis0 clobberit=yes use_events=yes
Saving the Image:
Wrote image to file 74033000_sis0.img
Saving the Cleaned events list(s):
Wrote cleaned events file to 74033000_sis0.evt
Changing Data directory from:
/local/data/tproc/nandra/processing/74033000/unscreened/
to the current working directory.
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > clear mkf
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > set dumpcat
Obscat listing on
!ascascreen_sis0:ASCA-SIS0-BRIGHT2 > exit save=no
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000s100112m.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
197854 148912 0 48942 0 0
Writing events file
148912 events written to the output file
No events selected from file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000s100312l.unf
Writing events file
148912 events written to the output file
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000s100212h.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
47064 26499 0 20565 0 0
Writing events file
175411 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
244918 175411 0 69507 0 0
in 31156. seconds
CLEANSIS_V1.6
allocating image arrays...
PROGRAM TO MAKE AN SIS SCIENCE FILE CLEANED OF ANOMALOUS PIXELS.
* Anomalous pixels may consist of at least two populations.
1. Persistent HOT pixels are removed by comparing to the chip mean.
2. Flickering WARM pixels are removed by comparing to the cell mean.
3. In faint areas (zero bgd), flickering pixels are removed with a
cutoff threshold.
Hints:
Choose cell size and thresholds based on the expected background and the PSF.
Use the DIRTYSIS option to examine the anomalous pixel spectra.
Try a multiple pass clean:
Choose a PHA cut to optimize the S/N of the flickering pixels,
then a broad band clean.
Be suspicious of extended source cleans.
For very bright sources you may need to turn off the iteration option.
See the help page for further info (fhelp cleansis)
Poisson clean cell size : 5
Poisson probability threshold : 0.631E-05
Zero Bgd Cutoff threshold (>) : 3
Iterate : T
Dirtysis : F
Minimum PHA value (inclusive) : 0
Maximum PHA value (inclusive) : 4095
open output file: /local/data/tproc/nandra/processing/74033000/work/ascascr
reading data file: /local/data/tproc/nandra/processing/74033000/work/ascascr
copying primary header to output file...
making chip image...
Total counts in chip images : 175411
copy bad pix array...
cleaning chip # 0
cleaning chip # 1
cleaning chip # 2
Hot pixels & counts : 38 91258
Flickering pixels iter, pixels & cnts : 1 29 1684
cleaning chip # 3
Hot pixels & counts : 36 76346
Flickering pixels iter, pixels & cnts : 1 19 619
Number of pixels rejected : 122
Number of (internal) image counts : 175411
Number of image cts rejected (N, %) : 16990796.86
By chip : 0 1 2 3
Pixels rejected : 0 0 67 55
Image counts : 0 0 96194 79217
Image cts rejected: 0 0 92942 76965
Image cts rej (%) : 0.00 0.00 96.62 97.16
filtering data...
Total counts : 0 0 96194 79217
Total cts rejected: 0 0 92942 76965
Total cts rej (%) : 0.00 0.00 96.62 97.16
Number of clean counts accepted : 5504
writing history cards...
copying extensions...
writing out hot pixs...
Number of rejected pixels : 122
updating NEVENTS keywords...
closing data file...
closing clean file...
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: ascascreen_sis1_in_event.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
4029 4029 0 0 0 0
Writing events file
4029 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
4029 4029 0 0 0 0
in 31156. seconds
Image has 4029 counts for 0.1293 counts/sec
** XSELECT V2.0 **
!> Enter session name >[xsel] ascascreen_sis1
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!ascascreen_sis1:ASCA > set mission ASCA
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
!ascascreen_sis1:ASCA > set instru SIS1
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
!ascascreen_sis1:ASCA-SIS1 > set datadir /local/data/tproc/nandra/processing/74033000/unscreened
Setting data directory to /local/data/tproc/nandra/processing/74033000/unscreened/
Setting mkf directory to /local/data/tproc/nandra/processing/74033000/aux/
!ascascreen_sis1:ASCA-SIS1 > set dumpcat
Obscat listing off
!ascascreen_sis1:ASCA-SIS1 > set datamode BRIGHT2
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > make obscat cat_filt=@74033000_sis1_obscat.sel lststr = '[af][dt]*[Ss]1*[HhMmLl].unf'
''!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > choose 1-** switch=yes
Setting datamode to BRIGHT2
Got the minimum time resolution of the chosen data: 0.80000E+01,
Getting Min and Max for Energy Column...
Got min and max for PI: 0 4095
Number of files read in: 3
Files currently in use:
1 ad74033000s100112m.unf
2 ad74033000s100312l.unf
3 ad74033000s100212h.unf
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > set image detector
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > select mkf @74033000_sis1_mkf.sel
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > extract events
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > sisclean clean=2 cellsize=5 log_prob=-5.24 bkg_thr=3 clean_phalow=0 clean_phahi =4095 sis_plot2=no saoimage2=no
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > select events "grade==0||(grade>=2&&grade<=4)" save_file=no
The select output will overwrite the cleaned event list
if you have not saved it already.
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > extract "event image"
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > save obscat 74033000_sis1 clobberit = yes
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > $rm -f ascascreen_sis1*.cat 74033000_sis1_list.tmp 74033000_sis1_obscat.lis
Spawning...
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > save all 74033000_sis1 clobberit=yes use_events=yes
Saving the Image:
Wrote image to file 74033000_sis1.img
Saving the Cleaned events list(s):
Wrote cleaned events file to 74033000_sis1.evt
Changing Data directory from:
/local/data/tproc/nandra/processing/74033000/unscreened/
to the current working directory.
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > clear mkf
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > set dumpcat
Obscat listing on
!ascascreen_sis1:ASCA-SIS1-BRIGHT2 > exit save=no
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000g200170m.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
29600 10252 17934 1414 0 0
Writing events file
10252 events written to the output file
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000g200270l.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
9255 10 6063 3182 0 0
Writing events file
10262 events written to the output file
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000g200370h.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
5415 1662 3330 423 0 0
Writing events file
11924 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
44270 11924 27327 5019 0 0
in 34380. seconds
Infile # of rows Outfile # of rows # filtered
---------------- ----------------- ----------
11924 10537 1387
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: ascascreen_gis2_in_event.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 10537 0 0 0 0
Writing events file
10537 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 10537 0 0 0 0
in 34380. seconds
Image has 10537 counts for 0.3065 counts/sec
** XSELECT V2.0 **
!> Enter session name >[xsel] ascascreen_gis2
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!ascascreen_gis2:ASCA > set mission ASCA
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
!ascascreen_gis2:ASCA > set instru GIS2
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
!ascascreen_gis2:ASCA-GIS2 > set datadir /local/data/tproc/nandra/processing/74033000/unscreened
Setting data directory to /local/data/tproc/nandra/processing/74033000/unscreened/
Setting mkf directory to /local/data/tproc/nandra/processing/74033000/aux/
!ascascreen_gis2:ASCA-GIS2 > set dumpcat
Obscat listing off
!ascascreen_gis2:ASCA-GIS2 > set datamode PH
!ascascreen_gis2:ASCA-GIS2-PH > make obscat cat_filt=@74033000_gis2_obscat.sel lststr = '[af][dt]*[Gg]2*[HhMmLl].unf'
''!ascascreen_gis2:ASCA-GIS2-PH > choose 1-** switch=yes
Setting datamode to PH
Got the minimum time resolution of the chosen data: 0.20000E+01,
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Number of files read in: 3
Files currently in use:
1 ad74033000g200170m.unf
2 ad74033000g200270l.unf
3 ad74033000g200370h.unf
!ascascreen_gis2:ASCA-GIS2-PH > set image detector
!ascascreen_gis2:ASCA-GIS2-PH > select mkf @74033000_gis2_mkf.sel
!ascascreen_gis2:ASCA-GIS2-PH > filter region 74033000_gis2_randc.reg
!ascascreen_gis2:ASCA-GIS2-PH > extract events
!ascascreen_gis2:ASCA-GIS2-PH > gisclean
Using table:/software/lheasoft/develop/refdata/rti_gis_1024_040693.fits
!ascascreen_gis2:ASCA-GIS2-PH > extract "event image"
!ascascreen_gis2:ASCA-GIS2-PH > save obscat 74033000_gis2 clobberit = yes
!ascascreen_gis2:ASCA-GIS2-PH > $rm -f ascascreen_gis2*.cat 74033000_gis2_list.tmp 74033000_gis2_obscat.lis
Spawning...
!ascascreen_gis2:ASCA-GIS2-PH > save all 74033000_gis2 clobberit=yes use_events=yes
Saving the Image:
Wrote image to file 74033000_gis2.img
Saving the Filtered Events list:
Wrote events list to file 74033000_gis2.evt
Changing Data directory from:
/local/data/tproc/nandra/processing/74033000/unscreened/
to the current working directory.
!ascascreen_gis2:ASCA-GIS2-PH > clear mkf
!ascascreen_gis2:ASCA-GIS2-PH > clear region all
!ascascreen_gis2:ASCA-GIS2-PH > set dumpcat
Obscat listing on
!ascascreen_gis2:ASCA-GIS2-PH > exit save=no
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000g300170m.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
28240 11242 15370 1628 0 0
Writing events file
11242 events written to the output file
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000g300270l.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
8727 12 5215 3500 0 0
Writing events file
11254 events written to the output file
Doing file: /local/data/tproc/nandra/processing/74033000/unscreened/ad74033000g300370h.unf
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
6495 2377 3520 598 0 0
Writing events file
13631 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
43462 13631 24105 5726 0 0
in 35470. seconds
Infile # of rows Outfile # of rows # filtered
---------------- ----------------- ----------
13631 12127 1504
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: ascascreen_gis3_in_event.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 12127 0 0 0 0
Writing events file
12127 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 12127 0 0 0 0
in 35470. seconds
Image has 12127 counts for 0.3419 counts/sec
** XSELECT V2.0 **
!> Enter session name >[xsel] ascascreen_gis3
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!ascascreen_gis3:ASCA > set mission ASCA
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
!ascascreen_gis3:ASCA > set instru GIS3
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
!ascascreen_gis3:ASCA-GIS3 > set datadir /local/data/tproc/nandra/processing/74033000/unscreened
Setting data directory to /local/data/tproc/nandra/processing/74033000/unscreened/
Setting mkf directory to /local/data/tproc/nandra/processing/74033000/aux/
!ascascreen_gis3:ASCA-GIS3 > set dumpcat
Obscat listing off
!ascascreen_gis3:ASCA-GIS3 > set datamode PH
!ascascreen_gis3:ASCA-GIS3-PH > make obscat cat_filt=@74033000_gis3_obscat.sel lststr = '[af][dt]*[Gg]3*[HhMmLl].unf'
''!ascascreen_gis3:ASCA-GIS3-PH > choose 1-** switch=yes
Setting datamode to PH
Got the minimum time resolution of the chosen data: 0.20000E+01,
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Number of files read in: 3
Files currently in use:
1 ad74033000g300170m.unf
2 ad74033000g300270l.unf
3 ad74033000g300370h.unf
!ascascreen_gis3:ASCA-GIS3-PH > set image detector
!ascascreen_gis3:ASCA-GIS3-PH > select mkf @74033000_gis3_mkf.sel
!ascascreen_gis3:ASCA-GIS3-PH > filter region 74033000_gis3_randc.reg
!ascascreen_gis3:ASCA-GIS3-PH > extract events
!ascascreen_gis3:ASCA-GIS3-PH > gisclean
Using table:/software/lheasoft/develop/refdata/rti_gis_1024_040693.fits
!ascascreen_gis3:ASCA-GIS3-PH > extract "event image"
!ascascreen_gis3:ASCA-GIS3-PH > save obscat 74033000_gis3 clobberit = yes
!ascascreen_gis3:ASCA-GIS3-PH > $rm -f ascascreen_gis3*.cat 74033000_gis3_list.tmp 74033000_gis3_obscat.lis
Spawning...
!ascascreen_gis3:ASCA-GIS3-PH > save all 74033000_gis3 clobberit=yes use_events=yes
Saving the Image:
Wrote image to file 74033000_gis3.img
Saving the Filtered Events list:
Wrote events list to file 74033000_gis3.evt
Changing Data directory from:
/local/data/tproc/nandra/processing/74033000/unscreened/
to the current working directory.
!ascascreen_gis3:ASCA-GIS3-PH > clear mkf
!ascascreen_gis3:ASCA-GIS3-PH > clear region all
!ascascreen_gis3:ASCA-GIS3-PH > set dumpcat
Obscat listing on
!ascascreen_gis3:ASCA-GIS3-PH > exit save=no
gnt_infrm: Checking for G3BITFIX problem...
gnt_infrm: ========================
gnt_infrm: End of procedure do_scrn
gnt_infrm: ========================
Fri Apr 28 04:45:19 EDT 2000
gnt_infrm: *************************
gnt_infrm: Running procedure do_cent
gnt_infrm: *************************
Fri Apr 28 04:45:19 EDT 2000
gnt_infrm: Getting RA and DEC from attitude file...
gnt_infrm: Getting OTIME from attitude file...
gnt_infrm: Checking permanent area...
gunzip: No match.
gnt_infrm: Files not in permanent area; performing centroiding...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS PHA_BINS
1 MRK507 PH MEDIUM 16/12/95 04:34:57 0.34E+05 10537 1024
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 566 9943 0 0 28
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 566 9943 0 0 28
in 34380. seconds
Spectrum has 566 counts for 1.6463E-02 counts/sec
... written the PHA data Extension
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 2710 7629 0 0 198
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 2710 7629 0 0 198
in 34380. seconds
Spectrum has 2710 counts for 7.8826E-02 counts/sec
... written the PHA data Extension
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_gis2.evt
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Got the minimum time resolution of the read data: 0.50000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-GIS2-PH > set binsize 128
!xsel:ASCA-GIS2-PH > set image sky
!xsel:ASCA-GIS2-PH > filter region gis2_src_reg.tmp
!xsel:ASCA-GIS2-PH > filter pha_cutoff 60 900
!xsel:ASCA-GIS2-PH > extract spectrum
!xsel:ASCA-GIS2-PH > save spectrum gis2_spec_src.tmp clobber=yes group=no
Wrote spectrum to gis2_spec_src.tmp
!xsel:ASCA-GIS2-PH > filter region gis2_bgd_reg.tmp
!xsel:ASCA-GIS2-PH > extract spectrum
!xsel:ASCA-GIS2-PH > save spectrum gis2_spec_bgd.tmp clobber=yes group=no
Wrote spectrum to gis2_spec_bgd.tmp
!xsel:ASCA-GIS2-PH > exit save=no
****** statistics for /tproc/nandra/processing/74033000/work/gis2_spec_src.tmp ******
The sum of the selected image = 560.000000
The mean of the selected image = 0.832095
The standard deviation of the selected image = 1.050031
The number of points used in calculation = 673
The minimum of selected image = -1.0
The maximum of selected image = 7.0
The location of minimum is at pixel number = (1,1)
The location of maximum is at pixel number = (11,16)
****** successfully exited ******
****** statistics for /tproc/nandra/processing/74033000/work/gis2_spec_bgd.tmp ******
The sum of the selected image = 2668.000000
The mean of the selected image = 0.466271
The standard deviation of the selected image = 0.912072
The number of points used in calculation = 5722
The minimum of selected image = -1.0
The maximum of selected image = 15.0
The location of minimum is at pixel number = (1,1)
The location of maximum is at pixel number = (30,94)
****** successfully exited ******
gnt_infrm: SDS = 13.85
gnt_infrm: Source was detected with confidence because S = 13.85
gnt_infrm: The scripts will find centroids from smoothed sky images.
gnt_infrm: The source coordinates will be X and Y of the centroid.
gnt_infrm: Centroid for sis0...
gnt_infrm: Centroiding region is circle(179,205,33).
gnt_infrm: Creating sky image for sis0...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS S0CCDPOW
1 MRK507 BRIGHT2 MEDIUM 16/12/95 04:34:49 0.32E+05 5703 1100
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_sis0.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
4049 978 3071 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
4049 978 3071 0 0 0
in 32032. seconds
Image has 978 counts for 3.0532E-02 counts/sec
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_sis0.evt
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 4095
Got the minimum time resolution of the read data: 8.0000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-SIS0-BRIGHT2 > set binsize 128
!xsel:ASCA-SIS0-BRIGHT2 > set image sky
!xsel:ASCA-SIS0-BRIGHT2 > filter region init_reg.tmp
!xsel:ASCA-SIS0-BRIGHT2 > extract image
!xsel:ASCA-SIS0-BRIGHT2 > save image sis0_sky.tmp clobber=yes
Wrote image to file sis0_sky.tmp
!xsel:ASCA-SIS0-BRIGHT2 > exit save=no
gnt_infrm: Smoothing sky image for sis0...
gnt_infrm: Finding maximum pixel (centroid) for sis0...
****** statistics for /tproc/nandra/processing/74033000/work/sis0_sky_sm.tmp ******
The sum of the selected image = 978.000000
The mean of the selected image = 0.173343
The standard deviation of the selected image = 0.197463
The number of points used in calculation = 5642
The minimum of selected image = 0.0
The maximum of selected image = 1.2
The location of minimum is at pixel number = (1,1)
The location of maximum is at pixel number = (187,204)
****** successfully exited ******
gnt_infrm: Initial sky posns are 187, 204
gnt_infrm: Converting to det co-ordinates
/tproc/nandra/processing/74033000/work/74033000_sis0_subevt.tmp
The sum of the selected column is 59880.000
The mean of the selected column is 440.29412
The standard deviation of the selected column is 8.6940743
The minimum of selected column is 418.00000
The maximum of selected column is 458.00000
The number of points used in calculation is 136
The sum of the selected column is 65311.000
The mean of the selected column is 480.22794
The standard deviation of the selected column is 9.0348846
The minimum of selected column is 460.00000
The maximum of selected column is 500.00000
The number of points used in calculation is 136
gnt_infrm: Writing source region for sis0...
gnt_infrm: Writing SIS background region for sis0...
110,120
gnt_infrm: Centroid for sis1...
gnt_infrm: Centroiding region is circle(179,205,33).
gnt_infrm: Creating sky image for sis1...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS S1CCDPOW
1 MRK507 BRIGHT2 MEDIUM 16/12/95 04:34:49 0.31E+05 5504 0011
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_sis1.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
4029 792 3237 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
4029 792 3237 0 0 0
in 31156. seconds
Image has 792 counts for 2.5420E-02 counts/sec
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_sis1.evt
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 4095
Got the minimum time resolution of the read data: 8.0000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-SIS1-BRIGHT2 > set binsize 128
!xsel:ASCA-SIS1-BRIGHT2 > set image sky
!xsel:ASCA-SIS1-BRIGHT2 > filter region init_reg.tmp
!xsel:ASCA-SIS1-BRIGHT2 > extract image
!xsel:ASCA-SIS1-BRIGHT2 > save image sis1_sky.tmp clobber=yes
Wrote image to file sis1_sky.tmp
!xsel:ASCA-SIS1-BRIGHT2 > exit save=no
gnt_infrm: Smoothing sky image for sis1...
gnt_infrm: Finding maximum pixel (centroid) for sis1...
****** statistics for /tproc/nandra/processing/74033000/work/sis1_sky_sm.tmp ******
The sum of the selected image = 792.000001
The mean of the selected image = 0.143869
The standard deviation of the selected image = 0.160607
The number of points used in calculation = 5505
The minimum of selected image = 0.0
The maximum of selected image = 1.0
The location of minimum is at pixel number = (1,1)
The location of maximum is at pixel number = (186,204)
****** successfully exited ******
gnt_infrm: Initial sky posns are 186, 204
gnt_infrm: Converting to det co-ordinates
/tproc/nandra/processing/74033000/work/74033000_sis1_subevt.tmp
The sum of the selected column is 49067.000
The mean of the selected column is 442.04505
The standard deviation of the selected column is 8.9131031
The minimum of selected column is 423.00000
The maximum of selected column is 459.00000
The number of points used in calculation is 111
The sum of the selected column is 57164.000
The mean of the selected column is 514.99099
The standard deviation of the selected column is 9.0458383
The minimum of selected column is 498.00000
The maximum of selected column is 535.00000
The number of points used in calculation is 111
gnt_infrm: Writing source region for sis1...
gnt_infrm: Writing SIS background region for sis1...
110,128
gnt_infrm: Centroid for gis2...
gnt_infrm: Centroiding region is circle(136,148,14).
gnt_infrm: Creating sky image for gis2...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS PHA_BINS
1 MRK507 PH MEDIUM 16/12/95 04:34:57 0.34E+05 10537 1024
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 594 9943 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 594 9943 0 0 0
in 34380. seconds
Image has 594 counts for 1.7278E-02 counts/sec
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_gis2.evt
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Got the minimum time resolution of the read data: 0.50000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-GIS2-PH > set binsize 128
!xsel:ASCA-GIS2-PH > set image sky
!xsel:ASCA-GIS2-PH > filter region init_reg.tmp
!xsel:ASCA-GIS2-PH > extract image
!xsel:ASCA-GIS2-PH > save image gis2_sky.tmp clobber=yes
Wrote image to file gis2_sky.tmp
!xsel:ASCA-GIS2-PH > exit save=no
gnt_infrm: Smoothing sky image for gis2...
gnt_infrm: Finding maximum pixel (centroid) for gis2...
****** statistics for /tproc/nandra/processing/74033000/work/gis2_sky_sm.tmp ******
The sum of the selected image = 594.000001
The mean of the selected image = 0.329086
The standard deviation of the selected image = 0.384074
The number of points used in calculation = 1805
The minimum of selected image = 0.0
The maximum of selected image = 1.5
The location of minimum is at pixel number = (1,1)
The location of maximum is at pixel number = (139,147)
****** successfully exited ******
gnt_infrm: Initial sky posns are 139, 147
gnt_infrm: Converting to det co-ordinates
/tproc/nandra/processing/74033000/work/74033000_gis2_subevt.tmp
The sum of the selected column is 17044.000
The mean of the selected column is 105.86335
The standard deviation of the selected column is 2.2652177
The minimum of selected column is 101.00000
The maximum of selected column is 111.00000
The number of points used in calculation is 161
The sum of the selected column is 18502.000
The mean of the selected column is 114.91925
The standard deviation of the selected column is 2.3531233
The minimum of selected column is 110.00000
The maximum of selected column is 121.00000
The number of points used in calculation is 161
gnt_infrm: Writing source region for gis2...
gnt_infrm: Writing GIS background region for gis2...
105,114
gnt_infrm: Centroid for gis3...
gnt_infrm: Centroiding region is circle(136,148,14).
gnt_infrm: Creating sky image for gis3...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS PHA_BINS
1 MRK507 PH MEDIUM 16/12/95 04:34:57 0.35E+05 12127 1024
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 732 11395 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 732 11395 0 0 0
in 35470. seconds
Image has 732 counts for 2.0637E-02 counts/sec
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_gis3.evt
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Got the minimum time resolution of the read data: 0.50000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-GIS3-PH > set binsize 128
!xsel:ASCA-GIS3-PH > set image sky
!xsel:ASCA-GIS3-PH > filter region init_reg.tmp
!xsel:ASCA-GIS3-PH > extract image
!xsel:ASCA-GIS3-PH > save image gis3_sky.tmp clobber=yes
Wrote image to file gis3_sky.tmp
!xsel:ASCA-GIS3-PH > exit save=no
gnt_infrm: Smoothing sky image for gis3...
gnt_infrm: Finding maximum pixel (centroid) for gis3...
****** statistics for /tproc/nandra/processing/74033000/work/gis3_sky_sm.tmp ******
The sum of the selected image = 732.000000
The mean of the selected image = 0.403751
The standard deviation of the selected image = 0.521380
The number of points used in calculation = 1813
The minimum of selected image = 0.0
The maximum of selected image = 2.2
The location of minimum is at pixel number = (1,1)
The location of maximum is at pixel number = (140,148)
****** successfully exited ******
gnt_infrm: Initial sky posns are 140, 148
gnt_infrm: Converting to det co-ordinates
/tproc/nandra/processing/74033000/work/74033000_gis3_subevt.tmp
The sum of the selected column is 27815.000
The mean of the selected column is 110.81673
The standard deviation of the selected column is 2.1740007
The minimum of selected column is 106.00000
The maximum of selected column is 116.00000
The number of points used in calculation is 251
The sum of the selected column is 28937.000
The mean of the selected column is 115.28685
The standard deviation of the selected column is 2.1774725
The minimum of selected column is 110.00000
The maximum of selected column is 120.00000
The number of points used in calculation is 251
gnt_infrm: Writing source region for gis3...
gnt_infrm: Writing GIS background region for gis3...
110,115
gnt_infrm: Comparing SIS and GIS centroids respectively...
gnt_infrm: Combining respective sky images...
gnt_infrm: Comparing combined GIS centroid to SIS0 and SIS1...
****** statistics for /tproc/nandra/processing/74033000/work/gis_sky_sm.tmp ******
The sum of the selected image = 1326.000000
The mean of the selected image = 1.272553
The standard deviation of the selected image = 1.331626
The number of points used in calculation = 1042
The minimum of selected image = 0.0
The maximum of selected image = 7.6
The location of minimum is at pixel number = (1,1)
The location of maximum is at pixel number = (140,148)
****** successfully exited ******
gnt_infrm: Copying .reg files to permanent area...
gnt_infrm: ========================
gnt_infrm: End of procedure do_cent
gnt_infrm: ========================
Fri Apr 28 04:46:10 EDT 2000
gnt_infrm: *************************
gnt_infrm: Running procedure do_prod
gnt_infrm: *************************
Fri Apr 28 04:46:10 EDT 2000
gnt_infrm: Running extraction procedure for 74033000...
gnt_infrm: Running SISPI...
SISPI v1.1.1
SISPI v1.1.1
gnt_infrm: DATAMODE = BRIGHT2.
gnt_infrm: BITFIX = n.
gnt_infrm: Extracting src data for sis0...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS S0CCDPOW
1 MRK507 BRIGHT2 MEDIUM 16/12/95 04:34:49 0.32E+05 5703 1100
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_sis0.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
4049 4049 0 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
4049 4049 0 0 0 0
in 32032. seconds
Image has 4049 counts for 0.1264 counts/sec
Processing file: /tproc/nandra/processing/74033000/work/74033000_sis0.evt
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1885 1368 517 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1885 1368 517 0 0 0
in 32032. seconds
Spectrum has 1368 counts for 4.2708E-02 counts/sec
... written the PHA data Extension
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS0 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 32032. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 6.12010E-02 Background scaling factor
BACKFILE - none Associated background file
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - none Associated redistribution matrix file
ANCRFILE - none Associated ancillary response file
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
... QUALITY
...
... -------
... QUALITY
... -------
... Bad Channels (Channel - Channel)
... ---------------------------------------------
... 0 - 25 have quality 5
... ---------------------------------------------
...
...... exiting, changes written to file : 74033000_sis0_src.pha
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1885 1294 517 0 0 74
Writing events file
1294 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1885 1294 517 0 0 74
in 32032. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1885 753 517 0 0 615
Writing events file
753 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1885 753 517 0 0 615
in 32032. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1885 542 517 0 0 826
Writing events file
542 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1885 542 517 0 0 826
in 32032. seconds
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_sis0.evt
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 4095
Got the minimum time resolution of the read data: 8.0000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-SIS0-BRIGHT2 > set binsize 128
!xsel:ASCA-SIS0-BRIGHT2 > set image sky
!xsel:ASCA-SIS0-BRIGHT2 > set xybinsize 4
!xsel:ASCA-SIS0-BRIGHT2 > extract image
!xsel:ASCA-SIS0-BRIGHT2 > save image clobber=yes 74033000_sis0_sky.img
Wrote image to file 74033000_sis0_sky.img
!xsel:ASCA-SIS0-BRIGHT2 > set image det
!xsel:ASCA-SIS0-BRIGHT2 > select events CCDID.EQ.1
!xsel:ASCA-SIS0-BRIGHT2 > filter region 74033000_sis0_src.reg
!xsel:ASCA-SIS0-BRIGHT2 > extract spectrum
!xsel:ASCA-SIS0-BRIGHT2 > save spectrum group=yes clobber=yes 74033000_sis0_src.pha
Wrote spectrum to 74033000_sis0_src.pha
!xsel:ASCA-SIS0-BRIGHT2 > filter pha_cutoff 140 2796
!xsel:ASCA-SIS0-BRIGHT2 > extract events
!xsel:ASCA-SIS0-BRIGHT2 > save events use=no clobber=yes 74033000_sis0_src.evt
Wrote events list to file 74033000_sis0_src.evt
!xsel:ASCA-SIS0-BRIGHT2 > clear events
!xsel:ASCA-SIS0-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS0-BRIGHT2 > filter pha_cutoff 140 560
!xsel:ASCA-SIS0-BRIGHT2 > extract events
!xsel:ASCA-SIS0-BRIGHT2 > save events use=no clobber=yes 74033000_sis0_src_soft.evt
Wrote events list to file 74033000_sis0_src_soft.evt
!xsel:ASCA-SIS0-BRIGHT2 > clear events
!xsel:ASCA-SIS0-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS0-BRIGHT2 > filter pha_cutoff 560 2796
!xsel:ASCA-SIS0-BRIGHT2 > extract events
!xsel:ASCA-SIS0-BRIGHT2 > save events use=no clobber=yes 74033000_sis0_src_hard.evt
Wrote events list to file 74033000_sis0_src_hard.evt
!xsel:ASCA-SIS0-BRIGHT2 > clear events
!xsel:ASCA-SIS0-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS0-BRIGHT2 > clear region all
!xsel:ASCA-SIS0-BRIGHT2 > exit save=no
gnt_infrm: Extracting src data for sis1...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS S1CCDPOW
1 MRK507 BRIGHT2 MEDIUM 16/12/95 04:34:49 0.31E+05 5504 0011
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_sis1.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
4029 4029 0 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
4029 4029 0 0 0 0
in 31156. seconds
Image has 4029 counts for 0.1293 counts/sec
Processing file: /tproc/nandra/processing/74033000/work/74033000_sis1.evt
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1541 1061 480 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1541 1061 480 0 0 0
in 31156. seconds
Spectrum has 1061 counts for 3.4054E-02 counts/sec
... written the PHA data Extension
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS1 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 31156. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 5.63770E-02 Background scaling factor
BACKFILE - none Associated background file
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - none Associated redistribution matrix file
ANCRFILE - none Associated ancillary response file
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
... QUALITY
...
... -------
... QUALITY
... -------
... Bad Channels (Channel - Channel)
... ---------------------------------------------
... 0 - 25 have quality 5
... ---------------------------------------------
...
...... exiting, changes written to file : 74033000_sis1_src.pha
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1541 994 480 0 0 67
Writing events file
994 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1541 994 480 0 0 67
in 31156. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1541 564 480 0 0 497
Writing events file
564 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1541 564 480 0 0 497
in 31156. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1541 431 480 0 0 630
Writing events file
431 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1541 431 480 0 0 630
in 31156. seconds
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_sis1.evt
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 4095
Got the minimum time resolution of the read data: 8.0000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-SIS1-BRIGHT2 > set binsize 128
!xsel:ASCA-SIS1-BRIGHT2 > set image sky
!xsel:ASCA-SIS1-BRIGHT2 > set xybinsize 4
!xsel:ASCA-SIS1-BRIGHT2 > extract image
!xsel:ASCA-SIS1-BRIGHT2 > save image clobber=yes 74033000_sis1_sky.img
Wrote image to file 74033000_sis1_sky.img
!xsel:ASCA-SIS1-BRIGHT2 > set image det
!xsel:ASCA-SIS1-BRIGHT2 > select events CCDID.EQ.3
!xsel:ASCA-SIS1-BRIGHT2 > filter region 74033000_sis1_src.reg
!xsel:ASCA-SIS1-BRIGHT2 > extract spectrum
!xsel:ASCA-SIS1-BRIGHT2 > save spectrum group=yes clobber=yes 74033000_sis1_src.pha
Wrote spectrum to 74033000_sis1_src.pha
!xsel:ASCA-SIS1-BRIGHT2 > filter pha_cutoff 140 2796
!xsel:ASCA-SIS1-BRIGHT2 > extract events
!xsel:ASCA-SIS1-BRIGHT2 > save events use=no clobber=yes 74033000_sis1_src.evt
Wrote events list to file 74033000_sis1_src.evt
!xsel:ASCA-SIS1-BRIGHT2 > clear events
!xsel:ASCA-SIS1-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS1-BRIGHT2 > filter pha_cutoff 140 560
!xsel:ASCA-SIS1-BRIGHT2 > extract events
!xsel:ASCA-SIS1-BRIGHT2 > save events use=no clobber=yes 74033000_sis1_src_soft.evt
Wrote events list to file 74033000_sis1_src_soft.evt
!xsel:ASCA-SIS1-BRIGHT2 > clear events
!xsel:ASCA-SIS1-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS1-BRIGHT2 > filter pha_cutoff 560 2796
!xsel:ASCA-SIS1-BRIGHT2 > extract events
!xsel:ASCA-SIS1-BRIGHT2 > save events use=no clobber=yes 74033000_sis1_src_hard.evt
Wrote events list to file 74033000_sis1_src_hard.evt
!xsel:ASCA-SIS1-BRIGHT2 > clear events
!xsel:ASCA-SIS1-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS1-BRIGHT2 > clear region all
!xsel:ASCA-SIS1-BRIGHT2 > exit save=no
gnt_infrm: Extracting src data for gis2...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS PHA_BINS
1 MRK507 PH MEDIUM 16/12/95 04:34:57 0.34E+05 10537 1024
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 10537 0 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 10537 0 0 0 0
in 34380. seconds
Image has 10537 counts for 0.3065 counts/sec
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 1342 9195 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 1342 9195 0 0 0
in 34380. seconds
Spectrum has 1342 counts for 3.9035E-02 counts/sec
... written the PHA data Extension
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 1266 9195 0 0 76
Writing events file
1266 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 1266 9195 0 0 76
in 34380. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 752 9195 0 0 590
Writing events file
752 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 752 9195 0 0 590
in 34380. seconds
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_gis2.evt
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Got the minimum time resolution of the read data: 0.50000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-GIS2-PH > set binsize 128
!xsel:ASCA-GIS2-PH > set image sky
!xsel:ASCA-GIS2-PH > set xybinsize 1
!xsel:ASCA-GIS2-PH > extract image
!xsel:ASCA-GIS2-PH > save image clobber=yes 74033000_gis2_sky.img
Wrote image to file 74033000_gis2_sky.img
!xsel:ASCA-GIS2-PH > set image det
!xsel:ASCA-GIS2-PH > filter region 74033000_gis2_src.reg
!xsel:ASCA-GIS2-PH > extract spectrum
!xsel:ASCA-GIS2-PH > save spectrum group=no clobber=yes 74033000_gis2_src.pha
Wrote spectrum to 74033000_gis2_src.pha
!xsel:ASCA-GIS2-PH > filter pha_cutoff 43 850
!xsel:ASCA-GIS2-PH > extract events
!xsel:ASCA-GIS2-PH > save events use=no clobber=yes 74033000_gis2_src.evt
Wrote events list to file 74033000_gis2_src.evt
!xsel:ASCA-GIS2-PH > clear events
!xsel:ASCA-GIS2-PH > clear pha_cutoff
!xsel:ASCA-GIS2-PH > filter pha_cutoff 170 850
!xsel:ASCA-GIS2-PH > extract events
!xsel:ASCA-GIS2-PH > save events use=no clobber=yes 74033000_gis2_src_hard.evt
Wrote events list to file 74033000_gis2_src_hard.evt
!xsel:ASCA-GIS2-PH > exit save=no
gnt_infrm: Extracting BITFIX=n src data for gis3...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS PHA_BINS
1 MRK507 PH MEDIUM 16/12/95 04:34:57 0.35E+05 12127 1024
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 12127 0 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 12127 0 0 0 0
in 35470. seconds
Image has 12127 counts for 0.3419 counts/sec
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 1611 10516 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 1611 10516 0 0 0
in 35470. seconds
Spectrum has 1611 counts for 4.5419E-02 counts/sec
... written the PHA data Extension
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 1541 10516 0 0 70
Writing events file
1541 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 1541 10516 0 0 70
in 35470. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 866 10516 0 0 745
Writing events file
866 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 866 10516 0 0 745
in 35470. seconds
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_gis3.evt
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Got the minimum time resolution of the read data: 0.50000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-GIS3-PH > set binsize 128
!xsel:ASCA-GIS3-PH > set image sky
!xsel:ASCA-GIS3-PH > set xybinsize 1
!xsel:ASCA-GIS3-PH > extract image
!xsel:ASCA-GIS3-PH > save image clobber=yes 74033000_gis3_sky.img
Wrote image to file 74033000_gis3_sky.img
!xsel:ASCA-GIS3-PH > set image det
!xsel:ASCA-GIS3-PH > filter region 74033000_gis3_src.reg
!xsel:ASCA-GIS3-PH > extract spectrum
!xsel:ASCA-GIS3-PH > save spectrum group=no clobber=yes 74033000_gis3_src.pha
Wrote spectrum to 74033000_gis3_src.pha
!xsel:ASCA-GIS3-PH > filter pha_cutoff 43 850
!xsel:ASCA-GIS3-PH > extract events
!xsel:ASCA-GIS3-PH > save events use=no clobber=yes 74033000_gis3_src.evt
Wrote events list to file 74033000_gis3_src.evt
!xsel:ASCA-GIS3-PH > clear events
!xsel:ASCA-GIS3-PH > clear pha_cutoff
!xsel:ASCA-GIS3-PH > filter pha_cutoff 170 850
!xsel:ASCA-GIS3-PH > extract events
!xsel:ASCA-GIS3-PH > save events use=no clobber=yes 74033000_gis3_src_hard.evt
Wrote events list to file 74033000_gis3_src_hard.evt
!xsel:ASCA-GIS3-PH > exit save=no
gnt_infrm: Extracting bgd data for sis0...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS S0CCDPOW
1 MRK507 BRIGHT2 MEDIUM 16/12/95 04:34:49 0.32E+05 5703 1100
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_sis0.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
4049 4049 0 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
4049 4049 0 0 0 0
in 32032. seconds
Image has 4049 counts for 0.1264 counts/sec
Processing file: /tproc/nandra/processing/74033000/work/74033000_sis0.evt
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1885 357 1528 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1885 357 1528 0 0 0
in 32032. seconds
Spectrum has 357 counts for 1.1145E-02 counts/sec
... written the PHA data Extension
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS0 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 32032. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 3.17870E-02 Background scaling factor
BACKFILE - none Associated background file
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - none Associated redistribution matrix file
ANCRFILE - none Associated ancillary response file
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
... QUALITY
...
... -------
... QUALITY
... -------
... Bad Channels (Channel - Channel)
... ---------------------------------------------
... 0 - 25 have quality 5
... ---------------------------------------------
...
...... exiting, changes written to file : 74033000_sis0_bgd.pha
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1885 323 1528 0 0 34
Writing events file
323 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1885 323 1528 0 0 34
in 32032. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1885 179 1528 0 0 178
Writing events file
179 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1885 179 1528 0 0 178
in 32032. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1885 144 1528 0 0 213
Writing events file
144 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1885 144 1528 0 0 213
in 32032. seconds
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_sis0.evt
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 4095
Got the minimum time resolution of the read data: 8.0000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-SIS0-BRIGHT2 > set binsize 128
!xsel:ASCA-SIS0-BRIGHT2 > set image sky
!xsel:ASCA-SIS0-BRIGHT2 > set xybinsize 4
!xsel:ASCA-SIS0-BRIGHT2 > extract image
!xsel:ASCA-SIS0-BRIGHT2 > save image clobber=yes 74033000_sis0_sky.img
Wrote image to file 74033000_sis0_sky.img
!xsel:ASCA-SIS0-BRIGHT2 > set image det
!xsel:ASCA-SIS0-BRIGHT2 > select events CCDID.EQ.1
!xsel:ASCA-SIS0-BRIGHT2 > filter region 74033000_sis0_bgd.reg
!xsel:ASCA-SIS0-BRIGHT2 > extract spectrum
!xsel:ASCA-SIS0-BRIGHT2 > save spectrum group=yes clobber=yes 74033000_sis0_bgd.pha
Wrote spectrum to 74033000_sis0_bgd.pha
!xsel:ASCA-SIS0-BRIGHT2 > filter pha_cutoff 140 2796
!xsel:ASCA-SIS0-BRIGHT2 > extract events
!xsel:ASCA-SIS0-BRIGHT2 > save events use=no clobber=yes 74033000_sis0_bgd.evt
Wrote events list to file 74033000_sis0_bgd.evt
!xsel:ASCA-SIS0-BRIGHT2 > clear events
!xsel:ASCA-SIS0-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS0-BRIGHT2 > filter pha_cutoff 140 560
!xsel:ASCA-SIS0-BRIGHT2 > extract events
!xsel:ASCA-SIS0-BRIGHT2 > save events use=no clobber=yes 74033000_sis0_bgd_soft.evt
Wrote events list to file 74033000_sis0_bgd_soft.evt
!xsel:ASCA-SIS0-BRIGHT2 > clear events
!xsel:ASCA-SIS0-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS0-BRIGHT2 > filter pha_cutoff 560 2796
!xsel:ASCA-SIS0-BRIGHT2 > extract events
!xsel:ASCA-SIS0-BRIGHT2 > save events use=no clobber=yes 74033000_sis0_bgd_hard.evt
Wrote events list to file 74033000_sis0_bgd_hard.evt
!xsel:ASCA-SIS0-BRIGHT2 > clear events
!xsel:ASCA-SIS0-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS0-BRIGHT2 > clear region all
!xsel:ASCA-SIS0-BRIGHT2 > exit save=no
gnt_infrm: Extracting bgd data for sis1...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS S1CCDPOW
1 MRK507 BRIGHT2 MEDIUM 16/12/95 04:34:49 0.31E+05 5504 0011
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_sis1.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
4029 4029 0 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
4029 4029 0 0 0 0
in 31156. seconds
Image has 4029 counts for 0.1293 counts/sec
Processing file: /tproc/nandra/processing/74033000/work/74033000_sis1.evt
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1541 339 1202 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1541 339 1202 0 0 0
in 31156. seconds
Spectrum has 339 counts for 1.0881E-02 counts/sec
... written the PHA data Extension
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS1 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 31156. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 3.75100E-02 Background scaling factor
BACKFILE - none Associated background file
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - none Associated redistribution matrix file
ANCRFILE - none Associated ancillary response file
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
... QUALITY
...
... -------
... QUALITY
... -------
... Bad Channels (Channel - Channel)
... ---------------------------------------------
... 0 - 25 have quality 5
... ---------------------------------------------
...
...... exiting, changes written to file : 74033000_sis1_bgd.pha
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1541 310 1202 0 0 29
Writing events file
310 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1541 310 1202 0 0 29
in 31156. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1541 163 1202 0 0 176
Writing events file
163 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1541 163 1202 0 0 176
in 31156. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /local/data/tproc/nandra/processing/74033000/work/xsel_work1001.xsl
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
1541 147 1202 0 0 192
Writing events file
147 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
1541 147 1202 0 0 192
in 31156. seconds
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_sis1.evt
Setting...
Image keywords = X Y with binning = 4
WMAP keywords = DETX DETY with binning = 8
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 4095
Got the minimum time resolution of the read data: 8.0000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-SIS1-BRIGHT2 > set binsize 128
!xsel:ASCA-SIS1-BRIGHT2 > set image sky
!xsel:ASCA-SIS1-BRIGHT2 > set xybinsize 4
!xsel:ASCA-SIS1-BRIGHT2 > extract image
!xsel:ASCA-SIS1-BRIGHT2 > save image clobber=yes 74033000_sis1_sky.img
Wrote image to file 74033000_sis1_sky.img
!xsel:ASCA-SIS1-BRIGHT2 > set image det
!xsel:ASCA-SIS1-BRIGHT2 > select events CCDID.EQ.3
!xsel:ASCA-SIS1-BRIGHT2 > filter region 74033000_sis1_bgd.reg
!xsel:ASCA-SIS1-BRIGHT2 > extract spectrum
!xsel:ASCA-SIS1-BRIGHT2 > save spectrum group=yes clobber=yes 74033000_sis1_bgd.pha
Wrote spectrum to 74033000_sis1_bgd.pha
!xsel:ASCA-SIS1-BRIGHT2 > filter pha_cutoff 140 2796
!xsel:ASCA-SIS1-BRIGHT2 > extract events
!xsel:ASCA-SIS1-BRIGHT2 > save events use=no clobber=yes 74033000_sis1_bgd.evt
Wrote events list to file 74033000_sis1_bgd.evt
!xsel:ASCA-SIS1-BRIGHT2 > clear events
!xsel:ASCA-SIS1-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS1-BRIGHT2 > filter pha_cutoff 140 560
!xsel:ASCA-SIS1-BRIGHT2 > extract events
!xsel:ASCA-SIS1-BRIGHT2 > save events use=no clobber=yes 74033000_sis1_bgd_soft.evt
Wrote events list to file 74033000_sis1_bgd_soft.evt
!xsel:ASCA-SIS1-BRIGHT2 > clear events
!xsel:ASCA-SIS1-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS1-BRIGHT2 > filter pha_cutoff 560 2796
!xsel:ASCA-SIS1-BRIGHT2 > extract events
!xsel:ASCA-SIS1-BRIGHT2 > save events use=no clobber=yes 74033000_sis1_bgd_hard.evt
Wrote events list to file 74033000_sis1_bgd_hard.evt
!xsel:ASCA-SIS1-BRIGHT2 > clear events
!xsel:ASCA-SIS1-BRIGHT2 > clear pha_cutoff
!xsel:ASCA-SIS1-BRIGHT2 > clear region all
!xsel:ASCA-SIS1-BRIGHT2 > exit save=no
gnt_infrm: Extracting bgd data for gis2...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS PHA_BINS
1 MRK507 PH MEDIUM 16/12/95 04:34:57 0.34E+05 10537 1024
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 10537 0 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 10537 0 0 0 0
in 34380. seconds
Image has 10537 counts for 0.3065 counts/sec
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 2865 7672 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 2865 7672 0 0 0
in 34380. seconds
Spectrum has 2865 counts for 8.3334E-02 counts/sec
... written the PHA data Extension
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 2689 7672 0 0 176
Writing events file
2689 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 2689 7672 0 0 176
in 34380. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
10537 1458 7672 0 0 1407
Writing events file
1458 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
10537 1458 7672 0 0 1407
in 34380. seconds
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_gis2.evt
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Got the minimum time resolution of the read data: 0.50000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-GIS2-PH > set binsize 128
!xsel:ASCA-GIS2-PH > set image sky
!xsel:ASCA-GIS2-PH > set xybinsize 1
!xsel:ASCA-GIS2-PH > extract image
!xsel:ASCA-GIS2-PH > save image clobber=yes 74033000_gis2_sky.img
Wrote image to file 74033000_gis2_sky.img
!xsel:ASCA-GIS2-PH > set image det
!xsel:ASCA-GIS2-PH > filter region 74033000_gis2_bgd.reg
!xsel:ASCA-GIS2-PH > extract spectrum
!xsel:ASCA-GIS2-PH > save spectrum group=no clobber=yes 74033000_gis2_bgd.pha
Wrote spectrum to 74033000_gis2_bgd.pha
!xsel:ASCA-GIS2-PH > filter pha_cutoff 43 850
!xsel:ASCA-GIS2-PH > extract events
!xsel:ASCA-GIS2-PH > save events use=no clobber=yes 74033000_gis2_bgd.evt
Wrote events list to file 74033000_gis2_bgd.evt
!xsel:ASCA-GIS2-PH > clear events
!xsel:ASCA-GIS2-PH > clear pha_cutoff
!xsel:ASCA-GIS2-PH > filter pha_cutoff 170 850
!xsel:ASCA-GIS2-PH > extract events
!xsel:ASCA-GIS2-PH > save events use=no clobber=yes 74033000_gis2_bgd_hard.evt
Wrote events list to file 74033000_gis2_bgd_hard.evt
!xsel:ASCA-GIS2-PH > exit save=no
gnt_infrm: Extracting BITFIX=n bgd data for gis3...
OBJECT DATAMODE BIT_RATE DATE-OBS TIME-OBS ONTIME NEVENTS PHA_BINS
1 MRK507 PH MEDIUM 16/12/95 04:34:57 0.35E+05 12127 1024
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 12127 0 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 12127 0 0 0 0
in 35470. seconds
Image has 12127 counts for 0.3419 counts/sec
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 3695 8432 0 0 0
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 3695 8432 0 0 0
in 35470. seconds
Spectrum has 3695 counts for 0.1042 counts/sec
... written the PHA data Extension
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 3487 8432 0 0 208
Writing events file
3487 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 3487 8432 0 0 208
in 35470. seconds
extractor v3.75 8 Mar 2000
Getting FITS WCS Keywords
Doing file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
10% completed
20% completed
30% completed
40% completed
50% completed
60% completed
70% completed
80% completed
90% completed
100% completed
Total Good Bad: Region Time Phase Cut
12127 1821 8432 0 0 1874
Writing events file
1821 events written to the output file
===============================================================================
Grand Total Good Bad: Region Time Phase Cut
12127 1821 8432 0 0 1874
in 35470. seconds
** XSELECT V2.0 **
!> Enter session name >[xsel]
Notes: XSELECT set up for ASCA
Time keyword is TIME in units of s
Default timing binsize = 16.000
Command not found; type ? for a command listing
!xsel:ASCA > clear all proceed=yes
WARNING: CLEAR ALL will remove all temporary files
!xsel > set datadir ./
Setting data directory to /tproc/nandra/processing/74033000/work/
Setting mkf directory to /tproc/nandra/processing/74033000/aux/
!xsel > read e 74033000_gis3.evt
Setting...
Image keywords = X Y with binning = 1
WMAP keywords = DETX DETY with binning = 1
Energy keywords = PI with binning = 1
Getting Min and Max for Energy Column...
Got min and max for PI: 0 1023
Got the minimum time resolution of the read data: 0.50000
Number of files read in: 1
******************** Observation Catalogue ********************
Data Directory is: /tproc/nandra/processing/74033000/work/
HK Directory is: /tproc/nandra/processing/74033000/work/
!xsel:ASCA-GIS3-PH > set binsize 128
!xsel:ASCA-GIS3-PH > set image sky
!xsel:ASCA-GIS3-PH > set xybinsize 1
!xsel:ASCA-GIS3-PH > extract image
!xsel:ASCA-GIS3-PH > save image clobber=yes 74033000_gis3_sky.img
Wrote image to file 74033000_gis3_sky.img
!xsel:ASCA-GIS3-PH > set image det
!xsel:ASCA-GIS3-PH > filter region 74033000_gis3_bgd.reg
!xsel:ASCA-GIS3-PH > extract spectrum
!xsel:ASCA-GIS3-PH > save spectrum group=no clobber=yes 74033000_gis3_bgd.pha
Wrote spectrum to 74033000_gis3_bgd.pha
!xsel:ASCA-GIS3-PH > filter pha_cutoff 43 850
!xsel:ASCA-GIS3-PH > extract events
!xsel:ASCA-GIS3-PH > save events use=no clobber=yes 74033000_gis3_bgd.evt
Wrote events list to file 74033000_gis3_bgd.evt
!xsel:ASCA-GIS3-PH > clear events
!xsel:ASCA-GIS3-PH > clear pha_cutoff
!xsel:ASCA-GIS3-PH > filter pha_cutoff 170 850
!xsel:ASCA-GIS3-PH > extract events
!xsel:ASCA-GIS3-PH > save events use=no clobber=yes 74033000_gis3_bgd_hard.evt
Wrote events list to file 74033000_gis3_bgd_hard.evt
!xsel:ASCA-GIS3-PH > exit save=no
gnt_infrm: ========================
gnt_infrm: End of procedure do_prod
gnt_infrm: ========================
Fri Apr 28 04:47:12 EDT 2000
gnt_infrm: *************************
gnt_infrm: Running procedure do_spec
gnt_infrm: *************************
Fri Apr 28 04:47:12 EDT 2000
gnt_infrm: Group .pha files for 74033000...
gnt_infrm: Minimum channels are 60 (gis2), 60 (gis3).
gnt_infrm: Creating grouped spectrum files for sis0...
grppha
Fri Apr 28 04:47:27 EDT 2000
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS0 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 32032. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 6.12010E-02 Background scaling factor
BACKFILE - none Associated background file
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - none Associated redistribution matrix file
ANCRFILE - none Associated ancillary response file
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
...... exiting, changes written to file : 74033000_sis0_src.pha.tmp
** grppha 2.9.0 completed successfully
grppha
Fri Apr 28 04:47:27 EDT 2000
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS0 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 32032. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 6.12010E-02 Background scaling factor
BACKFILE - 74033000_sis0_bgd.pha
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - 74033000_sis0.rmf
ANCRFILE - 74033000_sis0.arf
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
...... Channel 1024 is not within the channel range !
...... Upper channel reset to last channel : 1023
...... exiting, changes written to file : 74033000_sis0_src_20.pha
** grppha 2.9.0 completed successfully
ascaarf
Fri Apr 28 04:47:28 EDT 2000
ascaarf 74033000_sis0_src.pha.tmp 74033000_sis0.rmf 74033000_sis0.arf point=yes simple=yes clobber=yes
ASCAARF vers 3.00 6 Oct 1998.
xrtrsp : /FTP/caldb/data/asca/xrt/bcf/xrt_ea_v2_0.fits
xrtpsf : /FTP/caldb/data/asca/xrt/bcf/xrt_psf_v2_0.fits
Input WMAP array has size 45 by 42 bins
expanded to 45 by 42 bins
First WMAP bin is at detector pixel 256 296
8 detector pixels per WMAP bin
WMAP bin size is 0.21600 mm
0.21216 arcmin
Selected region size is 70.522 arcmin^2
Optical axis is detector pixel 662.72 559.02
1180 energies from RMF file
Effective area fudge applied
Arf filter applied
Point source at 439.00 467.00 (detector coordinates)
Point source at 27.97 11.50 (WMAP bins wrt optical axis)
Point source at 6.42 22.36 (... in polar coordinates)
Total counts in region = 1.36600E+03
Weighted mean angle from optical axis = 6.534 arcmin
gnt_infrm: Creating grouped spectrum files for sis1...
grppha
Fri Apr 28 04:49:03 EDT 2000
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS1 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 31156. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 5.63770E-02 Background scaling factor
BACKFILE - none Associated background file
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - none Associated redistribution matrix file
ANCRFILE - none Associated ancillary response file
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
...... exiting, changes written to file : 74033000_sis1_src.pha.tmp
** grppha 2.9.0 completed successfully
grppha
Fri Apr 28 04:49:03 EDT 2000
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS1 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 31156. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 5.63770E-02 Background scaling factor
BACKFILE - 74033000_sis1_bgd.pha
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - 74033000_sis1.rmf
ANCRFILE - 74033000_sis1.arf
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
...... Channel 1024 is not within the channel range !
...... Upper channel reset to last channel : 1023
...... exiting, changes written to file : 74033000_sis1_src_20.pha
** grppha 2.9.0 completed successfully
ascaarf
Fri Apr 28 04:49:03 EDT 2000
ascaarf 74033000_sis1_src.pha.tmp 74033000_sis1.rmf 74033000_sis1.arf point=yes simple=yes clobber=yes
ASCAARF vers 3.00 6 Oct 1998.
xrtrsp : /FTP/caldb/data/asca/xrt/bcf/xrt_ea_v2_0.fits
xrtpsf : /FTP/caldb/data/asca/xrt/bcf/xrt_psf_v2_0.fits
Input WMAP array has size 45 by 38 bins
expanded to 45 by 38 bins
First WMAP bin is at detector pixel 256 328
8 detector pixels per WMAP bin
WMAP bin size is 0.21600 mm
0.21216 arcmin
Selected region size is 64.963 arcmin^2
Optical axis is detector pixel 618.28 773.83
1180 energies from RMF file
Effective area fudge applied
Arf filter applied
Point source at 439.00 483.00 (detector coordinates)
Point source at 22.41 36.35 (WMAP bins wrt optical axis)
Point source at 9.06 58.35 (... in polar coordinates)
Total counts in region = 1.05700E+03
Weighted mean angle from optical axis = 8.734 arcmin
gnt_infrm: Creating grouped spectrum files for gis2...
grppha
Fri Apr 28 04:50:29 EDT 2000
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - GIS2 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 34380. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 3.66360E-02 Background scaling factor
BACKFILE - none Associated background file
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - none Associated redistribution matrix file
ANCRFILE - none Associated ancillary response file
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
...... exiting, changes written to file : 74033000_gis2_src.pha.tmp
** grppha 2.9.0 completed successfully
grppha
Fri Apr 28 04:50:30 EDT 2000
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - GIS2 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 34380. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 3.66360E-02 Background scaling factor
BACKFILE - 74033000_gis2_bgd.pha
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - 74033000_gis2.rmf
ANCRFILE - 74033000_gis2.arf
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
...... exiting, changes written to file : 74033000_gis2_src_20.pha
** grppha 2.9.0 completed successfully
ascaarf
Fri Apr 28 04:50:30 EDT 2000
ASCAARF vers 3.00 6 Oct 1998.
bethick : /FTP/caldb/data/asca/gis/bcf/s2bev1.fits
grid : /FTP/caldb/data/asca/gis/bcf/s2gridv3.fits
xrtrsp : /FTP/caldb/data/asca/xrt/bcf/xrt_ea_v2_0.fits
xrtpsf : /FTP/caldb/data/asca/xrt/bcf/xrt_psf_v2_0.fits
Input WMAP array has size 54 by 54 bins
expanded to 128 by 128 bins
First WMAP bin is at detector pixel 42 51
1 detector pixels per WMAP bin
WMAP bin size is 0.25000 mm
0.24555 arcmin
Selected region size is 144.80 arcmin^2
Optical axis is detector pixel 133.00 130.96
201 energies from RMF file
Effective area fudge applied
Arf filter applied
Point source at 104.50 113.50 (detector coordinates)
Point source at 28.50 17.46 (WMAP bins wrt optical axis)
Point source at 8.21 31.49 (... in polar coordinates)
Total counts in region = 1.33500E+03
Weighted mean angle from optical axis = 8.532 arcmin
gnt_infrm: Creating grouped spectrum files for gis3...
grppha
Fri Apr 28 04:58:49 EDT 2000
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - GIS3 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 35470. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 3.66360E-02 Background scaling factor
BACKFILE - none Associated background file
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - none Associated redistribution matrix file
ANCRFILE - none Associated ancillary response file
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
...... exiting, changes written to file : 74033000_gis3_src.pha.tmp
** grppha 2.9.0 completed successfully
grppha
Fri Apr 28 04:58:49 EDT 2000
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - GIS3 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 35470. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 3.66360E-02 Background scaling factor
BACKFILE - 74033000_gis3_bgd.pha
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - 74033000_gis3.rmf
ANCRFILE - 74033000_gis3.arf
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
...... exiting, changes written to file : 74033000_gis3_src_20.pha
** grppha 2.9.0 completed successfully
ascaarf
Fri Apr 28 04:58:49 EDT 2000
ASCAARF vers 3.00 6 Oct 1998.
bethick : /FTP/caldb/data/asca/gis/bcf/s3bev1.fits
grid : /FTP/caldb/data/asca/gis/bcf/s3gridv3.fits
xrtrsp : /FTP/caldb/data/asca/xrt/bcf/xrt_ea_v2_0.fits
xrtpsf : /FTP/caldb/data/asca/xrt/bcf/xrt_psf_v2_0.fits
Input WMAP array has size 54 by 54 bins
expanded to 128 by 128 bins
First WMAP bin is at detector pixel 47 52
1 detector pixels per WMAP bin
WMAP bin size is 0.25000 mm
0.24555 arcmin
Selected region size is 144.80 arcmin^2
Optical axis is detector pixel 119.36 134.44
201 energies from RMF file
Effective area fudge applied
Arf filter applied
Point source at 109.50 114.50 (detector coordinates)
Point source at 9.86 19.94 (WMAP bins wrt optical axis)
Point source at 5.46 63.69 (... in polar coordinates)
Total counts in region = 1.59800E+03
Weighted mean angle from optical axis = 6.048 arcmin
gnt_infrm: Creating response matrix for sis0...
Sisrmg Version 1.1, Configured 04/97
This version resolves *all* known keyword incompatibilities with
other FTOOLS tasks. If you have previously fudged *any* keywords
in the PHA file to compensate, incorrect results will follow.
Setting 1st PHA channel to 0
Making v1.1 1180x1024 S0C1 Bright2 PI RMF
Calibration data files:
ecd = /software/lheasoft/release/refdata/sisdata/sis0c1p40_290296.fits
cti = /software/lheasoft/release/refdata/sisdata/sisph2pi_110397.fits
echo = /software/lheasoft/release/refdata/sisdata/sisechos_290296.fits
rdd = /software/lheasoft/release/refdata/sisdata/sisrddis_290296.fits
Please stand by...
...Done.
gnt_infrm: Creating response matrix for sis1...
Sisrmg Version 1.1, Configured 04/97
This version resolves *all* known keyword incompatibilities with
other FTOOLS tasks. If you have previously fudged *any* keywords
in the PHA file to compensate, incorrect results will follow.
Setting 1st PHA channel to 0
Making v1.1 1180x1024 S1C3 Bright2 PI RMF
Calibration data files:
ecd = /software/lheasoft/release/refdata/sisdata/sis1c3p40_290296.fits
cti = /software/lheasoft/release/refdata/sisdata/sisph2pi_110397.fits
echo = /software/lheasoft/release/refdata/sisdata/sisechos_290296.fits
rdd = /software/lheasoft/release/refdata/sisdata/sisrddis_290296.fits
Please stand by...
...Done.
gnt_infrm: ========================
gnt_infrm: End of procedure do_spec
gnt_infrm: ========================
Fri Apr 28 05:07:51 EDT 2000
gnt_infrm: *************************
gnt_infrm: Running procedure do_expo
gnt_infrm: *************************
Fri Apr 28 05:07:51 EDT 2000
gnt_infrm: Grouping channels and creating new 4-channel .pha files...
gnt_infrm: Creating 4-channel spectrum for sis0...
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS0 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 32032. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 6.12010E-02 Background scaling factor
BACKFILE - 74033000_sis0_bgd.pha
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - 74033000_sis0.rmf
ANCRFILE - 74033000_sis0.arf
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
minchan(nocom) 41
maxchan(nocom) 136
numchan(nocom) 96
minchan(nocom) 137
maxchan(nocom) 340
numchan(nocom) 204
minchan(nocom) 341
maxchan(nocom) 477
numchan(nocom) 137
minchan(nocom) 478
maxchan(nocom) 683
numchan(nocom) 206
...... exiting, changes written to file : 74033000_sis0_4_ch.pha
** grppha 2.9.0 completed successfully
gnt_infrm: Creating efficiency map for sis0...
ASCAEFFMAP vers 2.27 5 May 1999.
xrtrsp : /FTP/caldb/data/asca/xrt/bcf/xrt_ea_v2_0.fits
385 grouped channels from the PHA file
Bin size is 0.0270 (mm) = 0.0265(arcmin)
Optical axis is 662.72 559.02
WMAP size is 45 x 42
WMAP offset is 256 296
WMAP bin factor is 8
1024 ungrouped channels from the RMF file
pha bin = 42, E = 0.600 - 2.004 keV ( 1 / 4) calculating ...
<efficiency> = 101.8149 weight = 7.9316305E-05
pha bin = 43, E = 2.004 - 4.987 keV ( 2 / 4) calculating ...
<efficiency> = 88.05466 weight = 5.1571231E-05
pha bin = 44, E = 4.987 - 6.991 keV ( 3 / 4) calculating ...
<efficiency> = 80.47253 weight = 1.2082048E-05
pha bin = 45, E = 6.991 - 10.002 keV ( 4 / 4) calculating ...
<efficiency> = 24.21966 weight = 3.4004290E-05
wrote /tproc/nandra/processing/74033000/work/74033000_sis0.effmap
gnt_infrm: Creating 4-channel spectrum for sis1...
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - SIS1 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 31156. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 5.63770E-02 Background scaling factor
BACKFILE - 74033000_sis1_bgd.pha
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - 74033000_sis1.rmf
ANCRFILE - 74033000_sis1.arf
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
minchan(nocom) 41
maxchan(nocom) 136
numchan(nocom) 96
minchan(nocom) 137
maxchan(nocom) 340
numchan(nocom) 204
minchan(nocom) 341
maxchan(nocom) 477
numchan(nocom) 137
minchan(nocom) 478
maxchan(nocom) 683
numchan(nocom) 206
...... exiting, changes written to file : 74033000_sis1_4_ch.pha
** grppha 2.9.0 completed successfully
gnt_infrm: Creating efficiency map for sis1...
ASCAEFFMAP vers 2.27 5 May 1999.
xrtrsp : /FTP/caldb/data/asca/xrt/bcf/xrt_ea_v2_0.fits
385 grouped channels from the PHA file
Bin size is 0.0270 (mm) = 0.0265(arcmin)
Optical axis is 618.28 773.83
WMAP size is 45 x 38
WMAP offset is 256 328
WMAP bin factor is 8
1024 ungrouped channels from the RMF file
pha bin = 42, E = 0.600 - 2.003 keV ( 1 / 4) calculating ...
<efficiency> = 89.79340 weight = 8.8239984E-05
pha bin = 43, E = 2.003 - 4.983 keV ( 2 / 4) calculating ...
<efficiency> = 75.05585 weight = 5.7313038E-05
pha bin = 44, E = 4.983 - 6.984 keV ( 3 / 4) calculating ...
<efficiency> = 66.25562 weight = 1.8072047E-05
pha bin = 45, E = 6.984 - 9.991 keV ( 4 / 4) calculating ...
<efficiency> = 18.62602 weight = 5.1586780E-05
wrote /tproc/nandra/processing/74033000/work/74033000_sis1.effmap
gnt_infrm: Creating 4-channel spectrum for gis2...
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - GIS2 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 34380. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 3.66360E-02 Background scaling factor
BACKFILE - 74033000_gis2_bgd.pha
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - 74033000_gis2.rmf
ANCRFILE - 74033000_gis2.arf
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
minchan(nocom) 61
maxchan(nocom) 170
numchan(nocom) 110
minchan(nocom) 171
maxchan(nocom) 425
numchan(nocom) 255
minchan(nocom) 426
maxchan(nocom) 594
numchan(nocom) 169
minchan(nocom) 595
maxchan(nocom) 848
numchan(nocom) 254
...... exiting, changes written to file : 74033000_gis2_4_ch.pha
** grppha 2.9.0 completed successfully
gnt_infrm: Creating efficiency map for gis2...
ASCAEFFMAP vers 2.27 5 May 1999.
bethick : /FTP/caldb/data/asca/gis/bcf/s2bev1.fits
grid : /FTP/caldb/data/asca/gis/bcf/s2gridv3.fits
xrtrsp : /FTP/caldb/data/asca/xrt/bcf/xrt_ea_v2_0.fits
240 grouped channels from the PHA file
Bin size is 0.2500 (mm) = 0.2456(arcmin)
Optical axis is 133.00 130.96
WMAP size is 54 x 54
WMAP offset is 78 87
WMAP bin factor is 1
1024 ungrouped channels from the RMF file
pha bin = 62, E = 0.719 - 2.016 keV ( 1 / 4) calculating ...
<efficiency> = 58.80453 weight = 6.3054073E-03
pha bin = 63, E = 2.016 - 5.022 keV ( 2 / 4) calculating ...
<efficiency> = 67.06849 weight = 5.6401626E-03
pha bin = 64, E = 5.022 - 7.014 keV ( 3 / 4) calculating ...
<efficiency> = 57.00737 weight = 1.9841052E-03
pha bin = 65, E = 7.014 - 10.008 keV ( 4 / 4) calculating ...
<efficiency> = 19.77522 weight = 3.5227379E-03
wrote /tproc/nandra/processing/74033000/work/74033000_gis2.effmap
gnt_infrm: Creating 4-channel spectrum for gis3...
-------------------------
MANDATORY KEYWORDS/VALUES
-------------------------
--------------------------------------------------------------------
--------------------------------------------------------------------
EXTNAME - SPECTRUM Name of this BINTABLE
TELESCOP - ASCA Mission/Satellite name
INSTRUME - GIS3 Instrument/Detector
FILTER - NONE Instrument filter in use
EXPOSURE - 35470. Integration time (in secs) of PHA data
AREASCAL - 1.0000 Area scaling factor
BACKSCAL - 3.66360E-02 Background scaling factor
BACKFILE - 74033000_gis3_bgd.pha
CORRSCAL - 1.0000 Correlation scaling factor
CORRFILE - none Associated correlation file
RESPFILE - 74033000_gis3.rmf
ANCRFILE - 74033000_gis3.arf
POISSERR - TRUE Whether Poissonian errors apply
CHANTYPE - PI Whether channels have been corrected
TLMIN1 - 0 First legal Detector channel
DETCHANS - 1024 No. of legal detector channels
NCHAN - 1024 No. of detector channels in dataset
PHAVERSN - 1.1.0 OGIP FITS version number
STAT_ERR - FALSE Statistical Error
SYS_ERR - TRUE Fractional Systematic Error
QUALITY - TRUE Quality Flag
GROUPING - FALSE Grouping Flag
--------------------------------------------------------------------
--------------------------------------------------------------------
minchan(nocom) 61
maxchan(nocom) 170
numchan(nocom) 110
minchan(nocom) 171
maxchan(nocom) 425
numchan(nocom) 255
minchan(nocom) 426
maxchan(nocom) 594
numchan(nocom) 169
minchan(nocom) 595
maxchan(nocom) 848
numchan(nocom) 254
...... exiting, changes written to file : 74033000_gis3_4_ch.pha
** grppha 2.9.0 completed successfully
gnt_infrm: Creating efficiency map for gis3...
ASCAEFFMAP vers 2.27 5 May 1999.
bethick : /FTP/caldb/data/asca/gis/bcf/s3bev1.fits
grid : /FTP/caldb/data/asca/gis/bcf/s3gridv3.fits
xrtrsp : /FTP/caldb/data/asca/xrt/bcf/xrt_ea_v2_0.fits
240 grouped channels from the PHA file
Bin size is 0.2500 (mm) = 0.2456(arcmin)
Optical axis is 119.36 134.44
WMAP size is 54 x 54
WMAP offset is 83 88
WMAP bin factor is 1
1024 ungrouped channels from the RMF file
pha bin = 62, E = 0.719 - 2.016 keV ( 1 / 4) calculating ...
<efficiency> = 69.14973 weight = 5.8732359E-03
pha bin = 63, E = 2.016 - 5.022 keV ( 2 / 4) calculating ...
<efficiency> = 79.22887 weight = 4.6916567E-03
pha bin = 64, E = 5.022 - 7.014 keV ( 3 / 4) calculating ...
<efficiency> = 70.30865 weight = 1.4685827E-03
pha bin = 65, E = 7.014 - 10.008 keV ( 4 / 4) calculating ...
<efficiency> = 26.06132 weight = 2.4972390E-03
wrote /tproc/nandra/processing/74033000/work/74033000_gis3.effmap
gnt_infrm: Creating exposure map for sis0...
instfile=/tproc/nandra/processing/74033000/work/74033000_sis0.effmap
ASCAEXPO_V0.9b
reading data file: /tproc/nandra/processing/74033000/work/74033000_sis0.evt
reading gti ext: STDGTI
reading hp ext: HOT_PIXELS
querying CALDB...
reading cal file: /FTP/caldb/data/asca/sis/bcf/s0_teldef_070294.fits
reading inst file: /tproc/nandra/processing/74033000/work/74033000_sis0.effm
making an inst map...
SIS AREA DISC ENABL OFF
CHIP: 0 1 2 3
CCD POWER ON/OFF: ON ON OFF OFF
AREA DISC IN/OUT: OUT OUT IN IN
AREA DISC H START: 6 6 6 316
AREA DISC H STOP: 425 425 200 425
AREA DISC V START: 2 2 2 2
AREA DISC V STOP: 422 422 150 112
multiply inst map...
reading att file: /tproc/nandra/processing/74033000/aux/fa951216_0434.0250
making a sky image...
writing sky image: /tproc/nandra/processing/74033000/work/74033000_sis0_sky_
making an exposure map...
Aspect RA/DEC/ROLL : 267.2530 68.6241 155.3170
Mean RA/DEC/ROLL : 267.2377 68.6466 155.3170
Pnt RA/DEC/ROLL : 267.5100 68.7147 155.3170
Image rebin factor : 1
Attitude Records : 26165
Hot Pixels : 129
GTI intervals : 57
Total GTI (secs) : 32031.787
Max attitude excursion (arcsecs) : 15.000
0 Percent Complete: Total/live time: 0.00 0.00
10 Percent Complete: Total/live time: 6080.00 6080.00
20 Percent Complete: Total/live time: 26829.57 26829.57
30 Percent Complete: Total/live time: 26829.57 26829.57
40 Percent Complete: Total/live time: 32026.07 32026.07
50 Percent Complete: Total/live time: 32026.07 32026.07
60 Percent Complete: Total/live time: 32026.60 32026.60
70 Percent Complete: Total/live time: 32026.60 32026.60
80 Percent Complete: Total/live time: 32027.12 32027.12
90 Percent Complete: Total/live time: 32027.12 32027.12
100 Percent Complete: Total/live time: 32031.77 32031.77
Number of attitude steps used: 16
Number of attitude steps avail: 25266
Mean RA/DEC pixel offset: 420.2253 10.0134
writing expo file: /tproc/nandra/processing/74033000/work/74033000_sis0_raw.
closing attitude file...
closing data file...
gnt_infrm: Creating exposure map for sis1...
instfile=/tproc/nandra/processing/74033000/work/74033000_sis1.effmap
ASCAEXPO_V0.9b
reading data file: /tproc/nandra/processing/74033000/work/74033000_sis1.evt
reading gti ext: STDGTI
reading hp ext: HOT_PIXELS
querying CALDB...
reading cal file: /FTP/caldb/data/asca/sis/bcf/s1_teldef_070294.fits
reading inst file: /tproc/nandra/processing/74033000/work/74033000_sis1.effm
making an inst map...
SIS AREA DISC ENABL OFF
CHIP: 0 1 2 3
CCD POWER ON/OFF: OFF OFF ON ON
AREA DISC IN/OUT: OUT OUT OUT OUT
AREA DISC H START: 6 6 6 6
AREA DISC H STOP: 425 425 425 425
AREA DISC V START: 2 2 2 2
AREA DISC V STOP: 422 422 422 422
multiply inst map...
reading att file: /tproc/nandra/processing/74033000/aux/fa951216_0434.0250
making a sky image...
writing sky image: /tproc/nandra/processing/74033000/work/74033000_sis1_sky_
making an exposure map...
Aspect RA/DEC/ROLL : 267.2530 68.6241 155.2978
Mean RA/DEC/ROLL : 267.2170 68.6326 155.2978
Pnt RA/DEC/ROLL : 267.5308 68.7287 155.2978
Image rebin factor : 1
Attitude Records : 26165
Hot Pixels : 122
GTI intervals : 78
Total GTI (secs) : 31156.166
Max attitude excursion (arcsecs) : 15.000
0 Percent Complete: Total/live time: 0.00 0.00
10 Percent Complete: Total/live time: 6016.00 6016.00
20 Percent Complete: Total/live time: 26081.95 26081.95
30 Percent Complete: Total/live time: 26081.95 26081.95
40 Percent Complete: Total/live time: 31150.45 31150.45
50 Percent Complete: Total/live time: 31150.45 31150.45
60 Percent Complete: Total/live time: 31150.97 31150.97
70 Percent Complete: Total/live time: 31150.97 31150.97
80 Percent Complete: Total/live time: 31151.50 31151.50
90 Percent Complete: Total/live time: 31151.50 31151.50
100 Percent Complete: Total/live time: 31156.15 31156.15
Number of attitude steps used: 16
Number of attitude steps avail: 25234
Mean RA/DEC pixel offset: 415.7812 81.8635
writing expo file: /tproc/nandra/processing/74033000/work/74033000_sis1_raw.
closing attitude file...
closing data file...
gnt_infrm: Creating exposure map for gis2...
instfile=/tproc/nandra/processing/74033000/work/74033000_gis2.effmap
ASCAEXPO_V0.9b
reading data file: /tproc/nandra/processing/74033000/work/74033000_gis2.evt
reading gti ext: STDGTI
querying CALDB...
reading cal file: /FTP/caldb/data/asca/gis/bcf/gis2_ano_on_flf_180295.fits
reading inst file: /tproc/nandra/processing/74033000/work/74033000_gis2.effm
making an inst map...
rebin gis: 1
multiply inst map...
reading att file: /tproc/nandra/processing/74033000/aux/fa951216_0434.0250
making a sky image...
writing sky image: /tproc/nandra/processing/74033000/work/74033000_gis2_sky_
making an exposure map...
Aspect RA/DEC/ROLL : 267.2530 68.6241 155.2746
Mean RA/DEC/ROLL : 267.1913 68.6392 155.2746
Pnt RA/DEC/ROLL : 267.5736 68.7258 155.2746
Image rebin factor : 1
Attitude Records : 26165
GTI intervals : 50
Total GTI (secs) : 34379.617
Max attitude excursion (arcsecs) : 15.000
0 Percent Complete: Total/live time: 0.00 0.00
10 Percent Complete: Total/live time: 21065.92 21065.92
20 Percent Complete: Total/live time: 21065.92 21065.92
30 Percent Complete: Total/live time: 22513.61 22513.61
40 Percent Complete: Total/live time: 22513.61 22513.61
50 Percent Complete: Total/live time: 32221.38 32221.38
60 Percent Complete: Total/live time: 32221.38 32221.38
70 Percent Complete: Total/live time: 34373.90 34373.90
80 Percent Complete: Total/live time: 34373.90 34373.90
90 Percent Complete: Total/live time: 34374.43 34374.43
100 Percent Complete: Total/live time: 34379.62 34379.62
Number of attitude steps used: 16
Number of attitude steps avail: 24935
Mean RA/DEC pixel offset: 39.2225 8.0651
writing expo file: /tproc/nandra/processing/74033000/work/74033000_gis2_raw.
closing attitude file...
closing data file...
gnt_infrm: Creating exposure map for gis3...
instfile=/tproc/nandra/processing/74033000/work/74033000_gis3.effmap
ASCAEXPO_V0.9b
reading data file: /tproc/nandra/processing/74033000/work/74033000_gis3.evt
reading gti ext: STDGTI
querying CALDB...
reading cal file: /FTP/caldb/data/asca/gis/bcf/gis3_ano_on_flf_180295.fits
reading inst file: /tproc/nandra/processing/74033000/work/74033000_gis3.effm
making an inst map...
rebin gis: 1
multiply inst map...
reading att file: /tproc/nandra/processing/74033000/aux/fa951216_0434.0250
making a sky image...
writing sky image: /tproc/nandra/processing/74033000/work/74033000_gis3_sky_
making an exposure map...
Aspect RA/DEC/ROLL : 267.2530 68.6241 155.3293
Mean RA/DEC/ROLL : 267.2498 68.6266 155.3293
Pnt RA/DEC/ROLL : 267.5146 68.7384 155.3293
Image rebin factor : 1
Attitude Records : 26165
GTI intervals : 53
Total GTI (secs) : 35469.617
Max attitude excursion (arcsecs) : 15.000
0 Percent Complete: Total/live time: 0.00 0.00
10 Percent Complete: Total/live time: 22187.92 22187.92
20 Percent Complete: Total/live time: 22187.92 22187.92
30 Percent Complete: Total/live time: 23619.61 23619.61
40 Percent Complete: Total/live time: 23619.61 23619.61
50 Percent Complete: Total/live time: 33311.38 33311.38
60 Percent Complete: Total/live time: 33311.38 33311.38
70 Percent Complete: Total/live time: 35463.90 35463.90
80 Percent Complete: Total/live time: 35463.90 35463.90
90 Percent Complete: Total/live time: 35464.43 35464.43
100 Percent Complete: Total/live time: 35469.62 35469.62
Number of attitude steps used: 16
Number of attitude steps avail: 24935
Mean RA/DEC pixel offset: 51.3012 9.2650
writing expo file: /tproc/nandra/processing/74033000/work/74033000_gis3_raw.
closing attitude file...
closing data file...
gnt_infrm: ========================
gnt_infrm: End of procedure do_expo
gnt_infrm: ========================
Fri Apr 28 05:12:37 EDT 2000
gnt_infrm: *************************
gnt_infrm: Running procedure do_lcvs
gnt_infrm: *************************
Fri Apr 28 05:12:37 EDT 2000
gnt_infrm: Making lightcurves with 3 binsizes and 3 energy bands...
gnt_infrm: Time ordering...
gnt_infrm: Source, full-band, 16s bin, SIS/GIS...
nbint = 4829
gnt_infrm: Command...
lcurve nser=1 cfile1=@/tproc/nandra/processing/74033000/work/lcvs.tmp
window=/home/rosserv/nandra/tartarus/scripts3.2/win_full2.wi dtnb=16 nbint=4829 tunits=1 clobber=yes
outfile=/tproc/nandra/processing/74033000/work/74033000_sis_src_16s.flc rescale=2.0 plot=no
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_src.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1294 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_sis1_src.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 994 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS1
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 78 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.3617E-01 Chisq 1981. Var 0.1173E-02 Newbs. 1911
Min 0.000 Max 0.2188 expVar 0.1131E-02 Bins 2289
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_src_16s
nbint = 4818
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis2_src.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1266 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS2
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 50 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_gis3_src.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1541 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS3
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 53 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 0.50000000 (s)
for Maximum Newbin No.. 154145
Default Newbin Time is: 150.70788 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4818
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4818 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4818 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:26: 1
Ser.1 Avg 0.4006E-01 Chisq 2147. Var 0.1272E-02 Newbs. 2114
Min 0.000 Max 0.2188 expVar 0.1253E-02 Bins 2808
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis_src_16s
gnt_infrm: Source, full-band, 256/5760s bin, SIS/GIS...
nbint = 302
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis_src_16s.f
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1911 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699178 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4828
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 256.00000 (s)
Maximum Newbin No. 302
Default Newbins per Interval are: 302
(giving 1 Interval of 302 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 302 Newbins of 256.000 (s)
302 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:25: 5
Ser.1 Avg 0.7196E-01 Chisq 79.93 Var 0.2960E-03 Newbs. 76
Min 0.4297E-01 Max 0.1250 expVar 0.2815E-03 Bins 1911
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_src_256
nbint = 302
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis_src_16s.f
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.171
No. of Rows ....... 2114 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834688713 (days) 2:50:25:171 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4817
Default Newbin Time is: 150.70786 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 256.00000 (s)
Maximum Newbin No. 302
Default Newbins per Interval are: 302
(giving 1 Interval of 302 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 302 Newbins of 256.000 (s)
302 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:28: 1
Ser.1 Avg 0.8146E-01 Chisq 111.9 Var 0.3459E-03 Newbs. 103
Min 0.3125E-01 Max 0.1289 expVar 0.3185E-03 Bins 2114
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis_src_256
nbint = 14
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis_src_16s.f
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1911 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699178 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4828
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 5760.0000 (s)
Maximum Newbin No. 14
Default Newbins per Interval are: 14
(giving 1 Interval of 14 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 14 Newbins of 5760.00 (s)
14 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 6:10:57
Ser.1 Avg 0.7179E-01 Chisq 5.039 Var 0.2648E-04 Newbs. 13
Min 0.6250E-01 Max 0.8306E-01expVar 0.6429E-04 Bins 1911
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_src_576
nbint = 14
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis_src_16s.f
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.171
No. of Rows ....... 2114 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834688713 (days) 2:50:25:171 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4817
Default Newbin Time is: 150.70786 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 5760.0000 (s)
Maximum Newbin No. 14
Default Newbins per Interval are: 14
(giving 1 Interval of 14 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 14 Newbins of 5760.00 (s)
14 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 6:13:53
Ser.1 Avg 0.7867E-01 Chisq 4.903 Var 0.5570E-04 Newbs. 13
Min 0.5515E-01 Max 0.8684E-01expVar 0.4984E-04 Bins 2114
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis_src_576
gnt_infrm: Source, soft-band, 16s/5760s bin, SIS...
nbint = 4829
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_src_soft
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 753 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_sis1_src_soft
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 564 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS1
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 78 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.2080E-01 Chisq 2006. Var 0.6834E-03 Newbs. 1911
Min-0.3125E-01 Max 0.1562 expVar 0.6510E-03 Bins 1318
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_src_16s
nbint = 14
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis_src_16s_s
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1911 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699178 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4828
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 5760.0000 (s)
Maximum Newbin No. 14
Default Newbins per Interval are: 14
(giving 1 Interval of 14 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 14 Newbins of 5760.00 (s)
14 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 6:10:57
Ser.1 Avg 0.4222E-01 Chisq 3.473 Var 0.1175E-04 Newbs. 13
Min 0.3763E-01 Max 0.4974E-01expVar 0.4076E-04 Bins 1911
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_src_576
gnt_infrm: Source, hard-band, 16s/5760s bin, SIS/GIS...
nbint = 4829
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_src_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 542 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_sis1_src_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 431 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS1
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 78 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.1539E-01 Chisq 1941. Var 0.4894E-03 Newbs. 1911
Min 0.000 Max 0.1250 expVar 0.4819E-03 Bins 974
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_src_16s
nbint = 14
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis_src_16s_h
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1911 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699178 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4828
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 5760.0000 (s)
Maximum Newbin No. 14
Default Newbins per Interval are: 14
(giving 1 Interval of 14 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 14 Newbins of 5760.00 (s)
14 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 6:10:57
Ser.1 Avg 0.2959E-01 Chisq 10.59 Var 0.2384E-04 Newbs. 13
Min 0.2083E-01 Max 0.3988E-01expVar 0.2355E-04 Bins 1911
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_src_576
nbint = 4818
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis2_src_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 752 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS2
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 50 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_gis3_src_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 866 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS3
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 53 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 0.50000000 (s)
for Maximum Newbin No.. 154145
Default Newbin Time is: 150.70788 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4818
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4818 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4818 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:26: 1
Ser.1 Avg 0.2296E-01 Chisq 2154. Var 0.7318E-03 Newbs. 2114
Min 0.000 Max 0.1875 expVar 0.7183E-03 Bins 1619
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis_src_16s
nbint = 14
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis_src_16s_h
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.171
No. of Rows ....... 2114 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834688713 (days) 2:50:25:171 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4817
Default Newbin Time is: 150.70786 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 5760.0000 (s)
Maximum Newbin No. 14
Default Newbins per Interval are: 14
(giving 1 Interval of 14 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 14 Newbins of 5760.00 (s)
14 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 6:13:53
Ser.1 Avg 0.4590E-01 Chisq 4.189 Var 0.9073E-05 Newbs. 13
Min 0.3878E-01 Max 0.5053E-01expVar 0.3272E-04 Bins 2114
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis_src_576
gnt_infrm: Background, full-band, 16s/5760s bin, SIS/GIS...
nbint = 4829
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_bgd.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 323 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_sis1_bgd.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 310 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS1
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 78 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.1001E-01 Chisq 1818. Var 0.2984E-03 Newbs. 1911
Min-0.3125E-01 Max 0.1250 expVar 0.3138E-03 Bins 634
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_bgd_16s
nbint = 14
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis_bgd_16s.f
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1911 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699178 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4828
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 5760.0000 (s)
Maximum Newbin No. 14
Default Newbins per Interval are: 14
(giving 1 Interval of 14 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 14 Newbins of 5760.00 (s)
14 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 6:10:57
Ser.1 Avg 0.2065E-01 Chisq 7.012 Var 0.1546E-04 Newbs. 13
Min 0.1439E-01 Max 0.3061E-01expVar 0.2057E-04 Bins 1911
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_bgd_576
nbint = 4818
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis2_bgd.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 2689 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS2
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 50 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_gis3_bgd.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 3487 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS3
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 53 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 0.50000000 (s)
for Maximum Newbin No.. 154145
Default Newbin Time is: 150.70788 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4818
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4818 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4818 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:26: 1
Ser.1 Avg 0.8846E-01 Chisq 2164. Var 0.2831E-02 Newbs. 2114
Min 0.000 Max 0.3438 expVar 0.2765E-02 Bins 6177
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis_bgd_16s
nbint = 14
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis_bgd_16s.f
Selected FITS extensions: 1 - RATE TABLE;
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `RATE ` Stop Time (d) ..... 10068 02:50:25.171
No. of Rows ....... 2114 Bin Time (s) ...... 16.00
Right Ascension ... Internal time sys.. Literal
Declination ....... Experiment ........
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 3- Y-axis; 4- Y-error; 5- Fractional exposure;
File contains binned data.
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834688713 (days) 2:50:25:171 (h:m:s:ms)
Minimum Newbin Time 16.000000 (s)
for Maximum Newbin No.. 4817
Default Newbin Time is: 150.70786 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 5760.0000 (s)
Maximum Newbin No. 14
Default Newbins per Interval are: 14
(giving 1 Interval of 14 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 14 Newbins of 5760.00 (s)
14 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 6:13:53
Ser.1 Avg 0.1783 Chisq 4.853 Var 0.5426E-04 Newbs. 13
Min 0.1640 Max 0.1931 expVar 0.1255E-03 Bins 2114
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis_bgd_576
gnt_infrm: Background, soft-band, 16s bin, SIS...
nbint = 4829
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_bgd_soft
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 179 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_sis1_bgd_soft
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 163 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS1
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 78 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.5396E-02 Chisq 1894. Var 0.1681E-03 Newbs. 1911
Min-0.3125E-01 Max 0.9375E-01expVar 0.1697E-03 Bins 343
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_bgd_16s
gnt_infrm: Background, hard-band, 16s bin, SIS/GIS...
nbint = 4829
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_bgd_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 144 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_sis1_bgd_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 147 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS1
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 78 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 151.05201 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.4595E-02 Chisq 1862. Var 0.1409E-03 Newbs. 1911
Min-0.3125E-01 Max 0.6250E-01expVar 0.1446E-03 Bins 292
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis_bgd_16s
nbint = 4818
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis2_bgd_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1458 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS2
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 50 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Series 1 file 2:/tproc/nandra/processing/74033000/work/74033000_gis3_bgd_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1821 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS3
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 53 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
**** Warning : Infiles for series 1 overlap in time
Having > 1 intv or using time winds. might cause data loss !
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 0.50000000 (s)
for Maximum Newbin No.. 154145
Default Newbin Time is: 150.70788 (s) (to have 1 Intv. of 512 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4818
Default Newbins per Interval are: 512
(giving 10 Intervals of 512 Newbins each)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4818 Newbins of 16.0000 (s)
**** Warning: All results and errors will be multiplied by 2.000000
4818 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:26: 1
Ser.1 Avg 0.4699E-01 Chisq 2102. Var 0.1461E-02 Newbs. 2114
Min 0.000 Max 0.2500 expVar 0.1469E-02 Bins 3280
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis_bgd_16s
gnt_infrm: ========================
gnt_infrm: End of procedure do_lcvs
gnt_infrm: ========================
Fri Apr 28 05:12:56 EDT 2000
gnt_infrm: *************************
gnt_infrm: Running procedure do_cols
gnt_infrm: *************************
Fri Apr 28 05:12:57 EDT 2000
gnt_infrm: Determine countrates for sis0 and sis1 in 2 energy bands...
gnt_infrm: Determining scaling factor...
gnt_infrm: Calculating values...
gnt_infrm: Countrate for SIS full-band...
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_bgd.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 323 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 8.0000000 (s) (to have 1 Intv. of 9657 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 4829
(giving 1 Interval of 4829 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.1007E-01 Chisq 1933. Var 0.6150E-03 Newbs. 1979
Min 0.000 Max 0.1250 expVar 0.6297E-03 Bins 323
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis0_bgd_16
gnt_infrm: Countrate for SIS soft-band...
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_bgd_soft
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 179 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 8.0000000 (s) (to have 1 Intv. of 9657 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 4829
(giving 1 Interval of 4829 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.5590E-02 Chisq 1959. Var 0.3457E-03 Newbs. 1979
Min 0.000 Max 0.1250 expVar 0.3494E-03 Bins 179
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis0_bgd_16
gnt_infrm: Countrate for SIS hard-band...
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_sis0_bgd_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:22:57.180
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 144 Bin Time (s) ...... 8.000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA SIS0
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 7- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:22:57.180
No. of Rows ....... 57 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Expected Start ... 10067.22427291948 (days) 5:22:57:180 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 8.0000000 (s)
for Maximum Newbin No.. 9657
Default Newbin Time is: 8.0000000 (s) (to have 1 Intv. of 9657 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4829
Default Newbins per Interval are: 4829
(giving 1 Interval of 4829 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4829 Newbins of 16.0000 (s)
4829 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:23: 5
Ser.1 Avg 0.4485E-02 Chisq 1949. Var 0.2760E-03 Newbs. 1979
Min 0.000 Max 0.1250 expVar 0.2803E-03 Bins 144
Writing output file: /tproc/nandra/processing/74033000/work/74033000_sis0_bgd_16
gnt_infrm: Countrate for GIS full-band...
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis2_bgd.evt
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 2689 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS2
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 50 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 0.50000000 (s)
for Maximum Newbin No.. 154145
Default Newbin Time is: 7.7076634 (s) (to have 1 Intv. of 10000 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4818
Default Newbins per Interval are: 4818
(giving 1 Interval of 4818 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4818 Newbins of 16.0000 (s)
4818 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:26: 1
Ser.1 Avg 0.7818E-01 Chisq 2109. Var 0.4862E-02 Newbs. 2120
Min 0.000 Max 0.3750 expVar 0.4887E-02 Bins 2689
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis2_bgd_16
gnt_infrm: Countrate for GIS hard-band...
lcurve 1.0 (xronos5.16)
Series 1 file 1:/tproc/nandra/processing/74033000/work/74033000_gis2_bgd_hard
Selected FITS extensions: 1 - RATE TABLE; 2 - GTIs
Source ............ MRK507 Start Time (d) .... 10067 05:25:53.171
FITS Extension .... 1 - `EVENTS ` Stop Time (d) ..... 10068 02:50:25.180
No. of Rows ....... 1458 Bin Time (s) ...... 0.5000
Right Ascension ... 2.6725E+02 Internal time sys.. Converted to TJD
Declination ....... 6.8624E+01 Experiment ........ ASCA GIS2
Filter ............ NONE
Corrections applied: Vignetting - No ; Deadtime - No ; Bkgd - No ; Clock - No
Selected Columns: 1- Time; 4- E-Channel;
File contains arrival-time data.
FITS Extension .... 2 - `STDGTI ` First GTI Start ... 10067 05:25:53.171
No. of Rows ....... 50 Last GTI Stop ..... 10068 02:50:25.180
Selected Columns: 1 - GTI Start; 2 - GTI Stop
Expected Start ... 10067.22630985185 (days) 5:25:53:171 (h:m:s:ms)
Expected Stop .... 10068.11834699355 (days) 2:50:25:180 (h:m:s:ms)
Minimum Newbin Time 0.50000000 (s)
for Maximum Newbin No.. 154145
Default Newbin Time is: 7.7076634 (s) (to have 1 Intv. of 10000 Newbins)
Type INDEF to accept the default value
Newbin Time ...... 16.000000 (s)
Maximum Newbin No. 4818
Default Newbins per Interval are: 4818
(giving 1 Interval of 4818 Newbins)
Type INDEF to accept the default value
Maximum of 1 Intvs. with 4818 Newbins of 16.0000 (s)
4818 analysis results per interval
1% completed
2% completed
3% completed
4% completed
5% completed
6% completed
7% completed
8% completed
9% completed
10% completed
11% completed
12% completed
13% completed
14% completed
15% completed
16% completed
17% completed
18% completed
19% completed
20% completed
21% completed
22% completed
23% completed
24% completed
25% completed
26% completed
27% completed
28% completed
29% completed
30% completed
31% completed
32% completed
33% completed
34% completed
35% completed
36% completed
37% completed
38% completed
39% completed
40% completed
41% completed
42% completed
43% completed
44% completed
45% completed
46% completed
47% completed
48% completed
49% completed
50% completed
51% completed
52% completed
53% completed
54% completed
55% completed
56% completed
57% completed
58% completed
59% completed
60% completed
61% completed
62% completed
63% completed
64% completed
65% completed
66% completed
67% completed
68% completed
69% completed
70% completed
71% completed
72% completed
73% completed
74% completed
75% completed
76% completed
77% completed
78% completed
79% completed
80% completed
81% completed
82% completed
83% completed
84% completed
85% completed
86% completed
87% completed
88% completed
89% completed
90% completed
91% completed
92% completed
93% completed
94% completed
95% completed
96% completed
97% completed
98% completed
99% completed
100% completed
Intv 1 Start 10067 5:26: 1
Ser.1 Avg 0.4234E-01 Chisq 2184. Var 0.2726E-02 Newbs. 2120
Min 0.000 Max 0.3750 expVar 0.2646E-02 Bins 1458
Writing output file: /tproc/nandra/processing/74033000/work/74033000_gis2_bgd_16
gnt_infrm: ========================
gnt_infrm: End of procedure do_cols
gnt_infrm: ========================
Fri Apr 28 05:13:04 EDT 2000
[1] 30185
gnt_infrm: Starting do_kill - checking for infinite xspec loop...
gnt_infrm: *************************
gnt_infrm: Running procedure do_fits
gnt_infrm: *************************
Fri Apr 28 05:13:05 EDT 2000
gnt_infrm: Performing spectral fitting to a powerlaw...
Xspec 11.0.1 05:13:12 28-Apr-2000
http://xspec.gsfc.nasa.gov/
Plot device not set, use "cpd" to set it
Type "help" or "?" for further information
XSPEC>@plfit.xcm
!XSPEC> set xs_return_result 1;
!XSPEC> open fit_result_pl.dat w
!XSPEC> set fileid [open fit_result_pl.dat w];
!XSPEC> log plfit.log;
!XSPEC> data 1:1 74033000_sis0_src_20;
Net count rate (cts/s) for file 1 2.1249E-02+/- 2.0519E-03( 49.8% total)
using response (RMF) file... 74033000_sis0.rmf
using auxiliary (ARF) file... 74033000_sis0.arf
using background file... 74033000_sis0_bgd.pha
1 data set is in use
!XSPEC> data 2:2 74033000_sis1_src_20;
Net count rate (cts/s) for file 2 1.7701E-02+/- 1.7821E-03( 52.0% total)
using response (RMF) file... 74033000_sis1.rmf
using auxiliary (ARF) file... 74033000_sis1.arf
using background file... 74033000_sis1_bgd.pha
2 data sets are in use
!XSPEC> data 3:3 74033000_gis2_src_20;
Net count rate (cts/s) for file 3 4.1038E-03+/- 1.3262E-03( 10.5% total)
using response (RMF) file... 74033000_gis2.rmf
using auxiliary (ARF) file... 74033000_gis2.arf
using background file... 74033000_gis2_bgd.pha
3 data sets are in use
!XSPEC> data 4:4 74033000_gis3_src_20;
Net count rate (cts/s) for file 4 1.7530E-03+/- 1.3883E-03( 3.9% total)
using response (RMF) file... 74033000_gis3.rmf
using auxiliary (ARF) file... 74033000_gis3.arf
using background file... 74033000_gis3_bgd.pha
4 data sets are in use
!XSPEC> ignore bad;
!XSPEC> ignore 1-4:0.1-0.6;
!XSPEC> ignore 1-4:10.0-20.0;
!XSPEC> ignore 1-4:5.0-7.5;
!XSPEC> setplot energy;
!XSPEC> query no;
Querying disabled - assuming answer is no
!XSPEC> model con*wabs*po ;1.0,-1, 0,0,1,1 ;0.0, 0.02,0,0,10000,10000 ;2.,0.2,-1,- ...
Model: constant[1]*wabs[2]( powerlaw[3] )
!Param# 1 : 1.0,-1, 0,0,1,1
!Param# 2 : 0.0, 0.02,0,0,10000,10000
!Param# 3 : 2.,0.2,-1,-1,3,3
!Param# 4 : .001,.0002,0,0,1e4,1e4
!Param# 5 : 0.99,0.01,0,0,2,2
!Param# 6 : =2
Equating parameter powerlaw:nH to parameter wabs:nH * 1
!Param# 7 : =3
Equating parameter constant:PhoIndex to parameter powerlaw:PhoIndex * 1
!Param# 8 : =4
Equating parameter wabs:norm to parameter constant:norm * 1
!Param# 9 : 0.99,0.01,0,0,2,2
!Param# 10 : =2
Equating parameter constant:nH to parameter wabs:nH * 1
!Param# 11 : =3
Equating parameter wabs:PhoIndex to parameter powerlaw:PhoIndex * 1
!Param# 12 : =4
Equating parameter powerlaw:norm to parameter constant:norm * 1
!Param# 13 : 0.99,0.01,0,0,2,2
!Param# 14 : =2
Equating parameter :nH to parameter wabs:nH * 1
!Param# 15 : =3
Equating parameter :PhoIndex to parameter powerlaw:PhoIndex * 1
!Param# 16 : =4
Equating parameter :norm to parameter constant:norm * 1
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Model: constant[1]*wabs[2]( powerlaw[3] )
Model Fit Model Component Parameter Unit Value Data
par par comp group
1 1 1 constant factor 1.000 frozen 1
2 2 2 wabs nH 10^22 0.000 +/- 0.000 1
3 3 3 powerlaw PhoIndex 2.000 +/- 0.000 1
4 4 3 powerlaw norm 1.0000E-03 +/- 0.000 1
5 5 4 constant factor 0.9900 +/- 0.000 2
6 2 5 wabs nH 10^22 0.000 = par 2 2
7 3 6 powerlaw PhoIndex 2.000 = par 3 2
8 4 6 powerlaw norm 1.0000E-03 = par 4 2
9 6 7 constant factor 0.9900 +/- 0.000 3
10 2 8 wabs nH 10^22 0.000 = par 2 3
11 3 9 powerlaw PhoIndex 2.000 = par 3 3
12 4 9 powerlaw norm 1.0000E-03 = par 4 3
13 7 10 constant factor 0.9900 +/- 0.000 4
14 2 11 wabs nH 10^22 0.000 = par 2 4
15 3 12 powerlaw PhoIndex 2.000 = par 3 4
16 4 12 powerlaw norm 1.0000E-03 = par 4 4
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Chi-Squared = 19551.94 using 194 PHA bins.
Reduced chi-squared = 103.9997 for 188 degrees of freedom
Null hypothesis probability = 0.00
!XSPEC> fit 25;
Chi-Squared Lvl Fit param # 1 2 3 4
5 6 7
299.353 -2 1.000 0.1674 0.8056 1.1763E-04
1.002 0.3691 0.2820
182.875 -3 1.000 0.1896 1.311 1.3733E-04
1.006 0.3533 0.2423
175.266 -4 1.000 0.3092 1.694 1.7993E-04
1.005 0.3012 0.1775
174.545 -5 1.000 0.3347 1.726 1.9175E-04
1.003 0.2673 0.1440
174.497 -6 1.000 0.3377 1.730 1.9388E-04
1.003 0.2636 0.1400
174.493 -7 1.000 0.3380 1.729 1.9410E-04
1.003 0.2632 0.1394
---------------------------------------------------------------------------
Variances and Principal axes :
2 3 4 5 6 7
7.52E-11 | 0.00 0.00 1.00 0.00 0.00 0.00
3.13E-03 | 0.92 -0.40 0.00 -0.01 0.04 0.04
9.88E-02 | 0.40 0.92 0.00 0.01 0.00 0.00
9.26E-03 | 0.03 0.00 0.00 -0.66 -0.73 -0.16
6.13E-03 | -0.04 0.02 0.00 -0.32 0.08 0.94
7.21E-03 | -0.02 0.01 0.00 -0.68 0.68 -0.29
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Model: constant[1]*wabs[2]( powerlaw[3] )
Model Fit Model Component Parameter Unit Value Data
par par comp group
1 1 1 constant factor 1.000 frozen 1
2 2 2 wabs nH 10^22 0.3380 +/- 0.1348 1
3 3 3 powerlaw PhoIndex 1.729 +/- 0.2893 1
4 4 3 powerlaw norm 1.9410E-04 +/- 0.5069E-04 1
5 5 4 constant factor 1.003 +/- 0.8948E-01 2
6 2 5 wabs nH 10^22 0.3380 = par 2 2
7 3 6 powerlaw PhoIndex 1.729 = par 3 2
8 4 6 powerlaw norm 1.9410E-04 = par 4 2
9 6 7 constant factor 0.2632 +/- 0.9108E-01 3
10 2 8 wabs nH 10^22 0.3380 = par 2 3
11 3 9 powerlaw PhoIndex 1.729 = par 3 3
12 4 9 powerlaw norm 1.9410E-04 = par 4 3
13 7 10 constant factor 0.1394 +/- 0.7932E-01 4
14 2 11 wabs nH 10^22 0.3380 = par 2 4
15 3 12 powerlaw PhoIndex 1.729 = par 3 4
16 4 12 powerlaw norm 1.9410E-04 = par 4 4
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Chi-Squared = 174.4933 using 194 PHA bins.
Reduced chi-squared = 0.9281558 for 188 degrees of freedom
Null hypothesis probability = 0.752
!XSPEC> tclout param 2;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par2 [string trim $xspec_tclout];
!XSPEC> tclout param 3;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par3 [string trim $xspec_tclout];
!XSPEC> tclout param 4;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par4 [string trim $xspec_tclout];
!XSPEC> tclout dof;
!XSPEC> string trim $xspec_tclout
!XSPEC> set dof [string trim $xspec_tclout];
!XSPEC> regsub -all { +} $par2 { } cpar2;
!XSPEC> split $cpar2
!XSPEC> set lpar2 [split $cpar2];
!XSPEC> regsub -all { +} $par3 { } cpar3;
!XSPEC> split $cpar3
!XSPEC> set lpar3 [split $cpar3];
!XSPEC> regsub -all { +} $par4 { } cpar4;
!XSPEC> split $cpar4
!XSPEC> set lpar4 [split $cpar4];
!XSPEC> regsub -all { +} $dof { } cpar5;
!XSPEC> split $cpar5
!XSPEC> set lpar5 [split $cpar5];
!XSPEC> lindex $lpar2 0
!XSPEC> set nh [lindex $lpar2 0];
!XSPEC> lindex $lpar3 0
!XSPEC> set gamma [lindex $lpar3 0];
!XSPEC> lindex $lpar4 0
!XSPEC> set norm [lindex $lpar4 0];
!XSPEC> lindex $lpar5 0
!XSPEC> set dof [lindex $lpar5 0];
!XSPEC> show fit
Chi-Squared = 174.4933 using 194 PHA bins.
Reduced chi-squared = 0.9281558 for 188 degrees of freedom
Null hypothesis probability = 0.752
!XSPEC> set chisq [show fit];
!XSPEC> error max 15 4.61 2
Parameter Confidence Range ( 4.610)
Minimization may have run into a problem, check your result
2 8.052036E-02 0.683220
!XSPEC> set str [error max 15 4.61 2];
!XSPEC> lindex $str 0
!XSPEC> set nhlo [lindex $str 0];
!XSPEC> lindex $str 1
!XSPEC> set nhhi [lindex $str 1];
!XSPEC> expr ($nhhi - $nhlo)/2.0
!XSPEC> set nh_err [expr ($nhhi - $nhlo)/2.0];
!XSPEC> error max 15 4.61 3
Parameter Confidence Range ( 4.610)
3 1.24024 2.30355
!XSPEC> set str [error max 15 4.61 3];
!XSPEC> lindex $str 0
!XSPEC> set glo [lindex $str 0];
!XSPEC> lindex $str 1
!XSPEC> set ghi [lindex $str 1];
!XSPEC> expr ($ghi - $glo)/2.0
!XSPEC> set g_err [expr ($ghi - $glo)/2.0];
!XSPEC> puts $fileid "$nh $nh_err $gamma $g_err $norm $chisq $dof";
!XSPEC> close $fileid;
!XSPEC> notice 1-4:5.0-7.5;
A total of 31 more channels will be noticed
Net count rate (cts/s) for file 1 2.0568E-02+/- 1.5238E-03( 52.8% total)
using response (RMF) file... 74033000_sis0.rmf
using auxiliary (ARF) file... 74033000_sis0.arf
using background file... 74033000_sis0_bgd.pha
Net count rate (cts/s) for file 2 1.6678E-02+/- 1.2866E-03( 54.5% total)
using response (RMF) file... 74033000_sis1.rmf
using auxiliary (ARF) file... 74033000_sis1.arf
using background file... 74033000_sis1_bgd.pha
Net count rate (cts/s) for file 3 4.1878E-03+/- 1.1981E-03( 11.6% total)
using response (RMF) file... 74033000_gis2.rmf
using auxiliary (ARF) file... 74033000_gis2.arf
using background file... 74033000_gis2_bgd.pha
Net count rate (cts/s) for file 4 3.0961E-03+/- 1.2849E-03( 7.3% total)
using response (RMF) file... 74033000_gis3.rmf
using auxiliary (ARF) file... 74033000_gis3.arf
using background file... 74033000_gis3_bgd.pha
Chi-Squared = 198.2365 using 225 PHA bins.
Reduced chi-squared = 0.9051893 for 219 degrees of freedom
Null hypothesis probability = 0.840
!XSPEC> ignore bad;
Chi-Squared = 198.2365 using 225 PHA bins.
Reduced chi-squared = 0.9051893 for 219 degrees of freedom
Null hypothesis probability = 0.840
!XSPEC> save all 74033000_webfit;
!XSPEC> show files;
Information for file 1
belonging to plot group 1, data group 1
telescope = ASCA , instrument = SIS0 , channel type = PI
Current data file : 74033000_sis0_src_20.pha
with integration time 3.2032E+04
effective area 1.000
selected region area 6.1201E-02
Background file : 74033000_sis0_bgd.pha
with integration time 3.2032E+04
and effective area 1.000
selected region area 3.1787E-02
No current correction
Response (RMF) file : 74033000_sis0.rmf
Auxiliary (ARF) file : 74033000_sis0.arf
Weighting method is standard
Information for file 2
belonging to plot group 2, data group 2
telescope = ASCA , instrument = SIS1 , channel type = PI
Current data file : 74033000_sis1_src_20.pha
with integration time 3.1156E+04
effective area 1.000
selected region area 5.6377E-02
Background file : 74033000_sis1_bgd.pha
with integration time 3.1156E+04
and effective area 1.000
selected region area 3.7510E-02
No current correction
Response (RMF) file : 74033000_sis1.rmf
Auxiliary (ARF) file : 74033000_sis1.arf
Weighting method is standard
Information for file 3
belonging to plot group 3, data group 3
telescope = ASCA , instrument = GIS2 , channel type = PI
Current data file : 74033000_gis2_src_20.pha
with integration time 3.4380E+04
effective area 1.000
selected region area 3.6636E-02
Background file : 74033000_gis2_bgd.pha
with integration time 3.4380E+04
and effective area 1.000
selected region area 8.7402E-02
No current correction
Response (RMF) file : 74033000_gis2.rmf
Auxiliary (ARF) file : 74033000_gis2.arf
Weighting method is standard
Information for file 4
belonging to plot group 4, data group 4
telescope = ASCA , instrument = GIS3 , channel type = PI
Current data file : 74033000_gis3_src_20.pha
with integration time 3.5470E+04
effective area 1.000
selected region area 3.6636E-02
Background file : 74033000_gis3_bgd.pha
with integration time 3.5470E+04
and effective area 1.000
selected region area 8.7402E-02
No current correction
Response (RMF) file : 74033000_gis3.rmf
Auxiliary (ARF) file : 74033000_gis3.arf
Weighting method is standard
!XSPEC> setplot command ma 17 on 2;
!XSPEC> setplot command la t Energy spectrum;
!XSPEC> setplot command la y Counts;
!XSPEC> setplot command time off;
!XSPEC> setplot command cs 1.3;
!XSPEC> setplot command h web_pha.gif/gif;
!XSPEC> plot ldata ratio;
!XSPEC> ignore 1-4:5.0-7.5;
Chi-Squared = 174.4933 using 194 PHA bins.
Reduced chi-squared = 0.9281558 for 188 degrees of freedom
Null hypothesis probability = 0.752
!XSPEC> query no;
Querying disabled - assuming answer is no
!XSPEC> model con*(wabs*po+wabs*po) ;1.0,-1, 0,0,1,1 ;0.03, 0.005,0,0,10,10 ;3.,0. ...
Model: constant[1]( wabs[2]( powerlaw[3] ) + wabs[4]( powerlaw[5] ) )
!Param# 1 : 1.0,-1, 0,0,1,1
!Param# 2 : 0.03, 0.005,0,0,10,10
!Param# 3 : 3.,0.05,1.5,1.5,5,5
!Param# 4 : .001,.0002,0,0,1e4,1e4
!Param# 5 : 1.0,0.01,0,0,1e5,1e5
!Param# 6 : 2.,0.05,-1,-1,3,3
!Param# 7 : .001,.0002,0,0,1e4,1e4
!Param# 8 : 0.99,0.01,0,0,2,2
!Param# 9 : =2
Equating parameter wabs:nH to parameter wabs:nH * 1
!Param# 10 : =3
Equating parameter powerlaw:PhoIndex to parameter powerlaw:PhoIndex * 1
!Param# 11 : =4
Equating parameter constant:norm to parameter wabs:norm * 1
!Param# 12 : =5
Equating parameter wabs:nH to parameter powerlaw:nH * 1
!Param# 13 : =6
Equating parameter powerlaw:PhoIndex to parameter constant:PhoIndex * 1
!Param# 14 : =7
Equating parameter wabs:norm to parameter wabs:norm * 1
!Param# 15 : 0.99,0.01,0,0,2,2
!Param# 16 : =2
Equating parameter constant:nH to parameter wabs:nH * 1
!Param# 17 : =3
Equating parameter wabs:PhoIndex to parameter powerlaw:PhoIndex * 1
!Param# 18 : =4
Equating parameter powerlaw:norm to parameter wabs:norm * 1
!Param# 19 : =5
Equating parameter wabs:nH to parameter powerlaw:nH * 1
!Param# 20 : =6
Equating parameter powerlaw:PhoIndex to parameter constant:PhoIndex * 1
!Param# 21 : =7
Equating parameter :norm to parameter wabs:norm * 1
!Param# 22 : 0.99,0.01,0,0,2,2
!Param# 23 : =2
Equating parameter :nH to parameter wabs:nH * 1
!Param# 24 : =3
Equating parameter :PhoIndex to parameter powerlaw:PhoIndex * 1
!Param# 25 : =4
Equating parameter :norm to parameter wabs:norm * 1
!Param# 26 : =5
Equating parameter :nH to parameter powerlaw:nH * 1
!Param# 27 : =6.
Equating parameter :PhoIndex to parameter constant:PhoIndex * 1
!Param# 28 : =7
Equating parameter :norm to parameter wabs:norm * 1
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Model: constant[1]( wabs[2]( powerlaw[3] ) + wabs[4]( powerlaw[5] ) )
Model Fit Model Component Parameter Unit Value Data
par par comp group
1 1 1 constant factor 1.000 frozen 1
2 2 2 wabs nH 10^22 3.0000E-02 +/- 0.000 1
3 3 3 powerlaw PhoIndex 3.000 +/- 0.000 1
4 4 3 powerlaw norm 1.0000E-03 +/- 0.000 1
5 5 4 wabs nH 10^22 1.000 +/- 0.000 1
6 6 5 powerlaw PhoIndex 2.000 +/- 0.000 1
7 7 5 powerlaw norm 1.0000E-03 +/- 0.000 1
8 8 6 constant factor 0.9900 +/- 0.000 2
9 2 7 wabs nH 10^22 3.0000E-02 = par 2 2
10 3 8 powerlaw PhoIndex 3.000 = par 3 2
11 4 8 powerlaw norm 1.0000E-03 = par 4 2
12 5 9 wabs nH 10^22 1.000 = par 5 2
13 6 10 powerlaw PhoIndex 2.000 = par 6 2
14 7 10 powerlaw norm 1.0000E-03 = par 7 2
15 9 11 constant factor 0.9900 +/- 0.000 3
16 2 12 wabs nH 10^22 3.0000E-02 = par 2 3
17 3 13 powerlaw PhoIndex 3.000 = par 3 3
18 4 13 powerlaw norm 1.0000E-03 = par 4 3
19 5 14 wabs nH 10^22 1.000 = par 5 3
20 6 15 powerlaw PhoIndex 2.000 = par 6 3
21 7 15 powerlaw norm 1.0000E-03 = par 7 3
22 10 16 constant factor 0.9900 +/- 0.000 4
23 2 17 wabs nH 10^22 3.0000E-02 = par 2 4
24 3 18 powerlaw PhoIndex 3.000 = par 3 4
25 4 18 powerlaw norm 1.0000E-03 = par 4 4
26 5 19 wabs nH 10^22 1.000 = par 5 4
27 6 20 powerlaw PhoIndex 2.000 = par 6 4
28 7 20 powerlaw norm 1.0000E-03 = par 7 4
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Chi-Squared = 23879.51 using 194 PHA bins.
Reduced chi-squared = 129.0784 for 185 degrees of freedom
Null hypothesis probability = 0.00
!XSPEC> chatter 0;
!XSPEC> fit 100;
!XSPEC> chatter 10;
!XSPEC> fit 100;
Chi-Squared Lvl Fit param # 1 2 3 4
5 6 7 8 9
10
173.253 0 1.000 9.1488E-09 4.995 1.2836E-05
0.5366 1.893 2.4122E-04 1.004 0.2530
0.1314
---------------------------------------------------------------------------
Variances and Principal axes :
2 3 4 5 6 7 8 9 10
1.11E-10 | 0.00 0.00 0.73 0.00 0.00 0.68 0.00 0.00 0.00
2.19E-10 | 0.00 0.00 -0.68 0.00 0.00 0.73 0.00 0.00 0.00
7.85E-03 | -0.01 0.00 0.00 0.07 -0.05 0.00 -0.34 0.10 0.93
9.44E-03 | -0.08 0.02 0.00 0.76 -0.60 0.00 0.23 -0.04 -0.01
9.13E-03 | -0.02 0.00 0.00 0.15 -0.11 0.00 -0.68 0.63 -0.33
1.16E-02 | 0.01 0.00 0.00 -0.09 0.06 0.00 0.61 0.77 0.15
1.63E-01 | -0.21 0.03 0.00 0.59 0.78 0.00 0.01 0.00 0.00
7.76E+00 | 0.97 -0.12 0.00 0.20 0.11 0.00 0.00 0.00 0.00
2.15E+04 | 0.12 0.99 0.00 -0.01 0.00 0.00 0.00 0.00 0.00
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Model: constant[1]( wabs[2]( powerlaw[3] ) + wabs[4]( powerlaw[5] ) )
Model Fit Model Component Parameter Unit Value Data
par par comp group
1 1 1 constant factor 1.000 frozen 1
2 2 2 wabs nH 10^22 9.1488E-09 +/- 18.10 1
3 3 3 powerlaw PhoIndex 4.995 +/- 145.7 1
4 4 3 powerlaw norm 1.2836E-05 +/- 0.2031E-03 1
5 5 4 wabs nH 10^22 0.5366 +/- 1.627 1
6 6 5 powerlaw PhoIndex 1.893 +/- 0.4549 1
7 7 5 powerlaw norm 2.4122E-04 +/- 0.1301E-03 1
8 8 6 constant factor 1.004 +/- 0.9985E-01 2
9 2 7 wabs nH 10^22 9.1488E-09 = par 2 2
10 3 8 powerlaw PhoIndex 4.995 = par 3 2
11 4 8 powerlaw norm 1.2836E-05 = par 4 2
12 5 9 wabs nH 10^22 0.5366 = par 5 2
13 6 10 powerlaw PhoIndex 1.893 = par 6 2
14 7 10 powerlaw norm 2.4122E-04 = par 7 2
15 9 11 constant factor 0.2530 +/- 0.1029 3
16 2 12 wabs nH 10^22 9.1488E-09 = par 2 3
17 3 13 powerlaw PhoIndex 4.995 = par 3 3
18 4 13 powerlaw norm 1.2836E-05 = par 4 3
19 5 14 wabs nH 10^22 0.5366 = par 5 3
20 6 15 powerlaw PhoIndex 1.893 = par 6 3
21 7 15 powerlaw norm 2.4122E-04 = par 7 3
22 10 16 constant factor 0.1314 +/- 0.8985E-01 4
23 2 17 wabs nH 10^22 9.1488E-09 = par 2 4
24 3 18 powerlaw PhoIndex 4.995 = par 3 4
25 4 18 powerlaw norm 1.2836E-05 = par 4 4
26 5 19 wabs nH 10^22 0.5366 = par 5 4
27 6 20 powerlaw PhoIndex 1.893 = par 6 4
28 7 20 powerlaw norm 2.4122E-04 = par 7 4
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Chi-Squared = 173.2530 using 194 PHA bins.
Reduced chi-squared = 0.9365025 for 185 degrees of freedom
Null hypothesis probability = 0.722
!XSPEC> notice 1-4:5.0-7.5;
A total of 31 more channels will be noticed
Net count rate (cts/s) for file 1 2.0568E-02+/- 1.5238E-03( 52.8% total)
using response (RMF) file... 74033000_sis0.rmf
using auxiliary (ARF) file... 74033000_sis0.arf
using background file... 74033000_sis0_bgd.pha
Net count rate (cts/s) for file 2 1.6678E-02+/- 1.2866E-03( 54.5% total)
using response (RMF) file... 74033000_sis1.rmf
using auxiliary (ARF) file... 74033000_sis1.arf
using background file... 74033000_sis1_bgd.pha
Net count rate (cts/s) for file 3 4.1878E-03+/- 1.1981E-03( 11.6% total)
using response (RMF) file... 74033000_gis2.rmf
using auxiliary (ARF) file... 74033000_gis2.arf
using background file... 74033000_gis2_bgd.pha
Net count rate (cts/s) for file 4 3.0961E-03+/- 1.2849E-03( 7.3% total)
using response (RMF) file... 74033000_gis3.rmf
using auxiliary (ARF) file... 74033000_gis3.arf
using background file... 74033000_gis3_bgd.pha
Chi-Squared = 198.2839 using 225 PHA bins.
Reduced chi-squared = 0.9179811 for 216 degrees of freedom
Null hypothesis probability = 0.801
!XSPEC> ignore bad;
Chi-Squared = 198.2839 using 225 PHA bins.
Reduced chi-squared = 0.9179811 for 216 degrees of freedom
Null hypothesis probability = 0.801
!XSPEC> save all 74033000_2plfit;
!XSPEC> open fit_result_flux.dat w
!XSPEC> set fileid [open fit_result_flux.dat w];
!XSPEC> flux 0.5 2.0
Model flux 1.3722E-04 photons ( 2.3764E-13 ergs)cm**-2 s**-1 ( 0.500- 2.000) DtSet : 1
Model flux 1.3778E-04 photons ( 2.3862E-13 ergs)cm**-2 s**-1 ( 0.500- 2.000) DtSet : 2
Model flux 3.4727E-05 photons ( 6.0138E-14 ergs)cm**-2 s**-1 ( 0.500- 2.000) DtSet : 3
Model flux 1.8037E-05 photons ( 3.1236E-14 ergs)cm**-2 s**-1 ( 0.500- 2.000) DtSet : 4
!XSPEC> set flux1 [flux 0.5 2.0];
!XSPEC> flux 2.0 10.0
Model flux 1.0321E-04 photons ( 6.9665E-13 ergs)cm**-2 s**-1 ( 2.000- 10.000) DtSet : 1
Model flux 1.0363E-04 photons ( 6.9951E-13 ergs)cm**-2 s**-1 ( 2.000- 10.000) DtSet : 2
Model flux 2.6113E-05 photons ( 1.7626E-13 ergs)cm**-2 s**-1 ( 2.000- 10.000) DtSet : 3
Model flux 1.3563E-05 photons ( 9.1552E-14 ergs)cm**-2 s**-1 ( 2.000- 10.000) DtSet : 4
!XSPEC> set flux2 [flux 2.0 10.0];
!XSPEC> lindex $flux1 1
!XSPEC> set s0_flux1 [lindex $flux1 1];
!XSPEC> lindex $flux2 1
!XSPEC> set s0_flux2 [lindex $flux2 1];
!XSPEC> puts $fileid "$s0_flux1 $s0_flux2";
!XSPEC> close $fileid;
!XSPEC> tclout param 2;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par2 [string trim $xspec_tclout];
!XSPEC> tclout param 3;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par3 [string trim $xspec_tclout];
!XSPEC> tclout param 4;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par4 [string trim $xspec_tclout];
!XSPEC> tclout param 5;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par5 [string trim $xspec_tclout];
!XSPEC> tclout param 6;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par6 [string trim $xspec_tclout];
!XSPEC> tclout param 7;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par7 [string trim $xspec_tclout];
!XSPEC> tclout dof;
!XSPEC> string trim $xspec_tclout
!XSPEC> set par8 [string trim $xspec_tclout];
!XSPEC> regsub -all { +} $par2 { } cpar2;
!XSPEC> split $cpar2
!XSPEC> set lpar2 [split $cpar2];
!XSPEC> regsub -all { +} $par3 { } cpar3;
!XSPEC> split $cpar3
!XSPEC> set lpar3 [split $cpar3];
!XSPEC> regsub -all { +} $par4 { } cpar4;
!XSPEC> split $cpar4
!XSPEC> set lpar4 [split $cpar4];
!XSPEC> regsub -all { +} $par5 { } cpar5;
!XSPEC> split $cpar5
!XSPEC> set lpar5 [split $cpar5];
!XSPEC> regsub -all { +} $par6 { } cpar6;
!XSPEC> split $cpar6
!XSPEC> set lpar6 [split $cpar6];
!XSPEC> regsub -all { +} $par7 { } cpar7;
!XSPEC> split $cpar7
!XSPEC> set lpar7 [split $cpar7];
!XSPEC> regsub -all { +} $par8 { } cpar8;
!XSPEC> split $cpar8
!XSPEC> set lpar8 [split $cpar8];
!XSPEC> lindex $lpar2 0
!XSPEC> set nhs [lindex $lpar2 0];
!XSPEC> lindex $lpar3 0
!XSPEC> set gs [lindex $lpar3 0];
!XSPEC> lindex $lpar4 0
!XSPEC> set norms [lindex $lpar4 0];
!XSPEC> lindex $lpar5 0
!XSPEC> set nhh [lindex $lpar5 0];
!XSPEC> lindex $lpar6 0
!XSPEC> set gh [lindex $lpar6 0];
!XSPEC> lindex $lpar7 0
!XSPEC> set normh [lindex $lpar7 0];
!XSPEC> show fit
Chi-Squared = 198.2839 using 225 PHA bins.
Reduced chi-squared = 0.9179811 for 216 degrees of freedom
Null hypothesis probability = 0.801
!XSPEC> set chisq [show fit];
!XSPEC> error max 15 4.61 2
Parameter Confidence Range ( 4.610)
Chi-Squared when model parameter 2= 0.000
is 196.5415, which is < previous minimum 198.2839
(critical delta = 0.0100)
!XSPEC> set str [error max 15 4.61 2];
!XSPEC> lindex $str 0
!XSPEC> set nhs_lo [lindex $str 0];
!XSPEC> lindex $str 1
!XSPEC> set nhs_hi [lindex $str 1];
!XSPEC> expr ($nhs_hi - $nhs_lo)/2.0
XSPEC>exit
XSPEC: quit
gnt_infrm: ========================
gnt_infrm: End of procedure do_fits
gnt_infrm: ========================
Fri Apr 28 05:13:49 EDT 2000
[1] + Done /home/rosserv/nandra/tartarus/scripts3.2/do_kill ...
gnt_infrm: *************************
gnt_infrm: Running procedure do_mosa
gnt_infrm: *************************
Fri Apr 28 05:13:49 EDT 2000
gnt_infrm: Creating the exposure corrected sky image and sky images...
[1] 30872
Executing: /usr/local/saord/bin.linux/SAOtng -title SAO042800044274033000 -xrm *cmapDir1:/usr/local/saord/Colormaps/ -xrm *port:-1 -xrm *geometry:+5+5 -xrm *errorlog:SAO042800044274033000_error.log
Welcome to SAOtng 1.9.1
Setting current scaling limits: data
Setting current scale: linear
Resetting zoom factor: 2 centered at: 256.5,256.5
Setting current scale: log
gnt_infrm: Making sis0 detector image...
Received new filename '/tproc/nandra/processing/74033000/work/74033000_sis0_det.img'
No WCS information available for image '/tproc/nandra/processing/74033000/work/74033000_sis0_det.img'
Display of image '/tproc/nandra/processing/74033000/work/74033000_sis0_det.img' complete!
Setting current scaling limits: data
Display of image '/tproc/nandra/processing/74033000/work/74033000_sis0_det.img' complete!
Setting current scaling limits: user 1 13
Display of image '/tproc/nandra/processing/74033000/work/74033000_sis0_det.img' complete!
Executing GIF creation command '(/usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' colormap display > /tmp/saotng.lut; /usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' display_data | /usr/local/saord/bin.linux/fits2gif -luts /tmp/saotng.lut > /tproc/nandra/processing/74033000/work/74033000_sis0.gif; echo "GIF file created!" | /usr/local/saord/bin.linux/xpaset SAO042800044274033000 message) &'
Destroying image '74033000_sis0_det.img-30881'
gnt_infrm: Making sis1 detector image...
Received new filename '/tproc/nandra/processing/74033000/work/74033000_sis1_det.img'
No WCS information available for image '/tproc/nandra/processing/74033000/work/74033000_sis1_det.img'
Display of image '/tproc/nandra/processing/74033000/work/74033000_sis1_det.img' complete!
Setting current scaling limits: data
Display of image '/tproc/nandra/processing/74033000/work/74033000_sis1_det.img' complete!
Setting current scaling limits: user 1 15
Display of image '/tproc/nandra/processing/74033000/work/74033000_sis1_det.img' complete!
Executing GIF creation command '(/usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' colormap display > /tmp/saotng.lut; /usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' display_data | /usr/local/saord/bin.linux/fits2gif -luts /tmp/saotng.lut > /tproc/nandra/processing/74033000/work/74033000_sis1.gif; echo "GIF file created!" | /usr/local/saord/bin.linux/xpaset SAO042800044274033000 message) &'
Destroying image '74033000_sis1_det.img-30881'
gnt_infrm: Making gis2 detector image...
Received new filename '/tproc/nandra/processing/74033000/work/74033000_gis2_det.img'
No WCS information available for image '/tproc/nandra/processing/74033000/work/74033000_gis2_det.img'
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis2_det.img' complete!
Setting current scaling limits: data
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis2_det.img' complete!
Setting current scaling limits: user 1 15
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis2_det.img' complete!
Executing GIF creation command '(/usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' colormap display > /tmp/saotng.lut; /usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' display_data | /usr/local/saord/bin.linux/fits2gif -luts /tmp/saotng.lut > /tproc/nandra/processing/74033000/work/74033000_gis2.gif; echo "GIF file created!" | /usr/local/saord/bin.linux/xpaset SAO042800044274033000 message) &'
Destroying image '74033000_gis2_det.img-30881'
gnt_infrm: Making gis3 detector image...
Received new filename '/tproc/nandra/processing/74033000/work/74033000_gis3_det.img'
No WCS information available for image '/tproc/nandra/processing/74033000/work/74033000_gis3_det.img'
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis3_det.img' complete!
Setting current scaling limits: data
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis3_det.img' complete!
Setting current scaling limits: user 1 21
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis3_det.img' complete!
Executing GIF creation command '(/usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' colormap display > /tmp/saotng.lut; /usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' display_data | /usr/local/saord/bin.linux/fits2gif -luts /tmp/saotng.lut > /tproc/nandra/processing/74033000/work/74033000_gis3.gif; echo "GIF file created!" | /usr/local/saord/bin.linux/xpaset SAO042800044274033000 message) &'
Destroying image '74033000_gis3_det.img-30881'
gnt_infrm: Adding images for the SIS...
gnt_infrm:adding and smoothing
gnt_infrm: Adding images for the GIS...
****** successfully exited ******
****** successfully exited ******
gnt_infrm: Making web page image with target marker...
Setting current colormap: Heat
Received new filename '/tproc/nandra/processing/74033000/work/74033000_gis_sky_sm.img'
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis_sky_sm.img' complete!
circle(267.1600d,68.7044d,10.0)
Setting current scaling limits: data
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis_sky_sm.img' complete!
Setting current scaling limits: user 1 16.5245
Display of image '/tproc/nandra/processing/74033000/work/74033000_gis_sky_sm.img' complete!
Executing GIF creation command '(/usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' colormap display > /tmp/saotng.lut; /usr/local/saord/bin.linux/xpaget 'SAO042800044274033000' display_data | /usr/local/saord/bin.linux/fits2gif -luts /tmp/saotng.lut > /tproc/nandra/processing/74033000/work/74033000_gis_sky_sm.gif; echo "GIF file created!" | /usr/local/saord/bin.linux/xpaset SAO042800044274033000 message) &'
gnt_infrm: ========================
gnt_infrm: End of procedure do_mosa
gnt_infrm: ========================
Fri Apr 28 05:15:43 EDT 2000
XPA$ERROR no 'xpaset' access points match template: 04_28_00.04:42
gnt_infrm: *************************
gnt_infrm: Running procedure do_html
gnt_infrm: *************************
Fri Apr 28 05:15:43 EDT 2000
gnt_infrm: Creating the web page for sequence 74033000...
gnt_infrm: Setting all variables...
spectrum
spectrum: /tproc/nandra/processing/74033000/work/web_pha.gif
lightcurve
lightcurve: /tproc/nandra/processing/74033000/work/74033000_sis_src_5760s.flc
sky image
sky image: /tproc/nandra/processing/74033000/work/74033000_gis_sky_sm.gif
countrate
All done!
countrate: 0.0380 0.0343 0.0230 0.0150 0.0059 0.0065
general info (.evt)
centroid
datamode
ccdmode
bitfix
spectral fit
gnt_warng(html): File fit_result_2pl.dat does not exist
warning
fatal
sds
name
object
version
gnt_infrm: Making veron.96 table...
gnt_infrm: Making images for the web page...
pha
flc
gnt_infrm: Creating the web page...
gnt_infrm: Creating the download web page...
gnt_infrm: Writing an entry into browse.table...
gnt_infrm: ========================
gnt_infrm: End of procedure do_html
gnt_infrm: ========================
Fri Apr 28 05:16:00 EDT 2000
gnt_infrm: *************************
gnt_infrm: Running procedure do_tran
gnt_infrm: *************************
Fri Apr 28 05:16:00 EDT 2000
gnt_infrm: Copying the files to the database (universe)...
gnt_infrm: Transferring web page files to html area...
(remove /www/tartarus/restricted/html/74033000)
(create /www/tartarus/restricted/html/74033000)
(set permissions)
74033000.html
74033000_gis_sky_sm.gif
74033000_flc.gif
74033000_pha.gif
74033000_sis0.gif
74033000_sis1.gif
74033000_gis2.gif
74033000_gis3.gif
veron96.txt
gnt_infrm: Tarring selected files...
74033000.tar ...
74033000_spectral.tar ...
gnt_infrm: Gzipping the tar files...
gnt_infrm: Transferring tar files to ftp area...
(remove /www/tartarus/restricted/ftp/74033000/*.tar)
gnt_infrm: Removing tar files, attitude file(s), raw exposure maps and raw sky images...
gnt_infrm: Gzipping all files in /tproc/nandra/processing/74033000/work/...
gnt_infrm: ========================
gnt_infrm: End of procedure do_tran
gnt_infrm: ========================
Fri Apr 28 05:17:34 EDT 2000
gnt_infrm: ========================
gnt_infrm: End of procedure do_proc
gnt_infrm: ========================
Fri Apr 28 05:17:35 EDT 2000
gnt_infrm: *************************
gnt_infrm: Running procedure do_rslt
gnt_infrm: *************************
Fri Apr 28 05:17:37 EDT 2000
gnt_infrm: Quality control procedure...
gnt_infrm: Finding warng/error/fatal messages...
down up up
gnt_infrm: Updating the web pages...
gnt_infrm: Updating sequence index...
gnt_infrm: Transferring web page and sum,log files...
rm: No match.
rm: No match.
| en |
all-txt-docs | 902196 | FPUS61 KALY 100214
SFTNY
NYZ026>066-082>084-101714-
TABULAR STATE FORECAST FOR NEW YORK
NATIONAL WEATHER SERVICE ALBANY NEW YORK
1014 PM EDT THU SEP 9 2004
ROWS INCLUDE...
DAILY PREDOMINANT DAYTIME WEATHER 6AM-6PM
FORECAST TEMPERATURES...EARLY MORNING LOW/DAYTIME HIGH
PROBABILITY OF PRECIPITATION 6AM-6PM
- INDICATES TEMPERATURES BELOW ZERO
MM INDICATES MISSING DATA
FCST FCST FCST FCST FCST FCST FCST
FRI SAT SUN MON TUE WED THU
SEP 10 SEP 11 SEP 12 SEP 13 SEP 14 SEP 15 SEP 16
...CENTRAL NEW YORK.....
BINGHAMTON, NY
PTCLDY SUNNY MOCLDY PTCLDY SUNNY PTCLDY PTCLDY
57/74 52/78 57/73 45/65 43/68 50/72 56/75
POP 10 POP 0 POP 40 POP 0 POP 0 POP 0 POP 0
...EAST CENTRAL NEW YORK.....
ALBANY, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY SUNNY PTCLDY
60/77 56/77 55/74 49/68 44/71 50/77 55/77
POP 20 POP 0 POP 30 POP 10 POP 0 POP 10 POP 20
COBLESKILL, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY SUNNY PTCLDY
56/73 51/76 51/73 44/64 42/72 50/76 53/77
POP 20 POP 0 POP 30 POP 10 POP 0 POP 10 POP 20
GLOVERSVILLE, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY SUNNY PTCLDY
56/74 52/77 52/73 45/65 41/70 49/77 53/77
POP 30 POP 0 POP 30 POP 10 POP 0 POP 10 POP 20
SARATOGA SPGS, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY SUNNY PTCLDY
59/76 52/75 52/73 46/68 40/70 49/77 52/77
POP 20 POP 0 POP 30 POP 10 POP 0 POP 10 POP 20
TANNERSVILLE, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY PTCLDY PTCLDY
55/71 50/73 49/71 44/64 42/71 48/74 52/75
POP 20 POP 0 POP 20 POP 10 POP 0 POP 10 POP 20
...NORTHEAST NEW YORK.....
GLENS FALLS, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY SUNNY PTCLDY
60/73 50/74 50/73 45/67 40/71 47/76 50/77
POP 30 POP 0 POP 30 POP 10 POP 0 POP 10 POP 20
MASSENA, NY
PTCLDY SUNNY PTCLDY PTCLDY SUNNY SUNNY PTCLDY
55/70 48/74 54/72 45/64 45/73 47/75 50/76
POP 10 POP 0 POP 30 POP 10 POP 0 POP 0 POP 20
SARANAC LAKE, NY
PTCLDY SUNNY PTCLDY PTCLDY SUNNY SUNNY PTCLDY
53/67 43/72 47/69 40/61 35/70 42/72 45/73
POP 20 POP 0 POP 30 POP 10 POP 0 POP 0 POP 20
SPECULATOR, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY SUNNY PTCLDY
52/68 47/74 49/70 40/63 40/71 45/75 51/75
POP 30 POP 0 POP 30 POP 10 POP 0 POP 10 POP 20
...SOUTHEAST NEW YORK.....
KINGSTON, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY PTCLDY PTCLDY
60/77 54/76 53/76 49/72 45/71 50/76 55/81
POP 20 POP 0 POP 20 POP 10 POP 0 POP 10 POP 20
POUGHKEEPSIE, NY
PTCLDY SUNNY PTCLDY SUNNY SUNNY PTCLDY PTCLDY
61/78 54/77 53/78 51/74 48/73 53/76 54/83
POP 10 POP 0 POP 10 POP 10 POP 0 POP 10 POP 20
$$
| en |
markdown | 862879 | # Presentation: 862879
## Analysis of Defects and Their Causes in Bulk Aluminum Nitride Crystals J.H. Edgar, Kansas State University, DMR-0408874
- Aluminum nitride crystals are being developed as substrates for group III-nitride semiconductor devices such as short wavelength (ultraviolet and blue) light emitting diodes, laser diodes and high power-high frequency electronics. In this research, the effects of process conditions and impurities on the types and densities of defects in the aluminum nitride crystals are being established. Using oxidation and etching, the distribution of the defects is determined, and in collaboration with J. Chaudhuri at Texas Tech University, the defects are being identified. Oxygen is a common impurity that creates point defects that can coalesce and form larger, extended defects. By identifying the types, distributions, and root causes of defects in the AlN crystals, processing strategies for making more perfect crystals can be developed. For example, the AlN can be purified, sintered, and compacted by partially subliming the source before commencing crystal growth. This greatly reduces the oxygen concentration in the source (by >50 times) and increases the final grain size.
- 25 mm dia, 8 mm thick AlN boule seeded on tungsten, and grown by sublimation.
- Etch pits formed at defects on an aluminum nitride crystal. The area is 75 μm x 50 μm.
**Notes:**
Notes Applications of short wavelength emitters and detectors include sensors for biological and chemical toxins and ultraviolet water sterilization. Applications of high frequency –high power electronics include cell phone base stations.
Explanations The left hand image is a polycrystalline AlN boule seeded on tungsten, approximately 25 mm in diameter and 8 mm thick. The dark color is due to point defects – most likely Al vacancies, and impurities, of which oxygen is present in the highest concentrations. These two types of defects are commonly present together as oxygen incorporation increase the Al vacancy concentration to maintain system charge neutrality.
The right hand image is a scanning electron micrograph of an AlN facet after it has been oxidized and subsequently etched in molten potassium hydroxide. Etching is selective at the defect. Work is underway to identify the type of defect at the etch pit.
The paper accepted for publication is: Thermal oxidation of polycrystalline and single crystalline aluminum nitride wafers, Z. Gu, J.H. Edgar, S.A. Speakman, D. Blom, J. Perrin, and J.Chaudhuri, accepted for publication in J. Electron. Mater.
Significance By identifying the types, distributions, and root causes of defects in the AlN crystals, processing strategies for making more perfect crystals can be developed. For example, the AlN can be purified, sintered, and compacted by partially subliming the source before commencing crystal growth. This greatly reduces the oxygen concentration in the source (by >50 times) and increases the final grain size.
Future plans Currently, the maximum grain size in our polycrystalline boules is approximately 3 mm in diameter, with an etch pit density on the order of 105 cm-2. Further source purification should make larger crystals possible, probably grains up to 10 mm in diameter with defect densities of 104 cm-2 using the current furnace.
Such crystals would be sufficiently large enough to make prototype devices. Defect densities on the order of 104 cm-2 would be a factor of 104 to 105 less than what is currently available. This should be particularly beneficial for improving the efficiency and maximum power possible for AlN-rich AlGaN light emitting diodes and laser diodes operating in the sub 300 nm wavelength regime. Lower defect densities are expected to result in more unform material properties and more reproducible device fabrication.
Additional plans include examining the changes in the lattice parameters of AlN caused by the incorporation of oxygen, carbon, and silicon, and identifying specific types of defects by TEM.
## Analysis of Defects and Their Causes in Bulk Aluminum Nitride Crystals J.H. Edgar, Kansas State University, DMR-0408874
- Fifteen 7th and 8th grade girls participated in the workshop *Crystals and Crystal Growth* as part of their participation in project GROW: G*irls Researching Our World*. This program is designed to encourage girls to consider science, technology, engineering, and mathematics as education options. They learned how symmetry, habit, and facets distinguish crystals from other materials. They constructed polyhedrons to illustrate different crystal symmetries. They examined a variety of simple crystals, to determine their basic structure.
- Undergraduate student Megan Winter developed procedures to grow crystals from simple, readily available chemicals in aqueous solutions. The procedures can be used for teaching K-12 students about the properties of crystals and illustrating methods of crystal growth.
- Education and Outreach
- Crystals with different
- symmetries grown from
- solution to illustrate the
- fundamental properties
- of crystals.
**Notes:**
Fifteen 7th and 8th grade girls participated in the workshop on crystals and crystal growth. The essential features of the crystals, such as their symmetry, crystal habits, common reoccurring angles, regular features, and flat, smooth facets were pointed out. The girls constructed three-dimensional tetrahedrons, cubes, octahedrons, and hexagons out of construction paper to illustrate the different types of common symmetries found in crystals. They examined several crystals (potassium alum, chrome alum, sodium chlorate, and potassium ferricyanide) under a microscope to identify the crystal symmetry group to which they belong. Nucleation and crystal growth were observed by preparing saturated aqueous solutions which were allowed to evaporate. The applications of crystals in industry (electronics, pharmaceutics, and chemical commodities) were described. The girls were given recipes for growing rock candy that they could try at home.
Natalie Lewis, a middle school science and mathematics teacher from the Kansas City school district helped with this activity.
The figure shows three types of crystals grown by evaporation from aqueous solutions. They are (from top to bottom) chrome alum (purple) potassium ferricyanide (red), and nickel sulfate (green). | en |
converted_docs | 561532 | {width="5.973611111111111in"
height="0.4576388888888889in"}
13_030303_CLN_01.doc
***TO: DISTRIBUTION***
***FROM: C NEUMEYER***
***SUBJECT: TF FLAG JOINT FORCES AND LOAD PATHS***
This memo provides rough estimates of in-plane forces on the TF flags
and evaluates the various load paths. It is intended to provide guidance
for the initial sizing of the various mechanical components of the
joint. Finite element analysis presently underway will provide more
accurate information for finalizing the design.
*Forces and Load Paths*
A schematic of a inner tier flag associated with an outer layer turn is
shown in the following figure.
{width="5.990972222222222in"
height="4.757638888888889in"}
A description of the forces and load paths is as follows:
F~em1~: Vertical EM force generated on the flag. Assumed to include
JxB~t~ contribution from both flag halves, along with attractive force
between the flags in the two tiers. Inner flag half assumed to carry 3x
current of outer flag half. Force on each conductor assumed equal to
Jx(B~self~/2 + B~ext~). Here B~self~ is the self-field and B~ext~ is the
field produced by the other conductors, including those from both the 24
and 12 turn tiers. The effective radius at which the force is applied is
that where the field is at its average value along the length in
question.
F~em2~: Vertical EM force generated on linkage between flags and outer
legs, consisting of solid connectors on either side of a flexible link.
Total force across link is shared between inner and outer leg
assemblies. Here it is assumed that force generated up to midpoint of
omega in flexible link is applied to inner leg assembly. Distance from
flag end to midpoint of omega is assumed to be 6". Again, forces are
based on Jx(B~self~/2 + B~ext~), and the effective radius at which the
force is applied is that where the field is at its average value along
the length in question.
F1, F2, F3, F4: These are the inward radial forces generated by the
tension in the thru-bolts.
F5: This is an additional inward radial force generated by a proposed
jack-screw arrangement which acts between the flag end and the hub disk.
F6: This is a downward force provided by the hub assembly via the flag
insulation, shim, hub disk, torque collar, wet lay-up, and TF ground and
turn insulation, all in series. It resists the vertical forces on the
flag as well as rotation of the flag about point X.
F7: This is an upward force provided by the hub assembly which resists
rotation of the flag about point X.
F8: This is an inward radial force which resists rotation of the flag
about point X. It acts through the flexible link.
F9: This is a downward vertical force which resists the vertical EM
forces on the flag via the frictional connection between the flag and
the inner leg conductor as well as shear of the bolts and/or pins
connected across the joint.
The EM forces on the flags and links at 6kG (71.2kA/turn) are given in
the following table.
**Summary of Forces and Moments at 6kG**
+-----------------------+----------+-----------------+-----------------+
| | F~v | dR from point | Moment |
| | ertical~ | of application | |
| | | to flag inboard | w.r.t. point X |
| | (lbs) | edge | |
| | | | (in-lbs) |
| | | (in) | |
+-----------------------+----------+-----------------+-----------------+
| Inner Tier Flag | 7380 | 4.3 | 31719 |
+-----------------------+----------+-----------------+-----------------+
| Inner Tier Link | 1855 | 13.8 | 25652 |
+-----------------------+----------+-----------------+-----------------+
| Outer Tier Flag | 1845 | 4.3 | 7930 |
+-----------------------+----------+-----------------+-----------------+
| Outer Tier Link | 464 | 13.8 | 6413 |
+-----------------------+----------+-----------------+-----------------+
| Total from All Turns | 249324 | | |
+-----------------------+----------+-----------------+-----------------+
Clearly the forces on the inner tier (associated with the 24 turn outer
layer) are much higher than the outer tier.
*Reaction of Applied Moments*
Because of the relatively high elasticity of the load paths associated
with F6, F7, and F8 they are discounted in the following discussion.
This is a worst case scenario for the bolted joint load path.
The applied moment on the flag is equal to
F~em1~\*dR~em1~+F~em2~\*dR~em2~. Assuming that F6, F7, and F8 do not
react against this moment it must be taken by F1, F2, F3, F4, and F5.
Let F5 be an input variable. Assume that the relative values of F1, F2,
F3, and F4 vary in proportion to their vertical distance z to point X.
This is based on the idea that, as the flag rotates through an angle
about point X, the elastic deformation of the bolts will be \~ zthe
associated force will be in proportion to z.
With these assumptions the values of the thru-bolt forces required to
counteract the applied moment can be estimated. Then the total tension
on the bolts is equal to the preload plus the additional force required
to react the moment.
The preload must be chosen such that, under full EM load, adequate
contact pressure is maintained. Given this requirement, the required
thru-bolt preload and peak force in the highest stressed bolt (the one
which supplies F1) can be estimated based on the assumption that the
radial force acting against the preload is equal to the applied moment
divided by the half height of the flag.
The following table shows the forces and stresses corresponding to the
case where an average contact force of 10000 lbs, equivalent to a
contact pressure of approximately 1000/5in^2^=2ksi, is maintained under
all conditions. An F5 force of 5000 lbs applied at a distance of 6"
below point X. For this case the required bolt preload is 2584 lbs.
**Inner Tier Forces and Reactions with 5000 lb. End-jack**
--------------------------------------- ---------------- ---------------
∑Applied Moments 57371.7 in-lbs
dZF1 4.750 in
dZF2 3.500 in
dZF3 2.125 in
dZF4 0.875 in
dZF5 6.000 in
F5 5000.0 lbs
F1 3242.8 lbs
F2 2389.4 lbs
F3 1450.7 lbs
F4 597.4 lbs
Bolt Preload 2584.2 lbs
Ftot1 5827.0 lbs
Ftot2 4973.7 lbs
Ftot3 4035.0 lbs
Ftot4 3181.6 lbs
∑Fr 10000.0 lbs
--------------------------------------- ---------------- ---------------
The following curve shows the required bolt preload, and the peak force
(in bolt 1) as a function of end-jack force F5.
{width="4.571527777777778in"
height="2.772222222222222in"}
The following table and curve show the results for the outer tier which
experiences considerably less force.
**Outer Tier Forces and Reactions with 0 lb. End-jack**
--------------------------------------- ---------------- ---------------
Fem1 1844.9 lbs
dRem1 4.3 in
Fem2 463.7 lbs
dRem2 13.8 in
∑Applied Moments 14342.9 in-lbs
F5 0.0 lbs
F1 1699.2 lbs
F2 1252.1 lbs
F3 760.2 lbs
F4 313.0 lbs
∑Reaction Moments 14342.9 in-lbs
Bolt Preload 2833.6 lbs
Ftot1 4532.8 lbs
Ftot2 4085.6 lbs
Ftot3 3593.7 lbs
Ftot4 3146.6 lbs
∑Fr 10000.0 lbs
--------------------------------------- ---------------- ---------------
{width="4.479861111111111in"
height="2.723611111111111in"}
*Reaction of Vertical Forces*
Two load paths are available to react the vertical loads. The first (F9)
is via shear at the interface between the flag and the inner leg
assembly, and the second (F6) is via the shims/hub assembly/torque
collar/wet lay-up/ground/turn insulation. The former is much stiffer
than the latter, so it probably takes most of the load.
The maximum force on a flag occurs on the inner tier, and is the sum of
the forces generated on the flag and on the link to the outer leg, equal
to 7379 + 1855= 9234 lbs. Assuming a contact pressure of order 10000
lbs, a coefficient of friction of 0.9234 would be required to react this
force, which is unrealistic. Therefore if most of the load has to pass
through the joint it is clear that additional shear components (shoulder
bolts, keys, etc.) are necessary.
The torque collar will end up carrying some fraction of the total load
of 249324 lbs. Additional stress is imposed on the collar wet lay-up
from the torsional load due to J~TF~ x B~rOH~. The following table
estimates the shear stress on the wet lay-up system from the combined
vertical and torsional loads, assuming that the full fraction of the
vertical load appears on the collar.
**Worst Case Forces and Reactions on Collar**
---------------------------------------- ---------------- --------------
Collar Height 3.25 in
Inner Leg Groundwall Outer Radius 3.96 in
Circumference 24.88 in
Area 80.86 in\^2
Vertical Force 249324.7 lbs
Torque 100000.0 N-m/m
8255 N-m
6088.3 ft-lbs
73060.0 in-lbs
Torsional Force 22480.0 lbs
Effective Force 250336.1 lbs
Average Shear Stress 3095.9 psi
---------------------------------------- ---------------- --------------
cc: A Brooks M Bell J Chrzanowski L Dudek
P Heitzenroeder M Kalish M Ono M Peng W Reiersen J Schmidt A VonHalle M
Williams I Zatz
| en |
log-files | 033544 | <!-- Title: 00:05:18 Mon Apr 9 2001 -->
<!-- Crewchief: JIM HUMBERT -->
<!-- Op1: JIM LOSKOT -->
<!-- Op2: -->
<!-- Op3: -->
<!-- Op4: -->
<!-- Op5: -->
<!-- Op6: -->
<!-- Notes: -->
ALL IS GOOD (SO FAR).
<!-- Date: Mon Apr 9 04:33:12 2001 -->
We attempted to repair the differential pressure level gauge on the LN2 dewar but the screws are siezed. Probably need a impact screw driver, which we do not have access to at this time.
<!-- Author: J.H. & J.L. -->
<!-- Date: Mon Apr 9 10:04:53 2001 -->
Dean replaced the liquid level gage (LI-1310-N) on LN2 dewar Tank 18 with the gage on dewar 32. It looks like someone beat on the old gage - perhaps the LN2 delivery driver smacked it to make it read better. The old gage doesn't work at all and will be given to Jerry Domoleczny to repair or replace.
<!-- Author: Sanders -->
<!-- Date: Mon Apr 9 18:37:02 2001 -->
CDF_S2 IS "HUNG" ----HEART-BEET DEAD ---- REBOOTING IN PROGRESS
<!-- Author: JL & JH -->
<!-- Comment: Mon Apr 9 18;45;05 comment by...JL &JH -->
HAD TO HIT BEBOOT BUTTON THREE TIMES (NOT ALL AT ONCE!), BEFORE IT WOULD START-UP.
| en |
markdown | 196455 | # Presentation: 196455
## Bioequivalence and Baseline Correction of Endogenous Substances Case Study: Levothyroxine Sodium Products
**Leonard Wartofsky, M.D.**
**Division of Endocrinology**
**Chairman, Department of Medicine, Washington Hospital Center**
**Clinical Professor of Medicine, Georgetown, Howard, & George Washington Universities**
**G. Richard Granneman, Ph.D.**
**Vice President, Center of Clinical Assessment, Abbott Laboratories**
**FDA Advisory Committee for Pharmaceutical Science**
**March 13, 2003**
## Bioequivalence and Baseline Correction of Endogenous Substances Case Study: Levothyroxine Sodium Products
**Leonard Wartofsky, M.D.**
**Division of Endocrinology**
**Chairman, Department of Medicine, Washington Hospital Center**
**Clinical Professor of Medicine, Georgetown, Howard, & George Washington Universities**
## Critical Scientific and Clinical Conclusions:
**Current FDA recommendations to determine bioequivalence are not sufficiently sensitive to detect small differences**
**Small differences in dosage or bioavailability have significant clinical impact, both on safety and efficacy**
## T4 is Required for the Treatment of Patients with Hypothyroidism and Thyroid Cancer
**T****4**** is the synthetic version of the naturally-occurring hormone thyroxine (T****4****)**** **
**No alternative drug is an adequate substitute **
**Virtually all patients require chronic, lifetime T****4**** treatment**
**Over 13 million Americans rely on T****4**
## Thyroid Hormone is Tightly Regulated by a Complex System, via the Exquisitely Sensitive Response of TSH
**Hypothalamus**
** ****Pituitary **
** ****Thyroid Gland**
**T****4**** **** T****3**** **
** ****Liver **
** ****Heart **
** ****Liver **
** ****Bone **
** ****CNS **
**TSH**
**T****4**
**TRH**
**Target Tissues**
**–**
## Dosage of T4 is Individualized for Safe and Effective Medical Treatment
**Physicians use TSH (thyroid stimulating hormone) to individualize the optimal T****4**** dose**
**Small changes in T****4**** dose causes significant changes in TSH levels**
**T****4**** is provided in 12 dosage strengths**
**Adjacent doses differ by as little as 9%**
## Accurate Patient Treatment Demands Controlling Both T4 and TSH Levels
**Euthyroid**
**Free-T****4**** ********0.8 – 2.7 ng/dL**
**TSH**** **** 0.4 – 4.0 μIU/mL**
**Mild hypothyroidism**
**Free-T****4**** is within the reference range**
**TSH is mildly elevated**
**Mild hyperthyroidism**
**Free-T****4**** is within the reference range**
**TSH <0.1 μIU/ml**
## Small Changes in T4 Dose Can Result in Abnormal TSH Levels
**Changes as small as 12.5 μg (~12.5%) would move many patients into mild hyperthyroidism or hypothyroidism**
*Carr D, et al, Clin Endocrin 1988; 28:325*
## Small Dosage Changes Can Result in Under- or Over-treatment, with Serious Clinical Outcomes
**Populations at greatest risk:**
**Elderly patients with cardiac disease**
**Pregnant women**
**Patients with thyroid cancer**
**Consequences of mild hypothyroidism**
**Elevated cholesterol levels**
**Atherosclerosis and myocardial infarction**
**Decreased intellectual function in the off-spring of women hypothyroid in early pregnancy**
**Consequences of mild hyperthyroidism**
**Atrial fibrillation and other arrhythmias**
## Bioequivalence and Baseline Correction of Endogenous Substances Case Study: Levothyroxine Sodium Products
**G. Richard Granneman, Ph.D.**
**Vice President, Center of Clinical Assessment, Abbott Laboratories**
## Does Bioequivalence = Therapeutic Equivalence for T4 Products?
**We fear that with current FDA criteria, this will not always be the case;**
**We expect that small differences in dosage or bioavailability will have clinical consequences**
## Key Findings of Abbott’s Study 417
**Without baseline correction, doses differing **_**<**_**33% are BE**
**All correction methods resulted in BE failure for 25% differences in dose**
**Baseline correction methods cannot distinguish doses that differ by 12.5%**
**Additional analyses, using TSH data, show significant promise of detecting 12.5% differences**
## Study 417: Designed to Assess and Compare Uncorrected and Baseline-Corrected BE
**Randomized 3-way, fasting, single dose, crossover**
**T****4**** doses (same pre-NDA lot of 50 μg tablets)**
**Washout = 44 and 53 days (**_**>**_** 6 half-lives of T****4****)**
**N=33 healthy male and female subjects evaluated for PK **
**Complete PK for Day–1 through Day 4 : T****3****, T****4****, TSH**** **
| Dose | Unit | % from 600 μg |
| --- | --- | --- |
| 600 μg | 12 • 50 μg | 0 |
| 450 μg | 9 • 50 μg | –25 |
| 400 μg | 8 • 50 μg | –33 |
## Correction Methods to Account for Endogenous T4 Levels
**Correction Methods to Account for Endogenous T****4**** Levels**
*Study M02-417*
**TSH change**
## Correction Methods and / or Goal Posts Need to Change to Ensure Bioequivalence
**Correction Methods and / or Goal Posts Need to Change to Ensure Bioequivalence **
## Simple Methods are Inadequate Because They Ignore Complex Biology
**Diurnal variation**
**p<0.001 18-hour *****vs.***** hours 0-4**
**Biologic carryover**
**Period: p=0.0001**
**Carryover: p=0.0003**
**Mean Endogenous ****T****4**** on Day–1 By Period**
*Study M02-417*
## All pathways are controlled by T3 and TSH
T4 t1/2 : 4 days in hyper
T4 t1/2 : 9 days in hypo
TSH changes exponentially with changes in free T4
In normals, T4 may be the only drug whose clearance increases when there is too much and decreases when there is not enough
**T****4**** t****1/2**** : 4 days in hyper**
**T****4**** t****1/2**** : 9 days in hypo**
**TSH changes exponentially with changes in free T****4**
**In normals, T****4**** may be the only drug whose clearance increases when there is too much and decreases when there is not enough**
- Plasma
**Thyroid**
**Thyroglobulin**
- T3
- T4
- T4
- T3
- T4
- T3
**Hypothal**
**Tissues**
**TBG**
**TBG**
- T4
- T3
- T2
- rT3
**T3**
**conj**
**Pituitary**
** ****TRH**
**TSH**
**T****3****R**
**Thyroid Homeostasis Obscures Real Differences Among Non-equivalent T****4****s in Healthy Subjects**
## TSH Adds Pharmacodynamic Perspective to T4 Results
**TSH Adds Pharmacodynamic Perspective to T****4**** Results**
**Express T4 and TSH as fold-change from pre-dose baseline**
**Invert TSH ratio**
**Large fold change in TSH for a small perturbation in T****4**
**Pronounced hysteresis**
**Discriminates doses**
**Adds biologic context**
## Biologically inconsistent
Reduces true AUC48 10-15%
Attenuates differences between nonequivalent formulations
Produces negative AUC values
2-3 day half-life estimate
Recall: Significant error in point estimate; 90% CI did not include actual value
** ****T****4 **** (μg/dL)**
**Hours**
**Biologically inconsistent**
**Reduces true AUC****48**** 10-15%**
**Attenuates differences between nonequivalent formulations**
**Produces negative AUC values**
**2-3 day half-life estimate**
**Recall: Significant error in point estimate; 90% CI did not include actual value**
**Horizontal Correction Ignores Thyroid Biology**
## Baseline Correction Summary
**All methods are OK for 25% differences, but not for 12.5%. Horizontal correction is biologically inconsistent**
**Intra-subject variability of T****4**** is low**
**To detect 12.5% differences, 80-125% criteria are too broad for T****4**** BE **
**Using TSH data, alone or with T****4****, is more discriminating than T****4**** alone**
## Physicians Want to Know that Switching Products Poses No Patient Risk
**Why not conduct BE studies in subjects with no thyroid function?**
**Precedent in estrogen products**
**Multi-dose, steady-state cross-over**
**Validate with a known difference (e.g., 100 *****vs.***** 88 ****μ****g)**
** **
**Bioequivalence criteria must be tied to clinically relevant marker **
**TSH is the medically acceptable marker**
**Must define maximal TSH changes**
## Conclusions
**Small differences matter for patient safety**
**Products that differ by 12.5% cannot be distinguished using current criteria**
**We should ****engage experts in establishing BE criteria for T****4**** products (i.e., utility function analysis of risk)**
**FDA**
**Academia**
**Endocrine Societies**
**Industry** | en |
all-txt-docs | 585765 | 1 78 THE YUKON TERRITORY.
a week. I soon found, by calculation, that we must be very careful with our flour, and was obliged to weigh out the daily allowance, a pound each, not a very large piece of such damp brown bread. I allowed each three pounds of sugar per month, and a pound of tea for all hands. In this way I managed to make our supply last, although we were often on short commons. Fish, rabbits, and grouse were unusually scarce, and often entirely deficient. No deer visit Nulato during the winter.
I had saved a small piece of frozen deer meat for Christmas, which found us without other supplies in the storehouse. Christmas morning I bought two white grouse, and sent Johnny out to shoot another, which he fortunately succeeded in doing. With these, some berry pies, and some sweetened short-cake, I made
Yukon grouse-snare.
out a pretty fair dinner, and invited Pavloff and Yagor to eat it with me, each bringing his own cup, plate, and spoon, as my stock did not set the table. It was a lonely Christmas compared with the last, or with any I had ever spent before. It was impossible to help thinking of the dear ones at home, of the Christmas-trees and festivities they were enjoying, and equally impossible to doubt that they were thinking of us as we were of them, though many thousand miles away.
New-Year's day brought cold weather, forty-eight below zero. My hunters were unsuccessful, and our dinner was reduced to fish soup, cranberry pie, bread, and tea. My family consisted of Johnny, two Indian boys, and Kurilla. I sent the boys out setting snares for grouse and rabbits. These were occasionally successful, and eked out our slender bill of fare. The snares are
| en |
markdown | 025538 | # Presentation: 025538
## Sysadmin Roundtable April 2008
## Angry
- Banana
## Agenda
- Red Team Phishing and cached creds badness
- LDAP service
- Web exemptions
- Remote access policy
- Cool thing : andlinux
**Notes:**
ST&E audit
- people have to live with the external auditors instead of CST
- The auditors report will satify CST's quarterly pentesting, so two pentests will not be done
DOE certs “renewal”
new kernel root bug on 64bit architectures. This was not declared a critical vulnerability, but since it is very easy to exploit, you should treat it as one and patch as soon as possible please. (note that “possible” is subject to when SLF team receives and releases updated kernels.
## OMG!!!
- Ponies!
- WITH
- GLITTER!!!
## Phishing; no u!
- SLAC noticed this first
- Red Teaming is starting
- hasn't been officially announced but...well...
- Level of detail in the email is really high
- Knowledge of who to send from
- Registered domain names are too specific
- Asking you to run an application
- So we think it's a Red Teaming thing going on at SLAC, but in case you also see it here
- Be aware of targeted (spear phishing) emails!
- HTML email or HTML email with view inline images
## Phishing + HTML; no u!
- You read HTML email?
- Images or links can fetch from an outside server and that server can log the fetch
- You're now a validated email address
- And an IP address is in that access log. If you marry that with GeoIP, you now have direct marketing!
## Value to vendors
- tarupp@fnal.gov
- $
- #1 verified
- $$
- #2 with GeoIP
- $$$
## More badware
- zip file with an MDB (said MS Access) file in it.
- Clickity click click causes stack overflow
- Code execution and then “uh oh”
- ANL CST had a bad run-in with this
- Cached credentials were used by code to skip around to other machines, trying to get admin/domain admin privileges
## Response
- Cut down # of cached creds to 1
- Only perceive potential problem with laptops
- Last logged on user will be cached
- Limits the possibility that the exploit can nab admin level privileges.
- And we'll probably be saying this for the rest of eternity, but...
## Pretty Please
**Pretty Please**
- with a
- on top
## Ask the person to
- resend the email
- Stop blindly clicking on
- links in your email
- If you're not sure...don't click
- Or
## Because we (CST) do love and look out for our community
- Users who blindly click links
- Computer Security Team
- Even if they make us angry from time to time
## More
- There are AV signatures for the aforementioned MDB problem
- Next patch Tuesday (April 8th) should have patches available
## Slide 14
## No, it's Central LDAP Service
- Going to be services.fnal.gov
- CST has been attempting to connect our own applications to it
- It's not ready for public use yet
- Core Services is in charge of it. When will it be production ready?
## WebEx...
- ...emptions
- Cleaning up list
- Removing non-validated in April
- Soon after remainder will need to meet web baseline
- Central logging of access, error and SSL logs
- Marc has instructions for doing this!
- Central means clogger.fnal.gov
## Web Server Baselines
- Apache
**cd-docdb # 1536**
- IIS
- see this man
## Enforcement of Remote Access Policy
## RA Policy slide 1 of 1000000000
- RDP
- On site only, using domain account
- Via VPN or kerb auth'd session if off site
- Or things that meet the following
- Accept centrally managed accounts and comply with Strong Auth Policy
- Reside on OS that complies with FNAL Baseline
## RA Policy slide 2 of 1000000000
- Need to tunnel through Kerb auth'd session
- Timbuktu
- PCAnywhere
- Back2MyMac
- RemotelyAnywhere
- GoToMyPC
- ...
## RA Policy slide 3 of 1000000000
- Provisions for WebEx and the like
- A badged Fermi user must negotiate with the connecting party a non-reoccurring time for the connection.
- A badged Fermi user must be manually authorize the WebEx connection at time of initiation, and must remain present during the WebEx activites.
- Any passwords that are created or changed by a non badged WebEx user must immediately be changed and not communicated back to the non-badged user after the WebEx session has ended.
- Deviations from the above (such as reoccurring or unattended WebEx sessions) require an exemption.
## slides 4 to 999999999 were just a bunch of pictures of Joe's house we took over Xmas
- Probably irrelevant for this meeting...
## RA Policy slide 1000000000 of 1000000000
- RA Policy
**cd-docdb # 2336**
- RA Technical Details (meat and potatoes)
**cd-docdb # 2360**
## It's not easy being green...
- ...and having no limbs
- time for Joe
## wait, in before Joe!
- Reminders
- basic auth with local password store is bad
- basic auth over non-https is worse
- Please reboot your Windows boxes to clear your credential cache
- Please keep your hands and arms inside the cars at all times (don't be like the frogs)
- Please don't go opening attachments or clicking links willy-nilly
## Cool Thing : andlinux
## What is it?
- Software stack
- coLinux
- Xming
- Ubuntu
- PulseAudio
- Use linux apps in Windows
- kate, rhythmbox, mplayer, nedit, whatever
- Install new apps with apt
## Why use it?
- One way to skip around Reflection and cygwin but get similar (better?) functionality
- Sandbox for running applications
- Use linux apps without rebooting into linux
- Integrates apps into the Windows shell
## If you install it
- Remove '-ac' from the run shortcut
- Use X0.host file to restrict who can connect to Xming
- Firewall off port 6000 to localhost or face the wrath of the “port 6000 exposed” email generator
- In a nutshell you're restricting Xserver access to “you and only you, so help you CST”
## Slide 31
| en |
converted_docs | 982446 | HQ 089956
May 11, 1992
CLA-2 CO:R:C:F 089956 STB
CATEGORY: Classification
TARIFF NO.: 9503.90.5000
District Director of Customs
P.O. Box 619050
1205 Royal Lane
Dallas, Texas 75261
RE: Decision on Application for Further Review of Protest No.
5501-90-100482, filed July 26, 1990, concerning the
classification of metallic balloons.
Dear Sir:
This is a decision on a protest filed July 26, 1990, against
your decision on the classification and liquidation of twenty-
nine (29) different entries of metallic balloons that were made
between the dates of July 7, 1989 and February 23, 1990. The
entries were all liquidated on April 27, 1990.
FACTS:
You classified the subject metallic balloons in subheading
9503.90.5000, Harmonized Tariff Schedule of the United States
(HTSUSA), the provision for other toys, other, other, inflatable
toy balls, balloons and punch balls. The applicable duty rate
for that provision is 6.8 percent ad valorem. Protestant claims
that the merchandise should be classified under subheading
9505.90.6000, HTSUSA, the provision for festive, carnival or
other entertainment articles, other, other, dutiable at 3.1
percent ad valorem.
The balloons in question are described by the protestant as
\"aluminum-coated mylar envelopes of various shapes and sizes.\"
They are sold at the retail level for a variety of uses but,
according to the importer, they are primarily marketed as
greetings and as decoration for festive occasions. The
importer\'s submission states that the subject merchandise
consists of aluminum-coated mylar envelopes imprinted with such
legends as \"Happy Birthday\" and \"Happy Anniversary\" while others
display stylized drawings of licensed characters such as Garfield
and Snoopy. Counsel for the importer stated in a meeting with
-2-
Customs Headquarters personnel that the importer does not possess
the rights to licensed characters such as Garfield, and therefore
invents its own characters but concentrates mostly on festive and
greeting themes. A review of the entries under protest
indicates many types of balloons, including balloons described as
\"Welcome Back\" balloons, \"Thank You\" balloons, \"Be My Valentine\"
balloons, \"Teddy Beddy Boy\" balloons, and plain, red balloons.
The three samples that were submitted to Customs all convey
Christmas/Holiday related messages and are predominantly
decorated in Christmas related colors. Counsel also stated that
the aluminum construction of this merchandise helps the items
maintain inflation for a long period of time and thus sets them
apart from latex balloons.
ISSUE:
Whether the subject merchandise should be classified under
subheading 9503.90.5000, HTSUSA, the provision for balloons or
under subheading 9505.90.6000, HTSUSA, the provision for festive,
carnival or other entertainment articles?
LAW AND ANALYSIS:
Classification under the Harmonized Tariff Schedule of the
United States Annotated (HTSUSA) is made in accordance with the
General Rules of Interpretation (GRI\'s). The systematic detail
of the harmonized system is such that virtually all goods are
classified by application of GRI 1, that is, according to the
terms of the headings of the tariff schedule and any relative
section or chapter notes. In the event that the goods cannot be
classified solely on the basis of GRI 1, and if the headings and
legal notes do not otherwise require, the remaining GRI\'s may
then be applied. The Explanatory Notes (EN\'s) to the Harmonized
Commodity Description and Coding System, which represent the
official interpretation of the tariff at the international level,
facilitate classification under the HTSUSA by offering guidance
in understanding the scope of the headings and GRI\'s.
The protestant has claimed classification in heading 9505,
HTSUSA. Heading 9505 provides, in pertinent part, for
\"\[f\]estive, carnival or other entertainment articles.\" The EN\'s
to heading 9505 indicate that the heading covers:
\(A\) Festive, carnival or other entertainment articles
which in view of their intended use are generally made
of non-durable material. They include:
\(1\) Decorations such as festoons, garlands,
-3-
Chinese lanterns, etc., as well as various
decorative articles made of paper, metal foil,
glass fibre, etc., for Christmas trees (e.g.,
tinsel, stars, icicles), artificial snow, coloured
balls, bells, lanterns, etc. Cake and other
decorations (e.g., animals, flags) which are
traditionally associated with a particular
festival are also classified here.
\(2\) Articles traditionally used at Christmas
festivities, e.g., artificial Christmas trees
(these are sometimes of the folding type),
nativity scenes, Christmas crackers, Christmas
stockings, imitation yule logs.
\* \* \*
Articles classifiable in heading 9505, HTSUSA, tend to have no
function other than decoration.
Heading 9505 is generally regarded as a use provision.
Consequently, Additional U.S. Rule of Interpretation 1(a) must be
reviewed. That rule indicates that:
In the absence of special language or context which
otherwise requires\--
\(a\) a tariff classification controlled by use (other
than actual use) is to be determined in accordance with
the use in the United States at, or immediately prior
to the date of importation, of goods of that class or
kind to which the imported goods belong, and the
controlling use is the principal use.
It is our determination that this merchandise is not
classified in heading 9505, HTSUSA. The various items that are
the subject of this protest display different motifs, including
not only Christmas and other holiday related themes but also
general greeting motifs and \"themeless\" motifs that could be
considered cute, humorous, or amusing, but are not related to any
specific festive occasion or greeting. Some of the balloons have
no message or picture. Regardless of motif, however, these items
are basically balloons. Balloons, as a class or kind of
merchandise, are not \"traditionally associated with a particular
holiday\" as required by the EN\'s; they are sold year-round in a
variety of motifs, as illustrated by the variety of balloons that
are the subject of this protest. Additionally, balloons are not
\"traditionally used at Christmas festivities\", also mentioned by
the EN\'s as a possible mode of inclusion in heading 9505, HTSUSA.
-4-
The protestant discusses several prior Customs rulings in
which various items were classified as festive articles in
heading 9505, HTSUSA, and argues that these rulings are analogous
to the current protest. Examination of those rulings, however,
reveals that the merchandise discussed therein can be readily
distinguished from the balloons presently considered.
We next consider classification in heading 9503, HTSUSA, and
specifically in subheading 9503.90.5000, HTSUSA, which provides
eo nomine for \"Other toys\...Inflatable toy balls, balloons and
punchballs.\" The EN\'s to Chapter 95 indicate that \"this chapter
covers toys of all kinds whether designed for the amusement of
children or adults.\" The phrase \"designed for the amusement of\"
is generally understood to indicate the use of an article will be
a factor when classification in Chapter 95 is being considered.
We again refer to Additional U.S. Rule of Interpretation 1(a),
supra. It is our determination that balloons as a class or kind
of merchandise, as well as the particular balloons at issue here,
are indeed designed for the amusement of children or adults and
that obtaining amusement is the principal use of this
merchandise.
As described above, many of the subject balloons have no
greeting or festive related message/picture and thus have little
use other than amusement. The balloons that do display such
messages and pictures are not transformed from their basic status
as balloons. The protestant contends that the balloons are
indeed transformed by the printed material in those instances and
cites Headquarters Ruling Letter (HRL) 086745, dated July 3,
1990, in which Customs classified a plastic, business-like card
as \"other printed matter\" rather than as a toy. That merchandise
consisted of a piece of plastic resembling a credit card in size
and composition. One side of the card contained information
similar to that found on a business or calling card. The other
side of the card contained a temperature and pressure sensitive
thumb-print size square of plastic sheeting, for use as a novelty
device to \"measure\" body temperature to determine stress,
tenseness, etc. Customs determined that \"the printed information
on the cards provides the essential purpose and use for the
goods\" and that the \"stress-test\" is just a gimmick to draw
attention to the cards.
HRL 086745 can be distinguished from the present matter,
however, in that the plastic cards described in that ruling would
have little value were it not for the printed messages that could
be displayed thereon. Balloons, on the other hand, have a well
known and established use for amusement purposes regardless of
the message or picture displayed. This distinction is supported
in two prior Customs rulings, HRL 062114, dated April 12, 1979,
-5-
and New York Ruling (NY) 814645, (1985). These rulings held that
various balloons, although imprinted with advertising messages,
were nevertheless classified in the TSUSA provision for toys.
Although the rulings were based on the TSUSA language, it is very
similar to the language of the present EN. We thus conclude that
the messages and pictures displayed on a portion of the subject
balloons do not remove the merchandise from classification as
balloons in the toy provision. This question does not arise, of
course, in the consideration of the plain balloon entries. As
for the balloons that display only some type of cute character,
their amusement value, and thus their identity as a toy, is
increased by the picture.
HOLDING:
The metallic balloons are classified in subheading
9503.90.5000, HTSUSA, the provision for other toys, other, other,
inflatable toy balls, balloons and punchballs, dutiable at the
column 1 rate of duty of 6.8 percent ad valorem.
The protest should be denied. A copy of this decision
should be attached to the Form 19 to be returned to the
protestant.
Sincerely,
John Durant, Director
Commercial Rulings Division
| en |
converted_docs | 793294 | 8000.1 REV-1
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
CHAPTER 8. STATE/LOCAL REFERRAL AGENCY REPORTING REQUIREMENTS
8-1 Applicability. The following applies to Fair Housing complaints
referred to State or local agencies for processing under the HUD
Regulation [24 CFR Part 115](http://www.gpoaccess.gov/cfr/index.html) -
Recognition of Substantially
Equivalent Laws. As indicated in Chapter Three of this document,
monitoring of Title VIII complaint processing by HUD Regional
Compliance Staff shall be recorded on the HUD 930.1A. In addition,
date of closure and result of closure activity for complaints
handled by State and local agencies is also reported on the HUD
930.1A. All other information on processing of Title VIII
complaints referred to State and local agencies deemed substantially
equivalent shall be recorded on the [HUD
948](http://www.hud.gov/offices/adm/hudclips/forms/hud9a.cfm#group3),
State/Local Referral
Agency Reporting Form.
8-2 General Instructions. A separate State/Local Referral Agency
Reporting Form, HUD 948, shall be completed for each and every
Title VIII complaint referred to State and handled by a State or
Local Referral Agency. That is, for every complaint recorded on
the HUD 930.1A as closed by a State or local agency, there will be
completed a HUD 948. In general, the State/Local Referral Agency
Reporting Form contains case identification information and case
disposition information necessary for evaluation and assessment
of the State or local agency\'s administration of its fair housing
law to insure that the law is, in fact, providing substantially
equivalent rights and remedies.
8-3 Procedure for Utilizing the HUD 948. The form is printed in
color coordinated NCR paper.
After thirty (30) days, the regional staff should complete the
top portion of the form (through respondent identification)
retaining the white copy and forward the remaining forms to the
referral agency for updating. The referral agency then updates
and returns all copies to the regional office.
After sixty (60) days, the regional staff should retain the green
copy of the form and forward the yellow, pink and gold copies to
the referral agency for updating. The referral agency then updates
and returns all copies to the regional office.
After ninety (90) days, the regional staff should retain the
yellow copy and forward the pink and gold copies to the referral
agency for further updating. After updating, the referral agency
retains the gold copy for its record and returns to the regional
office the pink copy.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Page 8-1 11/80
HUD-Wash., D. C.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
8000.1 REV-1
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
The white copy should have \"original copy\" printed on it, the
green, yellow and pink should have \"return to region\" and the
gold copy should be printed \"referral agency\'s copy.\"
The region shall keep one copy of the completed form in the
Title VIII case folder and will make two copies and send to
Headquarters, one copy will go to Office of Management and Field
Coordination and the other to Office of Fair Housing and Section
3 Compliance.
8-4 Instructions for Completion of HUD 948
a\. State/Local Agency Case Number. Fifteen character free-form
alpha numeric identification as provided for by the State or
local agency.
b\. Date State/Local Agency Received Complaint. Date complaint
was received from HUD by the State or local agency. Note that
this and all succeeding dates shall be calendar dates entered in
the six digit format YYMMDD indicating year, month and day. For
example, January 31, 1976 shall be entered as 760131.
c\. Date Referred. Date on which the complaint was referred to the
State or local agency for processing. This date should be
identical to the date referred on the HUD 930.1A.
d\. Referral Agency. Name or other appropriate identification of
State or local agency to whom complaint has been referred. Care
should be taken to ensure that whatever identification is used,
that it be consistently recorded on each and every complaint in
exactly the same manner. This is necessary to aggregate and
summarize all activity by a particular State or local agency.
Note also that this and all name fields are limited to 25
characters.
e\. HUD Case Number. Twelve digit file number (exclusive of the
special indicator) as recorded on the HUD 930.1A.
f\. HUD Monitor. Last name and initials of the FHEO Specialist
assigned to monitor this complaint.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
11/80 Page 8-2
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
8000.1 REV-1
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
g\. Date Received by HUD. Date on which the final information on
the closed case is received by the HUD-FHEO Specialist assigned
to monitor the case.
h\. Complainant\'s Name. Last name and initials of the complainant.
(Note that 25 positions of name fields will be input to the
automated complaint and compliance system).
i\. Address (Complainant\'s). Free-form item containing location of
of complainant. (This item of information is not electronically
stored in the automated system).
j\. Phone (Complainant\'s). Free-form item containing the phone
number where the complainant may be reached. (This information
item is not electronically stored in the automated system).
k\. Respondent\'s Name. Last name and initials of the respondent.
Care should be taken to consistently record the name of this
respondent each time he is recorded in the system. This is
necessary to facilitate retrieval of multiple offender
information.
l\. Address (Respondent\'s). Free-form item containing the location
of the respondent. (This item of information is not
electronically stored in the automated system).
m\. Phone (Respondent\'s). Free-form item containing the phone
number where the respondent may be reached. (This information
item is not electronically stored in the automated system).
n\. Basis. See page 14, Item j.
o\. Issue. See Page 15, Item k.
p\. Date Assigned. Date on which the complaint is assigned to
responsible individual within the agency for handling.
q\. Date Investigation Commenced. Date of initiation of
investigative activity by responsible staff person.
r\. Date Investigation was Completed. Date on which the final
investigation report is completed and transmitted to the
responsible official for a decision on probable cause.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Page 8-3 11/80
HUD-Wash., D. C.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
8000.1 REV-1
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
s\. Date Conciliation was Completed. Date on which all conciliation
activities are completed.
t\. Date Case was Closed. Date on which the case is considered
closed by the State or local agency.
u\. Conciliation in Process. \"Yes\" is checked if conciliation has
begun but has not been completed during the current status check
period; otherwise check \"no\". Note that this item is for use by
the HUD monitor only and shall not be input to the automated
system.
v\. Investigation Results. Appropriate item is checked to describe
the results of investigation. Only one checked item is
permissible to indicate investigation results.
w\. Final Disposition. Appropriate item is checked to indicate
final disposition of the case. This item may be left blank
if not applicable to this complaint. Only one checked item
is permissible to indicate final disposition.
x\. Date of Status Report. Appropriate item is checked to indicate
latest status report made. All items should eventually be
checked. Note that this item is for use by the HUD monitor
only and shall not be input to the automated system.
y\. Conciliated. Appropriate item is checked to indicate whether
or not conciliation activity took place.
z\. Conciliation Results. Appropriate item is checked to indicate
outcome of conciliation efforts. Only one item may be checked.
aa. Relief Obtained. Appropriate items are checked to indicate
the type of relief and amount of any monetary compensation
obtained as a result of conciliation. Any number of multiple
entries are permissible.
bb. Does Conciliation Agreement Provide for Future Monitoring of
Respondent\'s Operation. Appropriate item is checked to indicate
whether or not monitoring is provided for in the conciliation
agreement.
cc\. Agency Investigator. Name of investigator responsible for
complaint at State or local agency. This item is not input
to the automated system.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
11/80 Page 8-4
| en |
converted_docs | 199602 | {width="0.3993055555555556in" height="0.375in"}
National HIV Reference Laboratory
Check List for Annual WHO Accreditation
**1.Introduction.**
{width="5.701388888888889in"
height="5.875in"}Laboratory services are an essential component in the
diagnosis and treatment of persons infected with the human
immunodeficiency virus (HIV), in HIV screening of blood for transfusion,
in surveillance for HIV infection, and in HIV/AIDS related research.
Presently, the laboratory infrastructure for HIV testing and quality
assurance remain weak in most countries in Africa. There is therefore an
urgent need to strengthen the laboratory. The establishment of
accreditation systens will help countries to improve, and strengthen the
capacity of their laboratories.
Accreditation provides documentation that the laboratory has the
capability and the capacity to detect, identify, and promptly report HIV
that may be present in clinical and research specimens. The
accreditation process further provides a learning opportunity, a
mechanism for identifying resource and training needs, a measure of
progress, and a link to the WHO/AFRO HIV Laboratory Network.
Accreditation of Reference National HIV Laboratories is reviewed
annually by the WHO Regional Office and is based on laboratory
performance during the immediately preceding 12 months relying on
complete data, usually from the past 1-13 months to 1 month prior to
evaluation. Accreditation is given for the upcoming calendar year.
> **2.Six criteria for accreditation.**
1. **Test results are reported by the laboratory on at least 80% of HIV
specimens within 7 days of receipt.**
This criterion may be met for all negative specimens and positive
specimens which need a second test or third tests for result
confirmation according to WHO strategy used.
2. **Serology tests are performed on more than 150 specimens weekly.**
Fully active HIV laboratories that maintain the appropriate screening
weekly and test 250 specimens monthly of any origin for any HIV viruses
are deemed to meet this criterion.
3. **The accuracy of HIV screening result among all specimen is over
90%.**
> Accuracy is determined by the agreement in test results on all HIV
> specimen screened by the National Laboratory with the externall
> quality assurance run during the 12-month review period.
4. **Internal quality control (QC) procedures in HIV serology are
practised for all the test runs.**
> Ordinarily, each HIV test kit has a set of positive and negative
> controls that are to be included in each test run. These controls
> included with the test kit are considered internal control, while any
> other controls included in the run are referred to as external
> controls. QC data sheets and summaries of corrective action are
> retained for documentation and discussion with reviewer.
5. **The score on the most recent WHO approved proficiency test is over
90%.**
Proficiency test (PT) results must be reported within 15 days of panel
receipt to receive full credit.
6. **The score from the annual on-site review of laboratory operating**
**procedures and practices is at least 95%.**
For Laboratories with consistently high annual scores, the Regional
Laboratory Coordinator may waive the on-site review upon satisfactory
completion of the annual checklist by the laboratory.
A Laboratory that achieves less than the passing score on any one of the
applicable criteria will work with the HIV Regional OfficeLaboratory
Coordinator to:
{width="5.701388888888889in" height="5.875in"}•
Identify areas where improvement is needed.
> • Develop and implement a work plan.
>
> • Monitor laboratory progress.
>
> • Provide for re-testing where required.
>
> • Continue steps to achieve full accreditation.
A Laboratory that fails to achieve a passing PT test score within 6
months after annual review is deemed non-accredited and arrangements
must be made for an accredited Laboratory to perform duplicate tests on
all specimens.
**This checklist is designed primarily for Laboratories in countries
that perform HIV screening. Applicable components of criteria 2-6 may be
used for Laboratories in other public health-related activities.**
The checklist consists of four parts. **Part I** summarizes the findings
of the review and the data on which accreditation is based. **Part II**
provides a worksheet to calculate and record laboratory performance for
**criteria** **#1** through **#6** for the immediately preceding 12
months where data is complete. (Selection of the most recent 12-month
period, rather than the most recent calendar year as a basis for
calculation, provides an assessment of current performance and permits
review of laboratories at any time during the calendar year.) **Part
III** provides a profile of the laboratory and serves to identify
resource needs. **Part IV** is a checklist for evaluation of laboratory
operating procedures and practices for **criterion** **6**
This checklist does not include all laboratory activities or all
situations. It is intended to serve as a guide. The experienced reviewer
is expected to ask detailed questions and make additional suggestions as
appropriate to assure high quality laboratory performance.
{width="0.3993055555555556in" height="0.375in"}
National HIV Laboratory
Check List for Annual WHO Accreditation
***Laboratories are to be notified in advance of the accreditation
review and provided a copy of this form to assist in gathering
information.***
--------------------------------------------------- -- -- -- ---- -- -- ------- ------ ----------- --------------- --------- --------- -------
Dates of Review: Accreditation
for Calendar
Year:
Laboratory:
Address:
Phone: Fax: E-mail:
Head of Department:
{width="5.701388888888889in"
height="5.875in"}Head of Laboratory:
Technical Supervisor:
Reviewers:
Name of National Accrediting Authority and current
accreditation status:
--------------------------------------------------- -- -- -- ---- -- -- ------- ------ ----------- --------------- --------- --------- -------
**Part I: Summary of Review**
**Recommendations (check one):**
> Accredit: Laboratory meets all criteria
>
> Provisionally accredit: Laboratory passed the most recent proficiency
> test, but failed to achieve one or more of the remaining criteria
>
> Do not accredit: Laboratory did not pass the most recent proficiency
> test
**Findings:**
----------- ---------------------------------------------------------- --------
**1.** Test results on at least 80% of all HIV specimens are **%**
reported within 7 days:
**2.** Tests are performed on at least 3000 specimens annually
**3.** Accuracy of HIV screening is over 95%: **%**
**4.** Internal quality control procedures are implemented at
least monthly:
**5.** Result on most recent HIV PT is over 95%: **%**
**6.** Score on annual on-site review is at least 95%: **%**
Annual HIV **%**
screening
rate is:
----------- ---------------------------------------------------------- --------
*.*
+-----------------------------------------------------------------------+
| *SUMMARY, Comments and recommendations**:*** |
| |
| {width="5.701388888888889in" height="5.875in"} |
+-----------------------------------------------------------------------+
**Part II: Laboratory Performance in Previous 12 Months**
----------------- ------- ------- -- ------- -- ------- ----- ------- ------- -------- --
Dates from: **/** **/** to **/** **/**
*d* *m* *y* *d* *m* *y*
----------------- ------- ------- -- ------- -- ------- ----- ------- ------- -------- --
+-----+---------------------------------------------------------+------+
| 1 | **Percentage of HIV Test Results Reported within 7 | * |
| . | Days: (criteria 1)** | *%** |
+-----+---------------------------------------------------------+------+
| 1 | Number of HIV specimens tested: | |
| . | | |
+-----+---------------------------------------------------------+------+
| 2 | Number with screening test results reported within 7 | |
| . | days: | |
+-----+---------------------------------------------------------+------+
| ! | | |
| []( | | |
| med | | |
| ia/ | | |
| ima | | |
| ge2 | | |
| .pn | | |
| g){ | | |
| wid | | |
| th= | | |
| "5. | | |
| 701 | | |
| 388 | | |
| 888 | | |
| 888 | | |
| 889 | | |
| in" | | |
| he | | |
| igh | | |
| t=" | | |
| 5.8 | | |
| 75i | | |
| n"} | | |
+-----+---------------------------------------------------------+------+
| *Co | | |
| mme | | |
| nts | | |
| and | | |
| rec | | |
| omm | | |
| end | | |
| ati | | |
| ons | | |
| **: | | |
| *** | | |
+-----+---------------------------------------------------------+------+
+-----+---------------------------------------------------------+------+
| 2 | **Total Number of Specimens Tested for HIV: (Last 12 | |
| . | months)** | |
+-----+---------------------------------------------------------+------+
| | | |
+-----+---------------------------------------------------------+------+
| 2.1 | > Specimens tested for HIV from: Diagnosis: | |
+-----+---------------------------------------------------------+------+
| 2.2 | > Specimens tested for HIV from: Surveillance: | |
+-----+---------------------------------------------------------+------+
| 2.3 | > Specimens tested for HIV from: Special surveys: | |
+-----+---------------------------------------------------------+------+
| 2.4 | > Specimens tested for HIV from: Other: | |
+-----+---------------------------------------------------------+------+
| | | |
+-----+---------------------------------------------------------+------+
| *Co | | |
| mme | | |
| nts | | |
| and | | |
| re | | |
| com | | |
| men | | |
| dat | | |
| ion | | |
| s:* | | |
+-----+---------------------------------------------------------+------+
+-----+---------------------------------------------------------+------+
| **3 | **Accuray: Percent HIV concordance by external quality | * |
| .** | control :** | *%** |
+-----+---------------------------------------------------------+------+
| > | > Number of proficiency testing HIV screening test | |
| 3.1 | > done: | |
+-----+---------------------------------------------------------+------+
| > | > Number of specimen sent for PT from the regional | |
| 3.2 | > reference laboratory: | |
+-----+---------------------------------------------------------+------+
| > | > Percentage of concordance results by PT with the | * |
| 3.3 | > regional reference laboratory: | *%** |
+-----+---------------------------------------------------------+------+
| | | |
+-----+---------------------------------------------------------+------+
| *DE | | |
| SCR | | |
| IBE | | |
| ACT | | |
| ION | | |
| TA | | |
| KEN | | |
| FOR | | |
| ANY | | |
| SP | | |
| ECI | | |
| MEN | | |
| NOT | | |
| CON | | |
| FIR | | |
| MED | | |
| BY | | |
| Q | | |
| C:* | | |
| | | |
| *Co | | |
| mme | | |
| nts | | |
| and | | |
| rec | | |
| omm | | |
| end | | |
| ati | | |
| ons | | |
| **: | | |
| *** | | |
+-----+---------------------------------------------------------+------+
+-----+---------------------------------------------------------+------+
| **4 | **Routine Internal Quality Control Procedures | |
| .** | Implemented:** | |
+-----+---------------------------------------------------------+------+
| | 4.1 Monitoring of control values | |
+-----+---------------------------------------------------------+------+
| | 4.2 Monitoring with internal standards | |
+-----+---------------------------------------------------------+------+
| ! | 4.3 Monitoring quality of each new batches of kits | |
| []( | | |
| med | | |
| ia/ | | |
| ima | | |
| ge2 | | |
| .pn | | |
| g){ | | |
| wid | | |
| th= | | |
| "5. | | |
| 701 | | |
| 388 | | |
| 888 | | |
| 888 | | |
| 889 | | |
| in" | | |
| he | | |
| igh | | |
| t=" | | |
| 5.8 | | |
| 75i | | |
| n"} | | |
+-----+---------------------------------------------------------+------+
| | 4.4 Documentation of internals controls and kits | |
| | validation | |
+-----+---------------------------------------------------------+------+
| | | |
+-----+---------------------------------------------------------+------+
| *DE | | |
| SCR | | |
| IBE | | |
| R | | |
| ESU | | |
| LTS | | |
| (% | | |
| of | | |
| sp | | |
| eci | | |
| men | | |
| col | | |
| lec | | |
| ted | | |
| for | | |
| QC, | | |
| % | | |
| of | | |
| c | | |
| onc | | |
| ord | | |
| anc | | |
| e)* | | |
| | | |
| *co | | |
| mme | | |
| nts | | |
| and | | |
| re | | |
| com | | |
| men | | |
| dat | | |
| ion | | |
| s:* | | |
+-----+---------------------------------------------------------+------+
+-----+------------------------------------------------+---+---+------+
| **5 | **Result of Most Recent HIV Proficiency | | | * |
| .** | Test:** | | | *%** |
+-----+------------------------------------------------+---+---+------+
| > | > Date of panel receipt: | * | * | |
| 5.1 | | * | * | |
| | | / | / | |
| | | * | * | |
| | | * | * | |
+-----+------------------------------------------------+---+---+------+
| > | > Date of test report: | * | * | |
| 5.2 | | * | * | |
| | | / | / | |
| | | * | * | |
| | | * | * | |
+-----+------------------------------------------------+---+---+------+
| | | | | |
+-----+------------------------------------------------+---+---+------+
| *Co | | | | |
| mme | | | | |
| nts | | | | |
| and | | | | |
| rec | | | | |
| omm | | | | |
| end | | | | |
| ati | | | | |
| ons | | | | |
| **: | | | | |
| *** | | | | |
+-----+------------------------------------------------+---+---+------+
--------------------------------------------------------------- -------
**Annual HIV Screening Rate:** **%**
**Annual HIV Confirmation Rate:** **%**
total number of sera screened annually
total number of HIV positive sera screened annually
total number of confirmed HIV positive sera annually
--------------------------------------------------------------- -------
**Part III: Laboratory Profile**
+-----+----------------------------------------------------------------+
| 1 | **Staff** |
| . | |
+-----+----------------------------------------------------------------+
| 1 | > Number of scientific and technical staff assigned to HIV |
| . | > laboratory: Please list according to function, indicating |
| | > years of HIV laboratory experience and proportion of current |
| | > working time spent on HIV-related activities. |
+-----+----------------------------------------------------------------+
--------------------------------------------------- --------------------- ------------- --------- ------------
**Names of staff** **Position Title or **Full-time **% of **Years of
Duties** or time experience
Part-time** spent in HIV Lab**
working
on HIV**
{width="5.701388888888889in"
height="5.875in"}
*COMMENTS AND RECOMMENDATIONS:*
--------------------------------------------------- --------------------- ------------- --------- ------------
+-----+---------------------------------------------------------+------+
| 2 | **Space** (provide floor plan or sketch of laboratories | |
| . | if possible) | |
+-----+---------------------------------------------------------+------+
| 1 | > Total m^2^ available: | |
| . | | |
+-----+---------------------------------------------------------+------+
| 2 | > Number of rooms: | |
| . | | |
+-----+---------------------------------------------------------+------+
| 3 | > Separate room for molecular biology | |
| . | | |
+-----+---------------------------------------------------------+------+
| | | |
+-----+---------------------------------------------------------+------+
| *CO | | |
| MME | | |
| NTS | | |
| AND | | |
| RE | | |
| COM | | |
| MEN | | |
| DAT | | |
| ION | | |
| S:* | | |
+-----+---------------------------------------------------------+------+
**Part IV: Laboratory Operating Procedures and Work Practices**
+-----+------------------------------------------------+-------+------+
| 1 | **Space ***:* **9 points** | **Sco | |
| . | | re:** | |
+-----+------------------------------------------------+-------+------+
| 1 | > Space is used efficiently with appropriate | | |
| . | > equipment placement: 3 | | |
+-----+------------------------------------------------+-------+------+
| 2 | > Space configuration is adequate and | | |
| . | > consistent with good laboratory practices: 3 | | |
+-----+------------------------------------------------+-------+------+
| 3 | > Space is clean and well kept 3 | | |
| . | | | |
+-----+------------------------------------------------+-------+------+
| | | | |
+-----+------------------------------------------------+-------+------+
| *CO | | | |
| MME | | | |
| NTS | | | |
| AND | | | |
| RE | | | |
| COM | | | |
| MEN | | | |
| DAT | | | |
| ION | | | |
| S:* | | | |
| | | | |
| ! | | | |
| []( | | | |
| med | | | |
| ia/ | | | |
| ima | | | |
| ge2 | | | |
| .pn | | | |
| g){ | | | |
| wid | | | |
| th= | | | |
| "5. | | | |
| 701 | | | |
| 388 | | | |
| 888 | | | |
| 888 | | | |
| 889 | | | |
| in" | | | |
| he | | | |
| igh | | | |
| t=" | | | |
| 5.8 | | | |
| 75i | | | |
| n"} | | | |
+-----+------------------------------------------------+-------+------+
+-----+------------------------------------------------+-------+------+
| 2 | **Staff** *score maximum* **4 points** | **Sco | |
| . | | re:** | |
+-----+------------------------------------------------+-------+------+
| 1 | > Staff are effectively assigned: 2 | | |
| . | | | |
+-----+------------------------------------------------+-------+------+
| 2 | > The number of trained staff are adequate to | | |
| . | > handle the workload: 2 | | |
+-----+------------------------------------------------+-------+------+
| | | | |
+-----+------------------------------------------------+-------+------+
| *CO | | | |
| MME | | | |
| NTS | | | |
| AND | | | |
| RE | | | |
| COM | | | |
| MEN | | | |
| DAT | | | |
| ION | | | |
| S:* | | | |
+-----+------------------------------------------------+-------+------+
+-----+------------------------------------------------+-------+------+
| 3 | **Supervision** *score maximum* **9 points** | **Sco | |
| . | | re:** | |
+-----+------------------------------------------------+-------+------+
| 1 | > The lines of supervision and accountability | | |
| . | > are clear: 3 | | |
+-----+------------------------------------------------+-------+------+
| 2 | > Supervisor critically reviews test results: | | |
| . | > 3 | | |
+-----+------------------------------------------------+-------+------+
| 3 | > Tests results are properly recorded 3 | | |
| . | | | |
+-----+------------------------------------------------+-------+------+
| | | | |
+-----+------------------------------------------------+-------+------+
| *CO | | | |
| MME | | | |
| NTS | | | |
| AND | | | |
| RE | | | |
| COM | | | |
| MEN | | | |
| DAT | | | |
| ION | | | |
| S:* | | | |
+-----+------------------------------------------------+-------+------+
+-----+------------------------------------------------+-------+------+
| 4 | **Sera Specimens** *score maximum* **28 | **Sco | |
| . | points** | re:** | |
+-----+------------------------------------------------+-------+------+
| 1 | Appropriate written protocol for processing | | |
| . | specimens is available: 4 | | |
+-----+------------------------------------------------+-------+------+
| 2 | Specimens are processed by centrifugation: 4 | | |
| . | | | |
+-----+------------------------------------------------+-------+------+
| 3 | Plasma are stored at --20^o^C if not screened | | |
| . | on same day as processed: 4 | | |
+-----+------------------------------------------------+-------+------+
| 4 | All potentially infected clinical materials | | |
| . | are processed in a biological safety cabinet: | | |
| | 4 | | |
+-----+------------------------------------------------+-------+------+
| 5 | Original specimens (in original containers) | | |
| . | are appropriately labeled and stored at | | |
| | --20^o^C for at least 12 months: 4 | | |
+-----+------------------------------------------------+-------+------+
| 6 | Plasma products extracts are discarded within | | |
| . | 12 months of confirmation of result:**4** | | |
+-----+------------------------------------------------+-------+------+
| 7 | Specimens, and other potentially infectious | | |
| . | materials are stored separately from | | |
| | non-infectious materials in designated | | |
| | freezers and refrigerators: 4 | | |
+-----+------------------------------------------------+-------+------+
| | | | |
+-----+------------------------------------------------+-------+------+
| *CO | | | |
| MME | | | |
| NTS | | | |
| AND | | | |
| RE | | | |
| COM | | | |
| MEN | | | |
| DAT | | | |
| ION | | | |
| S:* | | | |
+-----+------------------------------------------------+-------+------+
+-----+------------------------------------------------+-------+------+
| 5 | **Biosafety and containment of HIV** *score | **Sco | |
| . | maximum* **26 points** | re:** | |
+-----+------------------------------------------------+-------+------+
| 1 | > Employees have been instructed in biosafety: | | |
| . | > 4 | | |
+-----+------------------------------------------------+-------+------+
| 2 | > Written instructions are available to all | | |
| . | > employees: 4 | | |
+-----+------------------------------------------------+-------+------+
| 3 | > Biosafety practices are enforced, including: | | |
| . | | | |
+-----+------------------------------------------------+-------+------+
| | > ![] | | |
| | (media/image2.png){width="5.701388888888889in" | | |
| | > height="5.875in"}a. Hand washing: 1 | | |
+-----+------------------------------------------------+-------+------+
| | > b\. Pipetting with aid of mechanical device: | | |
| | > 1 | | |
+-----+------------------------------------------------+-------+------+
| | > c\. Routine use of gloves and lab coats 1 | | |
+-----+------------------------------------------------+-------+------+
| | > d\. No eating, drinking, smoking, or storage | | |
| | > of food in laboratory 1 | | |
+-----+------------------------------------------------+-------+------+
| | > e\. Decontaminating all infectious or | | |
| | > clinical waste before discarding: 1 | | |
+-----+------------------------------------------------+-------+------+
| | > f\. Decontaminating lab work surfaces: 1 | | |
+-----+------------------------------------------------+-------+------+
| 4 | > Biosafety cabinets and clean air cabinets | | |
| . | > are used for potentially infected and clean | | |
| | > materials, respectively: 4 | | |
+-----+------------------------------------------------+-------+------+
| 5 | > Safety cabinets are maintained as | | |
| . | > recommended, including filter changes, and | | |
| | > dates recorded: 4 | | |
+-----+------------------------------------------------+-------+------+
| 6 | > A written inventory is available of all | | |
| . | > stored sera and materials that potentially | | |
| | > contain HIV 4 | | |
+-----+------------------------------------------------+-------+------+
| | | | |
+-----+------------------------------------------------+-------+------+
| *CO | | | |
| MME | | | |
| NTS | | | |
| AND | | | |
| RE | | | |
| COM | | | |
| MEN | | | |
| DAT | | | |
| ION | | | |
| S:* | | | |
+-----+------------------------------------------------+-------+------+
+-----+------------------------------------------------+-------+------+
| 6 | **Equipment** *score maximum* **12 points** | **Sco | |
| . | | re:** | |
+-----+------------------------------------------------+-------+------+
| 1 | > Equipment is functioning and in good | | |
| . | > condition: 3 | | |
+-----+------------------------------------------------+-------+------+
| 2 | > Equipment is maintained periodically as | | |
| . | > recommended and dates recorded: 3 | | |
+-----+------------------------------------------------+-------+------+
| 3 | > Equipment location is conducive to optimal | | |
| . | > performance: 3 | | |
+-----+------------------------------------------------+-------+------+
| 4 | > Records are kept on daily temperature | | |
| . | > readings of incubators, refrigerators, and | | |
| | > freezers: 3 | | |
+-----+------------------------------------------------+-------+------+
| | | | |
+-----+------------------------------------------------+-------+------+
| *CO | | | |
| MME | | | |
| NTS | | | |
| AND | | | |
| RE | | | |
| COM | | | |
| MEN | | | |
| DAT | | | |
| ION | | | |
| S:* | | | |
+-----+------------------------------------------------+-------+------+
+-----+------------------------------------------------+-------+------+
| 7 | **Supplies** *score maximum* **12 points** | **Sco | |
| . | | re:** | |
+-----+------------------------------------------------+-------+------+
| 1 | Current inventories are maintained: 3 | | |
| . | | | |
+-----+------------------------------------------------+-------+------+
| 2 | Adequate time is allowed for replenishing | | |
| . | supplies: 3 | | |
+-----+------------------------------------------------+-------+------+
| > | All reagents are stored in good condition 3 | | |
| 7.3 | | | |
+-----+------------------------------------------------+-------+------+
| > | A Buffer stock equal to three months supplies | | |
| 7.4 | is available 3 | | |
+-----+------------------------------------------------+-------+------+
| | | | |
+-----+------------------------------------------------+-------+------+
| *CO | | | |
| MME | | | |
| NTS | | | |
| AND | | | |
| RE | | | |
| COM | | | |
| MEN | | | |
| DAT | | | |
| ION | | | |
| S:* | | | |
+-----+------------------------------------------------+-------+------+
| en |
converted_docs | 242685 | D0 Note 3988
May 2002
# **Phase-5 Tests and Studies of the**
# **Run IIa Analog Front End Board**
Pushpa Bhat, Alan Bross, Kirsten Goldmann,
Rick Jesik, Yi Jiang, Mike Matulik,
Hugh Montgomery and Andriy Zatserklyaniy
# **Abstract**
Each of the 198 Analog Front End Boards that instrument the Central
Fiber Tracker and the Pre-shower Detectors were thoroughly tested in the
Phase-5 test stand and certified prior to commissioning in the Run IIa
D0 detector. We describe those tests and discuss the online and offline
analysis of the data taken on the test stand. We present a variety of
results on the SVX gains, discriminator turn on and gains and pedestal
behavior. We also discuss the board certification issues for
commissioning and show distributions that provide a global perspective
of the system.
##
##
## **Contents**
1. Introduction
2. Phase-5 Test Goals
3. Phase-5 Test Stand and Data Acquisition
4. Phase-5 Tests
5. Test Stand Data and Analysis
1. VREF Scan
2. Online Tests
3. Pedestals
4. SVX Response and SVX Gain
5. Discriminator Threshold Scans
1. Discriminator Turn-On and SIFT Gains
2. Turn-On Width
6. Zero Suppression Threshold Studies
1. Pedestals from Phase-5 Tests
2. Pedestals from Platform Tests
6. Board Certification Issues
1. Definition of a Bad Channel
2. Criteria for Grading AFE Boards
7. Summary
```{=html}
<!-- -->
```
1. **Introduction**
The Analog Front End (AFE) Boards instrument three Scintillation Fiber
detectors, the Central Fiber Tracker (CFT), the Central Pre-Shower (CPS)
and the Forward Pre-Shower (FPS), in the D0 detector. They receive
charge signals from the fibers via the Visible Light Photon Counters
(VLPCs) and provide (1) digital output for trigger and (2) analog
signals with charge amplitude information. The AFE board also provides
VLPC bias and temperature control functionalities.
There are three color-coded versions of the AFE board, which differ from
each other in input gain and VLPC control circuitry. The details are as
follows:
- CFT boards -- green -- 136 needed (76 for axial layers/trigger)
- CPS/CFT boards -- blue -- 30 needed (10 for axial layers/trigger)
- FPS boards -- red -- 32 needed (all needed for trigger)
Between the three versions of the AFE boards, they instrument 77,000
channels in the CFT, 7,680 channels in the CPS and 14,000 channels in
the FPS.
The AFE boards also have a handedness. There are Left-handed (LH) and
Right-handed (RH) boards because of the way the boards are installed in
a VLPC cassette. Each AFE board has eight Multi-Chip-Modules (MCMs) and
a total of 64 channels each of analog and digital outputs. Each MCM has
1 Silicon Vertex (SVX-IIe) charger sensitive ADC (64 banded channels out
of a total of 128) and 4 SIFT (Scintillating Fiber Trigger)
discriminator chips (64 total channels- 2 SIFTs with 14 channels and 2
with 18 channels). A photograph of an RH AFE board is shown in Fig.1,
with important components labeled. For detailed design specification see
Ref. 1. Other notable sub-systems apart from the eight MCMs are:
- 1553 Control & Communication systems
- A "virtual SVX" (VSVX) system to buffer discriminator data for
readout with SVX data
- A high-speed data multiplexing system which routes all discriminator
data from the SIFT chips via LVDS links to Digital Front End (DFE)
boards.
- Analog monitoring for the VLPC temperature and bias (bias & cryo
control)
- DAC system to develop all control voltages for SIFTs
- A clock generation system to generate all timing clock pulses for
the SIFTs
All major logic functions are provided using Complex Programmable Logic
Devices (CPLDs). Embedded software in the on-board microprocessor is
used to respond to commands from the external world that appear on the
1553 bus.
{width="5.665354330708661in"
height="5.004330708661417in"}
**Fig.1:** A photograph of a Right-handed AFE Board
2. **Phase-5 Test Goals**
The phase-5 test of the AFE involves an attempt to verify all functional
aspects of every AFE board and to evaluate it for installation in the
detector on the platform. The primary goals of the phase-5 testing are:
1. Re-testing the basic functionalities of the devices (communication
interfaces, microcontroller, SVX and SIFTs),
2. Studying the response of all 512 channels of the AFE to injection of
charge,
3. To test the ability of the AFE to operate the bias voltage and
cryogenic temperature control systems, and
4. The verification of the transfer of discriminator information to the
level-1 trigger system.
If the test results are satisfactory (see description in Sec. 6), the
board is ready for installation. If not, repairs are made and the board
is re-tested and re-evaluated.
3. **Phase-5 Test Stand and Data Acquisition**
To accomplish two of the primary goals of Phase V testing, an Analog
Front End Test Module (AFETM) was designed and built. An AFETM is
connected to the AFE by means of 8 VLPC 64 channel flexible cables
(V64), just as the AFE would be connected to the Visible Light Photon
Counters (VLPC) when installed in the Cryostat located under the D0
detector. Circuitry located on the AFETM is capable of injecting
variable and programmable amounts of charge into the conductors located
on the V64 cables and then onto the AFE. Also located on the AFETM is
circuitry used to emulate the response of the cryogenic temperature
monitoring resistors that are located under the VLPCs and circuitry that
can verify the operation of both the cryogenic temperature and bias
voltage control circuits on the AFE.
These aspects of the Phase V testing of the AFE are incorporated into
Visual Basic (VB) code (running under Excel) that controls the hardware
used to generate the test stimuli and read the AFE and AFETM for the
results. The test hardware (except for the AFETM) resides in a VME crate
located in the rack that holds the AFE backplane structure. The
computer, which runs the VB code, communicates with the VME crate via a
Bit3 card and cable system. Within the VME crate is the 1553 Controller
that sends instructions to and reads some test results back from the AFE
and the AFETM. Also within the VME crate is the Stand Alone Sequencer
(SASEQ) that is used to read Level 3 data from the AFE. To test the
response of channels on the AFE, the VB code sends 1553 commands to the
VME crate through the Bit3 system. The 1553 controller interprets the
commands and sends (or receives as necessary) appropriately coded 1553
compliant communication to either the AFE or the AFETM, to; set various
Digital to Analog Converters (DACs), configure patterns of channels to
inject charge to, set or clear various digital signal levels, etc. The
VB code then instructs the SASEQ (again using the Bit3 system) to
initiate a data transfer cycle, then reads the resulting AFE digitized
charge information and discriminator output information back from the
SASEQ. Typically, many events are taken for a given set up. For each
channel on the AFE, the mean of the digitized charge value and the
occupancy of the discriminated output is computed and compared to
limits. If the AFE is capable of performing the base level operations
and the channel response falls within limits, more extensive
characterization tests are run and analyzed off-line.
To accomplish the third goal of Phase V testing, a module used to verify
the design of the Digital Front End (DFE) module is used to read and
verify the Level 1 Trigger information from the AFE. The Data Pump
module can accept a stream of Low Voltage Differential Signal (LVDS)
from the AFE and make it available to the personnel computer running the
test. The AFE forms LVDS data streams from the discriminator output data
from the MCMs and would send the data to the DFE in normal running mode.
Code installed in some of the Complex Programmable Logic Devices (CPLD)
on the AFE can generate known patterns of diagnostic discriminator data
to the LVDS drivers when instructed to do so.
The LVDS portion of the Phase 5 test is run using different VB code. The
same path to the VME crate is utilized, but as noted above, the data
comes from the Data Pump module instead of the SASEQ. The data format is
sufficiently different and the LVDS test code was written late enough
that no effort was made to integrate both tests into a common package.
4. **Phase-5 Tests**
> The tests conducted on the AFE boards during phase-5 fall into three
> categories:
1. Retesting some of the basic functionalities of the AFE board even
though they were looked at in earlier phases of testing:
- The AFE can respond to the 1553 communication system
- The microcontroller is working
- The chain of SVX chips are functional and respond to commands
- The discriminators are functional
2. Testing the response of all 512 channels of the AFE to charge
injection:
```{=html}
<!-- -->
```
1. Establish the operating voltage V~ref~ (V~ref~ scan)
2. SVX response for different amounts of charge injected ⇒ SVX gain
3. Discriminator threshold scans with different amounts of charge
injected
4. SIFT gain ⇒ Discriminator turn-on curve
5. Pulse channels in different patterns and readout
6. Pedestals (means and sigmas) for all channels
```{=html}
<!-- -->
```
3. Testing the ability of the AFE to operate the bias voltage and
cryogenic temperature control.
```{=html}
<!-- -->
```
5. **Test Stand Data and Analysis**
Channel level testing of the AFE Module at the Phase V test Stand is
carried out in two sections, the VREF sweep and the On-line analysis,
followed by a section that generates data for off-line analysis. The
goal of the VREF sweep section is to determine the correct voltage to
apply to each SIFT as an operating parameter. The On-line test and
analysis procedure injects charge into AFE analog input channels in an
attempt to determine to what extent all channels are responding but not
to the detail attempted in the off-line testing.
The AFE Test Module (AFE TM) is designed to allow the injection of a
variable amount of charge into the analog input channels of the AFE. The
same flexible printed circuits used to connect the AFE to the Visible
Light Photon Counters in the Fiber Tracker Cryostat are used to connect
the AFE to the AFE TM in the test stand. The design of the AFE TM allows
the injection of charge into as few as 8 non-adjacent (but common to a
single Multi-Chip Module (MCM)) channels at a time.
The AFE test stand code operates in a series of steps. The code
processes each step by first reading an array of stored test parameter
values, writing these values to appropriate registers and
Digital-to-Analog Converters (DACs) on both the AFE and the AFE TM to
set up a given step in the test. The system is then triggered and data
(both discriminator and digitized) is read out from the AFE for a number
of events for each step. The data read from the AFE is stored by channel
into three arrays after discriminator occupancy, SVX mean and SVX
standard deviation calculations are computed. The VREF scan operates
under this arrangement changing the VREF DAC values in steps. The other
On-line tests as well as those associated with the generation of data
for the Off-line test use the constant values for the VREF DACs as
determined from the VREF scan, but vary other parameters depending on
what is to be tested.
1. **V~ref~ Scan**
The VREF input to the SIFT is used to match the quiescent SIFT output
capacitor voltage to the SVX input offset voltage. Differences in these
voltages are seen as charge by the SVX and can be either positive or
negative depending on the sign of the difference. Note that this charge
is due to the operation of the SIFT chip and not due to charge injected
into a SIFT input channel. For very small values of the VREF input
voltage, the difference between the SIFT and SVX is large and negative
(the capacitor output voltage is less than the SVX channel input
voltage). The effective negative charge transferred to the SVX is
sufficient to saturate the SVX. At the maximum voltage of the VREF
input, the difference is large and positive. The effective positive
charge transferred to the SVX is also sufficient to saturate the SVX.
The mean value of all saturated bonded SVX channels is a constant value,
dependent on the initialization values downloaded to the SVX chip. As
the voltage of the VREF input is increased, the SVX channels start to
come out of saturation and respond to the small negative charge with
mean values of less than the saturated value. As the VREF input voltage
continues to increase, the effective negative charge applied to the SVX
input decreases and the mean value of the SVX channels falls to zero. At
some VREF input voltage, the SIFT output capacitor voltage and the SVX
input voltages are equal. Increasing the VREF voltage past this point
results in the effective transfer of positive charge into the SVX. At
some greater VREF voltage, the amount of positive charge injected into
the SVX results in the channel mean to start to rise from zero. The mean
values of the SVX channels increase linearly with increasing VREF input
voltage (stored as a DAC value by the code) until the SVX approaches
saturation and the mean drops to the constant saturation value.
In the VREF sweep, the DACs that drive the VREF input to each of the 32
SIFT chips located inside the MCMs located on the AFE, are swept in 1
count steps through a portion of their range such that the lower and
upper saturation ranges of the SVX channels can be observed. For each
step of the VREF sweep, the AFE is triggered 20 times and the mean value
for each of the 512 channels on the AFE is calculated and stored in an
array. After all 58 steps that comprise the VREF sweep are completed,
the Visual Basic code that runs the AFE testing computes best VREF value
for each SIFT. Component variations do not allow the establishment of a
single global value for this voltage.
Each channel responds slightly differently to the VREF sweep. With one
VREF input to each SIFT, and a single SIFT controlling 18 channels, the
code attempts to determine the best VREF DAC value for each SIFT. This
is accomplished first on an individual channel basis, then by grouping
the results by SIFT and selecting the average value calculated from all
channels associated with a given SIFT. If channel responses are widely
divergent, the code may determine that a VREF value is not calculable
and generate an error. The method the code uses to determine the VREF
DAC value is to look for the VREF DAC value at which the SVX channel
mean first exceeds the saturation value by a fixed amount. In practice,
this offset (10 counts used in our tests) would be chosen in an attempt
to equalize the bonded channels at a common pedestal value and to allow
the differentiation of bonded from unbonded or unused channels. Once the
VREF DAC value for each SIFT had been determined, it is stored in an
array for future reference.
{width="5.024305555555555in"
height="5.115277777777778in"}
**Fig.3: V~ref~ Scan:** Plots of mean SVX response for each SVX channel
in each SIFT (one plot/SIFT) of an MCM for AFE Board 560480, as a
function of the applied reference voltage.
2. **Other Online Tests**
In the On-line analysis procedure, the test stand code instructs the AFE
TM to inject charge into all 512 channels on the AFE in 8 steps,
applying the same charge to the same 8 channels in each of the 8 MCMs on
each step. For each of these steps, the test stand code stores
discriminator and SVX data for 500 events.
With the VREF DAC values as determined in the VREF sweep loaded into the
parameter array, the amplitude of the digitized signal found for
channels into which charge has been injected is expected to be
relatively constant across all SIFT channels. The amount of charge
injected into each channel (implemented in the parameter array as the
value written to a DAC on the AFE TM) was empirically selected to result
in something less than full-scale response from the SVX for the
initialization values downloaded to the SVX. The mean value obtained for
each of the 1024 SVX channels on the AFE is compared to limits to gauge
the response of the channel. Since not all channels are subjected to
charge injection on each of the 8 steps, the test stand code considers
channels to be of one of four types for each step. There are 56 channels
on each SVX that are not connected to any input, these are considered to
be Unbonded channels. There are 8 channels on each MCM that are fully
instrumented but not connected to an analog input channel on the AFE,
these are Unused channels. The remaining 512 SVX channels are fully
instrumented on the MCMs and connected to analog input channels on the
AFE. Only 64 are capable of receiving charge from the AFE TM at a time
for a given step, these are considered Pulsed channels. The channels not
receiving charge for a given step are Unpulsed channels. For each step
in the On-line test section, all SVX channels are subjected to different
limits depending on what kind of channels they are. Channels with mean
values outside the established limits are flagged as failed.
At the same time that channels are subjected to injected charge for
determination of their mean SVX values, the discriminator function of
each of the channels is also being tested. There are 512 discriminated
outputs from the MCMs on the AFE. They are divided into pulsed and
unpulsed categories for each step depending on which ones are receiving
the charge from the AFE TM. For the evaluation of the discriminator
channels on the AFE, the test stand code computes the fraction of the
number of times a discriminator channel was found to be ON (charge found
to be in excess of threshold) by the number of events in a given step.
Correctly responding discriminator channels should have occupancy of no
less than 1 when they are being pulsed and no more than 0 when they
aren't. Circuitry on the AFE exists to apply an effective threshold
voltage to the SIFT chips for use in the charge discrimination
operation. These threshold voltages can be changed by writing to DACs
located on the AFE. The values to be written to the threshold DACs are
stored in the parameter array for each test step. The particular values
to be written to the threshold DACs (setting the charge threshold level
for discriminator operation) were chosen empirically based on the amount
of charge injected for the SVX channel testing.
3. **Pedestals**
The pedestals were read out multiple times (\~100-300) and the pedestal
mean and sigma for each channel is stored in the data files for offline
analysis. The pedestal means and sigmas for a typical board are shown in
Fig.4. The distributions of the same are shown in Fig.5. The pedestal
sigma was required to be within 7 ADC counts (or 1 p.e.) in the LG mode
for the channel to be tagged as a good channel. We have performed some
zero suppression studies using the pedestal data both from phase-5 test
data and some data taken on the platform. These are discussed in section
5.6.
{width="5.5in" height="6.501388888888889in"}
**Fig.4:** Pedestal means and sigmas for each of the 512 channels for
AFE board 560480 (Date: ) Note: Later modifications to the AFE board
yield much smaller variations in pedestals. See Fig X.XX.
{width="5.5in" height="6.501388888888889in"}
**Fig.5:** Distributions of pedestal means and sigmas for AFE board
560480.
4. **SVX Response and SVX Gain Studies**
During the tests, pre-determined amounts of charges (Q=20, 30, 40, 50
QDAC units, 1QDAC unit ≈ 4.5 fC) are injected into each of the SVX
channels and the response read out. This was done both in the "Low Gain"
(LG) and "High Gain" (HG) modes. For each channel, then, we perform a
linear fit (using MINUIT in PAW) to the SVX response as a function of
the input charge to determine the SVX gain for that channel. Fig.6 (a)
and (b) show such a linear fit for one of the channels in low gain and
high gain modes, respectively. The gains and offsets from the fits for
all used channels are shown in Figs.7,9. The distributions of gains and
offsets are shown in Figs.8,10. The average SVX gain for the AFE board
560575 in low-gain mode is 4.766 ADC counts/QDAC unit and in high gain
mode is 9.95. (One photoelectron, 1 p.e., corresponds to about 7 counts
in the LG mode and about 15 counts in the HG mode). The ratio of SVX
gain in HG mode to LG mode is \~ 2.1 for the board 560575. The
distribution of gain for all installed boards are discussed later.
{width="2.975in"
height="3.861111111111111in"}{width="2.9833333333333334in"
height="3.861111111111111in"}
a. **(b)**
**Fig.6:** SVX response in ADC units as a function of injected charge
(in QDAC units) for channel number 1014 in Low Gain mode (Top) and High
Gain mode (Bottom).
{width="5.5in" height="6.501388888888889in"}
**Fig.7:** Results of linear fits to SVX response vs. charge for all 512
used channels in Low Gain mode. (Top) Fitted SVX Gain, (Bottom) Fitted
offset.
{width="5.5in" height="6.622222222222222in"}
**Fig.8:** Distributions of Fitted SVX gains and offsets displayed in
Fig.7.
{width="5.5in" height="6.55625in"}
**Fig.9:** Same as Fig.7. in High Gain mode.
{width="5.5in" height="6.501388888888889in"}
**Fig.10:** Distributions of fitted SVX gains and offsets in High Gain
mode.
Any channel that has its SVX gain less than 75% of the nominal (average
gain for the board) is tagged as a bad channel.
5. **Discriminator Threshold Scans**
The test stand data also includes threshold voltage scans with different
set amounts of charges injected (Q=0, 20, 35, 50). For each amount of
charge injected (and in case of no charge injection), the threshold
voltage is varied and the digital output from the specific channels are
read out. The output averaged over X events are plotted as the occupancy
as a function of threshold voltage. These provide turn-on curves for
each channel and are shown in Figs.11 and 12 (1 plot/SIFT) for an MCM
for the cases Q=0 and Q=50 DAC units. (The turn-on value for each
channel is taken to be the threshold voltage corresponding to 50%
occupancy at a given charge.) We determine the turn-on width for each
channel as the voltage difference between those corresponding to 10%
occupancy and 90% occupancy.
{width="5.5in" height="5.973611111111111in"}
**Fig.11:** Plots of average occupancy as a function of threshold
voltage for each channel in a SIFT for MCM=3 and AFE Board 560480 in the
absence of charge injection. Most of the channels have overlapping
discriminator turn-on.
{width="5.5in" height="5.753472222222222in"}
**Fig.12:** Same as Fig.10, but in the presence of injected charge Q=50
DAC units
1. **Discriminator Turn-On and SIFT Gains**
The mid-point (50% average occupancy) of the turn-on curve for each
injected charge Q is taken as the threshold voltage value (V~th~). A
linear fit is performed to this V~th~ as a function of Q to obtain the
SIFT gain; the V~th~ values for the three Q values which are shown in
Fig.13 for an AFE board. The discriminator/SIFT gains and offsets for
all the channels are shown in insert from 560480.ps. The average SIFT
gain for this board is --4.34. The distributions for gain and offsets
are shown in Fig.14.
{width="5.372222222222222in"
height="6.413194444444445in"}
**Fig.13:** The threshold voltages (calculated as V~th~ at 50% average
occupancy) for each channel at Q = 20, 35 and 50 QDAC units for AFE
board 560480.
**Fig.14:** (a) SIFT gains and offsets for all channels using data from
Fig.13
Again, as in the case of SVX gain, any channel that has gain less than
75% in magnitude of the average SIFT gain for the board is tagged as a
bad channel.
2. **Turn-On Width**
For each channel, using the threshold voltage scan data (see Figs.11 and
12), we determine the discriminator turn-on width as the difference in
V~th~ for average occupancies of 10% and 90%. They are typically 3-6 DAC
counts.
6. **Zero Suppression Threshold Studies**
1. **Pedestals from Phase-5 Tests**
We studied the zero suppression threshold issues for 50 AFE-boards as
part of the Phase-5 analysis. The initial goal of this test was to find
zero suppression thresholds for every SIFT/MCM allowing for certain
occupancy and to determine the number of bad channels a board has for a
chosen threshold. The number of bad channels would then be included in
the total number of bad channels reported for the board, to be used to
classify the board. Eventually, however, there were problems in
determining and setting of appropriate V~ref~ voltages for different
SIFT chips and also the idea that the behavior of the pedestals on the
platform could be quite different than in Phase-5. So, we decided that
it is not useful to include the bad channels from the phase-5 zero
suppression study in the total bad channel count for board
certification. We, however, describe the study with phase-5 data here.
1. **Finding the Threshold**
For each SIFT, the SVXmean (mean pedestal) values are used to define a
rough zero suppression threshold. Since there are 4 SIFTs in each MCM
and 8 MCMs on an AFE board each board gets 32 different thresholds.
In Fig.15 the SVXmean values for MCM number 1 for board 560606 are
shown.
{width="3.9993055555555554in"
height="3.997916666666667in"} **Fig.15:** SVXmean values for MCM1,
AFE-board 560606
In the first iteration of the study a zero suppression threshold for
each MCM was considered but because of the wide spread in SVXmean values
the number of bad channels was too high. Therefore, subsequently, a
threshold for each SIFT was considered. Fig.16 shows the data for MCM 1
for each of the four SIFTs separately.
{width="6.924305555555556in"
height="6.738888888888889in"} **Fig.16:** SVXmean values for each SIFT
of MCM1, AFE-board 560606
2. **Strategy**
To find a proper threshold the following strategy is used. First one
determines the maximum pedestal mean for each SIFT, i.e. one looks for
the last filled bin. To have a sensitivity for two photoelectrons, 14
ADC counts (because the tests were done in LG mode) are subtracted from
this maximum and channels which have SVXmean entries below that are
identified and labeled as bad channels. If there are any bad channels
found, a new zero suppression threshold was applied. To this purpose the
last filled bin below the first threshold is taken as a new threshold
(that is the channel with mean below the highest). Then 14 ADC counts
are subtracted again and bad channels below this value are looked for.
If there are any we look for a third threshold and if necessary for a
fourth threshold as well. The search for bad channels is applied for all
thresholds in the same way as described above.
As an illustration of this procedure Fig.17 shows the SVXmean
distribution for SIFT 1 of MCM2 and board 560568. The last filled bin
and consequently the maximum pedestal has the SVXmean of 35.86. After
subtraction of 14 ADC counts 5 bad channels are found for the given
threshold (left of the arrow). If we apply the zero suppression
threshold at the second maximum there are no bad channels left because
of the big gap between the last but one and the last filled bin.
{width="4.267361111111111in"
height="4.152777777777778in"}
**Fig.17:** SVXmean distribution for SIFT1 of MCM2 of board 560568
For boards that have a big number of bad channels the SVXmean values are
clustered in some regions resulting in a lot of gaps dispersed over the
whole SVXmean distribution.
3. **Results**
36 boards out of 50 had pedestal widths below 14 counts for all SIFTs so
they had 0 bad channels with zero occupancy above the threshold. 14
boards out of 50 had bad channels by applying the threshold below the
maximum pedestal. By applying the threshold below the second maximum
only 10 boards with bad channels are left. It is possible to reduce this
number to 7 boards if the threshold is set below the third maximum.
Table 1 shows it is not possible to reduce this number again by applying
a new threshold. Table 1 summarizes the number of bad channels for these
14 boards.
**Table.1:** Number of bad channels as a function of number of channels
above threshold.
{width="5.996527777777778in"
height="5.836111111111111in"} **Fig.18:** Number of channels above
threshold.
2. **Pedestals from Platform Tests**
We also analyzed pedestal data recorded for 10 AFE boards on the
platform. These 10 boards have board-numbers:
560464, 560453, 560519, 560498, 560525, 560558, 560561, 560542, 560562,
560489
The distribution of pedestals (calculated in p.e. units and mean
subtracted) for channels in each SVX of the board 560464 are displayed
in Fig.19. In Fig.20(top), the pedestals of all channels from all 10
boards are shown. Fig.20(bottom) shows the distribution of the RMS of
the pedestal reading for each channel in all 10 boards. Since the
platform data was taken in the High Gain mode, we assume 1 photoelectron
(p.e.) = 15 ADC counts.
We then calculate probability for pedestal above a given cut. The
probabilities for each SVX of one board are shown in Fig.21 and for all
10 boards are shown in Fig.22. If we request 3% occupancy, for example,
the cut will be over 2 Pe. In Fig.23 we use mean of each SVX as the zero
point to calculate the probability of the pedestals over given cut of
all 10 boards and the cut will be 1.2 Pe for 3% occupancy. In Fig.24, we
use mean of each SIFT as the zero point to calculate the probability of
the hits over given cut of all 10 boards and the cut will be 1.0 Pe for
3% occupancy.
So, the best sensitivity to signal can be achieved by setting the zero
suppression threshold separately for each SIFT (as anticipated). In
principle the V~ref~ on these boards are set to bring pedestal means of
all the 4 SIFTs within a small range.
6. **Board Certification Issues**
1. **Definition of a Bad Channel**
A channel is defined as bad using the following criteria:
1\. **SVX and SIFT gain:** A channel is flagged as bad if its SVX or
SIFT gain is \< 75% of the nominal gain SVX or SIFT gain, respectively.
Nominal gain is taken as average gain for the board.
2\. **SVX pedestal sigmas:** A channel is flagged as bad if its SVX
pedestal sigma is \> 1 pe (7 ADC counts).
3\. **Discriminator turn-on:** A channel is flagged as bad if the
turn-on defined as the width in DAC counts for 0 to 90% occupancy is
greater than 2 pe (14 DAC counts assuming SVX and SIFT gain are about
equal)
4\. **SVX zero suppression:** A SIFT is flagged as bad if the pedestal
mean distribution for the 14 or 18 channels in the SIFT has a full width
greater than 2 pe (14 ADC counts). The bad channels are those channels
whose pedestal mean is more than 14 ADC counts below the maximum
pedestal mean.
Even though, we performed some simple and crude studies of zero
suppression as explained in section 5.6, we did not use the fourth
criterion (the zero suppression criteria) for grading and selecting
boards for commissioning. More careful and sophisticated studies of
pedestals, their variations and occupancies are needed,
post-installation, to establish appropriate zero-suppression thresholds
and to tag bad channels.
2. **Criteria for Grading AFE Boards**
For commissioning the AFE boards, they were graded based on the number
of bad channels that were found in the offline analysis of the phase-5
data and a few other loose parsing criteria. The boards were rejected if
the V~ref~ scans shoed a spread wider than 1p.e. for channels belonging
to a SIFT.
The classifications were then performed as follows:
Class Criteria
A N~bad~ \<8 channels, Pass LVDS, Bias tests
B N~bad~ \<20 channels, Not A.
C N~bad~ \<64 channels
7. **Summary**
In summary, we would like to show the results of the offline analysis of
the data from recent test data. Figs. 25 through 35 show various results
and typical distribution of pedestals, SVX and SIFT gains, offsets,
turn0on widths, etc. The results for a CFT/CPS board which instruments
CFT channels with outer 4 MCMs and CPS channels with inner 4 MCMs.
To get a global perspective of all the AFE boards, we show plots of
interesting quantities for all boards using latest test data for each
board. First of all, we show the distributions of bad channels for all
boards in Fig.36. The installed boards have bad channels\<20 and mainly
fall into the category of A or B class boards. Quite a bit of repair
work was done to replace/repair SIFTs and/or MCMs to reduce the number
of bad channels.
The pedestal mean and pedestal sigma distributions are shown in Fig.37.
The distributions of all SVX gains and SIFT gains are shown in Figs.38
and 39
{width="5.621527777777778in"
height="4.156944444444444in"}
**Fig.19:** Pedestal distributions in p.e. units (mean-subtracted) for
channels in each MCM for board 560464.
{width="5.500694444444444in"
height="3.876388888888889in"}
**Fig.20: (Top)** Pedestals of all channels for 10 boards listed in
section 5.6.2.
**(Bottom)** RMS of pedestals for all channels for the 10 boards.
{width="5.753472222222222in"
height="4.020833333333333in"}
{width="5.566666666666666in"
height="4.029166666666667in"}
**Fig.21:** Probability for pedestals above a given threshold for each
SVX in a board. Separate curves are shown for each SIFT.
{width="5.6875in" height="4.156944444444444in"}
**Fig.22:** Probability for pedestals above cut containing all boards.
{width="5.809027777777778in"
height="4.088888888888889in"}
**Fig.23:** Probability as in Fig.22 but calculated after subtracting
each SVX mean.
{width="5.809027777777778in"
height="4.250694444444444in"}
**Fig.24:** Same as Fig.23 but calculated after subtracting SIFT mean.
{width="5.993055555555555in"
height="6.622222222222222in"}
**Fig.25:** Results from fits to SVX gain for a CFT/CPS board. The inner
four MCMs are used for CPS and have gains smaller by approximately a
factor of 2.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.26:** Threshold voltage values (at 50% occupancy) for CFT channels
at Q = 20, 35, 50 QDAC units (Ignore inner MCMs)
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.27:** Same as Fig.26 for CPS channels (ignore outer MCMs)
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.28:** SIFT gains and offsets obtained from linear fits to data
from Figs.26 and 27 for CFT and CPS channels respectively.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.29:** Distribution of SVX fit gains and offsets.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.30:** Distributions of SIFT fit gains and offsets.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.31:** Pedestal means and sigmas for all channels for board 560650.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.32:** Distributions of pedestals and pedestal errors for board
560650.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.33:** Discriminator turn-on width in DAC units for all active
channels in AFE560650.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.34:** Distributions of turn-on widths shown in Fig.33.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.35:** Ratio of SVX gain to SIFT gain for all channels displayed as
a function of channel number.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.36:** Distribution of Number of bad channels for all AFE boards.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.37:** Distribution of pedestals for all AFE boards.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.38:** (TOP) Distribution of the SVX gain for all AFE boards.
(BOTTOM) Plots show the SVX gain distributions for the CPS/FPS and the
CFT boards.
{width="5.993055555555555in"
height="7.7555555555555555in"}
**Fig.39:** (TOP) Distribution of the SIFT gain for all AFE boards.
(BOTTOM) Plots show the SIFT gain distributions for the CPS/FPS and the
CFT boards.
| en |
markdown | 347415 | # Presentation: 347415
## Practical Evaluation for Public Health Programs
**2007 AIM / PROGRAM MANAGER MEETING**
**November 6, 2007**
**Betty Apt**
**Division of STD Prevention**
**Centers for Disease Control and Prevention**
## Background
- Two previous webinars
- How to choose what to evaluate
- CDC framework for evaluating public health programs
- Today- Address elements you will need to report on in your 2009 grant applications
## What is Program Evaluation?
- ...the **systematic** collection of information about the activities, characteristics, and outcomes of programs **to make judgments** about the program, **improve** **program effectiveness**, and/or **inform decisions** about future programming.
- *(Patton, Utilization Focused Evaluation, 1997)*
## Why Evaluate?
## Sharks Tracking Ketchup: How We Can Go Wrong
- County did extensive outreach to perform syphilis screening in the community in a variety of venues & settings. Lots of resources devoted to this.
- After one year they had not looked at their data. As part of evaluation project they did.
- Found
- No new cases of syphilis.
- Interventions that work in one setting might not work in another setting.
- Need to evaluate what you are doing.
## What Can Program Evaluation Do?
**Increase Program Knowledge **
**Direct Program Improvement**
**Maximize Resources**
**Provide Accountability**
## CDC’s Evaluation Framework
- Step 1: **Engage Stakeholders**
**Step 2: Describe the Program**
**Step 3: Focus the Evaluation Design**
**Step 4: Gather credible evidence**
**Step 5: Justify conclusions**
**Step 6: Ensure use and share lessons learned**
**Source: Centers for Disease Control and Prevention. Framework for Program Evaluation in Public Health. MMWR1999; 48 (No. RR-11). **
## CDC’s Evaluation Framework Standards
- Utility
- Feasibility
- Propriety
- Accuracy
**Source: Centers for Disease Control and Prevention. Framework for Program Evaluation in Public Health. MMWR1999; 48 (No. RR-11). **
## Program Evaluation Grant Requirement...
- As part of the submission of the continuing grant application for 2009, in August 2008, grantees are required to submit an evaluation plan.
## Evaluation Plan
- An evaluation plan is the “blueprint” that lays out a plan for implementation of your evaluation. The plan describes what the evaluation will look like as well as what information will be collected and what will be done with the results.
## Why do you need an evaluation plan?
- Outline evaluation design, activities and procedures
- Define responsibilities, timeline
- Clarify expectations
## Getting started
- Choose an evaluation component or activity
- Form an evaluation team at your program
- Assess the team’s capacity and resources to conduct evaluation
- Identify relevant stakeholders
## Some Potential Components/Activities to Evaluate
- Immunization information systems
- Adolescent immunization
- Perinatal hepatitis B prevention
- AFIX
- VFC
## Some Potential Criteria...
- Where am I *spending the most?*
- Where am I *concerned the most?*
- Where are my *big successes*?
- Where are my *failures?*
- Other...
- Other...
## Step 1: Engaging Stakeholders
## Who are Stakeholders?
**Stakeholders are individuals or organizations who are interested in, or affected by, the program and/or evaluation.**
## Some Key Stakeholders
- Type: Decision Makers
- Definition: Decide and direct program operations, including how evaluation findings are used
- Examples: Immunization program director, program manager, HD director, health** **commissioner, legislators
- Type: Implementers
- Definition: Involved in program operations
- Examples: Immunization program manager, program staff, private physicians, staff in physician offices
- Type: participants
- Definition: Served by the program / activities
- Examples: Clients/patients, parents, health service providers
- Type: partners
- Definition: Support/invested in the immunization program or target population
- Examples: Funders, managed care plans, schools, medical organizations
## Reasons to Involve Stakeholders
- Find out what they are interested in.
- Increase likelihood that evaluation results will be acted upon.
- Establish what role they will play in the evaluation.
- Obtain “reality check” on utility and feasibility of evaluation plan and methods.
## Tips for Working with Stakeholders
- Communicate to them the benefits of their involvement in the process.
- Incorporate their input, opinions, and insights (or explain why not possible).
- Promise only what you can deliver.
- Maintain regular communications about progress.
## Step 2: Describe the component
## Describing the Program Through
**Logic Models **
## Defining Logic Models
**A graphic representation, or a flow chart, that shows how a program is supposed to work, i.e., how the components of the program should produce desired outcomes. **
## Benefits of Logic Models
- Provides roadmap of expected program progress and results.
- Provides a framework and guide for program planning and evaluation.
- Builds clarity and understanding among stakeholders on how a program is supposed to work.
- Identifies resources needed.
- Identifies gaps.
## Describing the Program: Complete Logic Model
- A flow chart with boxes and arrows leading to the next item. The flowchart includes the following boxes horizontally:
- Inputs
- Activities
- Outputs
- Short Term Effects/Outcomes
- Intermediate Effects/Outcomes
- Long term effects/outcomes
## Inputs = resources
Activities = what the program and its staff actually do
Outputs = tangible products of activities
Outcomes = results of activities (who or what will change)
- Activities = what the program and its staff actually do
- Outputs = tangible products of activities
- Outcomes = results of activities (who or what will change)
## Types of Logic Models
- Type: Global
- Description:" Big picture” of entire program
- Type: Nested
- Description: segment or component of a program
## Global Logic Model for State X STD Program
- Note: The following slides show the boxes for each aspect of the logic model
**INPUTS**
- Funds
- Assigned Staff
- Technical assistance and collaboration
## ACTIVITIES
- -Provide community and individual behavior change interventions on syphilis.
- -Provide med and lab services.
- Provide Ct screening of young women.
- -Ensure syphilis partner services.
- -Promote leadership and program management.
- -Conduct surveillance and data management.
- -Provide professional development.
## Female admitees in juv detention facilities tested for Ct.
_**Community/ Individual Behavior Change Interventions**_
- -Interventions on syphilis implemented among at risk MSM.
_**Medical and Lab Services**_
- -Lab/med facilities and providers report test results.
**Female admitees in juv detention facilities tested for Ct.**
_**Partner Services**_
- -Syphilis cases’ partners identified.
_**Leadership and Program Management**_
- -Strategic plan in place.
- -Program operation plan to monitor program activities.
- -Appropriate program policies in place.
_**Surveillance and Data Management**_
- -Reported cases of P&S syphilis and Ct sent to CDC in timely manner.
_**Training and Professional Development**_
- -Staff training needs regularly assessed.
- -Training opportunities on syphilis and Ct provided.
_**STD Outbreak Response Planning**_
- -Plan includes required elements.** **
## SHORT-TERM OUTCOMES
- Increased knowledge:
- -consequences;
- -Safe behaviors;
- -Self assessment of risk.
- Increased intention to use condoms.
**INTERMEDIATE OUTCOMES**
- Increased safer sex behaviors:
- -Abstinence
- -Mutual monogamy
- -Fewer concurrent partners
**LONG-TERM OUTCOMES**
- -Reduced syphilis incidence
- - Reduced Ct prevalence
## Nested Logic Model of Chlamydia Screening Program for
**Adolescent Females in County Z Juvenile Detention Centers**
**Inputs**
_**Funds**_** **
** **
_**JDC Staff**_** **
_**Technical Direction, Assistance, and Collaboration**_
_**Materials**_
## Activities
**Provide professional development in Ct services**** **
**Provide JDC support for developing and implementing CT services**** **
**Conduct Ct services for female adolescent admittees****.**** **
## Outputs
**JDC clinical staff participated in professional development**** ****events. **
**JDC administration authorized time and staff for development and implementation of screening**** ****program. **
**Female adolescents counseled and screened**** **
## Short-term outcomes
_**JDC Providers**_**Improved knowledge and skills for Ct services **
_**JDCs**_
**Increased numbers of programs in JDCs that provide Ct services.**** **
## Intermediate Outcomes
_**JDC Providers**_
**Increased clinicians’ adherence to Ct clinical practice guidelines**** **
_**Adolescent Females**_
**Decreased number of partners. Increased health seeking behavior. **
## Long-term Outcomes
_**JDCs**_
**Reduction of Ct prevalence among adolescent females in JDCs. **
## Logic Model for AFIX
- Inputs
- Funding
- Staff
- Time
- CoCASA
## Activities
- Develop AFIX protocol
- Train AFIX staff
- Set up provider visits
- Review provider records & assess coverage level
- Provide feedback & recommend strategies for improvement
- Acknowledge & reward improved performance
- Document outcome of visit in database (CoCASA)
- Promote information exchange
## Outputs
- Protocols
- Trained staff
- Providers visited
- Coverage assessment
- Recommendations
- Rewards provided
- Data in database
- Information exchanged
## Outcomes
- Increased provider knowledge
- Increased provider motivation
- Change in office practices and policies
- Change in physician behavior
- decreased missed opportunities
- decreased invalid doses
- increased timely vaccine receipt
- Increased Vaccinations
- Decreased VPDs
## Describing the Program Through...
**Goals and**
**SMART Objectives**
## What is a goal?
- States what should happen as a result of the program/activity
- Describes the expected long-term effects of a program/activity.
- Serves as the foundation for development of objectives.
## Examples
- To improve the health status of Georgia children.
- To increase the proportion of children who are immunized.
- To decrease vaccine preventable diseases.
## What is an objective?
- Describes how you plan to achieve your goal.
- Reflects a _partial accomplishment_ of the goal.
- Serves as the _basis for monitoring progress_ towards achieving program goals.
*If you are meeting your objectives, you will hopefully meet your goal. *
## What’s the Connection between program goals and program objectives?
## Characteristics of a Well-Written Objective
_**It is SMART**_
_**S**_pecific
_**M**_easurable
_**A**_chievable
_**R**_elevant
_**T**_ime-Bound
## SMART Objectives and Evaluation
- Monitor progress
- Identify problems
## Specific
- “who”
- “what” –action
- one action verb per objective
- “where” – location of the action
## Specific
- “who” - target population
- Children ages 18-24 months
- “what” – action
- Conduct 1 workshop on AFIX protocol in every health region of the State
## Measurable
- “How much” change is expected
- Increase the number 18 -24 month old children who receive all vaccinations _**from 20% to 40%.**_
## Achievable
- Should be realistic – personnel, money, etc.
- At least 70% of private providers will implement one or more of the recommended interventions by the proposed date.
## Relevant
- Relates to the program goals.
- At least 50% of parents who attended the health fair and completed an evaluation will report increases in knowledge about VPD
_**T**_**ime-bound**
- “When” the objective will be measured/met
- By March 31, 2008, ...
## Example 1
- By Dec 31, 2009, 100% of AFIX feedback sessions conducted in 2009 will have included a quality improvement plan that includes all four key items.
***SMART?***
***Yes***
**S****pecific: **who, what, where
**M****easurable: **how much change
**Achievable: **realistic
**R****elevant: **relate to goals
**T****ime-bound: **when
## Example 2
- During 2008, physician practices will receive appropriate feedback.
***SMART?***
***NO***
**S****pecific**
**M****easurable**
**Achievable**
**R****elevant**
**T****ime-bound**
## Types of Objectives
**Process Objectives**
- Describe program activities
- Specify actions to be taken to measure program implementation
**Outcome Objectives**
- Relate to changes in the target population or end result of a program (changes in policies, regulations, sustainability)
- What the target population will know or will be able to do by the conclusion of the program
## Types of Outcome Objectives
- Type: Short Term
- Definition/Examples: Initial changes in target population/organization/group
- (awareness, knowledge, attitudes, skills)
- Type: Intermediate
- Definitions/Examples: Interim changes
- (norms, behavior, policy).
- Type: Long Term
- Definitions/Examples: Changes in health status, morbidity as result of sustained program implementation.
## SMART Objectives Group Exercise
- The State Immunization Program manager is concerned about the quality of feedback AFIX field staff are giving to physician practices.
- As a group, for the AFIX program, write:
- 1 process
- 1 short-term,
- 1 intermediate, and
- 1 long-term outcome objective based on the SMART criteria.
## Examples of Objectives
**Goal: Improve vaccination coverage among children **
**and adolescents in the state through the AFIX program****.**
- Include the following:
- process
- short term outcome
- intermediate outcome
- long term outcome
## Steps 3 & 4: Evaluation Focus & Data Collection
## Plan Your Evaluation by...
**What questions you want the evaluation to answer about your program?**** **
## Examples of Evaluation Questions
- Type: Process
- Definition: Determines if program activities are implemented as intended;
- Provides feedback for program improvement; conducted throughout project life.
- Examples: Were recommendations of the reviewers implemented by the providers?
- Type: Outcome
- Definition: Measures program effects; changes in target population’s knowledge,
- attitudes, skills, intentions, behaviors; or organizational changes
- (e.g., policy adoption); linked to process evaluation; provides feedback for program
- improvement.
- Examples: Did the number of missed opportunities decrease?
## Purpose of Evaluation Questions
- Helps focus the evaluation.
- Guides the evaluation planning process.
- Facilitates decision-making about evaluation methods to use.
- Helps ensure use of the evaluation findings
## How Questions Direct the Data Collection and Analysis Plan
**EXAMPLE QUESTION: During feedback sessions in 2007,did all physician **
**practices receive a quality improvement (QI) plan containing all four key items? **
- 1. Opportunity for improvement on which to focus
- 2. Define action steps for implementing the intervention
- 3. Responsible party for implementation
- 4. Date to implement intervention
## Steps To Develop Evaluation Questions
**Involve stakeholders.**** **
**2. Brainstorm on possible evaluation questions.**
** *****What do you want the evaluation to answer about the program component or activity?***
## Steps to Develop Evaluation Questions (continued)
**3.**** **Prioritize questions with criteria of:
- Important to stakeholders;
- Will provide information that can be acted upon;
- Can be answered with available resources;
- Can be answered within available timeframe; and
- Will be supported by program decision-makers.
- 4. Develop a final list.
## Data Collection and Analysis
**EXAMPLE QUESTION: During feedback sessions in 2007, did all physician **
**practices receive a quality improvement (QI) plan containing all four key items? **
- Flow chart diagram with the following boxes from left to right:
- Indicators, target, data sources, data collection, analysis
## What is an Indicator?
- The piece of information that you need to give you the answer to your evaluation question
- A measure that shows the progress made
- The “how will I know” answer
## What are Data Sources?
- Where or from whom you will get data for each of your indicators to answer your evaluation questions.
- Data Source: Documents
- Examples: medical records, meeting minutes, surveillance reports, interview records
- Data Source: Individuals
- Examples: staff, providers, partnership members
- Data Source: Observations
- Examples: data obtained from observations of staff, environment (reception area),
- office flow, activities, etc.
## Advantages/Disadvantages of Data Sources
- Data Source: Documents
- Advantages: data available and accessible
- Disadvantages: value of data depends on how accurately it was recorded; may lack data needed for the
- evaluation
- Data Source: Individuals
- Advantages: can be collected from target population
- Disadvantages: may be unreliable due to social desirability and/or recall difficulty
- Data Source: Observations
- Advantages: can supplement self-report; provide information on behavior, skill environment
- Disadvantages: value of data depends on training of observer and specificity of instrument
## Data Collection Methods
**Surveys**
**Interviews**
**Focus Groups**
**Observation**
**Document Review**
## Data Collection Methods
- Method: Survey
- Advantages: anonymity possible; can administer to groups; efficient and cost effective
- Disadvantages: forced choices limit response; wording may bias response; impersonal
- Method: Individual interviews
- Advantages: can build rapport; can probe for more information; can get breadth/depth of information
- Disadvantages: time consuming, expensive, interview style may bias
- Method: focus groups
- Advantages: can get breadth and depth of information in short time frame; can convey key information regarding the program
- Disadvantages: need trained facilitator; time consuming to analyze responses
- Method: Observation
- Advantages: Can assess fidelity as activities occur
- Disadvantages: interpretation of behavior difficult; expensive and time consuming
- Method: Document review
- Advantages: information already exists; does not disrupt program
- Disadvantages: depends on quality of information; time consuming
## Data Collection Procedures
- Use existing data when feasible
- Understand agency policies and regulations that may affect data collection
- Identify who will be responsible
- Identify the timeline of when the data will be collected.
- Be clear about the data you want to collect and sensitive to the time and effort that will need to be expended by the data providers
- Design instruments as needed
## Using Mixed Data Sources/Methods
- Involves using more than one data source and/or data collection method.
- Advantages:
- Allow examination of different facets of the same phenomenon
- Obtain comprehensive information
- Increase validity of results
## Step 5: Justify Conclusions
## Now that you’ve collected the data, what do you do with it?
**Analyzing data **
**Who**
**When**
**How**
**Interpretation of results and sharing findings**
## Things to Consider When Analyzing Data
- Quantitative Methods
- Develop a database for all fields in the data collection instrument
- Depending on type of analysis, specific quantitative skills may be needed
- Qualitative Methods
- Categorize similar findings (coding, subcoding)
- Look for patterns
## EXAMPLE QUESTION: During feedback sessions in 2007, did all physician
**practices receive a quality improvement (QI) plan containing all four key items*? **
- Indicator:
- Percent of practices that received a QI plan following an AFIX visit during 2007;
- percent of QI plans that included all four key items
- Target:
- 100% of practices received a QI plan following an AFIX visit during 2007;
- 100% of QI plans contained all four key items
- Data Sources: AFIX field staff; site visit notes or records
- Data Collection:
- Method – Review site visit notes or records; survey field staff
- Timeline – twice a year
- Person Responsible – state health department AFIX coordinator
- Analysis:
- Method – frequency
- Timeline – twice a year
- Person responsible – State health department AFIX coordinator
- *Four key items:
- 1. Opportunity for improvement on which to focus
- 2. Define action steps for implementing the intervention
- 3. Responsible party for implementation
- 4. Date to implement intervention
## Data Collection and Analysis Group Exercise
- Evaluation Question: During 2007, did physicians implement recommendations by the proposed date as outlined in the QI plan?
- As a group, using the exercise handout, complete
- the table by developing appropriate:
- indicators,
- targets
- data sources,
- data collection methods, and
- type of analysis.
## CDC Framework for Program Evaluation
## Share the results and lessons learned from the evaluation with stakeholders and others
Use your evaluation findings to modify, strengthen, and improve your program
**Use your evaluation findings to modify, strengthen, and improve your program**
**Step 6: ****Ensure Use and ****Share Lessons Learned**
## Step 6: Ensure Use and Share Lessons Learned
**Share the results and lessons learned from the evaluation with stakeholders and others**
**Use your evaluation findings to modify, strengthen, and improve your program**
## Interpreting Findings
**Always refer to your evaluation questions.**
**Identify findings that will help answer the evaluation questions.**
**Stakeholders may provide some insight about the findings**
## Developing Recommendations
- Your evaluation’s recommendations should be:
- Linked with the original purpose of your evaluation.
- Based on answers to your evaluation questions.
- Linked to findings from your evaluation
- Tailored to the users of the evaluation results to increase ownership and motivation to act.
## How to Share the Evaluation Results/Recommendations
- Consider information needs of the audience/stakeholders.
- Tailor message and format of dissemination to the users of the evaluation results
**Oral **
**Written**
**Full Report**
**Executive Summary**
## Type of Dissemination Methods
- _Evaluation Reports_
- Provide an executive summary.
- Use examples, graphics, quotes to highlight findings.
- Present data simply and concisely.
- Use active verbs to shorten sentences.
- Organize results by evaluation question.
## Type of Dissemination Methods
**Oral Presentations**
- Use slide show; provide handouts
- Involve audience in discussion of how to use findings to improve program, help set policy, etc.
**Mass Media**
- Use portions of executive summary.
- Follow your agency’s protocol on how to address the media.
## Acknowledgements
- _ISD/NCIRD_ _AIM_
- Nancy Fasano Helen Fox Fields
- Suchita Lorick Jesse Greene
- Greg Reed Claire Hannan
- Pascale Wortley
- Evaluation Workgroup
- _Division of STD Prevention_
- Health Services Research & Evaluation Branch
- Yamir Salabarría-Peña
- Tom Chapel
## This document
- This document can be found on the CDC website at:
- _[http://www.cdc.gov/vaccines/programs/progeval/downloads/prog-man-meeting07-508.ppt](http://www.cdc.gov/vaccines/programs/progeval/downloads/prog-man-meeting07-508.ppt)_** ** | en |
all-txt-docs | 699235 | new-eng-crop-weather
State
NEW ENGLAND WEEKLY CROP WEATHER
Week ending date
For week ending 05/27/01
Issue
NH-CW2101
Volume 21, Number 4
(issued weekly on the Internet, May - October)
May 29, 2001 - 4 pm
Agricultural Summary
For the week ending May 27, 2001, there were 5.1 days available for field work
across New England. Pasture condition was rated as 1% very poor, 23% poor,
38% fair, 37% good, 1% excellent. Major farm activities included: planting
row crops and vegetables, transplanting tobacco and some vegetables, applying
fertilizer, plowing, and spraying for weeds and insects.
SOIL MOISTURE ACROSS NEW ENGLAND
----------------------------------------------
-- Percent --
Soil Rating This Week Last Week Last Year
----------------------------------------------
Topsoil Moisture
Very Short 6 24 0
Short 34 42 1
Adequate 53 34 51
Surplus 7 0 48
Subsoil Moisture
Very Short 5 9 0
Short 32 33 1
Adequate 57 57 58
Surplus 6 1 41
----------------------------------------------
Field Crops Report
The rain which fell over most of New England this past week raised farmers'
spirits for the coming growing season; however, the northernmost parts of
the region are still looking for rain clouds. Growers were active with spring
fieldwork in between showers. Potato planting in Maine, Massachusetts, and
Rhode Island is almost complete. Transplanting of broadleaf tobacco has
begun. Farmers are expected to begin chopping haylage this next week as crops
have headed out; first cut hay crops are looking very short due to the lack of
rain early in the spring.
Fruit, Vegetable, and Specialty Crops Report
VEGETABLES: Farmers planted broccoli, sweet corn, onions, cucumbers, squash,
peas, peppers and other spring vegetables. Cole crops were in good condition.
Asparagus and rhubarb crops were being harvested. Farmers who were previously
hesitant to plant should be starting now that the ground has received some
moisture. Farmers who had vegetables already planted are hoping the rain will
accelerate growth; it had been previously reported as slow. Roadside stands
did well over the holiday weekend.
FRUIT: Growers were active in spraying fruit crops for weeds and insects between
showers. Orchard fruit in the southern New England states was still struggling
to improve from the frosts which hit earlier this month. Bees were being
moved onto berry fields in preparation for bloom. Most strawberry crops are
approaching petal fall stage. Maine wild blueberries are currently on the path
toward another successful season. Cranberry plants in Massachusetts appeared
to have weathered the near-drought conditions well and are nearing early bloom
stage.
Crop Progress Tables
FIELD CROP PROGRESS ACROSS NEW ENGLAND
---------------------------------------------------------
--Percent Planted-- Percent
Crop 2001 2000 5-yrAvg Emerged Condition
---------------------------------------------------------
Potatoes
Maine 90 55 65 5 Good
Mass 90 85 90 55 Good
Rhode Isl 100 99 85 80 Good
Oats, ME 85 75 75 45 Excel/Good
Barley, ME 90 80 75 50 Excel/Good
Silage Corn 80 30 50 35 Good
Sweet Corn 65 45 50 35 Good/Fair
Tobacco
Shade 60 55 55 -- Good
Broadleaf 5 10 15 -- Good
Dry Hay -Percent Harvested-
First Cut 10 <5 10 -- Fair/Good
------------------------------------------------------
FRUIT CROP DEVELOPMENT ACROSS NEW ENGLAND
--------------------------------------------------------
Fruit Fruit
Crop Stage Set Size Condition
--------------------------------------------------------
Apples Petal Fall Avg Avg Good
Peaches Petal Fall B.Avg/Avg Avg Fair
Pears Petal Fall B.Avg/Avg Avg Poor
Strawberries Full Blm -- -- Good/Excel
Cranberries,MA Bud -- -- Good
Blueberries
Highbush Full Blm Avg -- Good/Fair
Wild,ME Full Blm A.Avg -- Good
--------------------------------------------------------
Weather Summary
For the Week ending Sunday, May 27, 2001
---------------------------------------
AIR TEMPERATURES PRECIPITATION
STATE LO HI AVG DFN LO HI
-- --- --- --- --- ---- ----
ME 30 83 57 +2 0.00 0.28
NH 32 79 57 +0 0.00 1.66
VT 32 78 58 +2 0.02 3.09
MA 41 78 57 -2 0.87 4.47
RI 44 77 58 -1 2.84 4.68
CT 44 73 57 -3 2.45 5.02
--------------------------------------
Weather Information Table
AIR CUM SINCE MAR 1
TEMPERATURE GROWING DEGREE DAYS
----------- BASE-50F BASE-60F
STATION LO HI AVG DFN TOT DFN TOT DFN
------- -- -- -- -- --- ---- --- ----
MAINE
Albion 34 77 56 -3 193 +29 39 +24
Allagash 33 83 59 +7 146 +88 15 +15
Augusta_ME 42 74 57 -2 250 +106 64 +53
Bangor 38 79 58 +3 222 +114 48 +42
Barnard 37 77 58 +4 188 +106 31 +29
Bath 35 72 53 -4 161 +58 32 +28
Bethel 35 79 58 +2 216 +98 37 +28
Brassua_Dam 38 79 58 +6 140 +95 9 +9
Brunswick_ME 40 69 54 -3 189 +86 42 +38
Caribou 40 80 61 +8 210 +131 40 +37
Corinna 39 79 59 +3 223 +112 42 +35
Danforth 30 81 57 +3 164 +82 21 +19
Dover-Foxcroft 39 75 58 +4 171 +89 21 +19
Durham 36 73 55 -5 187 +39 42 +34
East_Hiram 37 74 56 -2 190 +72 41 +32
Eustis 36 75 55 +3 115 +64 6 +6
Frenchville 43 79 61 +9 195 +137 37 +37
Gray 40 71 55 -2 244 +144 67 +67
Greenville_ME 38 77 58 +4 170 +78 22 +17
Guilford 34 76 56 +2 180 +98 30 +28
Hollis 36 74 55 -1 204 +109 49 +49
Houlton 31 79 58 +5 181 +100 31 +27
Kennebunkport 39 69 51 -9 167 -8 54 +42
Livermore_Falls 35 80 57 +3 214 +132 51 +49
Moosehead 36 78 57 +5 140 +95 14 +14
New_Sharon 39 78 59 +5 247 +165 62 +60
Patten 37 76 56 +3 143 +62 16 +12
Portage 44 82 62 +9 225 +146 58 +55
Portland_ME 41 67 53 -4 201 +101 49 +49
Rangeley 37 75 56 +5 119 +71 4 +4
Sebec_Lake 35 79 58 +4 175 +83 28 +23
Vanceboro 35 78 58 +4 162 +91 21 +21
Waterville 38 76 57 -2 207 +43 37 +22
NEW HAMPSHIRE
Barnstead 40 74 57 -2 263 +101 68 +49
Benton 41 73 58 +2 213 +74 35 +18
Berlin_AG 40 78 60 +4 219 +100 35 +22
Bethlehem 40 77 59 +3 202 +65 28 +11
Concord 39 74 57 -2 281 +119 77 +58
Diamond_Pond 41 75 58 +7 157 +107 23 +23
First_Conn_Lake 39 75 57 +6 123 +73 3 +3
Greenville 38 78 54 -4 216 +65 51 +35
Keene_AP 45 73 59 -2 287 +64 67 +30
Lakeport 44 75 59 +3 274 +138 60 +47
Marlow 40 72 56 -4 186 -3 29 +2
Mt_Washington 32 57 43 +6 2 +2 0 +0
North_Conway 41 77 59 +2 282 +143 73 +59
Otter_Brook_Lk 44 74 58 -3 248 +25 48 +11
Plymouth 36 79 56 +1 210 +103 36 +27
Rochester 38 78 56 -4 275 +86 91 +65
Weare 40 70 55 -4 229 +40 58 +31
VERMONT
Ball_Mt_Lake 42 73 54 -4 146 +7 16 -1
Bethel 38 77 59 +4 226 +104 39 +26
Burlington_VT 53 78 63 +5 355 +153 107 +74
East_Haven 32 77 58 +5 174 +92 20 +15
Island_Pond 44 77 61 +8 188 +103 27 +22
Montpelier 43 72 58 +2 215 +80 39 +23
Morrisville_AG 39 74 58 +3 150 +28 19 +6
Mount_Mansfield 39 73 51 +3 93 +67 4 +4
Northfield 41 74 59 +5 213 +109 30 +21
Pownal 46 75 57 +2 258 +114 56 +37
Rochester 42 76 58 +3 203 +81 23 +10
Rutland_AG 49 74 60 +0 241 +4 41 -6
Sunderland 47 73 57 -3 195 -27 24 -13
Sutton 44 74 58 +6 199 +117 33 +28
Townshend_Lake 44 77 57 -2 222 +38 41 +13
Union_Vill_Dam 40 77 58 -1 223 +30 29 +0
MASSACHUSETTS
Ashburnham 47 70 56 -2 279 +149 73 +64
Boston 50 61 55 -7 367 +121 122 +98
Greenfield 45 76 57 -4 297 +48 81 +44
New_Bedford 46 68 59 -3 299 +52 73 +49
Otis_AFB 46 68 57 +1 252 +117 66 +60
Plymouth 43 72 57 -2 270 +119 65 +57
Walpole 48 72 58 -2 356 +165 115 +96
West_Medway 48 73 59 +0 355 +164 112 +93
Westover 50 73 58 -6 384 +55 119 +60
Worcester 46 68 55 -4 322 +157 101 +87
Worthington 43 70 54 -4 229 +90 59 +45
RHODE ISLAND
Providence 49 70 59 -2 381 +165 118 +100
Woonsocket 44 77 59 +0 368 +181 122 +108
CONNECTICUT
Bakersville 45 73 56 -7 290 -18 82 +24
Bridgeport 51 64 57 -5 377 +116 94 +52
Hartford_AP 48 73 58 -6 398 +97 124 +68
Norfolk 44 70 54 -3 267 +132 76 +64
Norwich 49 73 60 -2 377 +113 99 +57
Thomaston_Dam 46 73 57 -3 317 +110 83 +56
Willimantic 50 72 61 +2 399 +193 117 +91
1-WEEK PRECIP 4-WEEK CUM PRECIP
------------- -----------------
TOTAL TOTAL
STATION INCHES DFN DAYS INCHES DFN DAYS
------- ----- ---- --- ----- ---- ---
MAINE
Albion 0.00 -0.84 0 1.01 -2.32 5
Allagash 0.04 -0.69 1 0.68 -2.14 4
Augusta_ME 0.00 -0.84 0 0.52 -2.95 7
Bangor 0.00 -0.77 0 1.00 -2.24 9
Barnard 0.00 -0.84 0 0.91 -2.35 8
Bath 0.06 -0.77 1 0.34 -3.02 5
Bethel 0.01 -0.83 1 0.37 -2.94 4
Brassua_Dam 0.00 -0.78 0 1.21 -1.86 6
Brunswick_ME 0.00 -0.83 0 0.36 -3.00 5
Caribou 0.01 -0.69 1 0.53 -2.23 7
Corinna 0.00 -0.81 0 1.01 -2.21 5
Danforth 0.00 -0.85 0 1.70 -1.67 7
Dover-Foxcroft 0.00 -0.84 0 1.15 -2.11 8
Durham 0.00 -0.81 0 0.42 -2.88 5
East_Hiram 0.12 -0.72 1 0.49 -2.96 6
Eustis 0.00 -0.77 0 2.92 -0.03 6
Frenchville 0.00 -0.73 0 0.44 -2.38 5
Gray 0.01 -0.76 1 0.44 -2.87 5
Greenville_ME 0.00 -0.84 0 0.77 -2.49 7
Guilford 0.00 -0.84 0 1.00 -2.26 7
Hollis 0.26 -0.58 1 0.60 -2.86 4
Houlton 0.01 -0.76 1 0.93 -2.07 6
Kennebunkport 0.28 -0.56 2 0.82 -2.72 6
Livermore_Falls 0.00 -0.85 0 1.12 -2.27 6
Moosehead 0.00 -0.78 0 1.18 -1.89 7
New_Sharon 0.00 -0.85 0 1.28 -2.11 4
Patten 0.03 -0.74 2 1.03 -1.97 8
Portage 0.04 -0.66 1 0.57 -2.19 6
Portland_ME 0.04 -0.73 1 0.41 -2.90 4
Rangeley 0.01 -0.76 1 0.99 -1.85 6
Sebec_Lake 0.00 -0.84 0 0.94 -2.32 8
Vanceboro 0.00 -0.79 0 1.08 -2.23 7
Waterville 0.00 -0.84 0 0.79 -2.54 5
NEW HAMPSHIRE
Barnstead 0.62 -0.08 3 1.21 -1.59 9
Benton 0.22 -0.60 2 1.38 -1.66 6
Berlin_AG 0.00 -0.84 0 0.42 -2.76 4
Bethlehem 0.04 -0.74 2 0.81 -2.12 7
Concord 0.71 +0.01 2 0.90 -1.90 5
Diamond_Pond 0.01 -0.94 1 1.64 -1.85 6
First_Conn_Lake 0.06 -0.89 1 1.77 -1.72 6
Greenville 1.50 +0.64 5 1.61 -1.77 8
Keene_AP 0.02 -0.87 2 1.00 -2.40 3
Lakeport 0.32 -0.52 2 0.57 -2.66 6
Marlow 0.76 -0.15 5 0.95 -2.72 9
Mt_Washington 0.09 -1.59 1 1.32 -5.44 5
North_Conway 0.16 -0.75 1 0.52 -3.11 4
Otter_Brook_Lk 1.66 +0.77 5 2.24 -1.16 10
Plymouth 0.18 -0.73 3 0.46 -3.12 6
Rochester 0.25 -0.59 2 0.98 -2.59 7
Weare 0.85 -0.06 3 1.05 -2.62 7
VERMONT
Ball_Mt_Lake 2.04 +0.99 5 2.22 -1.92 6
Bethel 0.84 -0.14 3 0.98 -2.94 6
Burlington_VT 0.21 -0.49 3 1.10 -1.68 6
East_Haven 0.17 -0.70 1 0.56 -2.64 3
Island_Pond 0.02 -0.88 1 1.58 -1.67 4
Montpelier 0.51 -0.26 3 0.72 -2.15 6
Morrisville_AG 0.14 -0.70 3 1.06 -2.15 5
Mount_Mansfield 0.54 -0.76 3 2.10 -2.88 6
Northfield 0.76 -0.02 2 0.91 -2.25 3
Pownal 1.89 +0.84 6 2.10 -2.04 7
Rochester 1.03 +0.05 4 1.20 -2.72 6
Rutland_AG 1.02 +0.18 5 1.39 -1.71 8
Sunderland 1.50 +0.66 6 1.92 -1.28 9
Sutton 0.25 -0.62 2 1.27 -1.93 4
Townshend_Lake 3.09 +2.32 6 3.40 +0.19 10
Union_Vill_Dam 0.25 -0.59 3 0.67 -2.55 8
MASSACHUSETTS
Ashburnham 1.06 +0.22 5 1.22 -1.95 8
Boston 1.03 +0.33 5 1.11 -1.85 9
Greenfield 4.47 +3.56 6 4.48 +0.98 7
New_Bedford 4.22 +3.39 5 4.28 +0.94 7
Otis_AFB 2.79 +1.95 5 2.86 -0.55 8
Plymouth 4.19 +3.34 5 4.28 +0.64 7
Walpole 2.29 +1.52 6 2.39 -0.78 8
West_Medway 2.24 +1.47 5 2.47 -0.70 8
Westover 3.45 +2.50 6 3.55 -0.13 8
Worcester 1.90 +0.92 6 2.18 -1.74 9
Worthington 4.09 +3.05 6 4.12 -0.07 9
RHODE ISLAND
Providence 3.73 +2.89 5 3.75 +0.31 6
Woonsocket 4.68 +3.77 5 4.77 +1.07 8
CONNECTICUT
Bakersville 4.32 +3.40 6 4.69 +0.96 8
Bridgeport 2.92 +2.07 6 2.96 -0.62 7
Hartford_AP 4.13 +3.21 6 4.43 +0.70 9
Norfolk 4.10 +3.05 6 4.25 +0.11 11
Norwich 4.83 +3.87 6 4.84 +0.74 7
Thomaston_Dam 3.64 +2.66 6 3.70 -0.35 7
Willimantic 2.45 +1.54 5 2.46 -1.36 6
Summary based on NWS data.
DFN = Departure From Normal (Using 1961-90 Normals Period).
Precipitation (rain or melted snow/ice) in inches.
Precipitation Days = Days with precip of 0.01 inch or more.
Air Temperatures in Degrees Fahrenheit.
Copyright 2001: AWIS, Inc. All Rights Reserved.
For detailed ag weather forecasts and data visit the AWIS home
page at www.awis.com or call toll free at 1-888-798-9955.
Other Agricultural Comments and News
CONNECTICUT - Howard Rood (FSA), Fairfield/Litchfield: Several inches of much
needed rain fell this past week. Hay that has been cut up to this time has been
very short, due to the dry weather. Dry weather may have hurt weed control in
corn. Apple and peach crops may have been damaged by frosts early this week.
Dawn Pindell (FSA), Windham: Rain finally arrived and decided to stay, good
thing as farmers were comparing our current soil loss to the pictures of the
30's when the wind would blow it across the open plains. Rain was too late to
help first cutting hay, but corn and vegetables have happy feet soaking up the
moisture. Fruit crops are in sad shape due to earlier freeze, and early
vegetables stopped producing without irrigation. June around the corner should
bring better crop days. Richard Meinert (Ext), CT Cooperative: For weeks we
didn't have any rain - now we have TOO MUCH. Seven inches in 7 days - what a
difference a week makes! Grass hay/haylage is going by as timothy and orchard
grass are or have flowered. Yield of first cut low, most growers wondering if
it will even pay to go harvest it. Weeds are exploding out of the ground now
that they have some water.
MAINE - Marvin Hedstrom, Northern Aroostook: Potatoes: Growers finishing up
planting potatoes. Planting last of small grain crops. Emergence is very slow
due to extremely dry conditions. Grain that has emerged is suffering from dry
conditions. Rain is needed very badly. Dee Potter (Ext), Northern Aroostook:
Many farms have wrapped up planting of potatoes and small grains. Cattle are
out on pasture. Much needed rain began the evening of May 28; up until then it
had been hot and dry. Erin Chadbourne (Ext), Central Aroostook: Potato planting
finishing. Barley and oats emerging. Broccoli planting continuing. Herbicide
applications in potatoes has begun. Steve London (Ext), Southern Aroostook:
Planting has been going very well, could use some rain. Albert Dow (NRCS),
Piscataquis: Remained dry. Tilling and planting still going on. Silage corn has
emerged on some fields. Donna Lamb (Ext), Piscataquis: Weekend rains were a
great relief to farmers. Forage growth has started to respond to the added
moisture. Earlier this week berry growers were irrigating their crop. Janet
King/Jennifer Zweig (FSA), Somerset: Much needed rain on Sunday, although
moisture is still needed. Silage and sweet corn is being planted, much of it
has emerged. Rick Kersbergen (Ext), Waldo: Finally -- some substantial rain --
corn crops are popping out of the ground. Hay/haylage harvest should begin this
week. Strawberries will be flowering soon as well. Trudy Soucy (FSA),
Knox/Lincoln: The first crop of fresh greens has arrived. Much needed rain over
the weekend! Bees had a good week for pollination. Hay crop looking short. David
Yarborough (Ext), Washington: Wild Blueberries: Bees have been moved into all
fields for pollination. Cool weather has slowed development so crop development
is near normal. Plants have emerged on all pruned fields. Michael Tardy (FSA),
Androscoggin: The recent rain has helped but we need more. Planting has gone
great but water is needed to get things growing. There's talk about haying but
the crop will be short without the water. All producers have been able to get
field work done. We need the rain but it's nice to have the time to work the
fields. Let's hope that we get a good mix in the coming weeks. Parker Rand
(FSA), Cumberland/York: Great spring for all outside activities, but too dry. If
we don't get a lot of rain soon it will be very serious. Gary Raymond (FSA),
Franklin: The rain was timely once again. Pastures and hayfields are now
starting to grow. Planting conditions have been optimum. Sprouting plants look
good. Laura Rand (FSA), Oxford: Dry weather continues.
MASSACHUSETTS - Arthur Williams (FSA), Berkshire: Still some corn planting.
Several operators cutting and chopping forage (not much wilting), but real
short growth. Dry crops got rain as needed. Finally, some rain, a little over
1.5 inches. It's a real help. Everything is greening, nice! Paul Russell (FSA),
Southeast Massachusetts: Much needed rain arrived and has improved conditions
for all crops; however, more is needed. Row crops continue to be planted,
cranberry growers are applying fertilizer and moving bees onto their property
in anticipation of bloom. Shellfish growers are harvesting some product and
planting new seed. Kip Graham (FSA), Worcester: Asparagus and rhubarb
continuing to be harvested. The continuous mild rain is helping the freshly
planted crops for a good start for those who have planted. Frank Caruso (Ext),
Plymouth: Cranberries: The drought ended after 33 days with no measurable
precipitation; droughts like this past one hardly ever occur in April and May.
The vines held up well through the period. Rainfall amounts were in excess of
two inches in most locations. Good growth of the plants continues. Sporadic
outbreaks of cranberry weevil, gypsy moth, black-headed fireworm. Very little
oxygen deficiency injury or winterkill noted. Weed growth really has exploded
in response to the rainfall. John Devine (FSA), Franklin: The drought has
passed. Moderate to heavy rains for the past 5 days have ended farmer concerns
about dry conditions. These conditions have allowed much of the planted acreage
to be sprayed with herbicide. Hay and pasture conditions have improved,
although the first cut hay is "heading out" quickly. Broadleaf tobacco is being
transplanted now and shade tobacco is all planted in this county. Some parts of
Franklin County suffered hail damage on 5/28/01. Tree fruit was the only crop
affected, and the damage doesn't appear to be significant at this time. Ted
Smiarowski, Jr. (FSA), Hampshire/Hampden: Rained 5 out of 7 days with 2.5 to 3.5
inches total. The rain was well appreciated. Everyone wants to see the sun now
so they can start harvesting hay and plant their summer crops. Gary Guida,
Worcester: Well, we wanted rain and did we get it. One-half inch size hail
Monday afternoon. Transplanted crops are fine. Laying plastic, transplanting
tomatoes, peppers, squash, cukes, etc. Spraying post-emergence herbicide in
corn. Plant sales still strong with geraniums (of course), the main flower for
this weekend. Perennials looking good and selling well, vegetable plants in big
demand. Corn sales brisk. Consumer response to local grown products is on the
increase as big retail stores continue to market inferior or poor quality plant
material. Consumers are in a spending mood. David Rose (FSA), Norfolk and
Bristol: Field activity slowed as much needed rain fell on several different
days. The harvest of rhubarb and asparagus continues. The drought is over as
nearly 3 inches of rain fell last week.
NEW HAMPSHIRE - Steve Turaj (Ext), Coos: A welcome soaking rain ends what had
been a quite a spell of dry weather. Most field corn now planted. Hay and
pasture grasses have seemed somewhat behind normal for this time of year. Upper
soil conditions quite dry. Alfalfa at pre-bud stage, orchard grass about bud
stage. Past full bloom now for apples, highbush blueberries at full bloom.
Spring vegetables and peas planted and emerged. Good week to get field work
done. George Hamilton (Ext), Hillsborough: Fruits: Strawberries blooming. Fruit
growers are applying sprays for pest control. Field Crops: Planting and weed
spraying corn fields. Grasses in pastures and hayfields starting to
head. Vegetables: Plowing, disking, fertilizing fields, planting vegetables and
transplanting field tomatoes. Laying down plastic and drip irrigation.
Harvesting asparagus and rhubarb. Nada Haddad (Ext), Rockingham: The less than
one-inch of rain and showers on Sunday and Monday, May 27th and 28th, was
welcomed. However, more rain is needed. Spraying protective sprays on tree
fruit orchards and small fruit fields. Irrigating small fruits and vegetables.
Continuing to make successive plantings of sweet corn and many other
vegetables. Some vegetables are growing very slowly because of lack of rain.
RHODE ISLAND - Karen Menezes (Ext), Newport: A welcome rain for most of the week
helped most crops. Cole crops look great, lettuce, etc. doing well. Field and
sweet corn emerging. Strawberries and blueberries doing great, especially after
the frost. Most field work has been delayed, fungicides being applied to
potatoes, and let's hope not too many had hay down. Marilu Soileau (FSA), All
Counties: The rains finally came! Slow, steady showers were quickly absorbed by
the parched soil. Fields responded immediately. Pastures have greened up and
the weeds are trying to take over in many gardens. Field corn is mostly all
planted now. The soil is moist and germination is finally possible. More rain
is predicted for the next few days.
VERMONT - John St. Onge (FSA), Lamoille: Weekend rain gave thirsty plants a big
boost. Corn planting is starting to wind down and first cut of grass should be
underway soon. Pastures should also respond to the moisture. Northern areas in
the state missed much of the mid-week rain. Bill Snow (Ext), Orange: Most of
the field corn has been planted and some are thinking about chopping haylage.
However, lack of moisture may have made a short first crop. Rain and downpours
with large hail in some areas on Monday may not have helped much. Wait and see
if the hay crop responds. Ground was white from hail in White River area, and
other areas reported hail, too! Snow in the forecast for Wednesday in the
higher elevations. Looks like another odd year. Larry Hamel (NRCS), Orleans:
Farmers are waiting for the rains to stop from this weekend to finish up corn
planting. Hay/grass crop too high now for manure fertilizer application.
Getting equipment ready for haying! Hay/grass ready to harvest. Especially
orchard grass. Plenty of rain this weekend which will help get some more growth
for first cut. Lynette Hamilton (FSA), Windham: In the southern part of Windham
County we have had about 5 inches of rain in the past week. It is hard to tell
yet if the fertilizer will help the hay crop that was spread early this spring.
Orchard grass is all headed out and should be cut. Alfalfa crops took a
pounding from Sunday's heavy rains. Haylage harvesting should start as soon as
we have a weather change. George Cook (Ext), Lamoille: Rain over the weekend
was needed. Spring crop work going smoothly. Rain should give crops needed
boost. Jeff Carter (Ext), Addison: Finishing corn planting and spraying. New
seeded hay crops are coming up nicely. Much needed rain finally came at end of
week. First crop hay is light, grasses headed out, dandelions white, alfalfa
starting to bud. Richard Noel (FSA), Grand Isle/Franklin: Haying started last
week for haylage. Showers during the week slowed harvest up a little bit -
5/23: 0.15 in., 5/26: 0.25 in., 5/28: 0.06 in. Hay and corn needed the rain,
and all I did was the two-step! Now we need some sunshine. You don't get energy
or protein from clouds! Dennis Kauppila (Ext), Caledonia: Received about 3/4
inch of rain this week. First real rain this spring. Most of the corn planted
now, some has emerged. People getting ready to start haying. One rainy day
early in the week, then showers and thunderstorms on Sunday and Monday.
Everyone quite pleased to see the rain even though some of the Memorial Day
parades got soaked. Dairy cows out on pasture, this rain will really encourage
them. Prediction is for wet snow flurries tonight in higher elevations. We will
take moisture any way we can get it. Sherwin Williams, Rutland: Early
strawberries in full bloom. Early potatoes beginning to show. Early apple
blossoms full. Small vegetable crops coming slow. Asparagus volume down.
Too dry. One quarter inch of rain for the week. Hay crop very short and
stunted. Maria Garcia (Ext), Chittenden: There was a hail storm last night in
the area. Damage has yet to be assessed.
Reporters are from: Extension Service (Ext), Farm Service
Agency(FSA), Natural Resources Conservation Services (NRCS),
or other knowledgeable individuals.
Contact Information
To receive this report every Monday evening, send an e-mail
message to listserv@newsbox.usda.gov and in the body,
type subscribe usda-new-eng-crop-weather
Statisticians: Emily McAllister, Robin Helrich
Deputy: David Luckenbach
New England Agricultural Statistics Service
National Agricultural Statistics Service
United States Department of Agriculture
Aubrey R. Davis, Director
22 Bridge St, 3rd Floor
PO Box 1444
Concord, NH 03302-1444
Phone: (603) 224-9639
Fax: (603) 225-1434
Internet: http://www.usda.gov/nass/
E-Mail: nass.nh@nass.usda.gov
****************** end of report ***********************
| en |
markdown | 020362 | # Presentation: 020362
## Texas WIC Program Food Package Research and Nutrition Education Implications
**Texas WIC Program****Food Package Research and Nutrition Education Implications **
## Texas WIC Program
- Texas WIC Context:
- 900,000+ WIC Participants
- 2200+ WIC Staff
- 2300+ WIC Vendors
- 80 contracted local agencies
- Numerous partners and stakeholders
## Additional Challenges
- Statewide EBT rollout will occur right before food package implementation
- Food package implementation will occur statewide August 1, 2009
- Delay between when participants receive education and the actual food package change
**Notes:**
In Texas we will finish rolling EBT out right as we start rolling out the food package changes. There will be a group of people in the valley area that receive both WIC EBT education and new food package education at the same time.
In Texas we issue benefits for 3 months at a time and we are going to roll out the food package all at once on August 1, 2009 – so that means we will need to start educating participants 3 months before that and they will experience a delay between when they get education on the food package and when the actual food package change occurs.
## What are we going to do?
- 1. Get Help!
- Selected Burson-Marsteller a leading advertising firm through a competitive bid process
- 2. Started with research to
- Establish benchmark of overall knowledge
- Gage current perceptions of WIC and food package
- Gage potential perceptions of coming changes
- Identify potential barriers to success
**Notes:**
Since we are such a large state and we wanted a unified campaign that included all of our clinics, vendors, stakeholders and partners we knew that we would need help developing the campaign.
## We started with research
**We started with research**
| Education Campaign Research |
| --- |
| Focus group with WIC staff |
| In-depth interviews with WIC vendors and partners |
| Two focus groups with Spanish and English speaking WIC participants |
| Random sample phone survey with 611 WIC participants |
| State Agency Policy Research |
| --- |
| New WIC food package survey administered May 2007 |
| TexasWIC.org surveys |
| Pre/Post Implementation Survey |
| --- |
| Texas A&M baseline food behavior survey to be administered in Fall 2008 |
**Notes:**
Texas WIC has several research projects that we have conducted/are currently conducting related to the new WIC food package. This presentation is focused on the education campaign research but in a couple of cases there are references to the New WIC Food Package survey research and the surveys done on TexasWIC.org.
The new WIC food package survey was a survey conducted with WIC participants in the clinic in May 2007. There were 3,192 responses. This survey was done before the interim rule was released and focused on what participants would like to see on the new WIC food package.
The TexasWIC.org surveys are a series of short survey we put on our TexasWIC.org website for WIC participants. Each week 2000 WIC participants visit the site to complete their WIC class. Participants were asked to complete the survey before they could start their WIC class. Each survey was about 10 questions long and was on the site for 5-7 days. Each survey had 1500 -2000 responses.
## What research told us
- WIC staff focus group
- Positive about all of the changes
- See the changes as aligning with dietary guidelines
- Recognize the need to educate staff, partner agencies, vendors and WIC participants on the changes
- Most concerned about educating on whole grains and infant formula
***“...******Everything is going to be easy and wonderful, except explaining to mamas why they’re getting less formula.”***
*** ***
***– ******WIC Staff***
## Vendor in-depth interviews
- WIC Vendors
- Are positive but concerned about their bottom line
- Asked for DVDs and online training for cashiers
- Want participants to be educated at clinic
- Think brochures and posters are a must to help educate participants
- Like labeling WIC products that are least expensive brand
***“...******I think our profits will actually go down because we have a smaller profit level on produce.”***
*** ***
***– ******WIC Vendor, McAllen***
***“...******They’ll have to educate them; it’s not up to us to educate the customers when they come in.”***
***– ******WIC Vendor, Tyler***
## WIC partner in-depth interviews
- WIC partners and stakeholders
- Welcome the changes
- See opportunities to encourage breastfeeding and healthy eating habits
- Want to work hand in hand with WIC to help educate clients and families about nutrition
- Concerned that some participants may not know how to use the new foods
***“...******For us as educators, it gives us the opportunity to educate and have a deeper discussion about it.”****** ***
***–******Nutrition Manager, San Antonio Food Bank***
***“...******It would be nice if we had training or the same written material WIC is going to have...If we have that we can reemphasize what WIC is telling them”***
***–******Pediatrician, Midland***
## Participants
**Participant focus groups**** **
- Very positive about fruits and vegetables
- Mostly positive about lower fat milk
- Some uncertainty about whole grains
- Negative reaction to reductions in milk, eggs, cheese and juice!
***“...******Cheese is expensive. And the eggs are going up too.”***
*** ***
***– ******WIC Participant***
***“...******there is not enough to begin with so why decrease?”***
*** ***
***– ******WIC Participant***
## Baby Foods
**Participant focus groups**
- Most English speakers purchased jarred baby foods, but Spanish speakers were more likely to make their own
- Confusion about why moms and breastfed babies get more food than formula fed infants
- Fluctuations in the amount of formula were confusing to participants
## Telephone survey with 600+ participants
**% of WIC Participants that “Strongly Like” each of the changes**
## Likes and Dislikes of Food Package Changes
- Some differences among Hispanic participants and males on whole foods, baby food and reducing milk, cheese and eggs (shown as % strongly like)
| Please tell me how much you like or dislike each of the following changes. Do you...this change?
Showing % Strongly Like | Overall | White | African- American | Hispanic | Spanish Speaking Hispanics | Spanish Survey Takers | Male |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Adding fruits and vegetables | 93 | 94 | 90 | 92 | 92 | 89 | 86 |
| Adding whole grains | 79 | 84 | 74 | 78 | 85 | 81 | 69 |
| Adding baby food | 76 | 82 | 80 | 72 | 65 | 47 | 77 |
| Switching milk to 2% fat or lower | 58 | 56 | 51 | 61 | 65 | 67 | 52 |
| Adding soy milk and tofu | 35 | 36 | 29 | 35 | 39 | 28 | 41 |
| Reducing the amounts of cheese, milk and eggs | 29 | 28 | 32 | 28 | 41 | 42 | 15 |
| Cutting juice | 21 | 21 | 15 | 22 | 31 | 17 | 20 |
## Likelihood to Use Food Package Changes
**Likelihood to Use Food Package Changes**
***Now please tell me how likely you are to use your WIC food package to add the following items to your grocery shopping. Are you...***
## Which is closer to your view?
**Perceptions of WIC Changes**
***Which is closer to your view?**** *
## Fruits and vegetables
- Top fruits and vegetables
- Participants requested fresh, frozen and canned
- Top fresh fruit
- Apples, bananas, grapes, and watermelon
- Top fresh veggies
- Broccoli, carrots, potatoes, and tomatoes
- Avocados ranked first among Hispanics and Spanish speakers
## Fruits and vegetables
- Top frozen fruit
- Strawberries, mixed fruit, peaches, pineapple, and mangos
- Top frozen veggies
- Broccoli, mixed vegetables, and corn
- Top canned fruits
- Applesauce, fruit cocktail, peaches, and pineapple
- Top canned veggies
- Corn, green beans and tomatoes
## Baby Foods
** ****Baby Foods**
**Among participants with infants between the ages of 6 and 12 months a majority currently purchase baby foods for their infant**** **
***AMONG THOSE WITH INFANTS 6-12 MONTHS: Do you regularly buy baby foods for your baby?***
| AMONG THOSE SAYING NO: Why not? | Overall | White | African-American | Hispanic |
| --- | --- | --- | --- | --- |
| My baby is too young | 31 | 8 | 19 | 50 |
| Make my own for the baby | 22 | 29 | 15 | 25 |
| My baby does not like them | 16 | 13 | 22 | 19 |
| My baby eats table food | 8 | 8 | 7 | 6 |
| My baby won't eat them | 6 | 25 | 0 | 0 |
| My baby is too old | 6 | 0 | 15 | 0 |
| Too expensive | 4 | 8 | 7 | 0 |
| Others | 6 | 8 | 15 | 0 |
| Don't Know | 0 | 0 | 0 | 0 |
**Notes:**
Of the 611 about 182 had infants between 6 to 12 months. We really don’t have enough information to talk about specifics related to ethnicities here but we did find in the focus group that less of our Spanish Speaking participants used jarred baby foods. However when we asked about whether they would use jarred baby foods if they were provided by WIC 94% answered yes.
## Soy Milk / Tofu
**Two thirds say they would not use soy milk or tofu and would continue to use only cow’s milk. More Hispanic participants said they would be likely to add soy milk or tofu to replace some cow’s milk. **
| If WIC offered tofu or soy milk as a choice in place of all or some of the cow s milk, which would you most likely choose? | Overall | White | African- American | Hispanic | Spanish Speaking Hispanics |
| --- | --- | --- | --- | --- | --- |
| Tofu only | 1 | 0 | 0 | 1 | 3 |
| Soy milk only | 9 | 7 | 9 | 9 | 7 |
| Both tofu and soy milk | 3 | 1 | 1 | 4 | 10 |
| Tofu and cow's milk | 5 | 5 | 1 | 4 | 7 |
| Soy milk and cow's milk | 16 | 11 | 13 | 19 | 17 |
| Neither tofu or soy milk; I would keep using only cow's milk. | 64 | 71 | 73 | 61 | 50 |
| Don't know | 2 | 5 | 3 | 1 | 7 |
** ****Soy Milk / Tofu**
**Notes:**
The results are shown in percentages. The results are fairly similar to California with 65% of participants wanting only cow’s milk. The results seem somewhat culturally specific. We didn’t have enough Asian responses to break that category out separately here. Across the board people in Texas are less familiar with tofu than soy milk.
For more information on what type of food packages to develop with soy and tofu we did a survey on TexasWIC.org with 1,627 participants. Only 5.9% reported drinking soy milk and only 2.5% reported using tofu. Thus the percentage of participants who currently consume soy milk or tofu is a much smaller then the percentage that said they were “interested” in selecting soy milk or tofu in the phone poll.
We are not sure what the implication is from this – it’s possible that more participants are interested in trying soy milk or tofu than currently consume soy milk or tofu. This also means that while there is initial interest the actual number of participants who would actually want soy milk or tofu may be much lower.
## Whole Grains
**When it comes to whole grains, two-thirds or more say they are very confident in choosing whole grain products and nearly more than 3 in 4 say they already consume whole wheat or whole grain bread at least once a week. **
| How confident are you that you can select a whole grain product? | Overall | White | African- American | Hispanic |
| --- | --- | --- | --- | --- |
| CONFIDENT | 95 | 97 | 93 | 94 |
| Very confident | 72 | 80 | 80 | 67 |
| Somewhat confident | 23 | 17 | 13 | 27 |
| How often do you eat whole wheat or whole grain bread? | Overall | White | African- American | Hispanic |
| --- | --- | --- | --- | --- |
| Daily | 43 | 41 | 36 | 45 |
| Weekly | 34 | 32 | 34 | 38 |
| Monthly | 10 | 9 | 14 | 8 |
| A few times a year | 6 | 10 | 8 | 4 |
| Never | 7 | 7 | 9 | 5 |
| Don't know | 0 | 0 | 0 | 0 |
***Confidence In Choosing Whole Grains***
***Current Usage of Whole Grains***
**Whole Grains**
## Most prevalent responses by grain.
Whole wheat or whole grain bread (daily-45.6%)
Reason: “It is healthy for me and my family” (74%)
White bread (weekly-38.0%)
Reason: “My family likes the taste” (41.6%)
Brown rice (never -38.6%)
Reason: “I have never tried it” (56.4%)
Oatmeal (weekly-33.5)
Reason: “It is healthy for me and my family (52.6%)
Whole wheat tortillas (never-54.4%)
Reason: “I have never tried it” (54.6%)
Corn tortillas (monthly-31.2%)
Flour tortillas (monthly-37%)
Many significant differences in frequency related to ethnicity
- Whole wheat or whole grain bread (daily-45.6%)
- Reason: “It is healthy for me and my family” (74%)
- White bread (weekly-38.0%)
- Reason: “My family likes the taste” (41.6%)
- Brown rice (never -38.6%)
- Reason: “I have never tried it” (56.4%)
- Oatmeal (weekly-33.5)
- Reason: “It is healthy for me and my family (52.6%)
- Whole wheat tortillas (never-54.4%)
- Reason: “I have never tried it” (54.6%)
- Corn tortillas (monthly-31.2%)
- Flour tortillas (monthly-37%)
- Many significant differences in frequency related to ethnicity
**Choosing New Food Items – Whole Grains**
**To get more in-depth information we surveyed participants via TexasWIC.org **
**Notes:**
Participants were asked how frequently they ate certain grain products, the reasons for eating them if they responded daily or weekly, and if the product was never eaten, the reasons why.
## Change from whole to lower fat milk
| If you drink cow’s milk, what type do you usually drink?
(% of responses) | | |
| --- | --- | --- |
| 1% low fat milk | | 4.4% |
| 2% reduced fat milk | | 38.4% |
| Buttermilk | | 0.2% |
| None | | 1.8% |
| Skim or non-fat milk | | 3.6% |
| Whole milk (Vitamin D milk) | | 51.5% |
| | | |
**Notes:**
These results are again similar to California with over 50% drinking Whole Milk.
Important to remember that 78% said they are likely to drink 2% or lower fat milk if that is what WIC offers.
More in-depth analysis found that African American participants have greater odds of reporting that they usually drink whole milk compared to White-Caucasians. Paricipants in PHR 8 (San Antonio) have greater odds of reporting that they usually drink whole milk compared to PHR 11 (South Texas-Harlingen). Hispanic participants have lower odds of reporting that they drink whole milk compared to non-Hispanic participants as did those with greater levels of education (i.e., some college and those with a Bachelor's degree) compared to those with only a high school degree.
## Educating Participants
**Educating Participants**** **
***Please tell me how helpful each of the following would be to learn about changes. Would this be...Showing % Very Helpful ***
## Educating Participants
**Educating Participants **
| Please tell me how helpful each of the following would be to learn about changes. Would this be...
Showing % Very Helpful | Overall | White | African- American | Hispanic | Spanish Speaking Hispanics | Spanish Survey Takers | Male |
| --- | --- | --- | --- | --- | --- | --- | --- |
| A fold-out guide with pictures of the new food items and quantities | 89 | 91 | 89 | 88 | 85 | 89 | 79 |
| Information sent directly to your house. | 85 | 84 | 81 | 87 | 85 | 86 | 86 |
| One-on-one contact with WIC staff | 76 | 71 | 72 | 80 | 80 | 86 | 71 |
| Pamphlets or brochures | 73 | 69 | 73 | 74 | 70 | 78 | 60 |
| Flyers at the point of purchasing groceries | 65 | 61 | 66 | 66 | 62 | 75 | 59 |
| Materials from your doctor’s office | 65 | 58 | 69 | 68 | 73 | 69 | 75 |
| An in-store tasting of foods prepared with the new WIC foods | 64 | 58 | 62 | 66 | 73 | 78 | 62 |
| Group classes at WIC | 64 | 50 | 63 | 70 | 79 | 81 | 56 |
| Take home DVD | 61 | 51 | 64 | 65 | 68 | 56 | 57 |
| Cooking demonstrations at the WIC clinic | 61 | 50 | 55 | 68 | 80 | 86 | 49 |
| Online WIC classes | 59 | 53 | 66 | 59 | 48 | 33 | 44 |
| Information via the internet, a website or email | 57 | 54 | 64 | 56 | 45 | 47 | 51 |
** ****Spanish speaking participants see internet tools such as online classes and information via the web as less helpful. Alternatively these audiences are more welcoming to learning through in-store tastings, group classes and cooking demonstrations.**
**Notes:**
Appears to be some striking differences along racial and ethnic lines. Might need different approaches for different groups.
## Supplemental Materials Welcomed
| Which of the following are you interested in receiving along with materials explaining the WIC food program change? Please select all that apply. MULTIPLE RESPONSE | Overall | White | African- American | Hispanic | Spanish Speaking Hispanics | Spanish Survey Takers | Male |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Recipes | 86 | 89 | 82 | 86 | 83 | 75 | 80 |
| Materials geared toward children | 84 | 84 | 80 | 86 | 83 | 89 | 75 |
| Cooking tips | 81 | 82 | 78 | 81 | 82 | 69 | 75 |
| Nutrition tips | 81 | 80 | 80 | 81 | 80 | 72 | 73 |
| Health tips | 79 | 78 | 81 | 78 | 75 | 69 | 76 |
| Exercise recommendations | 78 | 75 | 77 | 80 | 80 | 78 | 67 |
| None - not interested in any of the above | 1 | 2 | 1 | 1 | 0 | 0 | 5 |
| Don't know | 1 | 1 | 2 | 0 | 0 | 0 | 1 |
**Supplemental Materials Welcomed**
## Interest in Children’s Materials
**Interest in Children’s Materials**
** ****DVDs, coloring sheets, story books and stickers get the most positive response in terms of children’s materials.**
| IF INTERESTED IN MATERIALS FOR CHILDREN: What specific topics or types of material do you personally feel would be helpful to help children learn about the new WIC food package?
MULTIPLE RESPONSE | Overall | White | African American | Hispanic | Spanish Speaking Hispanics | Spanish Survey Takers | Male |
| --- | --- | --- | --- | --- | --- | --- | --- |
| DVDs with characters geared toward kids | 86 | 84 | 88 | 86 | 86 | 81 | 79 |
| Coloring sheets | 83 | 82 | 87 | 81 | 80 | 78 | 76 |
| Story books about drinking low fat milk or eating whole grains | 83 | 85 | 87 | 82 | 80 | 66 | 73 |
| Stickers | 76 | 76 | 80 | 74 | 80 | 75 | 63 |
| Other | 5 | 6 | 4 | 4 | 0 | 3 | 4 |
| Don't know | 1 | 1 | 0 | 0 | 0 | 0 | 0 |
## Summary of research findings
**Overall Findings**
- WIC staff and partners welcome the changes
- WIC participants are positive but are concerned about decreases and are somewhat resistant to lower fat milk
- WIC vendors see the changes as positive for participants but are concerned about their bottom line
- There are cultural differences for some food items
**Food Specific Findings**
- Over 50% of participants drink whole milk
- WIC participants are somewhat familiar with whole grains
- Changes in the infant food package are confusing
## After the research
- Brand platform/messaging
- Using research to develop brand platform and key messages
- Next step is to develop communications plan and materials
- Materials will be tested with vendors, partners, staff and participants
## Key Challenges
**Overall Takeaways**
- Explaining the changes and reasons behind the changes
- Creating culturally specific and relevant materials
- Ensuring our staff, partners and vendors are all on the same page and have similar materials to use with participants
- Key Opportunities
- Recast WIC as a modern program that provides the foundation for a healthy lifestyle
- Broader outreach to WIC partners and vendors to amplify healthy diet and nutrition messages
- Impact beyond the food package
## For more information
- contact Amanda Hovis at _[amanda.hovis@dshs.state.tx.us](mailto:amanda.hovis@dshs.state.tx.us)__ or (512) 458-7111 ext 3411_ | en |
log-files | 637400 | <!-- Title: 13:53:00 Wed Jun 2 2004 -->
<!-- Crewchief: Dr ToF -->
<!-- Op1: -->
<!-- Op2: -->
<!-- Op3: -->
<!-- Op4: -->
<!-- Op5: -->
<!-- Op6: -->
<!-- Notes: -->
<pre>Fresh Log for the Summer</pre>
<!-- Date: Thu Jun 3 00:18:29 2004 -->
Smacs was hung. We killed and restarted it.
<!-- Author: Olga -->
<!-- Date: Fri Jun 4 00:21:01 2004 -->
The usual SMACS hang happened. I rebooted the TOF PC and restarted SMACS.
<!-- Author: Paul (monitoring ace) -->
<!-- Date: Sat Jun 5 01:44:57 2004 -->
<pre>Again the same problem with CAEN crate 1.
System doesn't respond either to to caenet or
front panel commands,
HV doesen't come up for even number channels,
even channels switched on but with HV ~100V
below the nominal value.
After powercycling the TOF PC and the crate 1
(I leaved the crate off for ~5 minutes),
everything worked again.
TOF Smacs/Ifix restarted, def. setup file loaded.
TOF HV full on now.
I had no time to make extensive test to try to
better understand the problem because we are taking
good data now ... if the problem will presents again
probably we'll have to decide to replace the crate.</pre>
<!-- Author: Stefano -->
<!-- Date: Wed Jun 9 14:58:05 2004 -->
<pre>Paged at 14:35. There was a problem to switch on
the HV. <a
href='/cgi/elog/elog.pl?nb=2004&action=view&page=405&frame=2&anchor=14:40:12.732'>
Aces fixed it </a>. The monitoring ace told me one of the two
running smacs had the following error:"NO MAGNETIC FIELD".</pre>
<!-- Author: Luca -->
<!-- Comment: Wed Jun 9 15;10;45 comment by...Luca -->
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=405&frame=2&anchor=14:40:12.732'>
This is the link </a>
<!-- Date: Sat Jun 12 01:10:16 2004 -->
<pre>There was an heartbeat from TOF HV. Ace restarted the smacs but
the problem was still there. When I arrived I found the smacs
paused. I just clicked on the start button and now it looks fine.
</pre>
<!-- Author: Luca -->
<!-- Date: Sun Jun 13 18:00:57 2004 -->
<pre>Heartbeat alarm. Found PC hung, restarted. See Eve shift, 6-13-04 for details.</pre>
<!-- Author: Bo (mon ACE) -->
<!-- Date: Fri Jun 18 03:17:33 2004 -->
<pre>Alarm from TOF HV at around 2am. Found PC hung, restarted. See owl log.</pre>
<!-- Author: Else (mon ace) -->
<!-- Date: Sun Jun 20 00:24:09 2004 -->
<pre>Heart beat alarm from TOF HV. Restarted smacs.</pre>
<!-- Author: Else (mon. ace) -->
<!-- Date: Sun Jun 27 08:12:06 2004 -->
<pre>We had again the problem with the CAEN crate 1. I tried just to
powercicle the TOF PC but after restarting the smacs program I
can not to turn on the HV for the crate 1 channels.
I powercicled the crate 1 (~10 minutes off) and restated
ifix and smacs programs. Now the system is working.
</pre>
<!-- Author: Luca -->
<!-- Date: Mon Jun 28 11:51:01 2004 -->
<pre>Channel 308 tripped twice this morning. Ace was able to recover it.
</pre>
<!-- Author: Luca -->
<!-- Date: Wed Jun 30 00:26:45 2004 -->
<pre>HB alarm. Smacs restarted in TOF1.</pre>
<!-- Author: takashi -->
<!-- Date: Mon Jul 5 00:20:04 2004 -->
<pre>I restarted TOF1 since it froze. </pre>
<!-- Author: takashi -->
<!-- Date: Sat Jul 10 06:54:18 2004 -->
<pre>TOF PC crashed. I had to hit the reset button and restart iFix.</pre>
<!-- Author: Adam Scott -->
<!-- Date: Tue Jul 27 00:31:04 2004 -->
<pre>Usual heartbeat alarm from TOF pc at 12:15. Restarted smacs.</pre>
<!-- Author: Else (monitoring ace) -->
<!-- Date: Sat Jul 31 15:34:39 2004 -->
<pre>TOF pc was hung. Reboot pc and start smacs.</pre>
<!-- Author: takashi -->
<!-- Date: Thu Aug 5 00:26:19 2004 -->
<pre>I can see that most aces have given up on reporting the TOF pc problems here ... it doesn't seem to have any effect anyway.
But, since there is nothing else to do at the moment: As expected we had a heart beat alarm a few minutes after midnight tonight. Restarted smacs.</pre>
<!-- Author: Else -->
<!-- Date: Fri Aug 6 00:17:09 2004 -->
<pre>Restart Smacs.</pre>
<!-- Author: takashi -->
<!-- Date: Sun Aug 8 00:24:43 2004 -->
Heartbeat alarm. Restarted Smacs.
<!-- Author: Takashi & Markus -->
<!-- Date: Sat Aug 14 00:18:32 2004 -->
<pre>Heartbeat alarm : restart smacs</pre>
<!-- Author: flanagan -->
<!-- Date: Sat Aug 14 12:41:41 2004 -->
We had a problem with wcal01 during the TAC calibration this morning. See <a href=
'/cgi/elog/elog.pl?nb=2004&action=view&page=603&frame=2&anchor=11:13:03.681'>
here </a>
<!-- Author: Luca -->
<!-- Comment: Sat Aug 14 18;31;09 comment by...Luca -->
They took <a href='http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=604&frame=2&anchor=18:07:46.922'>
another tac calibration </a> and this time it is good.
<!-- Date: Sun Aug 15 00:15:40 2004 -->
<pre>Heartbeat alarm. Restarted SMACS.</pre>
<!-- Author: Pete McNamara -->
<!-- Date: Mon Aug 16 00:16:33 2004 -->
<pre>Heartbeat alarm. Restarted SMACS.</pre>
<!-- Author: Pete McNamara -->
<!-- Date: Sun Aug 22 00:59:50 2004 -->
<pre>heart beat alarm just after midnight, smacs had hung. Another heartbeat alarm at 12:45. This time the PC had hung. Restarted it.</pre>
<!-- Author: Nicola -->
<!-- Date: Thu Aug 26 16:13:40 2004 -->
<pre>TOF PC hung. I rebooted it.</pre>
<!-- Author: Luca -->
<!-- Date: Sat Aug 28 08:34:38 2004 -->
<pre>Came in this morning to heartbeat alarm. Restarted SMACS.</pre>
<!-- Author: Pete McNamara -->
<!-- Date: Mon Aug 30 08:23:08 2004 -->
<pre>Regular daily restart of SMACS.</pre>
<!-- Author: Pete McNamara -->
<!-- Date: Fri Sep 3 14:16:16 2004 -->
<pre>Replaced CAFE card on b0wcal02 slot 7 ch 16 with S/N 05196.
This should fix the QIE calibration warning.
Also inspected the VTT cable in b0wcal01... moved it to slot 6
from slot 5 and the neon lamp on the supply seems to be on.
I did not check whether it was on before the move.
Also, the lamp on the VTT supply in b0wcal02 seems to be burned
out. Be careful... you can check VTT in this crate by looking
at the LED's on the TOMAIN boards or using
$ readadc b0wcal02 <n> -get VTT
and you can check the voltage at the enable input using a DMM.</pre>
<!-- Author: mjones -->
<!-- Comment: Fri Sep 3 14;18;45 comment by...mjones -->
<pre>The database is down so I can't run TAC or QIE calibrations.
The flash ram might need to be downloaded in this CAFE card.</pre>
<!-- Date: Fri Sep 3 15:17:15 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-240&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-240 width='300' align='top'></a></td><td>TAC calibration run 0x2da3a looks fine now that VTT in
b0wcal01 is on again. We should probably replace the
VTT enable cable during this shutdown.</td></tr></table>
<!-- Author: mjones -->
<!-- Date: Sat Sep 4 19:45:38 2004 -->
<pre>TOF PC hung, restarted it</pre>
<!-- Author: Gene -->
<!-- Comment: Tue Sep 7 08;41;48 comment by...Markus -->
<pre>Daily smacs restart.</pre>
<!-- Date: Thu Sep 16 08:08:03 2004 -->
<pre>Restarted the TOF pc at 8am</pre>
<!-- Author: Gene -->
<!-- Date: Thu Sep 16 11:12:59 2004 -->
<pre>
*************** WARNING ******************
Today I just noticed that the HV pc says the magnet is
"ON", this can't be...but it means we can over-voltage
our tubes!!
Load in the 50V file to protect ourselves....then try
to find out how this can be.</pre>
<!-- Author: bauerg -->
<!-- Date: Fri Sep 17 07:51:52 2004 -->
<pre>Restarted TOF pc</pre>
<!-- Author: gene -->
<!-- Date: Fri Sep 17 19:19:35 2004 -->
<pre>********************************************
*********** *************
*********** PMT REPLACEMENT *************
*********** *************
********************************************
This week I assembled PMT DA0859 to replace
the PMT in channel 281.
DA0859 was assembed with preamp ID P0167,
and arbitrarily called this Assembly 601.
The endcap used was tested for 6hrs at 3kV,
with no sign of defect.
Ran the tube at the test stand with cosmics.
Pulses look reasonable, except for the rather
bad reflections from the dual signal cables
(another old tube from test stand days behaved
the same).
So this evening Jeff and I made access to
replace tube 281 (west side, a little before
110 degrees). Dave Ambrose had already pulled
COT microcoax mostly out of the way. However,
to completely remove the tube assembly we had
to cut the cable ties and partially pull back
the cable tray cover to get a few more mm of
clearance.
Otherwise tube swapping went pretty smoothly.
the cookie disengaged by itself. We reused the
same one for the new tube. (did not notice, based
on historical memory, any discoloration of the
cookie.)
Inserted the new tube, replaced oval board
pretty easily. Afterwards we turned LV back on,
checked in the control room that the west LV
came back on ok (although Steve Hahn told us
there was an "alarm" for some time, maybe one
of the supplies was a little out of tolerance?)
We also turn on HV to a few hundred volts to see
reasoanble current draw....there was.
Have yet to check out the actual signals for
the new tube!</pre>
<!-- Author: Bauer and Miles -->
<!-- Date: Sun Sep 19 21:30:04 2004 -->
<pre>Check out signal from newly installed PMT281. After fooling
around some, see the signal, looks reasonable. Compared it
to PMT278: both tubes give average pulse height on the scope
of about 20mV when 278 is at 900V and 281 is at 999V.</pre>
<!-- Author: bauerg -->
<!-- Date: Mon Sep 20 08:47:50 2004 -->
<pre>Restarted the TOF pc at 8am.</pre>
<!-- Author: Pete McNamara -->
<!-- Date: Mon Sep 20 13:30:05 2004 -->
<pre>A few days after the last good TAC calibration (Sept 4th or thereabouts), b0wcal00 started suffering from VME bus problems
and it had to be removed from all run configurations. On
Friday, Sept 17th, Steve Hahn and I found that the CCFM module
was hanging the VME bus and that by unplugging this module the
VME bus was fine but when it was plugged back in, the VME bus
would hang. So it appears that the VME intrface for the CCFM
module is broken. Something needs to be done about it before we
can take any calibrations.</pre>
<!-- Author: M Jones -->
<!-- Date: Mon Sep 20 16:10:34 2004 -->
<pre>Heartbeat alarm - restarted smacs. Is anybody looking into the problem? We get about 5 heartbeat alarms a day.</pre>
<!-- Author: Markus -->
<!-- Date: Wed Sep 22 16:00:05 2004 -->
<pre>Came by to check on a tube, and found smacs has hung with
message "Run-Time Error"!....restarted SMACS
Wanted to check on PMT105. Recall we had problems last year
where we seemed to loose the HV connection *during* access,
but once the plug was things seemed ok. Wanted to check on the
status now. Put 500V on PMT105 and it drew reasonable currents.
So I guess it is *still* OK!
</pre>
<!-- Author: bauerg -->
<!-- Date: Thu Sep 23 22:08:38 2004 -->
<pre>Shut down TOF HV system for tomorrow's power outage!</pre>
<!-- Author: bauerg -->
<!-- Date: Wed Oct 27 18:08:33 2004 -->
Several weeks ago our clock modul apparently caused some
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=16&frame=2&anchor=13:30:05'>VME errors</a>.
A replacement board arrived from Pisa, and we installed it
this afternoon. There was a WCAL00 timeout occuring, a look
by Bill Badget suggested it may be due to corrupted FPGA in
the ADMEM in slot 5. With the help of ADMEM expert Kwangzoo Chung we downloaded it. Now TAC seems to not complain, but
we did not see anything showing up in DBAna.....
<br>
<!-- Author: gerry and stephanie -->
<!-- Comment: Thu Oct 28 10;47;04 comment by...Luca -->
<pre>It looks like there were not data processed:
*****
***** Opened output file: /data1/jslee/tacout/TacCalib.dat
*****
Entering APPConsumerInputModule::nextEvent
APPConsumerInputModule::nextEvent :about to request an event
APPConsumerInputModule::nextEvent :about to receive event
APPConsumerInputModule::nextEvent :Received message of length 684 bytes.
APPConsumerInputModule::nextEvent :
headerWords=4, bufferLength (bytes)=540
inputDataFormat = e0e00
Outfile datarep code = 20200
Format X Event size is 540 bytes
APPConsumerInputModule::nextEvent SUCCESS! :
event count = 1, byte count = 540
--------------------------------------------------------------------------------
ByteIn Class Name (ObjectId: Bank Info ) Proc Name, Description
--------------------------------------------------------------------------------
129 LRIH_StorableBank (1 : LRIH,1 ,0 ) RAW ,
112 LRIH_StorableBank (3 : LRIH,0 ,0 ) UNKN ,
--------------------------------------------------------------------------------
Exit OK from APPConsumerInputModule::nextEvent
Also, it seems the calibration ended bad. Maybe it was aborted.
I will have a look this afternoon.
</pre>
<!-- Date: Thu Oct 28 16:18:01 2004 -->
<pre>I took a tof tac calibration to try and understand the problems we saw yesterday. I needed to take off wcal03 since it was not responding (shepered was unsucesfull, was some expert working on it?). I found the same problems as yesterday: data look not to arrive, even if rc says 7000 events have been taken. The output file on /data1/jslee/toftac is empty.</pre>
<!-- Author: Luca -->
<!-- Date: Thu Oct 28 19:47:41 2004 -->
<pre>Tried to check for clock signals with monitor patch panel.
did not see anything (this was during a L2 torture run).....
they aren't there, or i did something
stupid....take your pick!</pre>
<!-- Author: bauerg -->
<!-- Date: Thu Nov 4 12:15:04 2004 -->
Yesterday there was a
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=770&frame=2&anchor=10:59:18.906'>water accident</a>
where SW-Bottom crate was sprayed with water. Yesterday electronics folks removed all ADMEM cards (including TOF) to
inspect and clean. This morning Peter Wilson and I removed all
the TOF transition cards. Generally looked ok, but some with
water spots. Peter and I will look at them this afternoon and decide which ones to clean.
<!-- Author: bauerg -->
<!-- Date: Mon Nov 8 09:17:55 2004 -->
<pre>The CSL still does not seem to work but data can be sent to
the look area by setting the CSLHost to b0dau32. TAC
calibration runs 2e11c and 2e2d0 together indicate that
all channels were working at one time. However, since all the
cards are removed from b0wcal02 there is still room for disaster
before the end of the shutdown.</pre>
<!-- Author: M Jones -->
<!-- Date: Mon Nov 8 09:21:25 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-245&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-245 width='300' align='top'></a></td><td>Here is calibration run 2e11c.</td></tr></table>
<!-- Author: M Jones -->
<!-- Date: Mon Nov 8 09:22:03 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-246&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-246 width='300' align='top'></a></td><td>Here is calibration run 2e2d0.</td></tr></table>
<!-- Author: M Jones -->
<!-- Date: Thu Nov 11 15:05:33 2004 -->
<pre>Yesterday i mounted CAFE/DECAF cards onto TOF ADMEMS
that had been cleaned from the water incident. These were
ADMEMs 329, 355, 379, and 195; ADMEMs 072, 218, 265 did
NOT have CAFE/DECAF removed.
Today Sham & I remounted all ADMEMs in WCAL02 (but did NOT
reconnect trigger cables, and transition cards remain out--peter
wilson asks us to wait until he can check for bent pins).
So, as per data base, we installed:
Slot5 ADMEM 329
6 335
7 265
8 218
9 195
10 379
checked front panel voltages on ADMEMs -- all ok
(did NOT yet reconnect enable cable for 2V supply)</pre>
<!-- Author: gerry & sham -->
<!-- Date: Thu Nov 11 21:38:38 2004 -->
<pre>After installing the ADMEMs, Bill Badgett helped us try to
read out the ADMEMs. We had trouble with some of the cards
not shoing up cuz not seated well enough, and even a bus
error. But repeated re-seatings solved the problem. However
QIE ped run did not succeed....looks like software problem
with libraries? not up to date? notified luca....</pre>
<!-- Author: sham & gerry -->
<!-- Comment: Fri Nov 12 10;49;13 comment by...Luca -->
<pre>
I tried to take a ped run and I found this problem:
/cdf/people1/cdfdaq/consumers/code/QiePed/qieped.4.11.2.2003.09.08/bin/Linux2-KCC_4_0/QiePed:
error while loading shared libraries: libCore.so: cannot open shared object file: No such file or directory
I looked in the consumer script and I found a corrupted line:
setup cdfsoft2 4.11.2ls
I changed it back to
setup cdfsoft2 4.11.2
and I took another ped calibration. This time it worked (run 189454). I found this run in dbana.
For the ped calibration we share the executable with calorimeter
guys. I saw they build a new executable in 5.3, so I think we
could switch to this new executable.
</pre>
<!-- Date: Thu Nov 11 21:40:04 2004 -->
<pre>For posterity, this is the record of ADMEMs pulled out of
WCAL02, and the CAFE/DECAF cards that were recorded:
4 TOF ADMEMs had the CAFE/DECAF cards unloaded and potentially cleaned: 329, 355, 379, 195
Cards in Chan 0-10 were apparently washed, 11-19 only inspected (at least, those were the
instructions)
Washed ADMEMs || Un-Washed ADMEMs
||
ADMEM 329 335 379 195 || 218 265
Ch ||
0 01414 04822 00488 01712 || 01436 02062
1D 000536 000209 000515 000532 || 000476 000470
2 03060 03736 00413 01774 || 01227 01680
3D 000131 000485 000430 000185 || 000482 000535
4 01572 03049 03775 06375 || 01368 01697
5D 000127 000261 000251 000088 || 000015 000181
6 01253 04506 02971 01672 || 01236 05161
7D 000142 000421 000524 000271 || 000250 000469
8 01355 01118 01962 02089 || 01419 04193
9D 000243 000259 000508 000196 || 000114 000244
10 01488 01892 00490 06263 || 01316 04527
11D 000113 000100 000016 000446 || 000013 000458
12 03092 01785 03788 06192 || 06379 01501
13D 000094 000246 000264 000258 || 000110 000096
14 04622 04887 00474 04141 || 03028 01791
15D 000537 000252 000274 000544 || 000425 000483
16 03274 01337 03695 06213 || 02461 05196
17D 000437 000530 000450 000451 || 000471 000439
18 --- ---- ---- --- || ---- ----
19D 000311 000319 000193 000239 || 000306 000315
||</pre>
<!-- Author: bauer -->
<!-- Date: Fri Nov 12 11:54:39 2004 -->
<pre>Re-installed transition cards, and completed recabling of
WCAL02</pre>
<!-- Author: bauer & sumorok -->
<!-- Date: Fri Nov 12 13:12:07 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-247&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-247 width='300' align='top'></a></td><td>Finally it looks like things are back to normal.
Reseated admems in wcal02 and took a TAC calibration
run. All channels look okay.</td></tr></table>
<!-- Author: M Jones -->
<!-- Date: Fri Nov 19 19:50:30 2004 -->
<pre>Here is some data from Youngdo Oh from their calibration records:
PMT alpha0 alpha 14 beta 0 beta 14 reduction factor
DA0050 8.9981 7.4959 5636.18 36.85 152.94
DA0859 9.4341 8.0014 6934.99 14.94 464.20
DA0901 9.0211 10.9121 4717.00 8.82 534.55
DA0931 9.1707 10.6044 28488.12 104.22 273.36
DA0933 9.2372 10.3978 14210.16 10.87 1307.11
DA0923 9.6206 8.4526 17112.82 36.44 469.68
</pre>
<!-- Author: mjones -->
<!-- Comment: Fri Nov 19 20;08;59 comment by...mjones -->
<pre>I think that these parameters are used as follows:
log G(V) = log(G0/R) + alpha14 log(V/V0).
This implies that DA0859 operated at 1941.29 volts
will have a gain of 30e3.</pre>
<!-- Date: Mon Nov 22 17:22:11 2004 -->
<pre>HV Board 6, Crate 1 replaced, due to a faulty channel (Ch 2,
PMT 49).
New board serial # 575502
Old (borken) board serial # 575521
Smacs restareted, 60V standard HV setup file loaded,
everything fine so far.
All HV channels fully opertaional.</pre>
<!-- Author: Stefano -->
<!-- Date: Tue Nov 23 12:00:44 2004 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Current Smacs Status:
There is a problem with the parallel port driver used by Smacs to read the magnetic field.
The driver needs to be reinstalled.
This means that the tof PC and smacs are not reading the parallel
port and so the magnetic field --> it is not possible to turn on
the tof HV from iFix (***i.e. form upstairs***).
For testing/study purposes is possible to turn off and on
the HV directly from the Smacs console using the turn HV OFF and
ON buttons.
I'll do that tomorrow.
Done that the TOF HV can be considered in "running" conditions.</pre></td></tr></td></table>
<!-- Author: Stefano -->
<!-- Comment: Tue Nov 23 12;02;29 comment by...Stefano -->
<pre>I'll do that tomorrow MEANS I'll reinstall the parallel port driver tomorrow.</pre>
<!-- Date: Tue Nov 23 16:15:49 2004 -->
<pre>Made exercise to explore new smacs. Made my own 500V file
to test. Looks ok, except the V/I spread of the tubes seems
to have more structure than i'd have hoped. See broad cluster
around "10MOhm", two large spikes around 10.4 and 10.6(?),
and a small spike around 11. Would be nice to have a scale that can be manipulated so one could identify which channels these
are....i thought this was possible, but i couldn't do it.
Also found one of the current settings in the 50/60 v file
was mis-saved as 50uA, changed back to 15uA and saved it.</pre>
<!-- Author: bauerg -->
<!-- Date: Sun Nov 28 20:23:14 2004 -->
Updating HV files...
<br><br>
Some time ago we
<a href=
'/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=16&frame=2&anchor=19:19:35'>
replaced PMT 281</a> with DA0859. Matthew has estimated
its new HV is 1941.29V.
Have moved OLD DEFAULT:<br>
> DEFAULT040218_today_b14kG_g30k.suf <br>
to the archive area as <br>
> DEFAULT040218_041128_b14kG_g30k.suf <br>
AND copied a it into a NEW default version <br>
> DEFAULT041201_today_b14kG_g30k.suf<br>
which includes changing the default/maxumum voltage for PMT281 FROM<br>
2096/2121 ====> 1841/1960 <br>
where I have *intentionally* entered the voltage 100V lower
than the expected setting.<br>
I wanted to try out the voltages, and maybe even get
in on a cosmic run, but SMACS thinks the solenoid is OFF,
and it isn't, but it will not let me turn things on. This is
a known problem that Stefano is looking into, but as it stands
I can not do anything more! Leave the 60V file as the active
default, and the currently loaded file.!
<!-- Author: bauer -->
<!-- Date: Mon Nov 29 13:54:54 2004 -->
<pre>I changed the version of the executable for tof qie calibrations from 4.11.2 to 5.3.0. New Executable has been tested successfully.</pre>
<!-- Author: Luca -->
<!-- Date: Mon Nov 29 14:56:54 2004 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Starting from this morning the Administrator privileges
have been restored for the cdf-cap-tof1 account.
These privileges are needed to correctly use the parallel
port driver and to allow smacs to read the magnetic field
status.
For security reasons the following two actions have been also taken:
1) an authomatic screen saver (password protected) will start
after 10 minutes of keyboard/mouse inactivity
2) the account password has been erased from the instructions
near the PC
So to enter the PC when the screen saver is active every TOF
expert/pager have to know the right password which is:
username: cdf-cap-tof1
password: blue9notes$
</pre></td></tr></td></table>
<!-- Author: Stefano -->
<!-- Date: Mon Nov 29 14:57:55 2004 -->
<pre>Smacs is running with 60V HV setup file.
Magnetic field is ON and correctly recognized.
All the tests have been succesful.
Ready to load running HV setup file.</pre>
<!-- Author: Stefano -->
<!-- Date: Sun Dec 5 22:14:44 2004 -->
<pre>we have some quite time --- load in REAL Hv file for full voltage</pre>
<!-- Author: bauerg -->
<!-- Date: Sun Dec 5 22:31:53 2004 -->
<pre>first attempt to turn on voltage ended in failure..smacs was
sort of hung (task manager said: "not responding")...tried to stop smacs, crashed whole computer!</pre>
<!-- Author: bauer -->
<!-- Date: Sun Dec 5 22:58:41 2004 -->
<pre>SMACS hung cuz CAENs LOST POWER!....rack circuit break had
tripped!....i can not swear they were on, but smacs started
out looking ok, like it was raising voltages...so suspect
it tripped on me as i was turning on HV!?</pre>
<!-- Author: bauerg -->
<!-- Date: Sun Dec 5 23:24:11 2004 -->
<pre>continue to have problems...try to load in 60V file, and seek
Stefano's expertese to straighten out what is going on...</pre>
<!-- Author: bauer -->
<!-- Date: Mon Dec 6 00:06:21 2004 -->
<pre>because i can not seem to load the 60V file, and it seems like
kilovolt settings have been remembered, i've powered OFF the
caen crates to prevent any non-expert activities. also, i notice
in the task manager that SMACS is often "not responding"...maybe
this is normal, but its response, when it responds certainly seems very sluggish!</pre>
<!-- Author: bauerg -->
<!-- Date: Mon Dec 6 13:20:07 2004 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Full reset of the CAEN crates seems to have fixed the problem experienced by Gerry yesterday.
The most likely cause of the massive failure seems to be related to the following two events (consequencial):
1) one of the power lines tripped when Gerry tried to turn on the HV (NOTE: the tripped powerline was powerline A: giving power to
crate 1, 3 and also the non tof crate in the same rack)
2) due to the loss of power the caenet get stuck at the same
time smacs was reading (or writing) in the crate number 2.
For some obscure (yet) reasons (maybe a preliminary indication of possible hw problems with crate 2) the crate got completely blocked. Powering off and on the crate didn't fix the problem.
Today after repowering the crate and asking smacs to download
the HV setting, crate two suddenly exit from the coma.
After the nice news, I tested te system with a new 1000V
HV setup file and then using the DEFAULT HV setup file
created yestarday by Gerry.
In all cases everything worked fine but for one channel:
PMT 288, crate 1, board 9, channel 1.
For this channel the monitored current is always 0
(I checked that the problem is not in the PMT but either in
the monitoring hardware or in smacs (unplugging the HV cable
and using the test load the IMON current is always 0).
This is a probable indication that the PMT is OK and
that the problem is in the monitoring harware or
in Smacs, so for the moment, together with Gerry, we
decided to keep the channel in ... (I'll post
an entry on the general e-log explaining that to the
ACEs).
NOTE: running some test on crate 2 are also indicating that
the crate is experiencing some (inital?) hadrware problems.
To avoid irrecoverable problems please:
********** DO NOT POWER OFF CRATE 2 !! ************
I'll send to prep the spare crate to be fixed, so we'll have
a replacement in case the situation will get worst.
Now everything has been restarted (crates, PC, iFix and
Smacs), DEFAULT HV file for running conditions loaded,
and the system is ready to take data withh al channels enabled.</pre></td></tr></td></table>
<!-- Author: Stefano -->
<!-- Date: Tue Dec 7 18:49:06 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-248&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-248 width='300' align='top'></a></td><td>tof ave charge and time</td></tr></table>
<!-- Author: Dean -->
<!-- Date: Tue Dec 7 18:54:46 2004 -->
<table><tr><td><a href=/elog/notebooks/tof/Tue_Dec__7_2004_185439.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-251 align='top'></a></td><td>tof ave charge and time</td></tr></table>
<!-- Author: Dean -->
<!-- Comment: Tue Dec 7 19;41;43 comment by...bauer -->
<pre>TOF data from 1st Store!</pre>
<!-- Comment: Tue Dec 7 20;41;49 comment by...mjones -->
<pre>Note that channel 281 does not look so different from
the others... not that I can see exactly which bin it
is, but at least there is no hot or cold channel there.</pre>
<!-- Date: Fri Dec 10 12:01:55 2004 -->
<pre>Studying new clock translator modules. First, taking a TAC
calibration run with original module. This will be run 0x2e998.</pre>
<!-- Author: M Jones -->
<!-- Date: Fri Dec 10 13:45:35 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-252&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-252 width='300' align='top'></a></td><td>This is the result of the TAC calibration with the original
clock translator module.</td></tr></table>
<!-- Author: M Jones -->
<!-- Date: Fri Dec 10 13:47:04 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-253&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-253 width='300' align='top'></a></td><td>This is the TAC calibration with the new clock translator
module. There are some small delay shifts that we do not
expect to significantly change anything.</td></tr></table>
<!-- Author: M Jones -->
<!-- Date: Fri Dec 10 15:16:14 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-254&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-254 width='300' align='top'></a></td><td>Here are the clock edges on the NIM output of module s/n 1.
Timing in these plots is not necessarily on the same clock
edge so the jitter is overestimated.</td></tr></table>
<!-- Author: M Jones -->
<!-- Date: Fri Dec 10 15:24:33 2004 -->
<pre>Relative timing on the new clock translator module seems to be
STOP0 = CAL + 382 ps
STOP1 = CAL + 513 ps
this is about what is expected for the extra propagation delay
of the of the EL11 fanout chip and the extra 2 cm of copper to
get to the stop1 output connector.
Again, these were for module s/n 1.</pre>
<!-- Author: M Jones -->
<!-- Date: Fri Dec 10 15:27:23 2004 -->
<pre>There was some noise present on the NIM output when there was
no ECL input present. We might want to build a triaxial
terminator to tie one of the inputs to ground.</pre>
<!-- Author: M Jones -->
<!-- Date: Wed Dec 15 20:10:06 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-255&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-255 width='300' align='top'></a></td><td>Channel 281 looks quite reasonable. The MIP response is
898 counts, which is quite typical.</td></tr></table>
<!-- Author: M Jones -->
<!-- Date: Mon Dec 20 16:04:59 2004 -->
<pre>From offline analysis Matthew notices a couple of log gain channels, we decide to raise the HV on these two channels
by 100V:
PMT129: was 1384/1409 ===> now 1484/1509
PMT400: was 1832/1857 ===> now 1932/1957
(first number is HV setting, second is HV *limit*)
new HV file made smacs default, it is:
DEFAULT041220-today-b14kg_g30k.suf
(old one put in archive folder)
</pre>
<!-- Author: bauer -->
<!-- Date: Mon Dec 20 16:24:53 2004 -->
<pre>It has been some time (ie, years?) since we have downloaded
the flash ram on the CAFE cards. We may be seeing evidence that
some ranges on some channels have drifted. So, QIE calibration
run 0x2ebad will be used to download the flash ram. The only
warning was from b0wcal02 slot 7, qie 16 which had a big sigma
on cap 0 range 4 (1.1545).</pre>
<!-- Author: m jones -->
<!-- Date: Mon Dec 20 16:27:09 2004 -->
<pre>Next, we will take a TAC calibration run to verify that the
pedestals still look reasonable. This will be TAC calibration
run 0x2ebb0.</pre>
<!-- Author: m jones -->
<!-- Comment: Mon Dec 20 16;39;51 comment by...M Jones -->
<pre>Pedestals look reasonable. I don't think anything got corrupted.</pre>
<!-- Date: Mon Dec 20 22:53:16 2004 -->
<pre>PMT 288 set back out of monitor.</pre>
<!-- Author: Stefano -->
<!-- Comment: Mon Dec 20 22;59;16 comment by...S -->
<pre>DEFAULT HV setting file modifed accordingly</pre>
<!-- Date: Sat Dec 25 04:03:58 2004 -->
<pre>TOF HV Crate 1 crashed, w/o accepting commands
both from caenet and from the front panel.
Status led was off.
I powered off the crate for 60 seconds and switched on again.
The crate rebooted correctly w/o problems.
SMACS restarted, default HV setting reloaded.
TOF HV full ON now.
</pre>
<!-- Author: Stefano -->
<!-- Date: Mon Dec 27 21:50:11 2004 -->
<pre>For future reference, here are the notes that I made a while
ago for downloading the firmware on one of our admems. This
comes from the file ~cdf_tof/notes/download.d...
b0dap30:/cdf/people2/cdf_tof/ more notes/download.d
Notes on downloading firmware for TOF admems:
$ vxlogin b0wcal04
b0wcal04-> cd "/cdf/code-common/cdfonline/fer/v3_15/VxWorks-5.3/PPC"
b0wcal04-> ld < qietest
b0wcal04-> qietest
--> 1 (Select ADMEM)
Enter 1 (only 1 admem)
Enter 9 (only ADMEM in slot 9)
--> 11 (L1 trigger Menu)
--> 1 (ADMEM type)
Enter 10 (TOF)
Enter 3 (Configure ADMEM's FPGA)
Enter 4 (Down load ET lookup table)
Q
Q
b0wcal04-> unld "qietest"
b0wcal04-> reboot
however, the directory in which 'qietest' can be found does
change so you might need to look for it. Today, the most
recent version was in
/cdf/code-common/cdfonline/fer/v3_50/VxWorks-5.3/PPC/qietest
</pre>
<!-- Author: M Jones -->
| en |
converted_docs | 725051 | caCORE 1040: Creating Well-formed Metadata and Metadata Business Rules
Completion Quiz
1. The preferred terminology for creating Common Data Elements in the
caDSR is:
a. NCI Thesaurus
b. NCI Metathesaurus
c. SNOMED
d. LOINC
2. One of the benefits of using the NCI Thesaurus as a source for CDE
names is that it is editable and maintainable in real time.
a. True
b. False
3. The "short name" is an abbreviated name for an Administered Item
(e.g. Data Element).
a. True
b. False
4. The required parts of a Data Element Concept include the Object
Class and Property.
a. True
b. False
5. To create a Data Element Concept name, you will need the following:
a. Object Class and Property
b. Data Element
c. Value Domain
d. Representation Term
6. The CDE Curation Tool provides links to search the NCI Thesaurus for
Object Class, Property and their Qualifiers.
a. True
b. False
7. What do you do if you can't find the term you need in EVS?
a. Make up your own term
b. Use the Admin Tool instead
c. Suggest a new term to EVS
d. Give up
8. To create a Value Domain name, you will need the following:
a. Data Element Concept
b. Data Element
c. Conceptual Domain
d. Representation Term
9. There are three options for selecting a short name for an
Administered Item. Which option do you choose if you want to enter a
[customized]{.underline} abbreviation of the name?
a. System Generated
b. Abbreviated
c. User Entered
10. CDE Long names can have duplicate terms in the name.
a. True
b. False
11. Good definitions promote metadata standardization and reuse of Data
Elements, which facilitates data sharing and interoperability of
information systems.
a. True
b. False
12. A metadata definition should be unique, singular and not contain
embedded definitions.
a. True
b. False
13. What caDSR Tool can be used to search for existing Data Element
Concepts and Value Domains?
a. UML Loader
b. caDSR Sentinel Tool
c. Semantic Integration Workbench
d. CDE Curation Tool
14. Within a context, a DEC and VD can be paired only once to make a
unique CDE.
a. True
b. False
15. An example of a major version change for a Data Element is:
a. v2.0 v3.0
b. v2.0 v2.1
c. v2.0 v2.0
16. An example of a minor version change for a Data Element is:
a. v2.0 v3.0
b. v2.0 v2.1
c. v2.0 v2.0
17. If you change the Value Domain Type from Non-enumerated to
Enumerated, you should:
a. Version the Value Domain to the next whole number
b. Version the Value Domain by one tenth (e.g. 2.1 to 2.2)
c. No versioning is necessary
18. Correcting typographical errors in a Data Element definition
requires a new version.
a. True
b. False
19. The workflow status assigned to Data Elements (and associated
Administered Items) that have been reviewed and approved by the
owning context\'s review process is:
a. DRAFT MOD
b. RELEASED
c. APPROVED FOR TRIAL USE
d. RETIRED PHASED OUT
20. A minor version change is required when a semantic change is made to
the definition of a Data Element Concept.
a. True
b. False
21. A major version change is required when a Value Domain is associated
to a different Conceptual Domain.
a. True
b. False
22. Changing the max length of a Permissible Value constitutes a minor
version change in the Value Domain.
a. True
b. False
23. Changing the Value Domain in a Data Element requires a minor version
change for the Data Element.
a. True
b. False
24. Adding a Permissible Value from the same source as the other values
to a Value Domain constitutes a major version change.
a. True
b. False
25. Changing the wording of the document text constitutes a minor
version change to the Data Element.
a. True
b. False
Answers:
1. A. NCI Thesaurus. It is a nonproprietary source of naming
components; editable; maintained in real time; provides semantic
linking of preferred terms; gives guidance in using homographs; and
shows equivalence, hierarchy, and associations between concepts.
2. A. True. Other benefits include: a nonproprietary source of naming
components; provides semantic linking of preferred terms; gives
guidance in using homographs; and shows equivalence, hierarchy, and
association between concepts.
3. A. True. The short name is a 30 character (maximum) abbreviated name
for an administered item. The short name may be generated by the
database system, abbreviated by the system, or entered by a user.
4. A. True. Object Class - a set of real world ideas, abstractions, or
things that have explicit boundaries and meanings; whose properties
and behaviors follow the same rules. Property - a characteristic
common to all members of the Object Class.
5. A. Object Class and Property. Object Class -- The concept or 'thing'
described in the data being captured. Property -- The characteristic
of the Object Class that makes it identifiable. You can add
additional descriptions or qualifiers to both.
6. A. True. The Curation Tool provides a search mechanism to search EVS
for concepts -- this way you can search for concepts when doing
curation activities instead of having to use multiple tools.
7. C. Suggest a new term to EVS. If a desired term is not in EVS, you
can suggest a term and definition by using the 'Suggest to EVS'
button located in the Curation Tool at the top right of any concept
search screen.
8. D. Representation Term. The semantics of the VD reside entirely
within the representation term and qualifiers. Best practice is to
build the name of the Value Domain using the Representation Term and
Qualifiers exclusively.
9. C. User Entered. The maximum character length for the short name
is 20. If a standard abbreviation doesn't exist, create a new
abbreviation by truncating the term to the first four letters of the
long name term or an appropriate short term that has meaning.
10. B. False. CDE Long Names should not contain duplicate terms -- you
have the ability to edit this field to delete redundant terms.
11. A. True. This data sharing is the purpose of a metadata registry.
Without standardization and sharing, we would continue to build and
maintain local databases, but there wouldn't be a frame of reference
to exchange data between them.
12. A. True. A well-formed definition should be distinguishable from
every other definition in the registry as well as express the
definition as a single instance.
13. D. Curation Tool. The Curation Tool is used to search for existing
Data Element Concepts and Value Domains. Remember, the CDE Browser
will only search directly for Data Elements.
14. A. True. A DEC and VD can only be paired once top make a CDE within
a context. If a VD is shared, you have to pair it with two different
DECs. The result is two different CDEs.
15. A. v2.03.0. When the version number is increased by a whole point,
it is considered to be a major version change.
16. B. v2.02.1. When the version number is increased by a tenth of a
point, it is considered to be a minor version change.
17. A. Version the Value Domain to the next whole number. Changing the
type of a Value Domain (non-enumerated to enumerated) is considered
to be a major version change.
18. B. False. Typographical corrections do not require a version change.
19. B. Released. Released Administered Items must be fully specified and
compliant with the caDSR naming guidelines and conventions as well
as the ISO 11179 model. Versioning rules apply. These CDEs may be
designated and reused by non-owning contexts.
20. A. True. A substantive or semantic change to a definition requires a
minor version change. Please note that typographical corrections are
not substantive or semantic changes.
21. A. True. A major version change is required when the Value Domain is
associated with a new Conceptual Domain or a different version of
the previously associated Conceptual Domain.
22. A. True. Changes to other Value Domain attributes warrants a minor
version change including: Data Type, Unit of Measure, Display
Format, Character Set, Maximum Length, Minimum Length, High Value,
Low Value, Decimal Place, and Representation.
23. B. False. Changing the Value Domain in a Data Element requires a
major version change.
24. B. False. Adding a Permissible Value from the same source as the
other values to a Value Domain requires no version change.
25. A. True. A Document Text change for a Data Element constitutes a
minor version change.
| en |
converted_docs | 053473 | Trustees of Torrington, Conn., Company Pension Plan to Make Restitution
to Plan Participants
**BOSTON** -- The U.S. Department of Labor has obtained a consent
judgment requiring the trustees of a Torrington, Conn., pension plan to
repay \$58,000 to the Interior Technology, Inc. Prevailing Wage Plan in
order to reverse the unlawful transfer of plan funds to the company.
"The law makes it very clear that trustees of employee pension and
benefit plans must administer the plan solely for the benefit of its
participants and beneficiaries," said James Benages, regional director
in Boston for the U.S. Labor Department's Pension and Welfare Benefits
Administration (PWBA). "Transferring plan assets to the company
sponsoring the plan is prohibited."
The judgment, signed by U.S. District Judge Dominic J. Squatrito on Dec.
18, 2002, requires defendants William C. Mascetti and Patricia J.
Mascetti to repay the funds to the plan within 30 days, and prohibits
them from future violations of the Employee Retirement Income Security
Act (ERISA).
A department lawsuit filed Dec. 28, 2001, in the U.S. District Court for
the District of Connecticut alleged that the defendants had violated
ERISA, the federal law which protects private employee pension and
welfare benefit plans, by causing the company's pension plan to transfer
nearly \$48,000 to Interior Technology, Inc. in 1994. The company, which
has since gone out of business, never repaid the funds to the plan.
While neither admitting nor denying the allegations of the department's
lawsuit, the defendants agreed to entry of the consent judgment, which
also prohibits them from serving as fiduciaries of any ERISA covered
plan for a period of five years from the date of the judgment.
The order further requires the defendants to make sure that all of the
pension plan's participants receive their proper share of the plan's
assets. Thereafter, the defendants must make sure the plan is terminated
in an orderly manner.
The PWBA regional office in Boston investigated this case. Employers and
workers can reach that office at 617-565-9600. PWBA's toll-free number,
1-866-275-7922, also may be called for help with problems relating to
private-sector pension and health plans.
Additional information is available on the agency's Internet web site at
[www.dol.gov/pwba](http://www.dol.gov/pwba).
\# \# \#
(Chao v. William C. Mascetti, et al)
Civil Action Number: 01-CV-2431-DJS
| en |
all-txt-docs | 015625 | 5R 5.02006999 298634595 147177062 151457533 118591496 120689489 18249700 19995872 1450388 1443712 6300450 6691350 267521 257585 2317507 2379525 120601645 122739997 19170847 20962843 2222683 2266227 7168492 7558891 504372 497622 97569000 101160389 17455221 19174105 1112732 1141861 6164937 6553999 207359 203412 2006809 2066128 99302475 102933918 18231821 19993931 1773888 1851856 6943164 7329307 411243 409900 21022496 19529100 794479 821767 337656 301851 135513 137351 60162 54173 310698 313397 21299170 19806079 939026 968912 448795 414371 225328 229584 93129 87722
5R 5.02006 0 4131044 2113608 2017436 1608205 1534558 315890 301985 21183 20233 91065 86904 3910 3734 73355 70022 1676332 1599590 360382 344461 27103 25875 117724 112352 6165 5889 1153399 1100817 301493 288250 18313 17488 88288 84257 2845 2717 63044 60177 1211809 1156574 340102 325104 22891 21853 111509 106419 4720 4510 454806 433741 14397 13735 2870 2745 2777 2647 1065 1017 10311 9845 464523 443016 20280 19357 4212 4022 6215 5933 1445 1379
5R 5.02006 1 4106225 2100850 2005375 1605352 1530064 310785 299841 20702 19970 90727 85949 3959 3629 69325 65922 1669553 1591138 352281 339370 26429 25512 116465 110229 6161 5735 1159352 1102942 296566 286294 17897 17249 88026 83312 2889 2652 59358 56470 1214164 1155113 332327 320417 22337 21547 110482 104453 4712 4419 446000 427122 14219 13547 2805 2721 2701 2637 1070 977 9967 9452 455389 436025 19954 18953 4092 3965 5983 5776 1449 1316
5R 5.02006 2 4087996 2090782 1997214 1599580 1524271 307517 298204 20534 19947 90968 86229 3968 3532 68215 65031 1662708 1584495 348211 337153 26171 25510 116477 110149 6137 5645 1153172 1096040 293357 284671 17754 17206 88273 83545 2905 2565 58400 55650 1207043 1147437 328402 318235 22139 21512 110547 104376 4689 4339 446408 428231 14160 13533 2780 2741 2695 2684 1063 967 9815 9381 455665 437058 19809 18918 4032 3998 5930 5773 1448 1306
5R 5.02006 3 4036123 2064785 1971338 1581951 1505834 303697 294994 19986 19526 89945 85269 3771 3407 65435 62308 1642379 1563423 342859 332359 25548 24826 113816 107789 6329 5930 1144855 1087044 291597 283395 17358 16936 87760 83135 2919 2624 55700 53155 1196213 1136126 325217 315657 21615 21051 108545 102611 4873 4557 437096 418790 12100 11599 2628 2590 2185 2134 852 783 9735 9153 446166 427297 17642 16702 3933 3775 5271 5178 1456 1373
5R 5.02006 4 4023775 2055669 1968106 1575910 1502989 307646 299576 19732 19327 85388 81670 3339 3319 63654 61225 1634640 1559427 346095 336554 25229 24683 107848 103378 6145 5976 1148127 1092468 296609 288876 17191 16854 83532 79906 2644 2633 54302 52254 1198214 1140585 329772 320745 21515 21033 102995 98784 4730 4645 427783 410521 11037 10700 2541 2473 1856 1764 695 686 9352 8971 436426 418842 16323 15809 3714 3650 4853 4594 1415 1331
5R 5.02006 5 4069224 2079097 1990127 1591244 1517199 314649 306213 19884 19275 87486 83655 3388 3267 62446 60518 1648794 1573050 352213 342796 25276 24650 109694 104970 6136 5845 1172775 1116532 303088 295105 17387 16801 85542 81885 2677 2614 53398 51696 1221927 1164145 335584 326618 21586 21018 104846 100499 4769 4574 418469 400667 11561 11108 2497 2474 1944 1770 711 653 9048 8822 426867 408905 16629 16178 3690 3632 4848 4471 1367 1271
5R 5.02006 6 3889396 1991052 1898344 1524349 1445201 294175 285702 23628 22624 77881 75819 4225 4038 66794 64960 1585127 1504243 328903 319844 37501 36093 102336 99392 9445 9065 1142082 1082414 276842 269142 17178 16446 74743 72797 2978 2847 57438 55676 1194486 1133172 307138 298843 28012 26831 96188 93410 7093 6821 382267 362787 17333 16560 6450 6178 3138 3022 1247 1191 9356 9284 390641 371071 21765 21001 9489 9262 6148 5982 2352 2244
5R 5.02006 7 3893493 1989981 1903512 1523578 1447646 295565 287205 24257 23239 76657 77652 4423 4217 65501 63553 1583039 1505325 329181 320210 38597 37163 100565 100582 9884 9307 1155505 1095788 278152 270159 17576 16958 73524 74604 3184 2996 56729 54718 1207132 1145615 307813 299052 28880 27810 94499 94666 7600 7055 368073 351858 17413 17046 6681 6281 3133 3048 1239 1221 8772 8835 375907 359710 21368 21158 9717 9353 6066 5916 2284 2252
5R 5.02006 8 3882331 1985633 1896698 1517615 1441331 298378 288383 23820 23012 79192 79172 4352 4096 62276 60704 1574034 1496292 330293 319834 37536 36229 101875 101146 9562 9054 1151795 1093097 281350 271929 17347 16751 76164 76214 3149 2935 53765 52343 1200621 1140591 309361 299465 28065 27129 96084 95494 7360 6915 365820 348234 17028 16454 6473 6261 3028 2958 1203 1161 8511 8361 373413 355701 20932 20369 9471 9100 5791 5652 2202 2139
5R 5.02006 9 3922535 2004595 1917940 1536149 1460591 299494 290821 23985 23251 80766 80776 4365 4095 59836 58406 1590259 1513308 329525 320385 37666 36448 102679 102124 9452 9136 1169372 1111110 282555 274470 17455 16983 77771 77868 3130 2926 51757 50521 1216290 1156810 308907 300447 28278 27398 97090 96673 7256 7006 366777 349481 16939 16351 6530 6268 2995 2908 1235 1169 8079 7885 373969 356498 20618 19938 9388 9050 5589 5451 2196 2130
5R 5.02006 10 4013782 2054912 1958870 1576016 1493473 308521 299395 24379 23408 82395 81391 4462 4303 59139 56900 1629319 1544652 337841 327997 38299 36730 104150 102176 9732 9237 1205609 1140003 291499 283065 17839 17208 79413 78591 3218 3129 51156 49197 1251811 1184378 317156 308198 28920 27865 98629 96763 7529 7123 370407 353470 17022 16330 6540 6200 2982 2800 1244 1174 7983 7703 377508 360274 20685 19799 9379 8865 5521 5413 2203 2114
5R 5.02006 11 4060343 2079876 1980467 1590722 1507050 320843 310957 24804 23837 81855 79064 4596 4322 57056 55237 1641882 1556481 348595 338284 38774 37270 102848 99235 9781 9307 1222403 1156045 303775 294464 18227 17563 78981 76240 3310 3138 49361 47887 1266731 1198991 328083 318450 29402 28370 97559 94046 7528 7186 368319 351005 17068 16493 6577 6274 2874 2824 1286 1184 7695 7350 375151 357490 20512 19834 9372 8900 5289 5189 2253 2121
5R 5.02006 12 4106484 2102784 2003700 1603874 1520350 331906 322813 25491 24969 82080 77585 4628 4505 54805 53478 1652928 1568074 357945 348827 39638 38774 102288 96864 9747 9431 1239134 1172449 314934 306072 19028 18637 79243 74866 3419 3381 47427 46267 1281648 1213788 337673 328851 30413 29794 97139 91877 7646 7412 364740 347901 16972 16741 6463 6332 2837 2719 1209 1124 7378 7211 371280 354286 20272 19976 9225 8980 5149 4987 2101 2019
5R 5.02006 13 4198718 2151684 2047034 1639833 1552880 345103 333498 26520 25920 82387 78306 4628 4436 53213 51994 1687311 1599106 369611 357918 40733 40150 102356 97237 9672 9409 1275378 1205394 328093 317063 19832 19416 79566 75594 3418 3287 46131 45072 1316612 1245534 349490 338420 31378 31025 97304 92337 7589 7375 364455 347486 17010 16435 6688 6504 2821 2712 1210 1149 7082 6922 370699 353572 20121 19498 9355 9125 5052 4900 2083 2034
5R 5.02006 14 4262128 2180584 2081544 1666045 1583420 347398 337856 27522 26904 82640 77703 4747 4395 52232 51266 1712482 1628867 370569 361220 42481 41472 102247 96512 9823 9400 1306178 1240192 330852 321550 20872 20439 79888 75021 3600 3297 45262 44322 1346433 1279510 351036 341860 33122 32319 97307 91682 7803 7463 359867 343228 16546 16306 6650 6465 2752 2682 1147 1098 6970 6944 366049 349357 19533 19360 9359 9153 4940 4830 2020 1937
5R 5.02006 15 4343040 2224934 2118106 1702686 1613632 354542 344374 27969 27324 83347 78021 4788 4643 51602 50112 1748335 1657897 376699 366243 43053 42224 103200 96845 10035 9724 1346781 1275595 337859 328155 21266 20736 80613 75336 3620 3483 44871 43376 1386525 1313951 357189 347218 33694 32923 98317 91997 7987 7720 355905 338037 16683 16219 6703 6588 2734 2685 1168 1160 6731 6736 361810 343946 19510 19025 9359 9301 4883 4848 2048 2004
5R 5.02006 16 4373865 2242806 2131059 1717779 1624159 357569 347550 28491 27544 83966 78529 4670 4551 50331 48726 1762278 1667157 378438 368237 43960 42683 103179 96877 9839 9432 1370261 1294555 341444 331779 21827 21096 81277 76038 3561 3475 43699 42228 1408961 1331860 359499 349701 34682 33622 98443 92333 7837 7556 347518 329604 16125 15771 6664 6448 2689 2491 1109 1076 6632 6498 353317 335297 18939 18536 9278 9061 4736 4544 2002 1876
5R 5.02006 17 4217761 2162006 2055755 1661113 1571884 337130 328076 27415 26510 84883 79109 4604 4295 46861 45881 1702456 1612161 355900 346835 42273 41295 103054 96581 9557 9017 1333076 1262773 322023 313725 20867 20443 82325 76745 3523 3279 40711 40004 1368966 1297961 338268 330085 33213 32765 98582 92398 7668 7226 328037 309111 15107 14351 6548 6067 2558 2364 1081 1016 6150 5877 333490 314200 17632 16750 9060 8530 4472 4183 1889 1791
5R 5.02006 18 4177543 2142026 2035517 1654975 1563030 327087 319329 27285 26277 83378 78430 4576 4302 44725 44149 1694319 1601819 344517 337041 42021 40883 100710 95302 9337 8871 1327381 1257616 312603 305317 21035 20112 80857 76093 3512 3324 38855 38384 1361568 1291380 327657 320612 33361 32276 96319 91180 7512 7184 327594 305414 14484 14012 6250 6165 2521 2337 1064 978 5870 5765 332751 310439 16860 16429 8660 8607 4391 4122 1825 1687
5R 5.02006 19 4131066 2120035 2011031 1645298 1550320 317639 310013 26844 25744 82369 78031 4464 4213 43421 42710 1683356 1587628 334025 326921 41696 40349 99166 94179 9177 8640 1319386 1250435 303460 296367 20554 19616 79980 75744 3418 3245 37752 37157 1352453 1282876 317570 310969 33021 31830 95007 90219 7407 6981 325912 299885 14179 13646 6290 6128 2389 2287 1046 968 5669 5553 330903 304752 16455 15952 8675 8519 4159 3960 1770 1659
5R 5.02006 20 4184615 2154438 2030177 1676920 1567677 317683 309802 27231 25694 85562 80924 4653 4321 42389 41759 1713857 1603971 333219 325755 42177 40513 102135 96836 9389 8853 1340506 1267532 303610 296412 20792 19725 83253 78671 3596 3353 36821 36277 1372542 1299038 316971 310126 33285 32197 98129 92883 7591 7230 336414 300145 14073 13390 6439 5969 2309 2253 1057 968 5568 5482 341315 304933 16248 15629 8892 8316 4006 3953 1798 1623
5R 5.02006 21 4186111 2159303 2026808 1684912 1568181 314037 304408 27109 25739 87469 83444 4783 4284 40993 40752 1720541 1603578 328473 319479 41936 40564 103866 99228 9397 8716 1336605 1265265 300071 291418 20554 19737 85056 81208 3661 3327 35629 35443 1367545 1296028 312443 304400 32978 32194 99816 95353 7563 7063 348307 302916 13966 12990 6555 6002 2413 2236 1122 957 5364 5309 352996 307550 16030 15079 8958 8370 4050 3875 1834 1653
5R 5.02006 22 4149733 2147542 2002191 1675857 1546184 310053 299780 26798 25453 90016 86783 4940 4386 39878 39605 1710336 1580359 323799 314028 41409 39987 105901 102313 9728 8949 1310218 1240890 295841 286732 19989 19495 87643 84554 3785 3420 34414 34399 1339892 1270526 307457 298951 32196 31683 101878 98488 7856 7290 365639 305294 14212 13048 6809 5958 2373 2229 1155 966 5464 5206 370444 309833 16342 15077 9213 8304 4023 3825 1872 1659
5R 5.02006 23 4236169 2197914 2038255 1719266 1575998 312748 302204 27895 25552 93934 90965 4890 4438 39181 39098 1752978 1609527 326201 316122 42486 40090 109445 106417 9552 9028 1322563 1256411 298043 288832 20470 19583 91392 88690 3616 3424 33777 33921 1351510 1285406 309295 300727 32727 31837 105358 102571 7602 7355 396703 319587 14705 13372 7425 5969 2542 2275 1274 1014 5404 5177 401468 324121 16906 15395 9759 8253 4087 3846 1950 1673
5R 5.02006 24 4265362 2200048 2065314 1722801 1592810 308113 306982 26613 24291 99227 97606 5251 4815 38043 38810 1755075 1625640 320774 320908 40810 38402 114833 113299 10105 9699 1307174 1263437 292661 292810 19032 18321 96701 95233 3883 3764 32637 33563 1334733 1291719 303144 304532 30818 30210 110757 109321 8038 7969 415627 329373 15452 14172 7581 5970 2526 2373 1368 1051 5406 5247 420342 333921 17630 16376 9992 8192 4076 3978 2067 1730
5R 5.02006 25 4340536 2225322 2115214 1744738 1628651 307496 314764 26671 24287 103948 104557 5528 4994 36941 37961 1775658 1660343 319608 328614 40193 37617 119515 120142 10682 10098 1315606 1291690 291543 299768 18791 18303 101261 101984 4086 3911 31628 32747 1341860 1318852 301385 311331 30065 29490 115371 116027 8615 8344 429132 336961 15953 14996 7880 5984 2687 2573 1442 1083 5313 5214 433798 341491 18223 17283 10128 8127 4144 4115 2067 1754
5R 5.02006 26 4287681 2198644 2089037 1723801 1604630 302904 312211 25724 23314 106145 107678 5616 4960 34454 36244 1752447 1634747 314434 325468 38360 36018 120583 122774 10457 9756 1284800 1263825 286722 297125 17868 17377 103398 105145 4159 3908 29235 31145 1308856 1289528 295907 308097 28348 27977 116449 118762 8392 8095 439001 340805 16182 15086 7856 5937 2747 2533 1457 1052 5219 5099 443591 345219 18527 17371 10012 8041 4134 4012 2065 1661
5R 5.02006 27 4082181 2093476 1988705 1644383 1524907 281266 294819 24395 21870 105969 109126 5484 4789 31979 33194 1670976 1552429 292017 306866 36104 33694 119416 122966 9896 9185 1219858 1195234 265885 279818 16913 16210 103308 106654 4068 3786 27014 28382 1242094 1218607 274384 289681 26576 25981 115451 119163 7873 7652 424525 329673 15381 15001 7482 5660 2661 2472 1416 1003 4965 4812 428882 333822 17633 17185 9528 7713 3965 3803 2023 1533
5R 5.02006 28 3987898 2041605 1946293 1610217 1496135 266307 282217 23597 21310 106213 110753 5292 4650 29979 31228 1635166 1522008 276227 293403 34626 32303 118956 124043 9331 8755 1185874 1163551 251082 267381 16196 15862 103672 108320 3867 3639 25223 26752 1206641 1185546 258796 276476 25214 25050 115271 120378 7347 7191 424343 332584 15225 14836 7401 5448 2541 2433 1425 1011 4756 4476 428525 336462 17431 16927 9412 7253 3685 3665 1984 1564
5R 5.02006 29 3908852 1995969 1912883 1573097 1466204 255454 275463 23155 20890 110689 116085 5247 4573 28327 29668 1596567 1490779 264548 286080 33640 31336 122943 128832 9126 8463 1156011 1131369 241269 260951 15874 15459 108216 113680 3872 3510 23715 25250 1175452 1152134 248294 269433 24425 24126 119245 125174 7261 6881 417086 334835 14185 14512 7281 5431 2473 2405 1375 1063 4612 4418 421115 338645 16254 16647 9215 7210 3698 3658 1865 1582
5R 5.02006 30 3851158 1961699 1889459 1542992 1444289 247922 269779 22314 20270 116609 122281 4984 4476 26878 28364 1565219 1467706 256488 279649 32341 30345 128238 134464 8707 8252 1130094 1109437 234048 255425 15220 15062 114227 119916 3612 3460 22526 24039 1148498 1129133 240583 263322 23478 23407 124755 130902 6836 6693 412898 334852 13874 14354 7094 5208 2382 2365 1372 1016 4352 4325 416721 338573 15905 16327 8863 6938 3483 3562 1871 1559
5R 5.02006 31 3948758 2008547 1940211 1581515 1484662 249769 273686 21760 19909 124046 129676 4937 4324 26520 27954 1603289 1507793 258181 283303 31645 29857 135585 141751 8576 7977 1171594 1149014 236171 259339 14964 14804 121678 127329 3610 3368 22242 23701 1189644 1168452 242594 266925 23069 23046 132153 138310 6786 6569 409921 335648 13598 14347 6796 5105 2368 2347 1327 956 4278 4253 413645 339341 15587 16378 8576 6811 3432 3441 1790 1408
5R 5.02006 32 3819366 1933840 1885526 1518836 1439421 240919 266614 20894 19500 123579 129234 4592 4162 25020 26595 1539390 1461397 248628 275656 30359 29107 134658 140832 8000 7576 1132441 1115770 228125 252778 14563 14600 121271 127024 3441 3239 21157 22634 1149554 1134266 234005 259917 22461 22637 131390 137616 6451 6190 386395 323651 12794 13836 6331 4900 2308 2210 1151 923 3863 3961 389836 327131 14623 15739 7898 6470 3268 3216 1549 1386
5R 5.02006 33 3953327 1996864 1956463 1564880 1492671 252852 279419 21494 19898 127531 133651 4625 4142 25482 26682 1585743 1514623 260601 288489 31291 29847 138692 145178 8119 7507 1178509 1166327 239886 265296 15120 14973 125185 131346 3461 3239 21584 22649 1195904 1184774 245833 272393 23329 23324 135408 141803 6537 6163 386371 326344 12966 14123 6374 4925 2346 2305 1164 903 3898 4033 389839 329849 14768 16096 7962 6523 3284 3375 1582 1344
5R 5.02006 34 4135586 2087028 2048558 1649164 1576250 259630 288270 21409 20424 126705 132673 4487 4175 25633 26766 1670137 1598227 267311 297041 31490 30462 137878 144348 8014 7717 1273065 1254755 246925 274177 15303 15416 124465 130344 3361 3244 21761 22861 1290617 1273313 252771 281118 23809 23919 134728 140976 6484 6352 376099 321495 12705 14093 6106 5008 2240 2329 1126 931 3872 3905 379520 324914 14540 15923 7681 6543 3150 3372 1530 1365
5R 5.02006 35 4370056 2197341 2172715 1749225 1685235 269857 303649 22092 21076 125244 131055 4528 4307 26395 27393 1770864 1707798 277743 312745 32716 31703 136550 142608 8142 7908 1376558 1364272 256855 289153 15879 16127 122927 128704 3451 3332 22424 23338 1394728 1383290 262876 296321 24836 25166 133264 139149 6626 6485 372667 320963 13002 14496 6213 4949 2317 2351 1077 975 3971 4055 376136 324508 14867 16424 7880 6537 3286 3459 1516 1423
5R 5.02006 36 4419361 2236018 2183343 1785979 1699690 272414 300774 21760 20678 125576 130934 4638 4302 25651 26965 1806938 1721680 280041 309464 32152 31555 136481 142236 8268 7919 1411929 1382239 259215 286553 15577 15731 123274 128617 3570 3405 21710 22996 1429426 1400812 264989 293405 24382 24998 133214 138832 6756 6537 374050 317451 13199 14221 6183 4947 2302 2317 1068 897 3941 3969 377512 320868 15052 16059 7770 6557 3267 3404 1512 1382
5R 5.02006 37 4144873 2086006 2058867 1671375 1609951 249945 277429 20777 19508 116474 123188 4081 3918 23354 24873 1690477 1630258 256587 285249 30733 29934 126211 133418 7397 7258 1331029 1315409 237864 264542 14949 14740 114427 120991 3122 3105 19740 21226 1346920 1332559 242807 270650 23425 23672 123279 130264 6077 6064 340346 294542 12081 12887 5828 4768 2047 2197 959 813 3614 3647 343557 297699 13780 14599 7308 6262 2932 3154 1320 1194
5R 5.02006 38 4099302 2060013 2039289 1651445 1592772 251052 281782 20243 19597 110798 117778 3996 3940 22479 23420 1669820 1611800 257416 289032 29940 29556 120047 127263 7212 7231 1316750 1302220 239108 268858 14689 14977 108780 115651 3056 3123 18975 19865 1332003 1318191 243813 274382 22967 23523 117231 124231 5927 6019 334695 290552 11944 12924 5554 4620 2018 2127 940 817 3504 3555 337817 293609 13603 14650 6973 6033 2816 3032 1285 1212
5R 5.02006 39 4116704 2061465 2055239 1661077 1616558 250257 281834 20129 19914 104231 109969 3930 3846 21841 23118 1678884 1635264 256344 289043 29816 30134 113130 119153 7033 7002 1341039 1335378 238770 269407 14692 15301 102371 107993 3064 3028 18527 19669 1355948 1351144 243278 274926 23012 24143 110486 116287 5788 5795 320038 281180 11487 12427 5437 4613 1860 1976 866 818 3314 3449 322936 284120 13066 14117 6804 5991 2644 2866 1245 1207
5R 5.02006 40 4256054 2132577 2123477 1713104 1665569 265535 297377 21083 20560 106361 112052 4068 3875 22426 24044 1731251 1685063 271762 304687 31252 31360 115346 121427 7278 7240 1391490 1384336 253730 284670 15539 15870 104457 110085 3119 3050 18985 20459 1406649 1400715 258311 290232 24287 25250 112636 118547 5960 6011 321614 281233 11805 12707 5544 4690 1904 1967 949 825 3441 3585 324602 284348 13451 14455 6965 6110 2710 2880 1318 1229
5R 5.02006 41 4560980 2284286 2276694 1845147 1796308 280915 315526 21988 21940 108932 114099 4147 4095 23157 24726 1864013 1816195 286931 322676 32844 33613 118115 123599 7495 7585 1521919 1510981 269349 303125 16357 17213 106993 112053 3252 3265 19828 21336 1537919 1527961 273880 308725 25758 27466 115367 120667 6218 6346 323228 285327 11566 12401 5631 4727 1939 2046 895 830 3329 3390 326094 288234 13051 13951 7086 6147 2748 2932 1277 1239
5R 5.02006 42 4569911 2273086 2296825 1846299 1823992 271672 308875 21945 22195 105933 113094 4135 3981 23102 24688 1865140 1843826 277649 315929 33113 34032 114841 122527 7425 7431 1543121 1549143 260451 296951 16575 17450 104142 111109 3309 3183 19886 21292 1559133 1566017 264992 302470 26333 27848 112298 119672 6236 6233 303178 274849 11221 11924 5370 4745 1791 1985 826 798 3216 3396 306007 277809 12657 13459 6780 6184 2543 2855 1189 1198
5R 5.02006 43 4559642 2264535 2295107 1843650 1829351 268359 304987 21528 21570 104253 110542 3921 3966 22824 24691 1862171 1849234 274017 311844 32874 33986 113074 119641 7089 7329 1555787 1564735 257739 293292 16424 17029 102483 108604 3152 3259 19810 21422 1571698 1581829 262037 298696 26441 28035 110568 116869 6005 6214 287863 264616 10620 11695 5104 4541 1770 1938 769 707 3014 3269 290473 267405 11980 13148 6433 5951 2506 2772 1084 1115
5R 5.02006 44 4580546 2274356 2306190 1866972 1851074 264004 302275 21292 21596 95671 103245 3875 3724 22542 24276 1885301 1870677 269510 308944 32750 34040 104202 112103 7018 6991 1589632 1597274 254111 291375 16350 17190 93974 101402 3076 3009 19626 21153 1605407 1614179 258330 296648 26464 28238 101823 109460 5905 5901 277340 253800 9893 10900 4942 4406 1697 1843 799 715 2916 3123 279894 256498 11180 12296 6286 5802 2379 2643 1113 1090
5R 5.02006 45 4623872 2287155 2336717 1879616 1877919 266331 304413 20819 21870 94214 104543 3786 3797 22389 24175 1897787 1897297 271794 311028 32278 34569 102702 113218 6893 7003 1614224 1629682 256691 293741 16039 17677 92528 102723 3035 3106 19584 21151 1629978 1646466 260937 299038 26233 29003 100318 110616 5816 5965 265392 248237 9640 10672 4780 4193 1686 1820 751 691 2805 3024 267809 250831 10857 11990 6045 5566 2384 2602 1077 1038
5R 5.02006 46 4710616 2341865 2368751 1919467 1897644 276686 313573 21245 22150 97844 106963 3929 3832 22694 24589 1937902 1917315 282233 320312 33042 35196 106343 115741 6927 7008 1653416 1652172 266873 302848 16548 17904 96165 105131 3215 3159 19944 21577 1669421 1669275 271191 308250 27122 29605 104032 113103 5900 5981 266051 245472 9813 10725 4697 4246 1679 1832 714 673 2750 3012 268481 248040 11042 12062 5920 5591 2311 2638 1027 1027
5R 5.02006 47 4476841 2208785 2268056 1820635 1827939 253645 292201 19576 20592 90186 100603 3484 3317 21259 23404 1837862 1846797 258811 298447 30773 33476 98081 108519 6269 6380 1587408 1605600 244967 282434 15309 16665 88652 98959 2857 2773 18667 20622 1602378 1622065 249013 287454 25297 28273 95913 106169 5375 5463 233227 222339 8678 9767 4267 3927 1534 1644 627 544 2592 2782 235484 224732 9798 10993 5476 5203 2168 2350 894 917
5R 5.02006 48 4522969 2233286 2289683 1845222 1853140 253231 289627 19784 20620 90404 100151 3389 3158 21256 22987 1862396 1871554 258218 295742 31187 33452 98211 107947 6309 6080 1618193 1635861 244737 280188 15546 16899 88928 98570 2794 2625 18790 20257 1633236 1651919 248680 285106 25815 28439 96116 105684 5437 5246 227029 217279 8494 9439 4238 3721 1476 1581 595 533 2466 2730 229160 219635 9538 10636 5372 5013 2095 2263 872 834
5R 5.02006 49 4405757 2166140 2239617 1793851 1813262 243584 282977 18815 19931 86209 97936 3183 3163 20498 22348 1810566 1831168 248356 288892 30086 32671 93558 105273 5806 5929 1581312 1606021 235500 273836 14835 16373 84839 96492 2666 2624 18249 19791 1596042 1621707 239296 278619 25073 27932 91641 103199 5064 5087 212539 207241 8084 9141 3980 3558 1370 1444 517 539 2249 2557 214524 209461 9060 10273 5013 4739 1917 2074 742 842
5R 5.02006 50 4276289 2099993 2176296 1741760 1762792 232976 271878 18056 19232 84652 97581 3025 3079 19524 21734 1757560 1780163 237555 277645 29055 31729 91549 104704 5490 5760 1539597 1564402 225145 263229 14300 15896 83331 96099 2519 2554 17388 19243 1553539 1579645 228796 267857 24253 27228 89750 102612 4745 4972 202163 198390 7831 8649 3756 3336 1321 1482 506 525 2136 2491 204021 200518 8759 9788 4802 4501 1799 2092 745 788
5R 5.02006 51 4297640 2116224 2181416 1757013 1770092 233212 270843 18094 18793 85451 97425 3034 3087 19420 21176 1772689 1787028 237850 276338 28962 31197 92173 104202 5563 5768 1559071 1576545 225373 262243 14444 15616 84160 95987 2534 2600 17230 18808 1572850 1591466 229013 266636 24268 26899 90399 102223 4830 5024 197942 193547 7839 8600 3650 3177 1291 1438 500 487 2190 2368 199839 195562 8837 9702 4694 4298 1774 1979 733 744
5R 5.02006 52 4059665 1983600 2076065 1657509 1695884 210937 249875 16701 17890 77936 89841 2733 2889 17784 19686 1671961 1711715 215062 254915 26934 29707 83993 95915 5021 5326 1481123 1518236 203845 242155 13399 14882 76755 88520 2311 2446 15827 17446 1493846 1532141 207116 246206 22709 25599 82334 94084 4391 4644 176386 177648 7092 7720 3302 3008 1181 1321 422 443 1957 2240 178115 179574 7946 8709 4225 4108 1659 1831 630 682
5R 5.02006 53 3961546 1933722 2027824 1620829 1661407 200386 238910 15861 17007 76617 88725 2639 2699 17390 19076 1634911 1676658 204332 243775 26040 28484 82465 94673 4863 5072 1455654 1492091 193761 231592 12815 14134 75547 87498 2217 2272 15563 17064 1468158 1505605 196890 235551 22110 24672 80975 92940 4254 4443 165175 169316 6625 7318 3046 2873 1070 1227 422 427 1827 2012 166753 171053 7442 8224 3930 3812 1490 1733 609 629
5R 5.02006 54 3821721 1864625 1957096 1570385 1608405 189762 229545 14969 16096 71093 82497 2497 2580 15919 17973 1583292 1622830 193391 234208 24526 27259 76180 87728 4493 4773 1415660 1450079 183671 222805 12227 13469 70073 81350 2099 2233 14208 16043 1427077 1462821 186558 226620 20965 23699 74776 86127 3908 4229 154725 158326 6091 6740 2742 2627 1020 1147 398 347 1711 1930 156215 160009 6833 7588 3561 3560 1404 1601 585 544
5R 5.02006 55 3696460 1797733 1898727 1506201 1553637 188671 226654 14776 15494 70018 83055 2472 2476 15595 17411 1518922 1567558 192261 231248 24144 26308 74914 88113 4431 4567 1356380 1399270 182824 219953 12150 12978 68991 81923 2093 2088 13960 15447 1367687 1411490 185654 223655 20750 22861 73518 86505 3893 3969 149821 154367 5847 6701 2626 2516 1027 1132 379 388 1635 1964 151235 156068 6607 7593 3394 3447 1396 1608 538 598
5R 5.02006 56 3714795 1809363 1905432 1514364 1557780 189411 226354 14593 15366 73370 86184 2506 2514 15119 17234 1526577 1571501 192929 230896 23755 26086 78050 91213 4548 4593 1367344 1404479 183552 219775 12043 12971 72392 85089 2153 2167 13556 15408 1378209 1416629 186350 223472 20468 22839 76699 89671 4025 4056 147020 153301 5859 6579 2550 2395 978 1095 353 347 1563 1826 148368 154872 6579 7424 3287 3247 1351 1542 523 537
5R 5.02006 57 3533051 1712406 1820645 1447787 1504967 168562 205205 13343 14140 66067 77771 2197 2308 14450 16254 1459611 1518166 171816 209404 22356 24435 70340 82263 3988 4179 1317496 1366845 163457 199383 11150 12024 65240 76823 1873 1965 12992 14515 1328042 1378539 166059 202802 19473 21507 69169 80888 3511 3636 130291 138122 5105 5822 2193 2116 827 948 324 343 1458 1739 131569 139627 5757 6602 2883 2928 1171 1375 477 543
5R 5.02006 58 3572385 1731508 1840877 1480299 1541127 159544 194582 13073 13942 62472 73059 2110 2077 14010 16090 1491816 1554171 162648 198549 21902 24282 66531 77464 3831 3976 1355236 1406893 154813 189159 10921 11898 61657 72152 1814 1769 12577 14513 1365503 1418572 157280 192436 19092 21474 65371 76171 3380 3489 125063 134234 4731 5423 2152 2044 815 907 296 308 1433 1577 126313 135599 5368 6113 2810 2808 1160 1293 451 487
5R 5.02006 59 3577116 1732217 1844899 1499446 1565850 146564 179958 12755 13238 57662 67868 1856 1998 13934 15987 1511102 1579117 149447 183828 21823 23821 61411 71899 3550 3673 1382868 1439878 142174 174733 10734 11306 56935 67023 1608 1680 12617 14458 1393366 1451793 144507 177904 19130 21179 60375 70718 3169 3206 116578 125972 4390 5225 2021 1932 727 845 248 318 1317 1529 117736 127324 4940 5924 2693 2642 1036 1181 381 467
5R 5.02006 60 2718601 1306875 1411726 1113412 1177012 120691 151767 9984 10673 50228 57941 1774 1806 10786 12527 1122271 1187205 123087 154907 16624 18505 53387 61493 3209 3358 1009791 1063490 116822 147106 8288 9026 49609 57230 1519 1560 9650 11203 1017649 1072527 118701 149625 14404 16259 52513 60474 2842 2974 103621 113522 3869 4661 1696 1647 619 711 255 246 1136 1324 104622 114678 4386 5282 2220 2246 874 1019 367 384
5R 5.02006 61 2730732 1310437 1420295 1120582 1188822 119278 150647 9576 10591 48724 56315 1647 1820 10630 12100 1129328 1198721 121519 153517 16241 18332 51782 59630 3094 3305 1022500 1081245 115792 146521 8028 8991 48141 55647 1432 1570 9602 10996 1030344 1090176 117593 148895 14197 16209 50960 58699 2760 2948 98082 107577 3486 4126 1548 1600 583 668 215 250 1028 1104 98984 108545 3926 4622 2044 2123 822 931 334 357
5R 5.02006 62 2696914 1287310 1409604 1110125 1192356 111567 142169 9283 9888 44939 51690 1474 1579 9922 11922 1118292 1202210 113695 145003 15626 17670 47709 54822 2793 3026 1020798 1090425 108282 138309 7856 8498 44434 51050 1302 1363 9022 10804 1028186 1099307 110018 140641 13779 15746 46992 53912 2494 2687 89327 101931 3285 3860 1427 1390 505 640 172 216 900 1118 90106 102903 3677 4362 1847 1924 717 910 299 339
5R 5.02006 63 2735639 1301343 1434296 1130018 1221675 108611 141070 8671 9606 42644 49118 1410 1475 9989 11352 1138415 1231124 110706 143800 15199 17108 45312 51942 2634 2750 1046392 1124551 105486 137258 7465 8236 42179 48510 1235 1298 9104 10322 1054017 1133095 107180 139520 13572 15241 44636 51116 2365 2480 83626 97124 3125 3812 1206 1370 465 608 175 177 885 1030 84398 98029 3526 4280 1627 1867 676 826 269 270
5R 5.02006 64 2406834 1137549 1269285 982821 1074336 96365 128203 7949 8604 40348 46827 1314 1318 8752 9997 990097 1082608 98194 130542 13681 15118 42690 49465 2352 2482 906234 986217 93692 124841 6825 7418 39915 46293 1152 1129 8006 9114 912855 993700 95212 126801 12196 13533 42080 48702 2099 2211 76587 88119 2673 3362 1124 1186 433 534 162 189 746 883 77242 88908 2982 3741 1485 1585 610 763 253 271
5R 5.02006 65 2233224 1049728 1183496 902601 997585 91744 122537 7428 8079 38677 44700 1243 1307 8035 9288 909289 1005208 93391 124774 12581 14067 40963 47164 2236 2468 829699 913018 89066 119262 6386 7034 38283 44227 1096 1124 7370 8425 835824 919880 90412 121106 11232 12623 40396 46499 2009 2193 72902 84567 2678 3275 1042 1045 394 473 147 183 665 863 73465 85328 2979 3668 1349 1444 567 665 227 275
5R 5.02006 66 2165258 1015286 1149972 869064 965189 91766 122886 7025 7770 38504 43758 1203 1335 7724 9034 875510 972604 93369 125057 11908 13459 40735 46264 2110 2433 797771 881517 89095 119635 6049 6726 38069 43277 1046 1164 7073 8208 803654 888210 90395 121439 10626 12002 40148 45601 1889 2193 71293 83672 2671 3251 976 1044 435 481 157 171 651 826 71856 84394 2974 3618 1282 1457 587 663 221 240
5R 5.02006 67 2053575 959283 1094292 828138 927685 81762 110701 6520 7173 34679 39481 1067 1172 7117 8080 834072 934379 83270 112567 11139 12283 36641 41680 1872 2162 763108 850384 79386 107608 5617 6215 34318 39033 936 1008 6522 7361 768534 856436 80639 109127 9935 11014 36134 41064 1683 1927 65030 77301 2376 3093 903 958 361 448 131 164 595 719 65538 77943 2631 3440 1204 1269 507 616 189 235
5R 5.02006 68 1996597 926959 1069638 799511 904671 80300 109773 6073 6901 33291 39260 1053 1209 6731 7824 805146 911073 81709 111683 10378 11818 35193 41424 1892 2148 737438 830006 78016 106734 5264 5896 32943 38819 922 1065 6168 7136 742580 835809 79195 108311 9312 10541 34704 40816 1685 1926 62073 74665 2284 3039 809 1005 348 441 131 144 563 688 62566 75264 2514 3372 1066 1277 489 608 207 222
5R 5.02006 69 1869993 860568 1009425 742724 855663 74176 102263 5567 6287 31026 36947 946 1012 6129 7253 747808 861586 75504 103962 9433 10847 32802 39028 1654 1891 685157 784516 72058 99515 4802 5377 30725 36530 819 895 5611 6609 689792 789874 73163 100929 8430 9653 32361 38446 1474 1705 57567 71147 2118 2748 765 910 301 417 127 117 518 644 58016 71712 2341 3033 1003 1194 441 582 180 186
5R 5.02006 70 1834900 836905 997995 723054 844840 73023 102755 5270 6124 28847 36270 827 970 5884 7036 727931 850614 74316 104453 8998 10587 30531 38268 1505 1758 667950 775706 70977 100031 4573 5309 28577 35877 731 852 5422 6405 672418 780933 72081 101472 8090 9459 30143 37716 1366 1586 55104 69134 2046 2724 697 815 270 393 96 118 462 631 55513 69681 2235 2981 908 1128 388 552 139 172
5R 5.02006 71 1814303 822470 991833 711681 842059 71376 100761 4974 5965 27963 35241 885 1003 5591 6804 716375 847634 72509 102401 8491 10152 29575 37227 1570 1822 657504 773976 69441 98235 4305 5109 27665 34882 801 857 5095 6196 661755 779017 70354 99611 7613 9023 29145 36704 1431 1621 54177 68083 1935 2526 669 856 298 359 84 146 496 608 54620 68617 2155 2790 878 1129 430 523 139 201
5R 5.02006 72 1638122 733819 904303 637229 768868 61620 90576 4369 5234 24721 32588 779 860 5101 6177 641532 773974 62652 92056 7564 9058 26196 34356 1393 1582 590018 708301 59985 88229 3790 4516 24467 32270 701 736 4699 5634 593976 712924 60847 89468 6815 8100 25822 33913 1271 1398 47211 60567 1635 2347 579 718 254 318 78 124 402 543 47556 61050 1805 2588 749 958 374 443 122 184
5R 5.02006 73 1642465 727860 914605 633668 779571 60578 90556 4239 5222 23841 32360 736 834 4798 6062 637665 784508 61619 92047 7169 8969 25267 34061 1328 1616 588974 720583 58984 88317 3679 4522 23595 32025 646 732 4420 5533 592638 725061 59863 89568 6432 8037 24936 33602 1195 1451 44694 58988 1594 2239 560 700 246 335 90 102 378 529 45027 59447 1756 2479 737 932 331 459 133 165
5R 5.02006 74 1596266 701840 894426 618829 772628 52830 81263 3791 4797 21388 29423 620 756 4382 5559 622518 777236 53763 82605 6573 8290 22605 30945 1149 1386 575724 716300 51460 79247 3300 4167 21197 29127 543 651 4031 5115 579095 720520 52261 80397 5906 7456 22329 30538 1036 1231 43105 56328 1370 2016 491 630 191 296 77 105 351 444 43423 56716 1502 2208 667 834 276 407 113 155
5R 5.02006 75 1579350 685058 894292 605891 775237 50074 78759 3702 4411 20611 29633 642 753 4138 5499 609349 779789 50984 80045 6229 7784 21858 31194 1160 1440 564125 719651 48705 76725 3188 3785 20430 29350 562 650 3792 5055 567280 723822 49458 77830 5561 6950 21587 30794 1043 1288 41766 55586 1369 2034 514 626 181 283 80 103 346 444 42069 55967 1526 2215 668 834 271 400 117 152
5R 5.02006 76 1562025 669026 892999 590977 772891 49541 80785 3646 4387 20280 28840 575 711 4007 5385 594350 777310 50380 82120 6153 7707 21460 30373 1058 1346 550401 717833 48179 78849 3165 3757 20097 28544 505 620 3693 4951 553498 721860 48894 79994 5509 6885 21200 29985 952 1208 40576 55058 1362 1936 481 630 183 296 70 91 314 434 40852 55450 1486 2126 644 822 260 388 106 138
5R 5.02006 77 1454089 614140 839949 546405 732250 42699 72209 3097 3930 17771 25983 514 635 3654 4942 549511 736286 43485 73454 5396 7000 18773 27380 954 1239 510472 682344 41574 70359 2677 3344 17621 25720 452 551 3353 4536 513308 686045 42224 71419 4849 6237 18546 26999 866 1106 35933 49906 1125 1850 420 586 150 263 62 84 301 406 36203 50241 1261 2035 547 763 227 381 88 133
5R 5.02006 78 1431431 595388 836043 531059 731392 40615 70646 2872 3741 16936 24847 470 624 3436 4793 534005 735334 41265 71818 5035 6717 17937 26182 869 1219 497565 684416 39608 68972 2495 3252 16767 24598 417 553 3174 4417 500275 688043 40164 69982 4530 6054 17705 25841 778 1091 33494 46976 1007 1674 377 489 169 249 53 71 262 376 33730 47291 1101 1836 505 663 232 341 91 128
5R 5.02006 79 1355366 553619 801747 494565 703905 37709 66568 2583 3490 15274 22684 381 622 3107 4478 497214 707586 38308 67648 4567 6355 16141 23915 740 1174 464340 660504 36739 65021 2250 3015 15148 22456 336 542 2876 4137 466777 663892 37249 65961 4133 5712 15953 23608 662 1052 30225 43401 970 1547 333 475 126 228 45 80 231 341 30437 43694 1059 1687 434 643 188 307 78 122
5R 5.02006 80 1282457 511018 771439 456365 677753 35208 64214 2293 3254 13935 21382 347 512 2870 4324 458824 681293 35837 65323 4113 5944 14706 22522 670 1031 428666 636859 34335 62790 2026 2849 13826 21168 299 444 2645 3967 430936 640102 34866 63729 3735 5393 14543 22218 597 924 27699 40894 873 1424 267 405 109 214 48 68 225 357 27888 41191 971 1594 378 551 163 304 73 107
5R 5.02006 81 1236609 482518 754091 431523 666528 32255 60195 2251 3143 13552 19715 348 480 2589 4030 433709 669864 32795 61216 3868 5714 14302 20764 653 951 406195 628132 31504 58821 1952 2727 13433 19518 312 416 2385 3747 408208 631231 31961 59699 3465 5182 14132 20491 590 850 25328 38396 751 1374 299 416 119 197 36 64 204 283 25501 38633 834 1517 403 532 170 273 63 101
5R 5.02006 82 1134497 434028 700469 389267 622510 28219 53675 1978 2790 12003 17400 291 415 2270 3679 391197 625627 28711 54541 3416 5151 12621 18343 558 821 366174 588700 27575 52512 1733 2437 11903 17261 251 359 2105 3409 367970 591591 27981 53250 3101 4687 12483 18131 497 729 23093 33810 644 1163 245 353 100 139 40 56 165 270 23227 34036 730 1291 315 464 138 212 61 92
5R 5.02006 83 1030490 387474 643016 347196 571668 25308 49335 1676 2480 11024 15803 254 409 2016 3321 348879 574410 25726 50192 2935 4617 11600 16671 520 780 326751 541574 24706 48274 1464 2191 10935 15660 220 366 1855 3076 328299 544109 25064 49001 2636 4221 11475 16468 462 711 20445 30094 602 1061 212 289 89 143 34 43 161 245 20580 30301 662 1191 299 396 125 203 58 69
5R 5.02006 84 979809 361905 617904 326099 553574 22481 44639 1582 2341 9629 13859 200 308 1914 3183 327734 556205 22896 45400 2741 4434 10194 14637 445 709 308084 525652 21959 43713 1397 2069 9563 13721 168 269 1767 2953 309596 528079 22316 44375 2491 4065 10085 14441 391 630 18015 27922 522 926 185 272 66 138 32 39 147 230 18138 28126 580 1025 250 369 109 196 54 79
5R 5.02006 85 867171 312005 555166 281961 498165 18846 39365 1233 2098 8162 12518 201 275 1602 2745 283318 500469 19209 40051 2220 3873 8652 13226 390 578 266932 473350 18369 38440 1073 1870 8121 12417 165 243 1483 2528 268189 475468 18680 39007 2006 3554 8574 13074 340 519 15029 24815 477 925 160 228 41 101 36 32 119 217 15129 25001 529 1044 214 319 78 152 50 59
5R 5.02006 86 773024 270094 502930 241454 446843 18411 39696 1123 1987 7574 11550 154 264 1378 2590 242589 448967 18715 40374 1990 3710 7979 12179 325 542 228077 424408 18040 38870 974 1762 7515 11444 133 236 1266 2410 229117 426389 18290 39467 1782 3399 7893 12022 296 497 13377 22435 371 826 149 225 59 106 21 28 112 180 13472 22578 425 907 208 311 86 157 29 45
5R 5.02006 87 635666 215847 419819 194374 377086 13590 30010 925 1565 5719 8832 154 234 1085 2092 195304 378836 13829 30508 1613 2933 6007 9346 292 504 184505 359764 13271 29369 798 1400 5675 8748 129 203 1018 1952 185379 361401 13481 29800 1462 2706 5942 9228 256 445 9869 17322 319 641 127 165 44 84 25 31 67 140 9925 17435 348 708 151 227 65 118 36 59
5R 5.02006 88 563387 187771 375616 170290 338170 11105 26135 757 1430 4613 7847 133 221 873 1813 171031 339684 11310 26588 1305 2640 4865 8277 247 424 161532 322458 10862 25568 660 1309 4583 7783 119 204 803 1708 162216 323883 11040 25972 1173 2467 4812 8190 223 392 8758 15712 243 567 97 121 30 64 14 17 70 105 8815 15801 270 616 132 173 53 87 24 32
5R 5.02006 89 473131 151703 321428 136896 288830 9263 22813 596 1193 4054 6758 97 166 797 1668 137576 290233 9437 23239 1083 2304 4280 7151 196 339 130161 275982 9040 22371 520 1091 4030 6698 81 138 741 1548 130793 277287 9191 22745 982 2148 4239 7055 167 294 6735 12848 223 442 76 102 24 60 16 28 56 120 6783 12946 246 494 101 156 41 96 29 45
5R 5.02006 90 404651 125241 279410 113204 251844 7663 19053 480 1087 3195 5817 97 150 602 1459 113715 253056 7782 19406 856 2057 3371 6154 180 339 107378 240484 7484 18686 434 1002 3172 5769 80 131 565 1361 107859 241617 7591 18986 790 1921 3337 6087 153 306 5826 11360 179 367 46 85 23 48 17 19 37 98 5856 11439 191 420 66 136 34 67 27 33
5R 5.02006 91 349691 104331 245360 93673 219939 6842 18211 446 963 2752 4848 57 124 561 1275 94142 220992 6967 18556 796 1851 2908 5124 134 254 88732 209742 6700 17848 379 889 2732 4812 48 113 519 1196 89166 210728 6804 18159 719 1744 2873 5060 116 229 4941 10197 142 363 67 74 20 36 9 11 42 79 4976 10264 163 397 77 107 35 64 18 25
5R 5.02006 92 283892 81188 202704 72815 181474 5420 15274 308 893 2160 3899 56 98 429 1066 73181 182386 5519 15507 589 1626 2286 4131 97 206 68633 172553 5301 14970 278 812 2144 3858 48 85 389 995 68966 173406 5382 15177 533 1509 2261 4068 85 186 4182 8921 119 304 30 81 16 41 8 13 40 71 4215 8980 137 330 56 117 25 63 12 20
5R 5.02006 93 232674 64138 168536 57158 150136 4550 13492 334 720 1703 3173 45 80 348 935 57453 150923 4638 13767 539 1343 1812 3363 86 177 53830 142651 4466 13245 291 664 1682 3146 38 62 322 877 54106 143394 4536 13488 489 1264 1779 3321 72 147 3328 7485 84 247 43 56 21 27 7 18 26 58 3347 7529 102 279 50 79 33 42 14 30
5R 5.02006 94 179074 47638 131436 42318 117733 3385 9902 232 586 1364 2440 53 94 286 681 42554 118302 3459 10063 407 1039 1467 2598 96 191 39666 111697 3311 9694 204 543 1350 2421 46 80 254 620 39876 112218 3368 9824 361 964 1441 2565 78 162 2652 6036 74 208 28 43 14 19 7 14 32 61 2678 6084 91 239 46 75 26 33 18 29
5R 5.02006 95 142692 35614 107078 30979 94625 3067 9259 195 549 1108 1997 29 48 236 600 31175 95119 3129 9437 315 957 1184 2131 76 112 28912 89643 3004 9110 166 498 1100 1986 23 43 214 566 29094 90112 3054 9266 275 888 1167 2110 64 99 2067 4982 63 149 29 51 8 11 6 5 22 34 2081 5007 75 171 40 69 17 21 12 13
5R 5.02006 96 106352 26049 80303 22712 71179 2204 6894 170 377 789 1384 16 39 158 430 22849 71535 2253 7009 261 664 839 1479 39 93 21132 67560 2163 6744 143 353 788 1376 15 33 143 400 21256 67893 2208 6843 229 622 829 1466 35 79 1580 3619 41 150 27 24 1 8 1 6 15 30 1593 3642 45 166 32 42 10 13 4 14
5R 5.02006 97 77120 17768 59352 15553 52990 1409 4759 105 285 557 948 14 27 130 343 15661 53283 1442 4834 182 495 603 1049 35 78 14447 50228 1378 4680 90 261 555 938 12 19 118 318 14544 50498 1405 4748 163 466 596 1025 31 65 1106 2762 31 79 15 24 2 10 2 8 12 25 1117 2785 37 86 19 29 7 24 4 13
5R 5.02006 98 59103 13333 45770 11493 40601 1236 3922 78 217 411 721 15 29 100 280 11568 40831 1268 4014 131 399 451 788 38 64 10611 38574 1216 3851 65 198 395 713 11 21 85 249 10676 38783 1240 3928 116 364 426 766 32 45 882 2027 20 71 13 19 16 8 4 8 15 31 892 2048 28 86 15 35 25 22 6 19
5R 5.02006 99 39454 8340 31114 7139 27313 784 2835 38 183 281 562 12 21 86 200 7198 27478 816 2907 80 316 321 605 29 45 6544 25803 766 2799 26 167 279 556 11 19 77 185 6596 25957 792 2863 64 293 314 595 24 39 595 1510 18 36 12 16 2 6 1 2 9 15 602 1521 24 44 16 23 7 10 5 6
5R 5.02006100 75610 15353 60257 12363 50996 1930 6994 182 461 488 1133 57 74 333 599 12587 51422 2089 7262 354 788 668 1351 160 217 10902 47735 1816 6866 114 391 463 1104 41 49 230 490 11066 48092 1909 7071 230 668 571 1265 98 157 1461 3261 114 128 68 70 25 29 16 25 103 109 1521 3330 180 191 124 120 97 86 62 60
| ru |
markdown | 415694 | # Presentation: 415694
## A Really Brief Crash Course in Semantic Web Technologies
- Rocky Dunlap
- Spencer Rugaber
- Georgia Tech
## Languages you may encounter...
- XML (eXtensible Markup Language)
- XML Schema
- XPath (navigate an XML document)
- XQuery (query an XML document)
- XSLT (Extensible Stylesheet Language Transformations)
- RDF (Resource Description Framework)
- RDF Schema
- OWL (Web Ontology Language)
- SPARQL (Query language for RDF triples)
- SQL (Structured Query Language – for RDBMS)
- UML (Unified Modeling Language – conceptual)
- SKOS (Simple Knowledge Organization System) – glossary
## Links to language specs
| Name | Source | Description |
| --- | --- | --- |
| RDF | W3C | Resource Description Framework |
| RDFS | W3C | RDF Schema |
| SKOS | W3C | Simple Knowledge Organisation Systems |
| SPARQL | W3C | RDF/OWL Query Language |
| SQL | ANSI/ISO | Structured Query Language |
| UML | OMG | Unified Modeling Language |
| OWL | W3C | Web Ontology Language |
| XML | W3C | Extensible Markup Language |
| XML Schema (XSD) | W3C | XML Schema |
| XPath | W3C | XML Path Language |
| XQuery | W3C | XML Query Language |
| XSLT | W3C | Extensible Stylesheet Language Transformations |
## XML
- General purpose markup language
- Mechanism for structured data exchange between heterogeneous systems
- Basically: elements (tags) and attributes
- Not really for human consumption, although it is easy for us to read and write in small amounts
- An XML file is often called an *instance document*
## XML Schema
- Defines the allowed structure of a set of instance documents
- Defines a set of “types” -- valid chunks of XML
- Typically the schema is defined up front and applications are written to process *valid* or *schema-conforming* instance documents
- The schema is a way to achieve standardization – like a contract
*“**If you provide a valid document, we’ll provide you with tools that do X, Y, and Z.”*
## RDF
- A *knowledge representation* *language*
*Conceptual* in nature
- It really has nothing to do with XML
- But, there happens to be an XML representation
- A way to make statements about pretty much anything you want:
- “The Curator meeting is at GFDL.”
- “The Curator meeting is Oct 18-19.”
- “Balaji works at GFDL.”
## RDF Statements
- “The Curator meeting is at GFDL.”
- Curator
- meeting
- GFDL
- hasLocation
**subject**
**predicate**
**object**
## RDF Statements
- “The Curator meeting is Oct 18-19.”
- Curator
- meeting
- GFDL
- “18 Oct 2007”
- “19 Oct 2007”
- hasLocation
- starts
- ends
**resource**
**literal**
## RDF Statements
- “Balaji works at GFDL.”
- Curator
- meeting
- GFDL
- “18 Oct 2007”
- “19 Oct 2007”
- Balaji
- hasLocation
- worksAt
- starts
- ends
## RDF XML Representation
- <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:esc="http://www.earthsystemcurator.org">
- <rdf:Description rdf:about=“http://....#OctCuratorMeeting">
- <esc:hasLocation rdf:resource=“http://....#GFDL”/>
- <esc:starts>18 Oct 2007</esc:starts>
- <esc:ends>19 Oct 2007</esc:ends>
- </rdf:Description>
- <rdf:Description rdf:about=“http://....#Balaji">
- <esc:worksAt rdf:resource=“http://....#GFDL”/>
- </rdf:Description>
- </rdf:RDF>
## RDF Schema
- Define a domain specific *data model* for RDF
- Includes classes and properties (along with subclasses and subproperties)
- Properties are first class (they are not defined as part of a particular class)
## RDF Schema
_**Classes**_
_**Properties**_
- Event
- Meeting
- Flight
- Person
**hasLocation**
- domain: Event
- range: Place
**starts**
- domain: Event
- range: date
- Place
**ends**
- domain: Event
- range: date
**worksAt**
- domain: Person
- range: Place
## OWL (Web Ontology Language)
- Builds on RDF by adding increased expressivity
- Every OWL file is RDF (but not necessarily the reverse)
## RDF vs. OWL
- Classes
- Subclasses
- Properties
- Subproperties
- Individuals
**RDF**
**OWL**
- Property constraints
- -allValuesFrom
- -someValuesFrom
- -hasValue
- Cardinality constraints on properties
- -cardinality (exact)
- -minCardinality
- -maxCardinality
- Class definitions
- -intersection
- -union
- -complement
- -equivalentClass
- -disjointWith
- -oneOf (enum)
- Transitive Properties
- Symmetric Properties
- Individuals
- -sameAs
- -differentFrom
## Things you can NOT say in RDF, but can say in OWL
- The class *TriangularUnstructuredGrid* is at the intersection of *TriangularGrid* and *UnstructuredGrid*
*UnstructuredGrid* is the complement of *StructuredGrid*
- A *Dataset* is generated by exactly one *Model*
- A *Model* is made up of at least one *Component*
- An *AtmosphereComponent* is a *Component* with *ScienceType* equal to “Atmosphere”
*X *subComponent *Y*, *Y* subComponent *Z* *X* subComponent *Z*
## Things you can NOT say in RDF, but can say in OWL
- The class *Model* is equivalent to *ConfiguredModel*
*ScienceType* is the exact enumeration *Atmosphere, Ocean, Ice, *and *Land*
*ObservationDataset* is disjoint from *SimulationDataset*
*Dataset123 *is the same object as *DatasetXYZ*
## SPARQL
- A language for querying RDF/OWL triples
- Example query:
- PREFIX foaf: <http://xmlns.com/foaf/0.1/>
- SELECT ?x ?name
- WHERE { ?x foaf:name ?name }
## Curator’s Current Strategy
- Curator data model written in XML Schema
- Models and Datasets (Resources*) annotated with conforming XML *instance* *documents*
- Portions of XML translated into RDF and exposed by CDP-Curator faceted search
- This means:
- Low level details remain in XML instance
- Higher level concepts pulled out into the RDF
- Can we confirm this strategy?
## Technical Challenges
- XML to RDF translation
- Hierarchical, low level graph-based, conceptual
- Is there a need to go from RDF back to XML?
- What stays in XML? What goes to RDF?
- Automation of translation
- Schema level (e.g., schema evolution)
- Instance level (e.g., submission of new resource to CDP-Curator) | en |
log-files | 799291 | ! Started logfile: J1104+3812_X_2001_07_05_pus_uvs.log on Thu Jul 5 15:18:06 2007
obs J1104+3812_X_2001_07_05_pus_uva.fits
! Reading UV FITS file: J1104+3812_X_2001_07_05_pus_uva.fits
! AN table 1: 93 integrations on 171 of 171 possible baselines.
! AN table 2: 81 integrations on 171 of 171 possible baselines.
! AN table 3: 103 integrations on 171 of 171 possible baselines.
! Apparent sampling: 0.186733 visibilities/baseline/integration-bin.
! *** This seems a bit low - see "help observe" on the binwid argument.
! Found source: J1104+3812
! Warning: Unknown AN-table MNTSTA value (3).
! Will assume that it is ground-based.
! Warning: Unknown AN-table MNTSTA value (3).
! Will assume that it is ground-based.
! Warning: Unknown AN-table MNTSTA value (3).
! Will assume that it is ground-based.
!
! There are 4 IFs, and a total of 4 channels:
!
! IF Channel Frequency Freq offset Number of Overall IF
! origin at origin per channel channels bandwidth
! ------------------------------------------------------------- (Hz)
! 01 1 8.40997e+09 8e+06 1 8e+06
! 02 2 8.47997e+09 8e+06 1 8e+06
! 03 3 8.79497e+09 8e+06 1 8e+06
! 04 4 8.89997e+09 8e+06 1 8e+06
!
! Polarization(s): RR
!
! Read 2374 lines of history.
!
! Reading 35380 visibilities.
select I
! Polarization I is unavailable.
! Selecting polarization: RR, channels: 1..4
! Reading IF 1 channels: 1..1
! Reading IF 2 channels: 2..2
! Reading IF 3 channels: 3..3
! Reading IF 4 channels: 4..4
print "field_size =",field_size
! field_size = 256
print "field_cell =",field_cell
! field_cell = 0.2
print "taper_size =",taper_size
! taper_size = 70
integer clean_niter
clean_niter = 100
float clean_gain
clean_gain = 0.03
float dynam
dynam = 6.0
float soltime1
soltime1 = 120
float soltime2
soltime2 = 20
float thresh
thresh = 0.5
float win_mult
win_mult = 1.8
float time_av
time_av = 16
float old_peak
float new_peak
float flux_cutoff
mapsize field_size, field_cell
! Map grid = 256x256 pixels with 0.200x0.200 milli-arcsec cellsize.
startmod
! Applying default point source starting model.
! Performing phase self-cal
! Adding 1 model components to the UV plane model.
! The established model now contains 1 components and 1 Jy
!
! Correcting IF 1.
! A total of 856 telescope corrections were flagged in sub-array 1.
! A total of 995 telescope corrections were flagged in sub-array 2.
! A total of 1546 telescope corrections were flagged in sub-array 3.
!
! Correcting IF 2.
! A total of 857 telescope corrections were flagged in sub-array 1.
! A total of 995 telescope corrections were flagged in sub-array 2.
! A total of 1546 telescope corrections were flagged in sub-array 3.
!
! Correcting IF 3.
! A total of 857 telescope corrections were flagged in sub-array 1.
! A total of 995 telescope corrections were flagged in sub-array 2.
! A total of 1546 telescope corrections were flagged in sub-array 3.
!
! Correcting IF 4.
! A total of 857 telescope corrections were flagged in sub-array 1.
! A total of 995 telescope corrections were flagged in sub-array 2.
! A total of 1546 telescope corrections were flagged in sub-array 3.
!
! Fit before self-cal, rms=0.903230Jy sigma=0.007186
! Fit after self-cal, rms=0.705262Jy sigma=0.005613
! clrmod: Cleared the established, tentative and continuum models.
! Redundant starting model cleared.
uvw 2,-1
! Uniform weighting binwidth: 2 (pixels).
! Gridding weights will be scaled by errors raised to the power -1.
! Radial weighting is not currently selected.
flux_cutoff = imstat(rms) * dynam
! Inverting map and beam
! Your choice of large map pixels excluded 6.23% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1582 milli-arcsec
! Estimated beam: bmin=0.5414 mas, bmaj=0.7909 mas, bpa=-15.62 degrees
! Estimated noise=850.426 mJy/beam.
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
selfcal
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
! Added new window around map position (0, 0).
! clean: niter=100 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.239625 Jy
! Component: 100 - total flux cleaned = 0.304478 Jy
! Total flux subtracted in 100 components = 0.304478 Jy
! Clean residual min=-0.008584 max=0.028590 Jy/beam
! Clean residual mean=0.000186 rms=0.003099 Jy/beam
! Combined flux in latest and established models = 0.304478 Jy
! Performing phase self-cal
! Adding 5 model components to the UV plane model.
! The established model now contains 5 components and 0.304477 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.195803Jy sigma=0.001368
! Fit after self-cal, rms=0.195570Jy sigma=0.001367
! Inverting map
! Your choice of large map pixels excluded 6.23% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1582 milli-arcsec
! clean: niter=100 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.0322126 Jy
! Component: 100 - total flux cleaned = 0.0508916 Jy
! Total flux subtracted in 100 components = 0.0508916 Jy
! Clean residual min=-0.007593 max=0.013737 Jy/beam
! Clean residual mean=0.000134 rms=0.002261 Jy/beam
! Combined flux in latest and established models = 0.355369 Jy
! Performing phase self-cal
! Adding 11 model components to the UV plane model.
! The established model now contains 13 components and 0.355369 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.188837Jy sigma=0.001287
! Fit after self-cal, rms=0.188705Jy sigma=0.001286
! Inverting map
! Your choice of large map pixels excluded 6.23% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1582 milli-arcsec
print "************** FINISHED UNIFORM WEIGHTING CLEAN **************"
! ************** FINISHED UNIFORM WEIGHTING CLEAN **************
!
uvw 0,-1
! Uniform weighting is not currently selected.
! Gridding weights will be scaled by errors raised to the power -1.
! Radial weighting is not currently selected.
win_mult = win_mult * 1.6
clean_niter = clean_niter * 2
dynam = dynam - 0.5
flux_cutoff = imstat(rms) * dynam
! Inverting map and beam
! Your choice of large map pixels excluded 6.23% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1582 milli-arcsec
! Estimated beam: bmin=0.6429 mas, bmaj=0.9408 mas, bpa=-17.8 degrees
! Estimated noise=493.542 mJy/beam.
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
selfcal
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
! Added new window around map position (-0.2, 0.8).
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.0246755 Jy
! Component: 100 - total flux cleaned = 0.0406517 Jy
! Component: 150 - total flux cleaned = 0.052046 Jy
! Component: 200 - total flux cleaned = 0.060586 Jy
! Total flux subtracted in 200 components = 0.060586 Jy
! Clean residual min=-0.005104 max=0.009094 Jy/beam
! Clean residual mean=0.000327 rms=0.001673 Jy/beam
! Combined flux in latest and established models = 0.415955 Jy
! Performing phase self-cal
! Adding 28 model components to the UV plane model.
! The established model now contains 34 components and 0.415955 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.185765Jy sigma=0.001248
! Fit after self-cal, rms=0.185507Jy sigma=0.001246
! Inverting map
! Your choice of large map pixels excluded 6.23% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1582 milli-arcsec
! Added new window around map position (-1.4, 1.2).
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.00979987 Jy
! Component: 100 - total flux cleaned = 0.0163147 Jy
! Component: 150 - total flux cleaned = 0.0212717 Jy
! Component: 200 - total flux cleaned = 0.0252483 Jy
! Total flux subtracted in 200 components = 0.0252483 Jy
! Clean residual min=-0.004525 max=0.005342 Jy/beam
! Clean residual mean=0.000201 rms=0.001292 Jy/beam
! Combined flux in latest and established models = 0.441204 Jy
! Performing phase self-cal
! Adding 35 model components to the UV plane model.
! The established model now contains 57 components and 0.441204 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.184934Jy sigma=0.001240
! Fit after self-cal, rms=0.184893Jy sigma=0.001240
! Inverting map
! Your choice of large map pixels excluded 6.23% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1582 milli-arcsec
print "************** FINISHED NATURAL WEIGHTING CLEAN **************"
! ************** FINISHED NATURAL WEIGHTING CLEAN **************
!
gscale true
! Performing overall amplitude self-cal
!
! Correcting IF 1.
! A total of 24 telescope corrections were flagged in sub-array 1.
! Telescope amplitude corrections in sub-array 1:
! BR 1.02 FD 0.99 GC 1.03 GG 1.00*
! HH 1.00* HN 0.94 KK 1.00 KP 0.96
! LA 0.98 MC 1.18 MK 1.01 NL 1.00
! NY 0.99 OV 1.02 PT 1.00 SC 1.02
! TS 1.00* WF 1.09 WZ 0.97
!
! A total of 39 telescope corrections were flagged in sub-array 2.
! Telescope amplitude corrections in sub-array 2:
! BR 0.96 FD 0.93 GC 1.05 GG 1.00*
! HH 1.00* HN 0.91 KK 1.00* KP 0.92
! LA 0.95 MC 1.00* MK 0.94 NL 1.02
! NY 0.97 OV 1.02 PT 0.96 SC 1.00*
! TS 0.92 WF 1.04 WZ 1.00*
!
! A total of 21 telescope corrections were flagged in sub-array 3.
! Telescope amplitude corrections in sub-array 3:
! BR 1.00* FD 1.00* GC 1.12 GG 1.00*
! HH 1.02 HN 1.00* KK 1.00* KP 1.00*
! LA 1.00* MC 1.00* MK 1.00* NL 1.00*
! NY 0.98 OV 1.00* PT 1.00* SC 1.00*
! TS 1.12 WF 1.00* WZ 0.98
!
!
! Correcting IF 2.
! A total of 24 telescope corrections were flagged in sub-array 1.
! Telescope amplitude corrections in sub-array 1:
! BR 1.03 FD 1.00 GC 0.99 GG 1.00*
! HH 1.00* HN 0.94 KK 1.01 KP 0.95
! LA 0.95 MC 1.21 MK 1.01 NL 0.97
! NY 1.07 OV 1.00 PT 0.96 SC 0.98
! TS 1.00* WF 1.11 WZ 1.00
!
! A total of 39 telescope corrections were flagged in sub-array 2.
! Telescope amplitude corrections in sub-array 2:
! BR 0.97 FD 0.94 GC 0.98 GG 1.00*
! HH 1.00* HN 0.92 KK 1.00* KP 0.93
! LA 0.95 MC 1.00* MK 0.95 NL 0.97
! NY 1.01 OV 1.01 PT 0.93 SC 1.00*
! TS 0.92 WF 1.02 WZ 1.00*
!
! A total of 21 telescope corrections were flagged in sub-array 3.
! Telescope amplitude corrections in sub-array 3:
! BR 1.00* FD 1.00* GC 1.08 GG 1.00*
! HH 1.00 HN 1.00* KK 1.00* KP 1.00*
! LA 1.00* MC 1.00* MK 1.00* NL 1.00*
! NY 1.07 OV 1.00* PT 1.00* SC 1.00*
! TS 1.07 WF 1.00* WZ 0.95
!
!
! Correcting IF 3.
! A total of 24 telescope corrections were flagged in sub-array 1.
! Telescope amplitude corrections in sub-array 1:
! BR 1.07 FD 1.00 GC 1.03 GG 1.00*
! HH 1.00* HN 0.96 KK 1.01 KP 1.00
! LA 0.98 MC 1.21 MK 1.01 NL 1.02
! NY 1.08 OV 1.04 PT 0.97 SC 1.00
! TS 1.00* WF 1.04 WZ 1.01
!
! A total of 39 telescope corrections were flagged in sub-array 2.
! Telescope amplitude corrections in sub-array 2:
! BR 1.03 FD 0.94 GC 1.03 GG 1.00*
! HH 1.00* HN 0.94 KK 1.00* KP 0.93
! LA 0.98 MC 1.00* MK 0.98 NL 1.00
! NY 1.03 OV 1.05 PT 0.97 SC 1.00*
! TS 0.92 WF 0.98 WZ 1.00*
!
! A total of 21 telescope corrections were flagged in sub-array 3.
! Telescope amplitude corrections in sub-array 3:
! BR 1.00* FD 1.00* GC 1.16 GG 1.00*
! HH 1.01 HN 1.00* KK 1.00* KP 1.00*
! LA 1.00* MC 1.00* MK 1.00* NL 1.00*
! NY 1.02 OV 1.00* PT 1.00* SC 1.00*
! TS 1.17 WF 1.00* WZ 0.98
!
!
! Correcting IF 4.
! A total of 24 telescope corrections were flagged in sub-array 1.
! Telescope amplitude corrections in sub-array 1:
! BR 1.04 FD 0.96 GC 1.03 GG 1.00*
! HH 1.00* HN 0.95 KK 1.05 KP 0.95
! LA 0.95 MC 1.20 MK 1.06 NL 1.01
! NY 0.99 OV 1.01 PT 0.98 SC 1.08
! TS 1.00* WF 1.07 WZ 1.01
!
! A total of 39 telescope corrections were flagged in sub-array 2.
! Telescope amplitude corrections in sub-array 2:
! BR 0.97 FD 0.93 GC 1.00 GG 1.00*
! HH 1.00* HN 0.94 KK 1.00* KP 0.95
! LA 0.94 MC 1.00* MK 0.99 NL 1.02
! NY 0.97 OV 1.05 PT 0.98 SC 1.00*
! TS 0.94 WF 0.98 WZ 1.00*
!
! A total of 21 telescope corrections were flagged in sub-array 3.
! Telescope amplitude corrections in sub-array 3:
! BR 1.00* FD 1.00* GC 1.04 GG 1.00*
! HH 1.04 HN 1.00* KK 1.00* KP 1.00*
! LA 1.00* MC 1.00* MK 1.00* NL 1.00*
! NY 1.03 OV 1.00* PT 1.00* SC 1.00*
! TS 1.01 WF 1.00* WZ 1.03
!
!
! Fit before self-cal, rms=0.184893Jy sigma=0.001240
! Fit after self-cal, rms=0.187175Jy sigma=0.001221
dynam = dynam - 0.5
flux_cutoff = imstat(rms) * dynam
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=0.6519 mas, bmaj=0.9451 mas, bpa=-17.27 degrees
! Estimated noise=495.151 mJy/beam.
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
selfcal
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = -0.00179836 Jy
! Component: 100 - total flux cleaned = -0.00131112 Jy
! Component: 150 - total flux cleaned = -0.00100493 Jy
! Component: 200 - total flux cleaned = -0.000916595 Jy
! Total flux subtracted in 200 components = -0.000916595 Jy
! Clean residual min=-0.002988 max=0.002959 Jy/beam
! Clean residual mean=0.000114 rms=0.000719 Jy/beam
! Combined flux in latest and established models = 0.440287 Jy
! Performing phase self-cal
! Adding 19 model components to the UV plane model.
! The established model now contains 70 components and 0.440287 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.187041Jy sigma=0.001220
! Fit after self-cal, rms=0.187090Jy sigma=0.001220
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
selfcal true, true, soltime1
! Performing amp+phase self-cal over 120 minute time intervals
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.187090Jy sigma=0.001220
! Fit after self-cal, rms=0.187364Jy sigma=0.001220
dynam = dynam - 0.75
clean clean_niter,clean_gain
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=0.6537 mas, bmaj=0.9466 mas, bpa=-17.23 degrees
! Estimated noise=495.457 mJy/beam.
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = -0.00152556 Jy
! Component: 100 - total flux cleaned = -0.00143711 Jy
! Component: 150 - total flux cleaned = -0.00143401 Jy
! Component: 200 - total flux cleaned = -0.00143243 Jy
! Total flux subtracted in 200 components = -0.00143243 Jy
! Clean residual min=-0.002633 max=0.002931 Jy/beam
! Clean residual mean=0.000107 rms=0.000682 Jy/beam
! Combined flux in latest and established models = 0.438854 Jy
selfcal
! Performing phase self-cal
! Adding 25 model components to the UV plane model.
! The established model now contains 73 components and 0.438854 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.187299Jy sigma=0.001219
! Fit after self-cal, rms=0.187300Jy sigma=0.001219
flux_cutoff = imstat(rms) * dynam
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
selfcal
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
! Added new window around map position (-3.4, 2.4).
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.00311533 Jy
! Component: 100 - total flux cleaned = 0.00469897 Jy
! Component: 150 - total flux cleaned = 0.00539218 Jy
! Component: 200 - total flux cleaned = 0.00593905 Jy
! Total flux subtracted in 200 components = 0.00593905 Jy
! Clean residual min=-0.002314 max=0.002558 Jy/beam
! Clean residual mean=0.000069 rms=0.000618 Jy/beam
! Combined flux in latest and established models = 0.444793 Jy
! Performing phase self-cal
! Adding 20 model components to the UV plane model.
! The established model now contains 86 components and 0.444793 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.187249Jy sigma=0.001218
! Fit after self-cal, rms=0.187242Jy sigma=0.001218
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
selfcal true, true, soltime2
! Performing amp+phase self-cal over 20 minute time intervals
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.187242Jy sigma=0.001218
! Fit after self-cal, rms=0.187810Jy sigma=0.001218
clean clean_niter,clean_gain
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=0.6552 mas, bmaj=0.9478 mas, bpa=-17.17 degrees
! Estimated noise=495.925 mJy/beam.
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = -0.000570805 Jy
! Component: 100 - total flux cleaned = -0.000311928 Jy
! Component: 150 - total flux cleaned = -2.43884e-05 Jy
! Component: 200 - total flux cleaned = 2.95448e-05 Jy
! Total flux subtracted in 200 components = 2.95448e-05 Jy
! Clean residual min=-0.002110 max=0.002366 Jy/beam
! Clean residual mean=0.000060 rms=0.000590 Jy/beam
! Combined flux in latest and established models = 0.444823 Jy
selfcal
! Performing phase self-cal
! Adding 27 model components to the UV plane model.
! The established model now contains 91 components and 0.444823 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.187776Jy sigma=0.001218
! Fit after self-cal, rms=0.187784Jy sigma=0.001218
flux_cutoff = imstat(rms) * dynam
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
selfcal
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.000368243 Jy
! Component: 100 - total flux cleaned = 0.000516671 Jy
! Component: 150 - total flux cleaned = 0.00065417 Jy
! Component: 200 - total flux cleaned = 0.000781964 Jy
! Total flux subtracted in 200 components = 0.000781964 Jy
! Clean residual min=-0.002023 max=0.002326 Jy/beam
! Clean residual mean=0.000055 rms=0.000577 Jy/beam
! Combined flux in latest and established models = 0.445605 Jy
! Performing phase self-cal
! Adding 27 model components to the UV plane model.
! The established model now contains 93 components and 0.445605 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.187765Jy sigma=0.001218
! Fit after self-cal, rms=0.187767Jy sigma=0.001218
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
uvtaper 0.3,taper_size
! Gaussian taper: value 0.3 at UV radius = 70 mega-wavelengths.
win_mult = win_mult * 1.2
selfcal true, true, soltime2
! Performing amp+phase self-cal over 20 minute time intervals
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.187767Jy sigma=0.001218
! Fit after self-cal, rms=0.188244Jy sigma=0.001218
clean clean_niter,clean_gain
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=2.12 mas, bmaj=2.335 mas, bpa=11.63 degrees
! Estimated noise=765.181 mJy/beam.
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.000452077 Jy
! Component: 100 - total flux cleaned = 0.000488641 Jy
! Component: 150 - total flux cleaned = 0.000457859 Jy
! Component: 200 - total flux cleaned = 0.000431461 Jy
! Total flux subtracted in 200 components = 0.000431461 Jy
! Clean residual min=-0.002847 max=0.003203 Jy/beam
! Clean residual mean=0.000164 rms=0.001031 Jy/beam
! Combined flux in latest and established models = 0.446036 Jy
selfcal
! Performing phase self-cal
! Adding 15 model components to the UV plane model.
! The established model now contains 102 components and 0.446036 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.188246Jy sigma=0.001218
! Fit after self-cal, rms=0.188240Jy sigma=0.001218
flux_cutoff = imstat(rms) * dynam
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
selfcal
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.000130829 Jy
! Component: 100 - total flux cleaned = 0.000110482 Jy
! Component: 150 - total flux cleaned = 0.000130569 Jy
! Component: 200 - total flux cleaned = 0.000113001 Jy
! Total flux subtracted in 200 components = 0.000113001 Jy
! Clean residual min=-0.002763 max=0.003161 Jy/beam
! Clean residual mean=0.000162 rms=0.001016 Jy/beam
! Combined flux in latest and established models = 0.446149 Jy
! Performing phase self-cal
! Adding 17 model components to the UV plane model.
! The established model now contains 110 components and 0.446149 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.188244Jy sigma=0.001218
! Fit after self-cal, rms=0.188240Jy sigma=0.001218
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
uvtaper 0,0
! No UV-taper is currently set.
win_mult = win_mult / 1.2
print "************** FINISHED AMPLITUDE SELF-CAL **************"
! ************** FINISHED AMPLITUDE SELF-CAL **************
restore
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=0.6562 mas, bmaj=0.9488 mas, bpa=-17.13 degrees
! Estimated noise=496.544 mJy/beam.
! restore: Substituting estimate of restoring beam from last 'invert'.
! Restoring with beam: 0.6562 x 0.9488 at -17.13 degrees (North through East)
! Clean map min=-0.0017758 max=0.32399 Jy/beam
if(peak(flux) > thresh)
selfcal true, true
clean clean_niter,clean_gain
selfcal
flux_cutoff = imstat(rms) * dynam
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
selfcal
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
selfcal true, true
end if
print "************** CLEARING MODEL AND STARTING OVER **********"
! ************** CLEARING MODEL AND STARTING OVER **********
clrmod true
! clrmod: Cleared the established and tentative models.
uvw 2,-1
! Uniform weighting binwidth: 2 (pixels).
! Gridding weights will be scaled by errors raised to the power -1.
! Radial weighting is not currently selected.
clean clean_niter,clean_gain
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=0.5506 mas, bmaj=0.7941 mas, bpa=-14.32 degrees
! Estimated noise=870.595 mJy/beam.
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.244523 Jy
! Component: 100 - total flux cleaned = 0.309542 Jy
! Component: 150 - total flux cleaned = 0.341104 Jy
! Component: 200 - total flux cleaned = 0.359885 Jy
! Total flux subtracted in 200 components = 0.359885 Jy
! Clean residual min=-0.005014 max=0.010362 Jy/beam
! Clean residual mean=0.000108 rms=0.001670 Jy/beam
! Combined flux in latest and established models = 0.359885 Jy
uvw 0,-1
! Uniform weighting is not currently selected.
! Gridding weights will be scaled by errors raised to the power -1.
! Radial weighting is not currently selected.
flux_cutoff = imstat(rms) * dynam
! Adding 13 model components to the UV plane model.
! The established model now contains 13 components and 0.359885 Jy
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=0.6562 mas, bmaj=0.9488 mas, bpa=-17.13 degrees
! Estimated noise=496.544 mJy/beam.
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
keep
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.0206542 Jy
! Component: 100 - total flux cleaned = 0.0339396 Jy
! Component: 150 - total flux cleaned = 0.0433587 Jy
! Component: 200 - total flux cleaned = 0.0505273 Jy
! Total flux subtracted in 200 components = 0.0505273 Jy
! Clean residual min=-0.002519 max=0.004291 Jy/beam
! Clean residual mean=0.000250 rms=0.000990 Jy/beam
! Combined flux in latest and established models = 0.410412 Jy
! Adding 36 model components to the UV plane model.
! The established model now contains 41 components and 0.410412 Jy
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Added new window around map position (-2.4, 2.2).
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.00566846 Jy
! Component: 100 - total flux cleaned = 0.0102825 Jy
! Component: 150 - total flux cleaned = 0.0141191 Jy
! Component: 200 - total flux cleaned = 0.017373 Jy
! Total flux subtracted in 200 components = 0.017373 Jy
! Clean residual min=-0.002171 max=0.002418 Jy/beam
! Clean residual mean=0.000151 rms=0.000688 Jy/beam
! Combined flux in latest and established models = 0.427785 Jy
! Adding 41 model components to the UV plane model.
! The established model now contains 64 components and 0.427785 Jy
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
uvtaper 0.3,taper_size
! Gaussian taper: value 0.3 at UV radius = 70 mega-wavelengths.
clean clean_niter,clean_gain
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=2.12 mas, bmaj=2.335 mas, bpa=11.63 degrees
! Estimated noise=765.181 mJy/beam.
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.00731245 Jy
! Component: 100 - total flux cleaned = 0.0114367 Jy
! Component: 150 - total flux cleaned = 0.0139911 Jy
! Component: 200 - total flux cleaned = 0.0156256 Jy
! Total flux subtracted in 200 components = 0.0156256 Jy
! Clean residual min=-0.002848 max=0.003138 Jy/beam
! Clean residual mean=0.000224 rms=0.001040 Jy/beam
! Combined flux in latest and established models = 0.443411 Jy
flux_cutoff = imstat(rms) * dynam
repeat
if (peak(flux) > flux_cutoff) peakwin win_mult
clean clean_niter,clean_gain
flux_cutoff = imstat(rms) * dynam
keep
new_peak = peak(flux)
until(new_peak<=flux_cutoff)
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.00105861 Jy
! Component: 100 - total flux cleaned = 0.00174809 Jy
! Component: 150 - total flux cleaned = 0.00204104 Jy
! Component: 200 - total flux cleaned = 0.00210522 Jy
! Total flux subtracted in 200 components = 0.00210522 Jy
! Clean residual min=-0.002771 max=0.003168 Jy/beam
! Clean residual mean=0.000174 rms=0.001018 Jy/beam
! Combined flux in latest and established models = 0.445516 Jy
! Adding 58 model components to the UV plane model.
! The established model now contains 110 components and 0.445516 Jy
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
uvtaper 0,0
! No UV-taper is currently set.
clean
! Inverting map and beam
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! Estimated beam: bmin=0.6562 mas, bmaj=0.9488 mas, bpa=-17.13 degrees
! Estimated noise=496.544 mJy/beam.
! clean: niter=200 gain=0.03 cutoff=0
! Component: 050 - total flux cleaned = 0.000361289 Jy
! Component: 100 - total flux cleaned = 0.000316092 Jy
! Component: 150 - total flux cleaned = 0.000275547 Jy
! Component: 200 - total flux cleaned = 0.000238146 Jy
! Total flux subtracted in 200 components = 0.000238146 Jy
! Clean residual min=-0.001851 max=0.002226 Jy/beam
! Clean residual mean=0.000047 rms=0.000555 Jy/beam
! Combined flux in latest and established models = 0.445754 Jy
selfcal
! Performing phase self-cal
! Adding 18 model components to the UV plane model.
! The established model now contains 121 components and 0.445754 Jy
!
! Correcting IF 1.
!
! Correcting IF 2.
!
! Correcting IF 3.
!
! Correcting IF 4.
!
! Fit before self-cal, rms=0.188256Jy sigma=0.001217
! Fit after self-cal, rms=0.188181Jy sigma=0.001217
wmodel J1104+3812_X_2001_07_05_pus_map.mod
! Writing 121 model components to file: J1104+3812_X_2001_07_05_pus_map.mod
wobs J1104+3812_X_2001_07_05_pus_uvs.fits
! Writing UV FITS file: J1104+3812_X_2001_07_05_pus_uvs.fits
wwins J1104+3812_X_2001_07_05_pus_map.win
! wwins: Wrote 5 windows to J1104+3812_X_2001_07_05_pus_map.win
x = (field_size-8) * field_cell / 4
addwin -x,x,-x,x
clean (field_size*4),0.01
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! clean: niter=1024 gain=0.01 cutoff=0
! Component: 050 - total flux cleaned = 0.000989592 Jy
! Component: 100 - total flux cleaned = 0.00164016 Jy
! Component: 150 - total flux cleaned = 0.00218928 Jy
! Component: 200 - total flux cleaned = 0.00261561 Jy
! Component: 250 - total flux cleaned = 0.0029634 Jy
! Component: 300 - total flux cleaned = 0.00323966 Jy
! Component: 350 - total flux cleaned = 0.00338999 Jy
! Component: 400 - total flux cleaned = 0.00344896 Jy
! Component: 450 - total flux cleaned = 0.00356407 Jy
! Component: 500 - total flux cleaned = 0.00362032 Jy
! Component: 550 - total flux cleaned = 0.00367588 Jy
! Component: 600 - total flux cleaned = 0.0037305 Jy
! Component: 650 - total flux cleaned = 0.00375735 Jy
! Component: 700 - total flux cleaned = 0.00375777 Jy
! Component: 750 - total flux cleaned = 0.00378381 Jy
! Component: 800 - total flux cleaned = 0.00380906 Jy
! Component: 850 - total flux cleaned = 0.00380891 Jy
! Component: 900 - total flux cleaned = 0.00380871 Jy
! Component: 950 - total flux cleaned = 0.00380887 Jy
! Component: 1000 - total flux cleaned = 0.00376096 Jy
! Total flux subtracted in 1024 components = 0.00380892 Jy
! Clean residual min=-0.001547 max=0.001495 Jy/beam
! Clean residual mean=0.000015 rms=0.000448 Jy/beam
! Combined flux in latest and established models = 0.449563 Jy
keep
! Adding 79 model components to the UV plane model.
! The established model now contains 200 components and 0.449563 Jy
wmap "J1104+3812_X_2001_07_05_pus\_map.fits"
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
! restore: Substituting estimate of restoring beam from last 'invert'.
! Restoring with beam: 0.6562 x 0.9488 at -17.13 degrees (North through East)
! Clean map min=-0.0015918 max=0.32529 Jy/beam
! Writing clean map to FITS file: J1104+3812_X_2001_07_05_pus_map.fits
float peak_flux
peak_flux = peak(flux,max)
print "The peak flux is",peak_flux
! The peak flux is 0.32529
invert
! Inverting map
! Your choice of large map pixels excluded 6.13% of the data.
! The x-axis pixel size should ideally be below 0.1646 milli-arcsec
! The y-axis pixel size should ideally be below 0.1583 milli-arcsec
float image_rms
image_rms = imstat(rms)
print "The final image rms is",image_rms
! The final image rms is 0.000448293
device "J1104+3812_X_2001_07_05_pus\_map.eps/VPS"
! Attempting to open device: 'J1104+3812_X_2001_07_05_pus_map.eps/VPS'
loglevs 100*3*image_rms/peak_flux
! The new contour levels are:
! -0.41344 0.41344 0.826881 1.65376 3.30752 6.61504 13.2301 26.4602 52.9204
print "clev=",int(3*image_rms*10000)/10000
! clev= 0.0013
print "peak=",int(1000*peak_flux)/1000
! peak= 0.325
mapcolor none
! Mapplot colormap: none, contrast: 1 brightness: 0.5.
mapplot cln
! restore: Substituting estimate of restoring beam from last 'invert'.
! Restoring with beam: 0.6562 x 0.9488 at -17.13 degrees (North through East)
! Clean map min=-0.0015918 max=0.32529 Jy/beam
mapcolor color, 0.9
! Mapplot colormap: rainbow, contrast: 0.9 brightness: 0.5.
device "J1104+3812_X_2001_07_05_pus\_map.gif/vgif"
! Attempting to open device: 'J1104+3812_X_2001_07_05_pus_map.gif/vgif'
mapplot cln
quit
! Quitting program
! Log file J1104+3812_X_2001_07_05_pus_uvs.log closed on Thu Jul 5 15:19:17 2007
| en |
all-txt-docs | 439354 | Subject:
RE: comments on LCG persistency talk
From:
"Dirk Duellmann" <Dirk.Duellmann@cern.ch>
Date:
Tue, 21 May 2002 10:57:33 +0200
To:
"David Adams" <dladams@bnl.gov>
CC:
"Torre Wenaus" <wenaus@bnl.gov>, "David Malon" <malon@anl.gov>, "RD Schaffer" <R.D.Schaffer@cern.ch>, <project-lcg-peb-persistency@cern.ch>
Hi David,
thanks very much for your comments! I repost them also to the persistency list
and added some initial comments/questions (indicated by DD and indentation).
Cheers, Dirk
Comments on LCG persistency
David Adams
17may02 1200 EDT
1. Self-describing data
-----------------------
I would like to distinguish gathering and storing data from
processing data and require the latter be possible without
reference to any catalog/database. Job processing has three steps:
1. Identifying input files (logical ID's), mapping these to
the appropriate physical files.
2. Processing the data, i.e. opening and reading input files
and creating and writing output files.
3. Registering the output in the persistent data store.
I would like to be to step 2 without consulting any DB's.
DD: I guess, many people agree on the goal of minimising the
coupling to a (potentially) central service like the catalog.
It's just not trivial to have the knowledge about all files
at the start of a job, without loosing the capability of
transparent navigation from the user code. How would you
discover a deref operation which would pull in yet another
file? Should we forbid it / allow it in rare cases / use it
as the main data access mechanism?
This implies the files that files provide information about their
contents (metadata). At the generic level (i.e. not just event data),
all objects have unique identifiers and the file provides access
to its objects via this identifier. Event data can be handled by
including event header objects in the same or a different file. These
headers which hold the identifiers for the objects in the event.
DD: I got the impression, I have frequently confused people by using
the word "metadata" (and still frequently get confused by other people
using it [;-)] . I think, I maybe should try to make it more explicit
what kind of data is meant - since "metadata" is kind of not-invariant
from the observer perspective.
I assume, with "metadata" you mean : which detector components / processing
steps are included in a particular file?
If that's the case, do you see this content description as common (being the
the same for all experiments) or application specific?
2. File identifiers
-------------------
Every logical file should have a unique identifier and all physical
representations of this file (replicas) should carry this same
identifier. I want to be able to hand someone a list of files which
are sufficient for job input and I need a way to uniquely identify
logical files. Grid sites can use this to estimate the effort
required to gather the data for a job.
DD: We agree on the basic requirement - now how do we generate unique id's
without introducing too much coupling?
Using your three phase model of the job we could in phase 1 one of :
a) use the catalog layer ensures the uniqueness of all newly
created lfn's (e.g. with the help a (location specific) creator prefix which
allows the break the lfn space into manageable independent sub-spaces).
After the lfn has been added it is never changed and therefore can be
eg embedded in read-only streaming layer files. In this model there may be
many separate catalogs (private ones, public one) but they could all be
merged at any time without changing the streaming data.
b) give up on file id uniqueness at creation time (CMS has argued, they could not
keep lfns unique) and possibly rename / alias files as a clash arises
when new files are added to a catalog. At any time the lfn needs to be
at least unique in the scope of it's current catalog.
It's not quite clear to me how this integrates into the rest of the Grid tools which
may make assumptions about the stability of LFNs. Maybe assuming
c) navigation to objects in files is based on a immutable machine generated file ID
only this fid is used in streaming layer object references.
For convenience of the user a human readable description can be attached
to this file id eg by the RDBMS layer. Since this is not directly used in the navigation
it can freely be changed - result maybe a confused user (description is now different)
but stable navigation.
in short
a) globally unique and immutable lfn
b) locally unique and mutable lfn + non-trivial catalog attach
c) lfn is only a human readable description attached to a machine generated file ID (eg GUID)
3. Object replication
---------------------
I would like to see support for object replication. This is more
than file replcation. It means taking objects from different files
and replicating them in a single file. Refernces to these objects
can then be satisfied using this new file or the original file.
DD: This sounds similar as (part of) CMS's deep copy request to me.
Again, the basic requirement is: make logical object id work
without getting into the scalability issues (big central by object
lookup table) they are know for. This will most likely mean
that we have to use some blending between just enough of a "logical ID"
to gain the flexibility move the objects around, but still physical
enough to get reasonable decoupling a scalability.
4. Multiple persistency technologies
------------------------------------
I assume we want to allow multiple persistence technolgies, i.e.
not just ROOT. I am not objecting to the latter, but we should
choose one path: either provide full support to plug in multiple
technologies or simply adopt ROOT. In the following, I assume we
want multiple technologies.
DD: Yes, that's what the RTAG said in it's document, and that what
I'm assuming as well.
5. Object references
--------------------
Object references should be handled at the LCG level. Every object should be
assigned a unique identifier and this identifier serves as the persistent
representation of the reference. The object identifier should probably include
the identifier of the file which owns the original copy of the object to aid
in navigation.
DD: I agree, with the handling on LCG level - it's almost
a direct consequence from the requirement of multi-technology refs
which are not handled by any backend implementation.
Still the lcg ref could/would try to use back end refs in its
implementation. I also agree that the OID should better be designed
such that it is easy to derive the lfn/file id from it, without having
to consult a lot of file/process description ("meta") data.
The problem is, this is currently not the case in root I/O refs and
(maybe more important) it may clash with the request for a logical OID
(move an object between files - without changing it's id).
6. Dictionary
-------------
Again, this should be implemented at the LCG method with a clear
mechanism to support different technologies.
DD: I agree, but still see again implementation questions
that need to be clarified.
7. Documentation
----------------
It appears from you talk that design is proceeding in a small group.
This should be documented and shared with a larger community.
Meetings are neccessary but far from sufficient to communicate the
design or event the definitions of the terms. I read all messages
on the LCG persistency mailing list hpoing to see reference to some
sort of documenmtation.
DD: I agree with all of this - yes we were less than 2FTE so far and
we are only just entering a real design phase in some areas. Also so far,
even reading all the email on the persistency list did not help very much - as
this is the very first one [:-)]
Anyway, I know that efficient communication will be one of the real
problems of this project, since most people are not at CERN or even
in the CERN time zone. I'm hoping that this mailing list will become
much more active and its web archive a useful starting point for new
people. I'd therefore invite everybody to copy
mailto:project-lcg-peb-persistency@cern.ch
on any technical discussions of more general interest.
Cheers, Dirk
> -----Original Message-----
> From: David Adams [mailto:dladams@bnl.gov]
> Sent: Friday, May 17, 2002 18:01
> To: Dirk Duellmann
> Cc: Torre Wenaus; David Malon; RD Schaffer; David Adams
> Subject: comments on LCG persistency talk
>
>
> Dirk:
>
> I have posted some comments on today's talk at
>
> http://www.usatlas.bnl.gov/~dladams/hybrid/comments/lcg/adams01.txt
>
> da
>
> --
> David Adams desk: 631-344-6049
> Brookhaven National Lab fax: 631-344-5078
> PAS group, Building 510A email: dladams@bnl.gov
> Upton, NY 11973-5000 http://www.usatlas.bnl.gov/~dladams
>
| en |
log-files | 639737 | 2003.12.15 15:25 B W:\rr\amed\iraqreport\iraqreport.html --> rs7.loc.gov /.mnt.marvel.www.data.rr/amed/iraqreport iraqreport.html
2003.12.15 15:28 B W:\rr\amed\iraqreport\iraqreport.html --> rs7.loc.gov /.mnt.marvel.www.data.rr/amed/iraqreport iraqreport.html
2003.12.15 15:29 B W:\rr\amed\iraqreport\iraqreport.html --> rs7.loc.gov /.mnt.marvel.www.data.rr/amed/iraqreport iraqreport.html
2003.12.15 15:35 B W:\rr\amed\iraqreport\iraqreport2.html --> rs7.loc.gov /.mnt.marvel.www.data.rr/amed/iraqreport iraqreport2.html
2003.12.15 15:36 B W:\rr\amed\iraqreport\iraqreport2.html --> rs7.loc.gov /.mnt.marvel.www.data.rr/amed/iraqreport iraqreport2.html
2003.12.15 15:59 B W:\rr\amed\iraqreport\iraqreport2.html --> rs7.loc.gov /.mnt.marvel.www.data.rr/amed/iraqreport iraqreport2.html
2003.12.15 16:28 B W:\rr\amed\iraqreport\iraqreport2.html --> rs7.loc.gov /.mnt.marvel.www.data.rr/amed/iraqreport iraqreport2.html
2003.12.15 16:40 B W:\rr\amed\iraqreport\iraqreport2.html --> rs7.loc.gov /.mnt.marvel.www.data.rr/amed/iraqreport iraqreport2.html
| en |