OpenFreeEnergy / OpenFreeEnergy/openfe
Capture standard out and standard error (as well as other logs)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 332
- Forks
- 56
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 13
Description
We should try and capture everywhere a log could end up and include it in a result object/json.
The most direct way (I think) may be (as proposed by @ianmkenney ) will be to use python to capture standard out and stander error streams and then add them to the return object (I think in this location is where we can add this https://github.com/OpenFreeEnergy/openfe/blob/main/openfe/protocols/openmm_rfe/equil_rfe_methods.py#L1124 )
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
Start by reading openfe/protocols/openmm_rfe/equil_rfe_methods.py around line 1124 and identify how the return object or JSON is assembled. Trace where standard output, standard error, and other logs can be emitted; done means the relevant captured logs are included in the result object or JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100