Log files not handled by Bluefors agent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
At Cornell we had to get a new computer recently for controlling one of our DRs, and this required re-installing the software that Bluefors uses for control and logging of DR pressures. Bluefors has a new "Bluefors Control Software" that replaces the old ValveControl software, and it seems to make at least one new type of log file that is not handled by the current Bluefors agent.
The old software makes at least three log files with the prefixes "Channels," "Flowmeter," and "maxigauge." The new software makes up to five log files with the prefixes "Channels," "Flowmeter," "maxigauge," "Heaters," and "Status." Due to these new log files, the docker logs for the Bluefors agent look like this on the computer with the new software:
2022-12-06T16:20:07+0000 None acq
2022-12-06T16:20:07+0000 acq:0 Status is now "running".
2022-12-06T16:20:07+0000 /logs/22-12-06/Heaters 22-12-06.log not yet open, opening...
2022-12-06T16:20:07+0000 /logs/22-12-06/Status_22-12-06.log not yet open, opening...
2022-12-06T16:20:07+0000 /logs/22-12-06/Channels 22-12-06.log not yet open, opening...
2022-12-06T16:20:07+0000 /logs/22-12-06/Flowmeter 22-12-06.log not yet open, opening...
2022-12-06T16:20:07+0000 /logs/22-12-06/maxigauge 22-12-06.log not yet open, opening...
2022-12-06T16:20:28+0000 Warning: Unknown log type. Skipping publish step. This probably shouldn't happen.
2022-12-06T16:20:28+0000 Filename: /logs/22-12-06/Heaters 22-12-06.log
2022-12-06T16:20:49+0000 Warning: Unknown log type. Skipping publish step. This probably shouldn't happen.
2022-12-06T16:20:49+0000 Filename: /logs/22-12-06/Heaters 22-12-06.log
2022-12-06T16:21:10+0000 Warning: Unknown log type. Skipping publish step. This probably shouldn't happen.
2022-12-06T16:21:10+0000 Filename: /logs/22-12-06/Heaters 22-12-06.log
2022-12-06T16:21:10+0000 Warning: Unknown log type. Skipping publish step. This probably shouldn't happen.
This isn't a high priority, but it may be worth adding the ability to handle these Heater files, especially if we ever update the Bluefors software used at the site to the new version instead of ValveControl.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Bluefors agent entry point that discovers and classifies the Channels, Flowmeter, maxigauge, Heaters, and Status logs; start by tracing the unknown-log warning shown in the Docker logs. Confirm that Heaters files are handled without that warning and verify the agent’s existing behavior for the other log types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100