This page contains an index of burst data from 4U 1705-44. Click on the burst number/time to go to the page for each burst

ID flag1 ObsID UT MJD PRE?
1 20074-02-01-00 1997 Feb 16 22:43:51 50495.947120 Y
2 20073-04-01-00 1997 Apr 1 14:03:14 50539.585580 N
3 20073-04-01-00 1997 Apr 1 17:05:08 50539.711910 N
4 20073-04-01-00 1997 Apr 1 18:45:29 50539.781590 N
5 20073-04-01-03 1997 Apr 4 12:04:08 50542.502870 Y
6 b,d 20161-01-02-00 1997 May 16 12:40:20 50584.528020
7 b,d 20161-01-02-00 1997 May 16 14:36:52 50584.608940
8 b,d 20161-01-02-00 1997 May 16 16:31:33 50584.688580
9 b,d 20161-01-02-01 1997 May 17 14:59:08 50585.624400
10 b,d 20161-01-02-02 1997 May 18 13:01:33 50586.542750 N
11 b,d 20161-01-02-03 1997 May 19 08:31:12 50587.355010
12 b,d 20161-01-02-03 1997 May 19 10:51:00 50587.452080
13 b 20161-01-02-03 1997 May 19 11:01:58 50587.459700 N
14 b,d 20161-01-02-04 1997 May 19 15:45:10 50587.656370
15 b 20161-01-02-04 1997 May 19 15:52:22 50587.661370
16 40051-03-03-00 1999 Feb 14 12:48:49 51223.533900 N
17 40051-03-04-00 1999 Feb 16 12:20:39 51225.514350 N
18 40051-03-11-00 1999 Mar 2 10:21:25 51239.431550 N
19 40051-03-12-00 1999 Mar 4 21:31:38 51241.896980 N
20 40051-03-13-00 1999 Mar 6 23:14:40 51243.968530 N
21 40034-01-05-00 1999 Jun 4 09:29:15 51333.395320 Y
22 40034-01-04-05 1999 Jul 14 15:14:24 51373.635010 N
23 40034-01-05-05 1999 Jul 31 03:15:44 51390.135940 N
24 40034-01-08-02 2000 Feb 3 01:17:59 51577.054160 N
25 40034-01-09-05 2000 Feb 7 15:13:29 51581.634380 N
26 40034-01-09-05 2000 Feb 7 15:20:53 51581.639500 N
27 40034-01-09-05 2000 Feb 7 15:30:12 51581.645980 N
28 40034-01-09-00 2000 Feb 7 18:35:29 51581.774650 N
29 40034-01-09-00 2000 Feb 7 21:27:51 51581.894350 N
30 70038-01-01-00 2002 Apr 28 22:12:41 52392.925480 N
31 70038-01-01-00 2002 Apr 29 00:08:09 52393.005670 N
32 70038-01-01-00 2002 Apr 29 01:05:17 52393.045340 N
33 70038-01-01-00 2002 Apr 29 01:55:28 52393.080190 N
34 70038-01-01-01 2002 Apr 29 02:41:03 52393.111840 N
35 70038-01-01-01 2002 Apr 29 03:41:29 52393.153810 N
36 70038-01-01-01 2002 Apr 29 04:35:53 52393.191590 N
37 70038-01-01-01 2002 Apr 29 06:29:02 52393.270170 N
38 70038-01-01-01 2002 Apr 29 07:29:45 52393.312340 N
39 d 70038-03-01-01 2002 Jun 29 19:54:43 52454.829670 N
40 91039-01-01-12 2005 May 31 14:09:18 53521.589800 N
41 91039-01-01-20 2005 Jun 4 09:03:32 53525.377450 N
42 91039-01-01-32 2005 Jun 15 07:50:47 53536.326940 N
43 91039-01-01-51 2005 Jun 27 17:23:31 53548.724680 N
44 91039-01-01-60 2005 Jul 1 03:07:42 53552.130350 N
45 91039-01-02-02 2005 Sep 21 03:57:01 53634.164610 N
46 91039-01-02-30 2005 Oct 7 13:43:10 53650.571650 N
47 91039-01-02-52 2005 Oct 25 21:52:07 53668.911190 Y?

Flag values indicates a range of potential analysis issues, as follows:

  1. The burst was observed during a slew, and thus offsetfrom the source position.
  2. The observation was offset from the source position. In cases (a) and (b) we scaled the flux and fluence by the mean collimator response appropriate for the position of the source in the field of view, as described in Appendix B.
  3. The origin of the burst is uncertain; the burst may have been from another source in the field of view (we rescaled the flux and fluence, if necessary, based on the assumed origin).
  4. Buffer overruns (or some other instrumental effect) caused gaps in the high time resolution data.
  5. The burst was so faint that only the peak flux could be measured, and not the fluence or other parameters.
  6. An extremely faint burst or possibly problems with the background subtraction, resulting in no fit results.
  7. The full burst profile was not observed, so that the event can be considered an unconfirmed burst candidate. Typically in these cases the initial burst rise is missed, so that the measured peak flux and fluence are lower limits only.
  8. High time resolution data modes did not cover the burst.