You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/orbital/satellite-imagery-with-orbital-ground-station.md
+70-64Lines changed: 70 additions & 64 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ In this tutorial, we will follow these steps to collect and process Aqua data:
24
24
> *[Process Aqua direct broadcast data using RT-STPS](#step-2-process-aqua-direct-broadcast-data-using-rt-stps).
25
25
> *[Create higher level products using IPOPP](#step-3-create-higher-level-products-using-ipopp).
26
26
27
-
Optional setup steps for capturing the ground station telemetry are included in the [Appendix](#appendix).
27
+
Optional setup steps for capturing the ground station telemetry are included the guide on [receiving real-time telemetry from the ground stations](receive-real-time-telemetry.md).
28
28
29
29
## Step 1: Schedule a contact and collect Aqua direct broadcast data using AOGS
30
30
@@ -107,65 +107,75 @@ In the steps below, you'll process the Level-0 data generated in the previous st
107
107
> [!NOTE]
108
108
> Due to potential resource contention, DRL recommends installing RT-STPS and IPOPP on separate machines. But for this tutorial, we install both on the our receiver-vm because we don't run them at the same time. For production workloads, please follow sizing and isolation recommendations in the user guides available on the DRL website.
109
109
110
-
### Attach a data disk to the receiver-vm
110
+
### Increase OS disk size on the receiver-vm
111
111
112
-
IPOPP installation and subsequent generation of products requires more disk space and I/O throughput than what is available on the receiver-vm by default.
113
-
To provide more disk space and throughput, attach a 1TB premium data disk to the receiver-vm by following steps in [Attach a data disk to a Linux VM](../virtual-machines/linux/attach-disk-portal.md)
112
+
IPOPP installation and subsequent generation of products requires more disk space than what is available on an Azure VM by default.
114
113
115
-
### Create a file system on the data disk
114
+
Follow the steps below to increase the size of the OS disk on the ```receiver-vm``` to 1TB.
1. On the **Disk** pane, navigate to **Size + performance** page.
123
+
1. Select **Premium SSD(locally redundant storage)** from the **Disk SKU** dropdown.
124
+
1. Select the **P30** Disk Tier (1024GB).
125
+
1. Select **Save**.
126
+
1. Navigate back to **Virtual Machine** pane.
127
+
1. On the **Overview** page, select **Start**
128
+
129
+
On the receiver-vm, verify that the root partition now has 1TB available
130
+
131
+
```bash
132
+
lsblk -o NAME,HCTL,SIZE,MOUNTPOINT
125
133
```
126
-
> [!NOTE]
127
-
> To ensure that the datadrive is mounted automatically after every reboot, please refer to [Attach a data disk to a Linux VM](../virtual-machines/linux/attach-disk-portal.md#mount-the-disk) for instructions on how to add an entry to ```/etc/fstab```
134
+
This should show ~1TB allocated to the root ```/``` mountpoint.
128
135
136
+
```console
137
+
NAME HCTL SIZE MOUNTPOINT
138
+
sda 0:0:0:0 1T
139
+
├─sda1 500M /boot
140
+
├─sda2 1023G /
141
+
├─sda14 4M
142
+
└─sda15 495M /boot/efi
143
+
```
129
144
130
145
### Install Desktop and VNC Server
131
146
132
147
IPOPP installation requires using a browser to sign on to the DRL website to download the installation script. This script must be run from the same host that it was downloaded to. The subsequent IPOPP configuration also requires a GUI. Therefore, we install a full desktop and a vnc server to enable running GUI applications on the receiver-vm.
133
148
134
-
```console
149
+
```bash
135
150
sudo yum install tigervnc-server
136
151
sudo yum groups install "GNOME Desktop"
137
152
```
138
153
139
154
Start VNC server:
140
155
141
-
```console
156
+
```bash
142
157
vncsever
143
158
```
144
159
Enter a password when prompted.
145
160
146
161
Port forward the vncserver port (5901) over ssh:
147
162
148
-
```console
163
+
```bash
149
164
ssh -L 5901:localhost:5901 azureuser@receiver-vm
150
165
```
151
166
152
167
Download the [TightVNC](https://www.tightvnc.com/download.php) viewer and connect to ```localhost:5901``` and enter the vncserver password entered in the previous step. You should see the GNOME desktop running on the VM.
153
168
154
169
Start a new terminal, and start the Firefox browser
155
170
156
-
```console
171
+
```bash
157
172
firefox
158
173
```
159
174
160
175
[Log on the DRL website](https://directreadout.sci.gsfc.nasa.gov/loginDRL.cfm?cid=320&type=software) and download the downloader script.
161
176
162
-
Run the downloader script from the ```/datadrive/ipopp``` directory because
163
-
the home directory isn't large enough to hold the downloaded content.
Before we can create Level-1 and Level-2 products from the Level-0 PDS files generated by rt-stps, we need to configure IPOPP. IPOPP must be configured with its dashboard GUI. To start the dashboard, first port forward the vncserver port (5901) over ssh:
210
+
The above steps start IPOPP services with the default configuration. IPOPP services must be configured using the dashboard GUI.
204
211
205
-
```console
212
+
To start the dashboard, first port forward the vncserver port (5901) over ssh:
213
+
214
+
```bash
206
215
ssh -L 5901:localhost:5901 azureuser@receiver-vm
207
216
```
208
217
209
-
Using the TightVNC client, connect to localhost:5901 and enter the vncserver password. On the virtual machine desktop, open a new terminal and start the dashboard:
218
+
Using the TightVNC client, connect to localhost:5901 and enter the vncserver password that you previously set.
210
219
211
-
```console
212
-
cd /datadrive/ipopp
213
-
./drl/tools/dashboard.sh &
220
+
On the virtual machine desktop, open a new terminal and start the dashboard:
221
+
222
+
```bash
223
+
cd~/drl/tools
224
+
./dashboard.sh
214
225
```
226
+
Configure services:
215
227
216
-
1. IPOPP Dashboard starts in process monitoring mode. Switch to **Configuration Mode** by using the menu option.
228
+
1. IPOPP dashboard starts in process monitoring mode. Switch to **Configuration Mode** by using the menu option.
217
229
218
-
2. Aqua related products can be configured from EOS tab in configuration mode. Disable all other tabs. We're interested in the MODIS Aerosol L2 (MOD04) product, which is produced by IMAPP SPA. Therefore, enable the following in the **EOS** tab:
230
+
1. Aqua related products can be configured from **EOS** tab in configuration mode. Disable all other tabs. We're interested in the MODIS Aerosol L2 (MOD04) product, which is produced by IMAPP SPA. Therefore, enable the following in the **EOS** tab:
219
231
220
232
- gbad
221
233
@@ -225,46 +237,40 @@ cd /datadrive/ipopp
225
237
226
238
- IMAPP
227
239
228
-
3. After updating the configuration, switch back to **Process Monitoring** mode using the menu. All tiles will be in OFF mode initially.
240
+
1. After updating the configuration, switch back to **Process Monitoring** mode using the menu. All tiles will be in OFF mode initially.
229
241
230
-
4. When prompted, save changes to the configuration.
242
+
1. When prompted, save changes to the configuration.
231
243
232
-
5. Click **Start Services** in the action menu. Note that **Start Services** is only enabled in process monitoring mode.
244
+
1. Click **Start Services** in the action menu. Note that **Start Services** is only enabled in process monitoring mode.
233
245
234
-
6. Click **Check IPOPP Services** in action menu to validate.
246
+
1. Click **Check IPOPP Services** in action menu to validate.
235
247
236
248
## Ingest data for processing
237
249
238
-
Copy the Level-0 PDS files generated by RT-STPS to the IPOPP ingest directory for further processing.
250
+
Copy the PDS files generated by RT-STPS to the IPOPP ingest directory for further processing.
Follow steps here to [receive real-time telemetry from the ground stations](receive-real-time-telemetry.md).
267
-
268
274
## Next steps
269
275
270
276
For an end-to-end implementation that involves extracting, loading, transforming, and analyzing spaceborne data by using geospatial libraries and AI models with Azure Synapse Analytics, see:
0 commit comments