CDA - News Item 040
- ChaSeR
- Chandra Source Catalog ♦ CSCview
- Chandra Footprint Service
- Request for Acknowledgement
@ChandraArchive
The Archive
- Public Data
- Proprietary Data
- Repro III
- Repro IV
- Repro V
- Privacy Impact Assessment
- Release Notes
- Documentation
- Archive Operations Team
Search and Retrieve Data
Advanced Data Services
Archive User Services
- Synopsis of Services
- Processing Status
- Special Requests
- Dataset Identifiers (DOIs)
- Contributed Datasets
- CXO Papers Repository
Chandra Aggregated Datasets
Publishing Chandra Results
Data Analysis Links
- The archive is fully functional.
-
Reprocessing IV has been completed in December 2014.
- ASCDSVER: 10.13
- CALDBVER: 4.11.5
- Electrical Outage 11/05/21 - 11/06/21
2021-11-05
There will be a planned electrical outage Friday, November 5 2021, 5:30PM - Saturday, November 6 2021, 6:00PM EDT. During this time period ChaSeR and other archive interfaces will be unavailable. - Electrical Outage on 07/28/21
2021-07-26
There will be a planned electrical outage Wednesday, July 28 2021, 8:00PM - 10:00PM EDT. During this time period ChaSeR and other archive interfaces will be unavailable. - Downtime on 6/12/21
2021-06-10
Due to electrical work, the public interfaces of the Chandra Data Archive will not be available on Saturday 6/12 from 4 AM to 9 PM. - Repro V Begins
2020-10-26
The fifth major reprocessing of the archive (Repro V) has started! Details can be found here. - Past Notices
Update on CDFS 2010 Data
2010-09-01
Due to a problem with bad pixel processing in one of the 2010 CDFS observations
(ObsId 12218), a small percentage of its events were improperly omitted in the CDFS merged dataset released on 20 August 2010, with Chandra Announcement 61. This involved
almost 6000 events (out of 200,000) with Time > 392706012, CCD_ID = 0, and CHIPY > 512.
A corrected event file for ObsId 12218 was released on 1 September 2010, identified by "N002".
The 2010 and 2000-2007-2010 merged products were also regenerated, identified as "N002",
and released on the same date.
We caution that the problem may occur for this ObsId (12218) if a user re-runs acis_build_badpix or acis_run_hotpix (which calls acis_build_badpix), for example following the CIAO bad pixel science thread.
