Site Tests

April 2022

April 24: Target Placement

Placed twelve targets in initial locations around the site. Image at right: Blue is where we were thinking of putting them, blue is where they ended up on first pass.

NOTE: Several of the Yellow points changed, see below.

NOTE: Yellow points were from Rolo's phone coordinates and should not be used in analysis.

Map link

April 25: Desert Drone Flight

Test flight outside SPA to confirm systems operations.

Associated data? Probably just GPS and flight plan.

April 26: Source-OFF Drone Flights & GPS Tagging

Targets and tagging

Tagging of all targets as well as position adjustment. File with raw data is "20220426173122_geocoord.csv"

There is a GPS base station and a drone base station. For this survey, we took the coordinates delivered by the drone base station and adjusted them by 223cm? North for the position of the GPS base station which we input manually into the GPS base station setup to unify the drone and GPS coordinate systems. Both base stations were located on top of one of the CLASS containers
- POINT TO RESOLVE: It is unclear where the height of the GPS base station is taken into account, ie unclear if there is a 159.5cm height offset somewhere if this was not taken into account properly. Nominally it was entered into the base station as a correction... (Edit 2023: The height of the antenna entered into the base station is already considered, the measured heigh with the GPS is thus at floor level).
Pt 1, Pt 3, and Pt 8 were moved between drone flights. Notes on which flights will be made below.
CLASS mounts are complicated... but the lower points in the cluster were grabbed at a midpoint on the metal bases. Points on the Az platform were also obtained as well as points on the BS stage on and around the baffles. Need position information from CLASS to properly reference these to a model. (Edit 2022: the CLASS robot model is able to obtain the actual position of the VPM with respect to the measured points - see CLASS_robot.py in the Github)
ACT GS Foundation points were found where the metal met the concrete on the outside of the GS. The avg of all points serves as a fairly accurate central point for ACT. We assumed ~10 m to the center of the ACT beam from this point but a more accurate number needs to be produced. (Edit 2022: the ACT robot model is able to obtain the actual position of the camera with respect to the measure point - see ACT_robot.py in the Github)
PB2 points were grabbed at each of the 3 feet for each of the mounts.
LAT and SAT points were grabbed at many points at the outside of the metal foundation rings as well as a point that appeared to be the marked center of each of the foundations.
Tagged the SO highbay door edges.

GPS Tags

APRIL 26th FLIGHT SUMMARY

Test flights

Primarily to test drone systems and gather data on drone thermal emission. No RF source was on for these tests.

Sequence with rough timing from the cameras, to be refined with GPS data:

Flight 1: 150 GHz source
- Timing: 11:59 start from camera, see associated drone GPS file "FLY300.DAT" starting at 11:52
  1. GPS: TO - 11:59:19, SS - 12:01:34, ES - 12:06:43, TD - 12:09:17
- Camera settings: Video, auto ISO, 1/4000 shutter.
- Original target locations for 1/3/8
- Flight plan: Alt-scan (from GPS info) (Probably alt scan before we added 2 deg correction)
Flight 2: 90 GHz source
- Timing: 13:08 from "FLY301.DAT"
  1. GPS: TO - 13:10:01, SS - 13:12:31, ES - 13:18:08, TD - 13:21:17
- Camera settings: Photo, ISO-100, 1/1000 shutter
- Original target locations for 1/3/8
- Flight plan: Alt-scan (from GPS info)
- NOTE: Camera battery failure (unable to turn on the camera), most likely due to cold weather. Source was left sitting outside for at least 20 min. (Confirm with Gabriele that this was the flight in which this happened)
Flight 3: 150 GHz source
- Timing: 15:20 from "FLY302.DAT"
  1. GPS: TO - 15:24:59, SS - 15:27:19, ES - 15:33:12, TD - 15:35:20
- Camera settings: Video, ISO-125, 1/2000 shutter
- Original target locations for 1/3/8
- Flight plan: Alt-scan (from GPS info)
Flight 4: 90 GHz source
- Timing: 16:54 from "FLY303.DAT"
  1. GPS: TO - 16:56:02, SS - 16:58:09, ES - 17:06:02, TD - 17:07:58 (estimated)
