Skip to content

Commit fb7d40f

Browse files
Add files via upload
1 parent b6bf79d commit fb7d40f

File tree

1 file changed

+121
-0
lines changed

1 file changed

+121
-0
lines changed
Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
layout: page
3+
type: tutorial
4+
title: Creating and Scheduling Observation Files
5+
permalink: tutorials/make-observations
6+
---
7+
8+
# Creating and Scheduling Observation Files
9+
10+
### Introduction
11+
12+
Though the LWA Pulsar Archive is full of past observation data that needs to be processed, we will also be creating our own new observations to add to this data collection. When we create our timing solutions, the each observation creates a point on the residuals diagram; by scheduling new observations, we are adding a new and recent data point to the timing solution.
13+
14+
### Creating Observation Files
15+
16+
Follow the regular steps to log onto the LWA computers. Log onto a UCF after validating its availability at [LWAUCF Operations](http://lwalab.phys.unm.edu/CompScreen/cs.php). For example, to log onto **ucf1**, use the **ssh** shortcut:
17+
18+
```sh
19+
$ ucf1
20+
```
21+
22+
We will now create our session definition files for observing. More information can be found at the [LWA observing website](http://www.phys.unm.edu/~lwa/astro/scheds/schedhints.html). Use the shortcut
23+
24+
```sh
25+
$ sessionmaker
26+
```
27+
28+
to replace the command
29+
30+
```sh
31+
/usr/local/extensions/SessionSchedules/sessionGUI.py
32+
```
33+
34+
This pulls up a GUI for creating observation files.
35+
Go to **File** > **New** and fill in the following information:
36+
37+
#####Observer Information#####
38+
ID Number: 55
39+
First Name: Steven
40+
Last Name: Stetzler
41+
#####Project Information#####
42+
ID Code: LS012
43+
Title: <pulsar name>
44+
Comments: none (leave blank)
45+
#####Session Information#####
46+
ID Number: 190_<internal count 1,2,3,..>
47+
Title: <pulsar name>
48+
Comments: none (leave blank)
49+
50+
Session Type - select BEAM FORMING
51+
Data Return Method - select COPY TO UCF
52+
UCF Username: uvastudent
53+
54+
And then click **Ok**
55+
56+
Go to **Observations** > **Add** > **DRX-RA/DEC** and fill in across the row:
57+
Name: <pulsar name>
58+
Target: <pulsar name>
59+
Comments: none
60+
Start: Set the duration to 24h with **24:00:00**, then check **Observations** > **Session At A Glance**
61+
62+
Find the peak of the pulsar using your cursor, then close the window and set the time of the peak to your start time. As for the day, pick a date about 3 days in the future. Observations must be submitted between 2 and 30 days before the scheduled time, so choose a few days in the future if you will be submitting your observations the same day as creating this file. After setting the start time, set the duration to 1 hour with **01:00:00**. Reopen **Session At A Glance**, and the sinusoid should be replaced with an approximately horizontal line. Make slight alterations to the start time if the line has a significant slope.
63+
64+
If you know your pulsar is exceptionally bright, the duration can be shortened to 30 minutes, **00:30:00**. Likewise, if your pulsar is exceptionally dim, set the duration to 2 hours, **02:00:00**.
65+
66+
RA: Retrieve the right ascension from the [Australia Telescope National Facility website](https://www.atnf.csiro.au/people/pulsar/psrcat/) (ATNF Pulsar Catalog). Scroll down to "Pulsar names" and enter your pulsar name, and click "Get Ephemeris." You may think you are getting results for another pulsar, but the catalog simply uses synonyms for the pulsar names given in different epochs. For example, searching for PSR B0655+64 renders results for PSR J0700+6418, but these are the same object. Fill in with the value for "RAJ," where the "J" indicated the J2000 epoch.
67+
68+
DEC: Likewise, retrieve the "DECJ" value from ATNF, making sure to add the "+" or "-" sign.
69+
70+
You will be creating TWO obsevation files, 1 for each tuning, with pairs (35.1, 49.8) MHz and (64.5, 79.2) MHz. All other information is the same, simply change the Session ID number n+1 for the second file.
71+
72+
Tuning 1: **35.1** OR **64.5**
73+
Tuning 2: **49.8** OR **79.2**
74+
75+
Navigate to **Observations** > **Advanced Settings**. Carefully scroll down to DRX-Specific Information. Change BEAM to **1** for your first file and to **2** for the second file. This predetermines the two beams used in by the LWA. When the beam has been chosen, click **Ok**.
76+
77+
Now, you will check that all the information is correct. Navigate to **Observations** > **Validate All**. You should get a pop up: "Congratulations, you have a valid set of observations." Click **Ok** to close the window. If you don't get "Congratulations...", the error description will be displayed in the Terminal window. Make the needed changes until validation succeeds.
78+
79+
Now to save the file, use **File** > **Save As**. Name the file **<date>_<your name>_<pulsar name>_low.sdf** OR **<date>_<your_name>_<pulsar name>_high.sdf** respectively for the two tunings. Be sure to add the **.sdf**, as this is not automatically added as the file type when saved. Before saving, navigate to your directory (**/<computing ID>)in the file folder search bar. Click "Create Folder" and name it "Observations". Open "Observations" and now click **Save**.
80+
81+
Great! You can now check that the SDF (Session Definition File) is in
82+
```sh
83+
/uva_students/<your computing ID>/Observations
84+
```
85+
Now, make the second observation file with all the same information except Session ID Number n+1, higher tunings, BEAM = 2, and file name ** *_high.sdf**. A shortcut to doing this is to open your ** *_low.sdf** file, make the adjustments, and resave it as a new file. This prevents having to reenter the RA/DEC and start times.
86+
87+
Once both files have been saved, navigate to **File** > **Quit** to close the SDF GUI.
88+
89+
### Transferring Files
90+
91+
We will be submitting our SDF files to a LWA website that automatically schedules each valid observation file. However, to upload files from the LWA network, we must save the SDF files on the **lwalab** computer, rather than a **ucf**.
92+
93+
To transfer these files to the local system, exit the **ucf** via
94+
95+
```sh
96+
$ logout
97+
```
98+
99+
Your command line should now read
100+
101+
```sh
102+
uvastudent@lwalab:~$
103+
```
104+
105+
To transfer the files, we will use **scp**, the secure copy command. To use **scp**, input **scp <original location of file(s)> <new location of file(s)>**:
106+
107+
```sh
108+
$ scp uvastudent@lwaucf<#>:/home/uvastudent/uva_students/<your computing ID>/Observations/<date>_<your name>_<pulsar name>_* /home/uvastudent/observation_files/Fall2019
109+
```
110+
111+
Hit return/enter, and you will be prompted for the password to the **ucf**. Enter the password to allow the **scp** to go through.
112+
113+
Inserting the wildcard operator ** * ** into the file address allows for both tuning observations to be copied at once. The file destination ("Fall2019") will vary from year to year.
114+
115+
Success! You can now check that your file is in the right place on the local **lwalab** server.
116+
117+
### Scheduling Observations
118+
119+
To schedule observations, we must upload the files through the remote server. Open the Browser within the X2GO LWA desktop. Go to **http://fornax.phys.unm.edu/lwa/validator/index.html**
120+
121+
Click "Choose File". In the pop-up window, navigate to **uvastudent>observation_files>Fall2019**

0 commit comments

Comments
 (0)