Rebuild site

deployment/canada_deployments.csv

@@ -49,8 +49,8 @@ Argo Canada,Blair Greenan,BIO,OPERATIONAL,PROVOR,PROVOR_CTS4,2024-04-12T20:42:00
 Argo Canada,Blair Greenan,BIO,OPERATIONAL,PROVOR,PROVOR_CTS4,2024-04-27T21:23:00,43.4721,-57.5224,TELEOST,300125010915300,4902676,P41305-23CA003
 Argo Canada,Blair Greenan,BIO,OPERATIONAL,PROVOR,PROVOR_CTS4,2024-06-06T00:33:00,59.5045,-55.0209,CAPT. JACQUES CARTIER,300125010915310,4902675,P41305-23CA002
 Argo Canada,Blair Greenan,BIO,OPERATIONAL,PROVOR,PROVOR_CTS4,2024-06-06T00:35:00,59.5044,-55.0210,CAPT. JACQUES CARTIER,300125010917310,4902677,P41305-23CA004
-Argo Canada,Blair Greenan,IOS,CONFIRMED,ARVOR,ARVOR_SBE,2024-10-01T00:00:00,72.75,-136,LOUIS S. ST. LAURENT,300534063793390,4902666,AI2600-23CA010
-Argo Canada,Blair Greenan,IOS,CONFIRMED,ARVOR,ARVOR_SBE,2024-10-03T00:00:00,73,-150,LOUIS S. ST. LAURENT,300534060213390,4902565,AI2600-21CA006
+Argo Canada,Blair Greenan,IOS,OPERATIONAL,ARVOR,ARVOR_RBR,2024-09-19T02:37:00,73.0009,-139.9953,LOUIS S. ST. LAURENT,300534061174520,4902558,AI3500-21CA003
+Argo Canada,Blair Greenan,IOS,OPERATIONAL,ARVOR,ARVOR_SBE,2024-09-18T15:30:00,72.5983,-144.7050,LOUIS S. ST. LAURENT,300534060213390,4902565,AI2600-21CA006
 Argo Canada,Blair Greenan,SAEON,OPERATIONAL,ARVOR,ARVOR_SBE,2024-04-17T12:00:00,-39.4982,25.9525,AGULHAS II,300534063895250,4902654,AI2600-23CA005
 Argo Canada,Blair Greenan,SAEON,OPERATIONAL,ARVOR,ARVOR_SBE,2024-04-18T14:01:00,-43.4986,32.3057,AGULHAS II,300534063998880,4902657,AI2600-23CA002
 Argo ONC,Kohen Bauer,ONC,OPERATIONAL,Deep ARVOR,ARVOR_D,2024-09-09T10:15:00,48.2536,-154.9950,SIR WILFRID LAURIER,300534063708190,4902640,AD2700-23CA008

notes/notes.json