- Camera settings: Photo, ISO-125, 1/2000 shutter
- NEW target locations for 1/3/8
- Flight Plan: Raster type (from GPS info)

April 27: Source-OFF Drone Flights

APRIL 27th FLIGHT SUMMARY

More testing and measurements of thermal emission. I believe we also had four flights on this day and had some camera issues. We attempted to perform back-to-back flights for each source.

Flight 1: 150 GHz source
- Timing: 16:38 UTC from "FLY305.DAT"
  - GPS: TO ~16:41 UTC , SS - 16:43:53, ES - 16:48:44, TD ~16:50 UTC (from flight log)
- Camera settings: Video, ISO-125, 1/3200 shutter
  - C0037 starting at 3:00
  - C0038 ending at 2:20
- Flight plan: Alt-scan (from GPS info)
- NOTE: Source was left mounted on drone until next flight.
- NOTE (2022-09-28): Apparently, CLASS was not taking data during this flight (at least on the 150 GHz camera).
Flight 2: 150 GHz source
- Timing: 13:25 from "FLY306.DAT"
  - GPS: TO - 13:28:54, SS - 13:31:24, ES - 13:37:18, TD - 13:39:33
- Camera settings: Video, ISO-125, shutter 1/3200. CAMERA FAILURE, see C0039 which cuts out just after take off.
- Flight plan: Raster (from GPS info)
- NOTE: Camera failure a few seconds into the flight, most likely related to camera battery getting too cold from remaining outside for 15-20 min until the next flight .
Flight 3: 90 GHz source
- Timing: 13:59 from "FLY307.DAT"
  - GPS: TO - 14:02:32, SS - 14:05:03, ES - 14:11:59, TD - 14:14:17
- Camera settings: Photo, ISO-125, 1/2000 shutter
- Flight plan: Alt-scan (from GPS info)
Flight 4: 90 GHz source
- Timing: 14:47 from "FLY308.DAT"
  - GPS: TO - 14:48:39, SS - 14:50:58, ES - 14:56:12, TD - 14:58:26
- Camera settings: CAMERA FAILURE??? I think this was the other flight that conked out
- Flight plan: Raster (from GPS info)

April 28: Geyser day

No drones!

April 29: Source-ON Flights

ALMA window was 9am to 4pm which we filled with 11 flights.

Flight types:

1. 150 GHz, no chop, alt scan

2. 90 GHz, no chop, alt scan

3. 150 GHz, 47 Hz chop, alt scan

4. 90 GHz, 47 Hz chop, alt scan

5. 150 GHz, 47 Hz chop, rast scan

6. 90 GHz, 47 Hz chop, rast scan

7. 150 GHz, no chop, rast scan

8. 90 GHz, no chop, rast scan

CLASS information:

Mount 1: NW mount with 90 and 40 GHz receivers
Mount 2: SE mount with 150 GHz receiver

PB2a information:

Was either doing CES's or stares with the 90/150 GHz array.

ACT information:

Was performing CES scans continuously. Need parameter info.

Notes:

Takeoff (TO), Start scan (SS), End scan (ES), Touchdown (TD)
In the future, we should ensure schedule file maintains pointing away from ALMA. For these flights the source was pointed towards ALMA before and after the scheduled flight.
Found following checklist worked well for drone systems:
- Power cycle RTK base before heading out to drone launch, confirm light is green
- Power on drone, confirm its RTK goes green
- Power on iPad and bring up DJI app.
- Power on controller
- Power on Gimbal
- Confirm DJI app shows all system go, then open flight path app and load correct flight plan.

APRIL 29th FLIGHT SUMMARY

**Mount 1: 40 / 90 GHz arrays, Mount 2: 150 / 220 GHz arrays

FLIGHT LOGS

Flight 1: Type 1 ( 150 GHz, no chop, alt scan)

- Timing (CLT): TO - 9:25:12, SS - 9:27:42, ES - 9:32:37, TD - 9:35 (camera times, treat with skepticism)
  - GPS: TO - 9:20:05, SS - 9:22:25, ES - 9:27:30, TD - 9:30:00
