Multiple deployments for FREEBYRD amlr01 2019-20

[smwoodman]

@acossio @Kourtney-Burger in the database, there are deployments for both amlr01-20191206 and amlr01-20191216. I believe this is because the glider was put in the water on the 6th, recovered because of an issue, and redeployed on the 16th. We need to decide which deployment name to use, or how to handle this

The glider did at least a few dives on the 6th; I would have to go back and look for how long it was 'deployed'. We can either leave the deployment date as the 6th and add in a comment to the deployment metadata explaining the gap, or use the 16th, and ignore all data prior to the 16th. At first thought, I'm ok with either

[acossio]

TLDR: We can probably just go with 20191216.

If I remember correctly, this glider started power cycling for no reason. It was recovered and Christian and Randy worked on it at Palmer station and was able to tweak some wiring so that it wouldn't power cycle. I think it was deployed on the 6th and recovered on the 10th. With the old netcdf files, I can't tell easily how many profiles were done and I haven't gone back into the pilot log notes yet.
Looking back at the data, it looks like we didn't get far before we recovered the glider. Also, it looks like I didn't process the acoustic data before December 16, 2019. This dive into the data also made me realize that GCP doesn't have all the acoustic data for this deployment, just the first part of the deployment that had to be recovered. I'll try and upload that shortly.