cpcloud
However, if you import it from Ibis then it ceases to be used as "most recent result" and remains the ibis underscore object (unless of course you explicitly assign it to something else).
Regarding backend compatibility, there are definitely a few kinds of things that we don't currently abstract over. One is regular expression syntax and another is floating point math (e.g., various algebraic properties that are violated that result in slightly different outputs).
Hope you give it a go, and please report issues at https://github.com/ibis-project/ibis.
If it were better, we'd use it internally in Ibis for the Polars backend implementation.
If you're going down the mixed SQL, DataFrame API route then Ibis is probably the best solution out there for that.
I work on Ibis, so take what I say with a grain of salt. There may yet be other libraries out that there that have similar functionality.
Fully agree that if pandas is working for you, then you're better off sticking with it!
DuckDB was chosen as the default because Polars was too unstable to be the default backend two years ago.
We'd love to have a docs contribution that lays this out in detail if you'd be up for it!
Disclaimer: (I lead the project and work on it full time).
- The band: https://www.ebay.com/itm/225562259251
- The hotel chain: https://all.accor.com/brands/ibis.en.shtml
- The anime drawing program: https://ibispaint.com/?lang=en-US
- The beer: https://ibisrice.com/ibis-pale-ale/
- The whatever this is: https://ibis.ibo.org/
- The ibis python library: https://pypi.org/project/ibis-framework/ (disclaimer: I work on this library)
- The ibis python library: https://pypi.org/project/ibis/
- The software for reverse mortgage management: https://www.ibisreverse.com/
- The song: https://www.youtube.com/watch?v=mO-OpFjHRbE
1) In neuroscience there's an enormous lack of enthusiasm for software development, even if it makes large parts of a workflow easier. If a poorly written, undocumented piece of code stuck in a file called temp123_final_final_no_really_final.m produces the same output as a higher quality piece of code, no one cares as long as it leads to a publication.
2) You don't need a degree in neuroscience to do neuroscience research, however you'll probably need to take a few basic neuroscience courses to get up to speed depending on what area you're interested in focusing on. It sounds like you're interested in theoretical neuroscience. For that you'll need to take lots of probability and statistics.
3) Make no mistake, your ability to write clean, well documented code will be massively under-appreciated by nearly everyone.
4) As far as division of labor goes, that usually depends on the lab size. The smaller the lab, the more you do. Even in some large labs you have people building software AND doing animal surgeries AND running experiments. There usually isn't a person dedicated to a specific type of labor.
5) To "fiddle" with the brain, you'd have to get into animal research as you can't really do that with people (yet?)
A lab worth checking out is the lab of Gyorgy Buszaki: http://www.buzsakilab.com/
Google Maps Corner Cases
If you query Google Maps for directions to travel to China from the United States, when you get to northeast Washington state it tells you to kayak across the pacific ocean and head straight: http://imgur.com/Td8Z4. How are these types of corner cases handled in navigation software? Are they hard coded?