Skip to content

Commit 0d0afef

Browse files
authored
Update 2017-10-18-LWAPulsarDataReduction.md
1 parent 273187a commit 0d0afef

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/tutorials/2017-10-18-LWAPulsarDataReduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ A typical LWA pulsar observation results in about 130 files that are useful for
2626
A station of the LWA consists of ~256 dipole antennas each with two polarizations for a total of 512 signals. These signals go into an analog receiver (ARX or ASP) and then into a digital processor (DP) which then sends the data into "Data Recorders" where the signal is written to a set of disks. If there is a slow down in DP or when writing the disks, there can be a break in the data. In order to know whether or not such a break has occurred, the data are recorded in pieces that we call "frames". Each frame has a time tag recorded with it to let us know what time the data corresponds to. If there is a break in the data, we can tell from these time tags and we call these "timetag errors". So, before getting into the rest of the data analysis, it is generally a good idea to check for these timetag errors at the beginning. This can be done using the command:
2727

2828
```sh
29-
$ /home/jdowell/fastDRXCheck.py FILENAME
29+
$ /usr/local/extensions/Commissioning//DRX/fastDRXCheck.py FILENAME
3030
```
3131

3232
It would be useful to look at a case for a good file and for a bad one so that you know what you are looking for. Okay, so first a good file:

0 commit comments

Comments
 (0)