...
- 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.
...