@@ -13,7 +13,7 @@
     "categories": [],
     "contents": "\nMeeting Notes\nEffort to standardize the Argo mission\nDiscussion surrounding the technical details of standardizing the Argo mission, including cycle timing (not equal exactly 10 days) and park depth sampling (hourly T/P, 6-hour S). More experienced user groups will still set up their floats as they see fit. The goal is not to control how these type of groups program their floats, but to ensure smaller users that may not change the floats from their default configuration have an Argo mission compliant setup.\nAlso, Argo Canada’s sampling is not very typical of the array - we chose a setup that maximized the number of 1 dbar bins within our Iridium plan. 2 dbar bins throughout the water column is more common (CSIRO, Ifremer) or at least to 1000 dbar (UW), with 1 dbar bins only at the very surface. Our current setup returns just under 675 points (18-22 sbd messages, ~6kB). Moving to 1/2/10 with 20/1000 depth thresholds would result in 610 points. Our current park sample strategy is the NKE default, 12 hours, with some exceptions (Dal PROVORs sampling hourly).\nConnection with TWR\nConnecting with TWR staff was a helpful part of the week including getting some hands on experience with APEX floats. Pre-deployment testing will be similar, though there are some differences in deployment. General notes:\nshipped in IDLE (pressure activation) mode\nwork with floats though terminal emulator as before, but physical connection rather than bluetooth\nbased on physical connection, could have a much easier shipboard setup to test floats (ex. dedicated laptop, macro to run test, teraterm always open and active); unsure if TWR supplies necessary connection?\ncan fill bottom of the float (? there is a word for this) using a bucket to encourage faster sinking\nTWR developing in house tool for production testing that they want to eventually have users access - opportunity to be beta users\nTWR will contact us for RUDICS activation\nLarge amount of onboard storage, all test information, pressure inquiries in IDLE mode stored\nWill need to provide rough deployment regions before order is complete, floats need to be specifically ballasted\nChanges to Pre-deployment Routine\nAn emphasis on dockside testing was made, to (1) ensure problems do not arise in transport to a ship and (2) this also minimizes startup time as the GPS almanac will update. Typically we have testing within 1-2 months of a float going on a ship, but I would like to move that up to at least test the week of.\nSharing Raw Files w/ Manufacturers\nStrong recommendation to share raw data with float manufacturers so that they have access to the engineering data when helping address issues. Easy with SBD (add manufacturer email address to distribution list) but slightly more complicated with RUDICS. Will work with TWR to ensure they have access to RUDICS data (mirror on their server perhaps?). Does NKE already have access to the general RUDICS server? Do we need to revoke that?\nData Stream - upcoming new sensor on Dal float\nDalhousie is purchasing a PROVOR CTS5 that will be equipped with an RBR Tridente sensor instead of the SBS FLBB sensor. Data format coming from the float should be very similar, maybe different naming structure, but also may be differences in QC, processing, etc. Something to keep in mind.\nPolar Deployments\nTalked with Noe about deployments near ice - they will often let the float start its mission on deck (start to try to sink) in order to have the float sink faster and therefore reduce chance of hitting ice.\nNext Generation ARVOR\nNKE presented the next generation of ARVOR float. Hardware/structure is very similar, but software/firmware will have major upgrades and will address some of our complaints/issues from the past. Available 2025.\nFuture of Argo Tech\nArgo Tech plans to host quarterly virtual meetings and bi-annual in-person meetings. Next in person meeting September 2026 (WHOI?).\nNext two meetings will tentatively discuss float profiling, timing, parking, and the report to be made to the AST.\nAction Items\nA meeting report is being produced, however some action items are more relevant to Argo Canada than others. Those are listed here. Note that at the time of writing this the action items are still subject to change.\nData capture on pre-deployment testing: use binary or numerical scale to represent the level of pre-deployment dockside testing performed on a float.\nThis will encourage testing and allow for analysis of float failures in context of knowing the float was in working order as close to deployment as possible. Data capture methodology to be determined. Meta file may be a good place to store this data, however Argo Tech recognizes the challenges associated with additions to the data system.\nImproved sharing of post-deployment logs with vendors.\nTransmitted data and engineering log info should be sent to vendors so that they may monitor float performance as well. For SBD, simply add the preferred vendor email to the distribution list. For floats on RUDICS communication, collaborate with vendors to arrange appropriate access.\nArgo Tech asks for support as needed from AST/ADMT as DACs may need to facilitate.\nArgo Tech asks vendors to review and analyze data as it is submitted.\nEnhance understanding of float failure modes.\nLarger user groups should track float failures and present analysis at bi-annual Argo Tech meetings and/or updates at quarterly virtual meetings (see SIO failure analysis presentation as an example). Any systematic failures should be communicated to the vendors and the Argo Tech group to prevent deployment of compromised floats.\nImprove fault identification and record-keeping.\nThis action item is a call for improved record keeping prior to float deployment. This includes logging all interactions with the float, for example using date-stamped terminal logs. In addition, any problems discovered during float testing/ballasting/assembly should be formally recorded by the end user and shared with the vendor, even in cases where the problem can be fixed without any required RMA or similar action from vendors. WHOI maintains a github for this type of information, which is a good example to follow.\nUser groups will use ticketing systems provided by vendors for all float issues.\nUser groups, especially those with close relationships with float vendors or sensor manufacturers, will often bypass the typical customer service portals these companies have in place in favor of direct contact with a representative they may have a personal relationship with. Bypassing these types of ticketing systems however can lead to issues not being properly tracked internally by the vendors.\nUser groups should be motivated to use these ticketing systems as it is the best way for vendors to track issues, and make changes to their products based on that information. It is a way for both end users and vendors to contribute to the progress/reliability of a given float/sensor.\n\n\n\n",
     "preview": {},
