Adapted version from Software for scientists
Some things takes much less time and stress once you know the right tool. Below, there is my adaptation to a list of software for scientists for data scientists and when to use them.
Although, having a single editor for every project could be perfectly fine, there might be some situations where you can explode language specific features from the IDE, in that sense:
- When? The project your working lives on python
- Why? It will include all configurations you require for developing your python project, even using the community version.
- When? The project your working lives on R
- When? You are just testing ideas that may involve several languages.
- Why? It will be easy to syntax highlight every language and it's easy to interact with on desktop, also a lot of plugin could make a great experience to code (even more).
Vim:
- When? You are already interacting with the server where the code lives.
- Why? You'll need to learn some commands, practices and configurations, yes, but you'll be suited for interacting with every text file afterwards in a way that you are going to -almost- forget you are not on an IDE.
- When? You want to keep snippets of code and theoretical notes for work at hand.
- When? You want to keep a personal private server with the situation above and you might encounter yourself tweaking javascript code for improving your experience right on the tool
- When? (Always, it's amazing!)All-in-one workspace in the cloud for notes with powerful and flexible file structures
As a general thing, Markdown format may be convenient. It can be read on any system, and it is easy to cenvert it to HTML, PDF of DOC using Pandoc.
- Why? Usually much nicer than sending back and forth docs.
LaTeX ?
- Why? "easy to use, online, collaborative LaTeX editor", Agreed.
- Why? For sharing short math notes.
- Why? Standard de facto for Version Control and good starting point.
- Why? Standard de facto for public repositories.
- Why? for posting short codes or notes on anything
For personal homepages, lab notebooks and conference websites.
- Why?
- For writing blogs in Markdown and easily putting them on GitHub
- Why? Static websites with Git
- Why?
- With PDF, notes, arXiv field, BibTeX support, metadata extraction
- Free with large storage limit; owned by Elsevier
- Why?
- Strong browser integration - click a button in the URL bar to save a reference
- Syncs references between computers
- Open source
- Why?
- For sharing negative data, plots, posters, etc; gives you a DOI.
- Why? Easy readable on mobile devices
- Why? Aggregating different news sources and RSS
- Why? Interesting comments from experts about recent news
- Why? Interesting comments from experts about recent news
- Why? Recent news articles about the field
- Why? AI Problem specific QnA
- Why? Code specific QnA
- Why? Most extensive community backed packages for the field.
- When?:
- For interactive applications and visualizations (works on any system, no installations required)
- Nice introduction: http://eloquentjavascript.net/
- When?:
- Great for quick data preparation and visualization of experimentations
- For Python
- For Python
- For R
- For Javascript
- Standalone app
- For LaTex
- Standalone app
- For Latex
knitr combine R and markdown and export your report to pdf/doc/odt
- For R
- For R
- When? You want people to view online and download pdfs (no registration or adverts, as of now)
- When? Sharing artifacts of experimentation or papers.
- General purpose visual editions
LaTeX Templates - Conference Posters
- When?
- Symbolic calculations specific
- When?
- for online simple plots, units changing, integrals etc. a "demo version" of Mathematica
- When?
- for numerical calculations, supports scripting
- When?
- open source, GNU licence
- almost the same as MATLAB (sometimes incompatible), without graphical interface - only text
- may use Gnuplot for plots
- When?
- open source, licensed under the GPL
- mathematics software system (alternative to Magma, Maple, Mathematica and Matlab.) . It combines the power of many existing open-source packages into a common Python-based interface.
- When?
- for any kind of statistics
- Why? Todo list with easy synchronization
- Why? Simple notes across mobile devices
Feel invited to collaborate.
- Wilmer Gonzalez (author of the adaptation and maintainer)
- Piotr Migdał (author of the initial version from which structure was forked)
- Thomas Kluyver
- Marek Stępniowski
- Vasily Sochinsky
- Florence Piron
- Marta Czarnocka-Cieciura
- Krzysztof Zieleniewski
- Le
- Przemek Biecek
- Carolina Odman-Govender
- Marcin Kurczych
- David Ketcheson
- Steven Byrnes
- write your name (even if you contributed a single character :)) use name, pseudonym or increment the anonumous counter:
- ...and 2 Anonymous Contributors.
YOU ARE INVITED TO EDIT! :)
DO:
- Add programs you use and recommend
- Fix mistakes and omissions by others. :)
DON'T:
- Throw a pile of random programs (it is not a complete list of software for X - it is a recommendation list)
Additional pluses for:
[name](link)- comments on status (e.g. open source)
- one sentence of description what's that and what's that good for
- adding categories, their short intros or general links
- marking explitly if it only works under some OS