This perspective is a tad absolutist -- but of course I think that's Nick's point :). I would say that any code that's specific to your analysis should be open, while anything that is kinda generic can be closed. Where to draw that line is ...up for discussion!https://twitter.com/pathogenomenick/status/1184523767864840194 …
Odgovor korisniku/ci @ctitusbrown
IMHO the critical issue is that the code of scientific software should be able to be audited by anyone performing science. We should not be using black boxes whose implementation (and sometimes algorithm) cannot be examined. Open source is the easiest way to achieve this.
10:50 - 16. lis 2019.
0 replies
4 proslijeđena tweeta
8 korisnika označava da im se sviđa
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.