-    "last_modified": "2024-09-19T20:40:43+00:00",
+    "last_modified": "2024-09-20T13:56:13+00:00",
     "input_file": {}
   },
   {
@@ -30,7 +30,7 @@
     "categories": [],
     "contents": "\nChris’ notes before the meeting are in regular text. Notes taken during the meeting are in italics.\nRecent Deployments\nRecent deployments (since May 1) include 5 floats in the Lab Sea (3 Dal CTS5, 2 BIO CTS4), 1 float deployed from the sailing vessel Oceanolog (read more here), and 2 floats deployed along line P (1 deep ARVOR, 1 CTS4 w/ Nitrate).\nGoing a little further back, in April 4 floats were deployed, 2 on the AZMP (BIO CTS4) and 2 southeast of South Africa (ARVOR).\nDal floats: profiled daily while ship was in the area, now on 5-day cycles. Parking at 2000m to use as a pseudo-sediment trap via the BBP parking hook (see here for an example)\nNitrate float (4902679) is not on GDAC yet (Nitrate processing in progress), profiling daily?\n\n\nProgram\nInstitute\nModel\nDate\nLatitude\nLongitude\nShip\nIMEI\nWMO\nSerial No.\nArgo Canada\nIOS\nPROVOR\n04 May, 2024\n49.2800\n-134.6700\nJOHN P. TULLY\n300125010116590\n4902679\nP44168-23CA001\nArgo ONC\nONC\nDeep ARVOR\n07 May, 2024\n49.8361\n-144.6701\nJOHN P. TULLY\n300534063507930\n4902631\nAD2700-22CA001\nArgo Dalhousie\nDal\nPROVOR\n13 May, 2024\n56.5010\n-52.5990\nCELTIC EXPLORER\n300125062423120\n4902686\nP53865-23CA003\nArgo Canada\nBIO\nARVOR\n16 May, 2024\n17.9857\n-65.0987\nOCEANOLOG\n300534062474370\n4902609\nAI2600-22CA007\nArgo Dalhousie\nDal\nPROVOR\n17 May, 2024\n56.6650\n-48.9770\nCELTIC EXPLORER\n300125062031400\n4902687\nP53865-23CA004\nArgo Dalhousie\nDal\nPROVOR\n22 May, 2024\n58.4275\n-49.4418\nCELTIC EXPLORER\n300125062035430\n4902688\nP53865-23CA005\nArgo Canada\nBIO\nPROVOR\n06 Jun, 2024\n59.5045\n-55.0209\nCAPT. JACQUES CARTIER\n300125010915310\n4902675\nP41305-23CA002\nArgo Canada\nBIO\nPROVOR\n06 Jun, 2024\n59.5044\n-55.0210\nCAPT. JACQUES CARTIER\n300125010917310\n4902677\nP41305-23CA004\n\nArctic & Antarctic Floats\n\nWMO\nBasin\nDeployment Date\nLast Cycle\nLast Cycle Date\n4902610\nBeaufort Sea\nSep 19, 2023\n29\nJun 21, 2024\n4902611\nBeaufort Sea\nOct 03, 2023\n25\nMay 27, 2024\n4902664\nRoss Sea\nFeb 07, 2024\n11\nFeb 28, 2024\n4902665\nRoss Sea\nJan 30, 2024\n1\nJan 31, 2024\n4902667\nRoss Sea\nFeb 07, 2024\n20\nMar 21, 2024\n4902668\nRoss Sea\nFeb 03, 2024\n8\nMar 02, 2024\n4902669\nRoss Sea\nFeb 07, 2024\n11\nFeb 28, 2024\n\nBeaufort:\nBoth Beaufort Sea floats have resurfaced! 4902610 not on GDAC yet.\nISA does not seem to have prevented floats from approaching/bumping into the ice\nLost some data - ex. 4902611 did 3 cycles before going under ice, but newly sent data starts at cycle 13: reduce vertical resolution before next season?\nRoss:\nMost floats have not reported since near deployment time, but 4902664 just reported on June 16, not on GDAC yet\n\n\n\nNitrate\nWriting of Nitrate RTQC code is in progress. Official documentation is here. RTQC for Nitrate includes:\nglobal range test\nspike test\nstuck value test\ngrey list test\nnitrate specific tests\nSpecific tests include checking for saturation of the spectrophotometer, absorbance at 240nm (evaluate sensor optics) and error fitting to a model. There is also a check for high bisulfide concentrations such as in the black sea, but these are special cases and likely only going to be evaluated by expert researchers.\nLike oxygen, unadjusted nitrate is flagged as 3 by default. If TEMP_QC is 4, NITRATE_QC is also 4, and if PSAL_QC is 4, NITRATE_QC should be 3 as well, including for adjusted, but this can be reviewed at the DMQC step.\nNear Surface Sampling\nAt the most recent AST Brian King presented on an evaluation of Argo floats sampling all the way to the surface. The defauly configuration of the CTD pump for NKE floats is to turn off the pump at 5dbar. I am in the process of changing this parameter to 2dbar for all floats and will use as the default going forward.\n\n\n\n",
     "preview": {},
-    "last_modified": "2024-09-19T20:40:43+00:00",
+    "last_modified": "2024-09-20T13:56:13+00:00",
     "input_file": {}
   },
   {
@@ -47,7 +47,7 @@
     "categories": [],
     "contents": "\n\n\n\nUpdate/Takeaways from ADMT\nCHLA_ADJUSTED: Raphaelle Suazede presented on adjusting chlorophyll using a factor from a lookup table (date, location) or calculated based on first 5 cycles. Current process is to divide by 2 for all data (Roesler 2017). Simple to implement in python RTQC once we have LUT.\nRT adjustment of DOXY is a high priority. Can provide a gain value after 5 cycles, and populate DOXY_ADJUSTED in RT at python RTQC step. Chris needs to talk to Anh about this - new VMS variable and populating SCIENTIFIC_CALIB_COMMENT.\nCycle Timing\nCanadian floats are almost all compliant with time of day sampling. Only floats that appeared in Drucker/Riser audit list were NOVA, deep ARVOR floats and 2 very recently deployed ARVORs that have been reprogrammed to 235hr cycles already.\n\n\n\n\n\n\nDiscussion on indicating time of day sampling regime in the meta file by John Gilson via CONFIG_MISSION_COMMENT. Not totally clear to me but I think we are meant to set it to -1 (i.e. TOD sampling off?).\nPresented our method for actively reprogramming PROVOR floats to effectively result in 235 hour cycles.\n\n\n\nPROVOR CTS5 floats: the new floats will require new syntax to reprogram, and also carry radiometry sensors. Plan will be to cycle through 24hr cycle plus extra local noon surfacings through the year.\n\n\n\nRTQC Of PROVOR CTS5 Floats\nNeed to add radiometry RTQC to python setup - just range test, very simple\nDMQC Updates\n4 floats ready for submission, going to do a couple more and submit as a batch\nMaking an effort to do 1-2/week right now\nWill need to spend some time validating in-air method in code\nUpon DMQC, updating DOXY_QC=1 to DOXY_QC=3. Should we do that for all files more urgently?\nDeployment Summary\nAll completed and planned deployments can be seen on the development blog planning page.\nSo far in 2023, 24 floats have been deployed:\n5 PROVOR / 14 ARVOR / 5 deep ARVOR\n11 BIO / 8 IOS / 5 ONC\n3 RBR / 21 SBE\nIn the remainder of 2023 and into early 2024, 13 more deployments are planned:\n2 PROVOR CTS5 / 9 ARVOR / 3 deep ARVOR\n7 BIO / 2 IOS / 2 ONC / 2 Dalhousie\n4 RBR / 9 SBE\nNotable deployments:\nThe crew of the DISCOVREY will be deploying 6 floats on their way to Cape Town, South Africa.\nAn additional 6 floats (not in table) will be delivered to a vessel in Cape Town via the DISCOVERY for deployment in the Western Indian Ocean, date TBD.\nThe HMCS VANCOUVER will deploy 2 floats near Hawaii\nThe 2 PROVOR CTS5 floats will be deployed in the Lab Sea from the MERIAN, being loaded on November 21.\nThe sailing vessel OCEANOLOG will deploy an ARVOR float as part of Sail for Science\n2 deep ARVOR floats will be deployed from the HESPERIDES in the Southern Ocean (more floats to avoid ice!)\nAn additional 5 floats (not in the table) will be sent on a joint Italian/NZ voyage to the Ross Sea\nBeaufort Floats\nFloat Programming\nThe two floats deployed in the Beaufort Sea (4902610 and 4902611) were updated with new ice sensing algorithm (ISA) parameters. The parameters were provided by Steve Jayne based on data analysis of the Beaufort Gyre.\nISA works by detecting a temperature threshold over a certain depth range. The suggested range was between 20-10dbar with a threshold of -1.21deg C (90% success rate of avoiding ice when present) or -1.03 deg C (95% success rate).\nI ran the parameter change by Jerome at NKE. He was cautious about it as the depth range Steve provided was more shallow than their default setting (-1.79 deg C between 50 and 20dbar), but that the changes looked fine in terms of reprogramming the float:\n!MC 2 235    # cycle timing\n!MC 3 235    # cycle timing phase 2, inaccessible\n!MC 17 475   # surface/mid threshold \n!MC 18 1000  # mid/bottom threshold\n!MC 20 5     # mid resolution\n!MC 21 10    # bottom resolution\n!IC 2 3      # number of detections to confirm ice, default\n!IC 3 20     # start pressure detection\n!IC 4 10     # stop pressure detection\n!IC 5 -1210  # temperature threshold, millidegrees\nBoth floats successfully received the parameter change, but I cannot see ice parameter values in the messages. May consult NKE on this.\nPreliminary Data\nFloat 4902610 collected 2 profiles before stopping reporting (last Oct 1, 2023). Float 4902611 has collected 3 (last reported Oct 25, 2023).\n\n\n\n\n\n\n\n\n\n\n\n\n",
     "preview": {},
-    "last_modified": "2024-09-19T20:40:43+00:00",
+    "last_modified": "2024-09-20T13:56:13+00:00",
     "input_file": {}
   }
 ]