- GPS: "FLY310.DAT" - I think
- Camera settings: Video, ISO 125, shutter 1/3200
  - C0040: Start at 3:00
  - C0041: End at 2:11
- Flight plan: altscan_20220427_CLASS_9deg_41alt_dh-2
- Telescopes:
  - CLASS - CES range? 90 GHz mount was at BS 0 deg and 150 GHz mount was at BS 30 deg
    - Mount 1: From notes, Az 176, El 45
    - Mount 2: From notes, Az 182, El 49.5
  - PB2a: Az 189.5, El 27.9? CES, 10 deg width
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 1
- Source output power: ~ -18 dBm

Flight 2: Type 2 (90 GHz, no chop, alt scan)

- Timing: TO - , SS - , ES - , TD -10:10???
  - GPS: TO - 10:02:12, SS - 10:04:41, ES - 10:10:43, TD - 10:13:01
- GPS: "FLY312.DAT"
- Camera settings:
- Flight plan: altscan_20220427_CLASS_9deg_41alt
- Telescopes:
  - CLASS - CES's, CES range? One was at BS 0 deg and another at BS 30 deg from recollection
    - Mount 1: From notes, Az 176, El 45
    - Mount 2: From notes, Az 182, El 49.5
  - PB2a: Az 189.5, El 27.9? CES, 10 deg width
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 3

Flight 3: Type 1 ( 150 GHz, no chop, alt scan)

- Timing: TO - 10:57:00, SS - 10:59:27, ES - 11:03:44, TD - 11:06:00 (from camera, treat with skepticism)
  - GPS: TO - 10:51:52, SS - 10:54:12, ES - 10:59:20, TD - 11:01:36
- GPS: "FLY313.DAT"
- Camera settings: Video, ISO 125, shutter 1/3200
  - C0042: Start 3:15
  - C0043: End 2:30
- Flight plan: altscan_20220427_CLASS_9deg_41alt_dh-2
- Telescopes:
  - CLASS - CES's with updated parameters. CES range?
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: Last minute change to look at a particular array with the 90 GHz, change cords to BS -45, Az 192, El 43
  - PB2a: Az 189.5, El 27.9? CES, 10 deg width
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 2, 14% remaining on landing
- Source output power: -18 dBm

Flight 4: Type 2 (90 GHz, no chop, alt scan)

- Timing: TO - , SS - , ES - , TD - 11:30
  - GPS: TO - 11:19:25, SS - 11:21:44, ES - 11:26:50, TD - 11:29:11
- GPS: "FLY314.DAT"
- Camera settings:
- Flight plan: altscan_20220427_CLASS_9deg_41alt
- Telescopes:
  - CLASS - CES's CES range?
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: BS -45, Az 192, El 43
  - PB2a: Az 189.5, El 27.9? CES, 10 deg width
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 1, landed with 12%

Flight 5: Type 3 (150 GHz, 47 Hz chop, alt scan)

- Timing: TO - 12:18:20, SS - 12:20:50, ES - ~12:25:30, 90 sec hold station, TD - 12:24:30 (camera timing, clearly some issue there)
  - GPS: TO - 12:13:17, SS - 12:15:36, ES - 12:22:04, TD - 12:24:13
- GPS: "FLY315.DAT"
- Camera settings: Video, ISO 125, shutter 1/3200
  - C0044: 3:30 start, HOWEVER, side two targets only visible 3:50 onwards, maybe flight plan was incorrect?
  - C0045: ~2:30 scan ends, then hold station until 4:06
  - C0046: Only landing
- Flight plan: altscan_20220427_CLASS_9deg_41alt_dh-2
- Telescopes:
  - CLASS - CES's CES range?
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: BS -45, Az 192, El 43
  - PB2a: Az 189.5, El 27.9? CES, 10 deg width
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 3, landed with 30%
- Source output power: ~ -18 dBm
- NOTE: Source potentially off by minute 4 after take off.

Flight 6: Type 4 (90 GHz, 47 Hz chop, alt scan)

