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

ID flag1 ObsID UT MJD PRE?
1 20084-02-01-00 1997 Jul 19 12:03:26 50648.502390 N
2 d 20084-02-01-00 1997 Jul 19 18:40:58 50648.778460 N
3 20084-02-02-00 1997 Jul 26 09:03:23 50655.377360 N
4 20084-02-02-00 1997 Jul 26 14:04:18 50655.586320 N
5 d 20084-02-01-02 1997 Jul 30 07:22:37 50659.307380 N
6 20084-02-01-02 1997 Jul 30 12:11:56 50659.508300 N
7 40025-04-01-00 1999 Feb 21 23:48:32 51230.992040 N
8 d 40025-04-01-01 1999 Feb 22 04:56:05 51231.205620 N
9 d 50030-01-01-04 2000 Jun 22 11:57:46 51717.498460 N
10 50030-01-02-00 2000 Jul 23 07:09:42 51748.298410 N
11 d 50025-01-01-00 2000 Aug 25 07:58:34 51781.332340 Y
12 d 50025-01-01-04 2000 Aug 25 14:46:46 51781.615810 Y?
13 50030-01-07-00 2001 Jan 30 04:39:16 51939.193940 N
14 50030-01-08-00 2001 Feb 4 03:50:29 51944.160070 N
15 50030-01-11-00 2001 Apr 1 15:47:17 52000.657840 N
16 50030-01-11-00 2001 Apr 1 21:55:53 52000.913820 N
17 50030-01-12-00 2001 Aug 9 20:44:53 52130.864510 N
18 50030-01-14-00 2001 Nov 16 17:02:10 52229.709850 N
19 80033-01-01-08 2003 Nov 14 15:05:51 52957.629070 Y
20 80033-01-02-00 2004 Jan 18 01:17:56 53022.054130 N
21 80033-01-01-07 2004 Jan 18 21:12:37 53022.883760 N
22 80033-01-01-04 2004 Jan 20 00:30:01 53024.020850 N
23 80033-01-04-00 2004 Feb 29 01:59:38 53064.083080 N
24 80033-01-04-02 2004 Feb 29 06:32:16 53064.272420 N
25 80033-01-05-02 2004 Mar 1 07:18:11 53065.304300 N
26 80033-01-05-01 2004 Mar 1 23:26:40 53065.976850 N
27 80033-01-06-00 2004 Mar 2 07:27:52 53066.311020 N
28 80033-01-07-02 2004 Apr 8 22:12:46 53103.925540 N
29 80033-01-09-02 2004 Apr 9 06:18:07 53104.262580 N
30 80033-01-09-00 2004 Apr 9 21:32:20 53104.897450 N
31 80033-01-15-02 2004 Apr 11 08:44:45 53106.364410 N
32 80033-01-11-02 2004 Apr 12 06:56:34 53107.289280 N
33 80033-01-12-00 2004 Apr 12 14:10:29 53107.590620 N
34 80033-01-12-00 2004 Apr 12 21:51:36 53107.910840 N
35 80033-01-14-04 2004 Apr 13 05:40:02 53108.236140 N
36 80033-01-13-00 2004 Apr 13 12:11:53 53108.508260 N
37 80033-01-13-00 2004 Apr 13 18:17:23 53108.762070 N
38 80033-01-14-00 2004 Apr 14 18:32:01 53109.772230 N
39 80033-01-14-02 2004 Apr 15 00:43:14 53110.030030 N
40 80033-01-16-03 2004 Apr 16 02:08:57 53111.089550 N
41 80033-01-16-00 2004 Apr 16 20:29:36 53111.853890 N
42 80033-01-16-08 2004 Apr 17 02:45:18 53112.114790 N
43 80033-01-19-04 2004 Jul 25 23:08:06 53211.963970 Y
44 80033-01-20-02 2004 Jul 26 19:02:46 53212.793590 Y
45 80033-01-21-00 2004 Nov 2 19:19:45 53311.805390 Y
46 f 80033-01-21-02 2004 Nov 3 03:28:32 53312.144810
47 91023-02-02-00 2005 Sep 17 10:26:25 53630.435020 N

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.