-
Notifications
You must be signed in to change notification settings - Fork 186
docs: Flex log files description and download #19863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: edge
Are you sure you want to change the base?
Conversation
Read the description in the PR.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## edge #19863 +/- ##
=======================================
Coverage 25.35% 25.35%
=======================================
Files 3523 3523
Lines 296771 296771
Branches 39620 39620
=======================================
Hits 75253 75253
Misses 221497 221497
Partials 21 21
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Proposed changes will break some links between pages. Checked mkdocs output for warnings and fixed broken links. Replaced "reference" style links with typical [ ]( ) style relative links.
There are 2 new log files: can_bus.log and update_server.log. I think I know what the former is, but not the update_server. checking on these to verify.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new text is good. I agree that we should discuss the overall structure, specifically whether we think downloading the logs qualifies as an "advanced operation".
|
|
||
| In an idle state or during a protocol run, your Flex constantly writes data to several different log files. Each of these files tracks the activities specific to different parts of the robot and its attachments. The following table summarizes the data captured in each file. | ||
|
|
||
| | Log file | Description | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make the first column wider so the file names fit without wrapping.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to be clever and apply a CSS rule to prevent line splitting on the first column:
.first-col-no-wrap th:first-child,
.first-col-no-wrap td:first-child {
white-space: nowrap;
}
This didn't work. Implemented an ugly-er fix. Might continue to test this separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My other fix didn't work. Trying this instead. I think it is good enough.
| !!!note | ||
| Flex produces a single `.zip` file that contains the logs. The compressed file name includes the robot’s name followed by `_logs.zip`. For example, if your robot is called “Flex1," the log file will be named `Flex1_logs.zip`. | ||
|
|
||
| 5. _(Optional)_ To read the logs, double-click the downloaded file to decompress it. The individual logs will expand into a new folder in the same location as the downloaded file. Any simple text editor should be able to open these files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe remove "simple"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing
| Opentrons Flex gives you command-line access to its operating system through a Secure Shell (SSH) terminal connection. Terminal access lets you: | ||
|
|
||
| ## Command line operation over SSH | ||
| - Run protocols directly via the [Python API and command line](https://docs.opentrons.com/v2/new_advanced_running.html#command-line). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updating URL.
| !!!note | ||
| - SSH keys are required before you can connect to Flex and issue commands from a terminal. | ||
| - If you're unable to use a Wi-Fi network for SSH, see [Hardwired SSH Connections][hardwired-ssh-connections] below. | ||
| If you're unable to use a Wi-Fi network for SSH, see [Making a hardwired SSH connection][making-a-hardwired-ssh-connection] below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this note go in the "Making a wireless SSH connection" section instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. That's odd. It should be in that section. Moving.
- update links - re-org TOC, put log files first. - fix table spacing - found errant trailing whitespace and missing closing } in CSS file, when working with a table rule
Trying to avoid line wrapping in the first col of the log file table. I do
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Overview
Having more info about Flex log files in the manual is helpful. Also, and perhaps more important, having this in the Flex manual allows us to get rid of another bad Help Center article (How to download the logs on Opentrons Flex).
For this article, we'll repurpose the intro and file download instructions from the Flex service manual, but without all the extra details used by the service techs.
See also RTC-824
Sandbox docs:
Test Plan and Hands on Testing
Changelog
On the surface, a simple change or PR: add steps on log file download.
I'd recommend some reorganization. This belongs with the other "advanced" operations articles. I'd like to:
advanced-operations.mdadvanced-operations/index.mdto summarize the sections.Review requests
Consider the reorg. Is there another place to put this without changing the structure?
Risk assessment
Low, docs changes only.