- Timing: TO - 12:52 , SS - 12:55, ES - , TD - 13:02
  - GPS: TO - 12:51:54, SS - 12:54:13, ES - 12:59:04, TD - 13:01:18
- GPS: "FLY316.DAT"
- Camera settings:
- Flight plan: altscan_20220427_CLASS_9deg_41alt
- Telescopes:
  - CLASS - CES's CES range?
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: BS -45, Az 192, El 43
  - PB2a: Az 189.5, El 27.9? CES, 10 deg width
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 2, landed with 13%

Flight 7: Type 5 (150 GHz, 47 Hz chop, rast scan)

- Timing: TO - 13:37, SS - 13:41, ES - , TD - 13:48
  - GPS: TO - 13:37:11, SS - 13:39:41, ES - 13:45:08, TD - 13:47:37
- GPS: "FLY317.DAT"
- Camera settings: Video, ISO 125, shutter 1/4000
- Flight plan: gridscan_20220427_CLASS_2x2deg_41alt_dh-2
- Telescopes:
  - CLASS - Stare
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: BS -45, Az 192, El 43
  - PB2a: Stare at Az 189.5, El 27.9?
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 1, landed with 15%
- Source output power: unintentionally set to ~ -8 dBm (instead of -18 dBm)
- NOTE: Weather became cloudy during this flight & source was off on landing.

Flight 8: Type 6 (90 GHz, 47 Hz chop, rast scan)

- Timing: TO - , SS - , ES - , TD - 14:25
  - GPS: TO - 14:12:41, SS - 14:15:11, ES - 14:22:12, TD - 14:24:31
- GPS: "FLY318.DAT"
- Camera settings:
- Flight plan: gridscan_20220427_CLASS_2x2deg_41alt
- Telescopes:
  - CLASS - Stare
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: BS -45, Az 192, El 43
  - PB2a: Stare at Az 189.5, El 27.9?
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 3, landed with ??

Flight 9: Type 7 ( 150 GHz, no chop, rast scan)

- Timing: TO - 14:50, SS - 14:53, ES - , TD - 15:00
  - GPS: TO - 14:49:11, SS - 14:51:41, ES - 14:56:55, TD - 14:59:20
- GPS: "FLY320.DAT"
- Camera settings: Video, ISO 125, shutter 1/5000
- Flight plan: gridscan_20220427_CLASS_2x2deg_41alt_dh-2
- Telescopes:
  - CLASS - Stare
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: BS -45, Az 192, El 43
  - PB2a: Stare at Az 189.5, El 27.9?
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 2, landed with 14%
- Source output power: ~ -18 dBm

Flight 10: Type 8 ( 90 GHz, no chop, rast scan)

- Timing: TO - 15:28, SS - 15:30, ES - , TD - 15:37
  - GPS: TO - 15:26:38, SS - 15:29:08, ES - 15:33:43, TD - 15;35:58
- GPS: "FLY321.DAT"
- Camera settings:
- Flight plan: gridscan_20220427_CLASS_2x2deg_41alt
- Telescopes:
  - CLASS - Stare
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: BS -45, Az 192, El 43
  - PB2a: Stare at Az 189.5, El 27.9?
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 1, landed with 14%

Flight 11: Type 3 (150 GHz, 47 Hz chop, alt scan)

- Timing: TO - 15:31, SS - 15:54, ES - , Hold station for ~30 sec, TD - 16:03
  - GPS: TO - 15:51:10, SS - 15:53:29, ES - 16:00:01, TD - 16:02:17
- GPS: "FLY322.DAT"
- Camera settings: Video, ISO 125, shutter 1/4000
- Flight plan: altscan_20220427_CLASS_9deg_41alt_dh-2
- Telescopes:
  - CLASS - CES's CES range?
    - Mount 1: BS -45, Az 176, El 45
    - Mount 2: BS -45, Az 192, El 43
  - PB2a: Az 189.5, El 27.9, CES, 10 deg width
  - ACT: el=32, az=173.27 +/- 2.5
- Batteries: Set 3, landed with 28%
- Source output power: ~ -18 dBm
- Source on during the whole flight | chopping extensively tested just before flying

Page updated

Report abuse