CDA - News Item 001
- 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.6
- 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
Changed Sequence Numbers
In the past, when observations needed to be split (for instance, a partially completed observation had to be continued with different ACIS chips), a new ObsId with a new Sequence Number was created. We have changed that policy and currently a new ObsId with the old Sequence Number is created. In order to facilitate uniform bookkeeping, we are now changing the Sequence Numbers of past observations for these split cases so that the current policy will appear uniformly applied since the beginning of the mission. This way, different pieces of the same observation can always be tied together by their common Sequence Number.
We have posted lists of ObsIds that had their Sequence Number changed, accompanied by their parent ObsIds, separately for GTO and GO observations.
