...
- Deliver the end-of-expedition report to the LO (that you have been writing throughout the expedition). Post a copy to the development team via Slack. See examples from prior technical reports for formats and variations.
- Establish with MCS, LOs, CoChiefs when the final database snapshot will be taken for EOX.
- Spot check data copy efforts. What data didn’t get into the database? To data1?
- Honor moratorium. Once content is uploaded to LIMS, and raw files have gone to data1, expedition-specific data may be cleaned off of instrument hosts and workstations. Good practice to confer with technical staff that manage this for their labs. There is variance between crews as to how these procedures are carried out.
- Conduct end of expedition procedures for backing up the database.
- Provide courier services if called upon to do so.
- Confirm with the MCS what is to be included in the backup going to shore and that it does cover all the information you are aware of that should go to shore.
- Ensure all your code changes are checked in.
- Clean the development office. Assist in the general cleaning efforts.
- Be ready to move out. Your replacement will be here soon.
- Provide assistance and information to oncoming developers.
Oncoming personnel expect functional laboratory and compute systems to successfully for successful execution of the new expedition.
Assist with those goals.
...