Search:

[Advanced Search]



BurstCube Archive: Getting started

General

The BurstCube data archive in the obs/ directory is divided into year_month subdirectories which each contain the BurstCube data divided into observations of one day in length. If continuously binned data (CBD) was recorded, it is located within the monitoring/ directory. Similarly, event data is located in the events/ directory. 

 
                                              data/
                                                |
                        obs/                                              trend/
                         |                                                  |
        2024_05/      2024_06/ .... YYYY_MM/          attitude/ gti_binning/ gti_poscnt/ gti_saa/ timeline/
                         |
         240602/     20240604/ .... YYMMDD/
                         |
              auxil/ monitoring/ events/

BurstCube derived data files

The trend/ directory in the data archive has multiple subdirectories that contain files created to facilitate the analysis of BurstCube data:

attitude/— attitude data at three separate time periods (FITS; bc_csa_att.fits)

gti_binning/— the time intervals containing good time bin sizes (0.256 seconds) broken up by detector (FITS; bc_cs#_bin0_256.gti)

gti_poscnt/— the time intervals containing positive counts broken up by detector (FITS; bc_poscounts_cs#.gti) and the unfiltered and filtered (*.gti and *_cl.gti respectively) GTI for times of odd counts.

gti_saa/— The unfiltered and filtered (*.gti and *_cl.gti respectively) GTI for the SAA.

timeline/— The timeline of events during the BurstCube mission.

Archive access : Web, wget, download script and special maxi download script

At the HEASARC the BurstCube archive can be accessed using the web interfaces Browse , the wget protocol, and the download script

  • Access via Web : The archive access via the Web makes use of database tables to search for the science data. The database tables are for: the BurstCube data, burcbmastr. Theis table records high-level information for each observation. It can be searched for time and other parameters and from the result page it is possible to select and retrieve the data files.

  • Wget : If you have wget installed, and the observation id is already known, the data can be retrieved via 'wget'. For example using the https protocol, if the user wants to retrieve the data for '240530' observed on May 30 2024, she/he can retrieve the entire sequence (see Example 1) or data for a single CBD file for the CS0 detector (see Example 2) 
    Example 1
 wget -q -nH --cut-dirs=6 -r -l0 -c -N -np -R 'index*' -erobots=off --retr-symlinks https://heasarc.gsfc.nasa.gov/FTP/burstcube/data/obs/2024_05/240530/ 

Example 2
  wget -q -nH --cut-dirs=7 -r -l0 -c -N -np -R 'index*' -erobots=off --retr-symlinks https://heasarc.gsfc.nasa.gov/FTP/burstcube/data/obs/2024_05/240530/monitor/bc240530cs0_3cbd_uf.fits.gz
  • download_wget : donwload_wget is a PERL script that uses the wget protocol, similarly to the example above, but simplify the command and allow for more flexility. Download the download_wget and place it in your local machine 
     
Example: To download a specific sequence type: 
     
  > download_wget.pl https://heasarc.gsfc.nasa.gov/FTP/burstcube/data/obs/2024_05/240530/ 


To get help type :  > download_wget.pl help

NOTE : The BurstCube team has released together with the data a list of caveats related to the data, operations, and time assignment relevant to the data analysis.