Summary
This is a set of scripts used to parse and display the FPGA processor temperature information for a Gatan K3 camera server as reported in the Digital Micrograph (DM) logs. This is useful for determining if there are overheating problems and to see if the fans on any of the FPGAs has died (indicated by a sustained increase in the temperature of one processor).
Requirements
This script requires a python installation of version 3.6 or higher. Matplotlib is required to use the --plot/-p option but is not required for the summary or csv output.
Installation
Install into an appropriate python environment using pip install card_temps or by cloning this repository. Cloning will require running the script directly using the ./card_temperatures style.
Usage
The script can be run pointing at DM log files and/or zip files containing DM logs. These are located by default at c:\ProgramData\Gatan\Logs. The default zipfile containing logs for the last year is DM.Archive.log and the log for the current day is .DM.log, filling in the date in YYYY-MM-DD format for . This makes the command to look at the log for 2021-07-27 card_temperatures c:\ProgramData\Gatan\Logs\2021-07-27.DM.log. When run without any parameters as card_temperatures it will search the default log path for any .DM.log files and operate on them automatically.
This mode (no flags) will output a min/max/avg summary for each processor, calculated over the entirety of the input data. In some versions of DM the logged values are the same for both of the processors on a card, in newer versions the temperature of each processor is reported independenly.
Specifying --output will write a csv file. The output will contain summary rows for each processor for each day in the input data. This can the be manipulated in other programs to further slice or analyze the data.
Specifying --plot (requires matplotlib) will plot the data on a per-processor basis in time-series, showing the min/max/avg values for each day.
Any day that has a zero is the result of a communication error occurring between DM and the card, during which it records 0.00 as the temperature.
Notes
I've only been able to test this on microscopes that are maintained in very similar condition and which run nearly-identical versions of DM. I'm fairly sure that other versions may cause bugs. If you suspect there's a bug related to the DM version, please contact me and I'll try to take a look at it.
Metadata
Release files for card-temps 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| card_temps-0.0.1.tar.gz | 4.7 kB | Without provenance | Details for card_temps-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| card_temps-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for card_temps-0.0.1-py3-none-any.whl |
Total release size: 10.0 kB
Release files / card_temps-0.0.1.tar.gz
| Download URL | card_temps-0.0.1.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
951f2747c54f4c5153aa20b6d9ddb26cce7802e2bf3db24b181b165e3274a8e7
|
|
BLAKE2b-256 checksum How to use checksums |
2e82d5017ce61360c7212312d0b8448232f81bdaa7550517d7ea9d4894bcbb11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Release files / card_temps-0.0.1-py3-none-any.whl
| Download URL | card_temps-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
04b44cedb0c241c4760dcf6e629cb0e91907eb1346791a84efef48a235cbbd9e
|
|
BLAKE2b-256 checksum How to use checksums |
55f9a812af61b5b6c0d1a5a33d4de9d61a648cb91a0cebc5699b87869af3960a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Security for card-temps 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.