Timeline for Python API for working with ENSEMBL genomes
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 6, 2019 at 15:57 | answer | added | Ad115 | timeline score: 6 | |
| Aug 15, 2018 at 7:49 | comment | added | Devon Ryan | If we wrote papers on every tool we create we'd never have time to do anything productive. That and the limited benefit of actually submitting a paper on a tool/package is the reason that most never get published in that way. | |
| Aug 10, 2018 at 23:53 | vote | accept | user345394 | ||
| Aug 6, 2018 at 15:35 | answer | added | Emily_Ensembl | timeline score: 4 | |
| Jul 31, 2018 at 15:04 | history | edited | user345394 | CC BY-SA 4.0 |
correction
|
| Jul 31, 2018 at 14:48 | comment | added | user345394 | @Llopis I agree with both points. (1) I just wonder why it is not published. It is is a very useful resource. I will remove the reliabilitypart from my question. Thanks. (2) Conventionally, for contributing (making pull requests), a potential contributor has to understand the code and to understand the code, the he/she has to go through the documentation (preferably the latest one). So that's why I feel documentation is an important issue. May be I will build the documentation myself and contribute. | |
| Jul 31, 2018 at 14:48 | history | edited | user345394 | CC BY-SA 4.0 |
Update
|
| Jul 31, 2018 at 14:28 | comment | added | llrs | "That makes you slightly worried about it's reliability." You have the source code, you can see what it does and you can copy and modify as you wish. Why do you think it is unreliable? You can improve the documentation and suggest changes, but it looks like it is documented well with docstrings although the documentation has not been rebuild in a pdf format in a couple of years. | |
| Jul 31, 2018 at 14:14 | history | edited | user345394 | CC BY-SA 4.0 |
clarification
|
| Jul 31, 2018 at 14:07 | history | asked | user345394 | CC BY-SA 4.0 |