...
Expedition 383 began and ended in Punta Arenas, Chile. Elisabetta Olivo, Ionela Samolia and Skyler Jordan worked as temporary technician in the core lab and the Paleomag lab. Operations included only APC/HAPC, XCB coring. Major differences to regular sediment expeditions were: 1) expansion of cores due to gas which produced an unusual high amount of shattered liners and liner patch usage as well as 2) a trial of a "speedy workflow" to prevent the expansion in the lab (once sections were caped). For details, see PP and CORE LAB report.
AMS/Inventory/Shipping:
A warehouse in Punta Arenas contains 120 D-Tube boxes. At the end of 379T port call, all must be onboard or shipped back to College Station. Brad Julson and ALOs/LO on 379T will determine how much excess bulk, not needed on 379T, will be shipped. In AMS we entered an approximate amount and D-Tubes and Core Boxes to be shipped home, so the shipping paper work will contain the bulk items. This may have to be modified based on actual shipment.
- Single World Courier shipment forms can be completely generated automatically in AMS (WC Job # can be added, see Fig. 1). If a person has a frozen and refrigerated shipment, the combined document can’t be generated in AMS. Recommend we do one pallet per scientist, with multiple parcels either frozen or refrigerated.
- From 375 tech report: Per Mitch Malone, core lab log sheets should be scanned and copied to data1, and sent to shore in surface freight not AF anymore.
- We were low on store items and phone cards, especially. Towards the end of an expedition, the ship ALO should ask shore to make sure phone cards are coming.
- We used a high amount of liner patch for core expansion. The usage history will reflect a higher amount than usual due to manufacturing of core extenders. There is a high possibility to encounter the same issue on JR100.
- IODP store items for San Diego port call #1 will be shipped separate from regular IODP store items. They will come as "gifts" specifically for that purpose.
...
- Confluence
I created a form for submitting software Bugs and issues in the lab note book general area based on Algie's test page, and a link to the form on each lab page. the programmers will have a way to The programmers can view all bugs and get notified when a bug is reported. The "All Reported Software Issues" page displays tables with all current and completed bugs separated automatically. A table showing lab specific bugs reported is in each lab notebook. When the tech decides an issue is resolved, they will change the "status" to verified and the issue will be removed from their notebook, but archived on the main issues page. Developers change the status to complete.
I put a similar system in our ALO Notebook for non-software issues and tasks. I wanted completed tasks to be separated so we know whats current. I recommend it for other notebooks instead of the check boxes. Try it out and let me know what you think. 383 ALO Technical Report
- Rad Van was cleaned up for Guymas. SOP for wipe test was developed by LO. ALO’s were trained by LO.
- 3D printer was used for a few projects.
- Hotplate, ultrasonic bath and stirrer hotplate inventory was made and saved in ALO Lab Notebook.
- Technical knowledge exchange was held - techs teaching techs about other research ships, their workflow, the database structure etc.
- Confluence 1: Laboratory Notebooks discussion about having it private (hidden from scientists) or public (scientists can see everything). Management decided to go with option 2.
- Confluence 2: General issues reporting got added. It reports to a central location and the Lab Notebook of the specific lab. The techs and developers can annotate and add notes etc. Check out here: All Reported Software Issues
- The heater on the catwalk closed to the rig floor failed and was repaired by the rig electricians. Nice and quiet now.
- We had a leak above the yellow cabinet with the chemicals in UTSHOP. SIEM fixed it and found another one. Currently a tarp is there to prevent water from getting into the cabinet. The leak will be a big project to fix. May be a while.
- Hard hat inventory was taken: SIEM will enforce a policy (time unclear) where hard hats can't be older than 5 years. Plus, no "unapproved" stickers or writing on them. We have to replace most of all of the lab and accommodation hard hats for the berths we are responsible for. It is not yet reflected in AMS when we will order them/they get replaced. They were tagged with a red dot, if expired.
- Water samples were collected during transits in International waters and stopped in the EZ zone.
...
- CORE_1 and CORE_2 to IODP. 2x40 Ft Reefers, Chilean and International (Cyprus) cores are separated. International core boxes have a red dot on them.
1x40 Ft SURF to IODP.
5 Cold shipment customers (3 frozen (HERB/LILO/RAVE), 3 refrigerated (HEBR/LILO/SMITH)),
Air freight to IODP (RAF).
A pallet of foreign Air Freight (FA).
- HC (Hand Carry) - NZ shipment of 3 crates of equipment (Rieselmann),
Since our recovery was a lot less than expected and due to this being the last port call in Punta Arenas, Chile, some of the oncoming freight (D-tubes, core boxes etc.) need to be turned around and send back to College Station. Some load out mock ups based on recovery are in the ALO expedition folder and we sent to shore. 120 D-Tube boxes remain in the Punta Arenas warehouse.
...
- We implemented a new method of shipping samples to New Zealand at the request of Christina Riesselman, University of Otago. Her institution does not use a permit to import. They use the New Zealand health standard and a weight maximum exception. The method requires a maximum of 10 kg per package, samples be identified as “Deep sea clay and sand sample for research purposes” in shipping documents, a intro letter, a copy of the New Zealand Health Standard, and a sample list by box. The process is similar to the permit, but much easier in terms of coordination. I saved copies of these examples in our 383 expedition folder. Maybe we should start a section in the lab notebooks for shipping to certain countries.
383_Bulk Return Estimates_loadout 1.tiff