- 1 peceto entero de unos 2 kgs
- 3 chorizos
- hongos secos, un puñado
- mostaza, bastante
- calditos de verdura, 1 o 2
- vino blanco, 2 vasos
today I found out about twisterd and I wanted to give it a try (and reserve my username ;) so I tried and it took a while to get all the dependencies right, to avoid you the pain here is the guide.
take into account the comments in the script.
just a console dump, it should work just by pasting the commands in order:
mkdir twister cd twister sudo apt-get update sudo apt-get install libssl-dev libdb-dev libdb++-dev libminiupnpc-dev libboost-all-dev build-essential git autoconf libtool git clone https://github.com/miguelfreitas/twister-core.git git clone https://github.com/miguelfreitas/twister-html.git mkdir ~/.twister mv twister-html ~/.twister/html cd twister-core/libtorrent # NOTE: the following command will fail with an error about boost, ignore # it and run the following commands ./bootstrap.sh ./configure --enable-logging --enable-debug --enable-dht --with-boost-libdir=/usr/lib/x86_64-linux-gnu/ make cd ../src make -f makefile.unix ./twisterd -daemon -rpcuser=user -rpcpassword=pwd -rpcallowip=127.0.0.1
BTW I'm @mariano :)
In the last two weeks I took a couple of friends and my car to a trip around
Deutschland and then some more. When I do this kind of road trips, the last
thing I do each night is to take a picture of the dashboard with the trip
counter showing the accumulated kilometers. Last year we did a slightly shorter
one all the way to Praha and back, and on the last day I noticed that the
counter seemed to reset a little bit beforehand. See, the trip counter only
shows three integer digits and one decimal digit, so once it reaches 1000 km
(1mm! Just not the small one :), it shows
000.0 again. So in this trip to Praha,
while coming back, the counter reseted back to 0, so at the end of the trip I
was not sure how many kilometers I did, only that it was around 3.5k km.
This time we were in the way between Hamburg and Köln when it happened again. This time I was sure we were around 3.2k km when it happened, and suddenly it struck me. But let me tell you how I was sure first.
In the first night, the numbers read 207780 for the total counter and 752.2 for the trip, which makes the start at around 207027.8. The last night they read 212048 and 743.3. Subtracting this last total counter to the belated start value makes some 5020.2 km!
Now, let's go back to the strange resetting problem. It's around the 3200.0 km mark, and the counter is digital. Digital counters need bits to count, and the amount of bits available determine the maximum number these bits can count. Also, this counter has a decimal place for counting kilometers... but what if it actually counted hundreds of meters (hectometers) and the display is just a representation? That would make the reset at around 32000 hectometers, hmm...
I just wonder why the technicians at BMW decided 20 years ago (my car is old) to use what looks like a signed int for this. With a two byte signed int a counter can go as up as 32767. If you're counting hectometers, that makes 3276.7 km, which seems to match the resetting point. Then, if we add the number from the last night, we get 4020.0. I knew that after Köln the digits shown wrapped once around 1000 km, so we end up with 5020.0 for the real trip. It's a suspiciously round number, but it's only a 1 in 10 probability.
So, cars can have bugs too. This time is just annoying bug for those us crazy people who make trips longer than 3.2k km, but with the tendency of making cars more and more dependent on computers (self-driving cars are the most clear cases), we have to be aware that worse things can happen. But then, we already have self-flying planes, which can even land mostly by themselves.
This is the last post of this year, so I try to do my best to give you something interesting to think about...
In this case, I will show you my git workflow... and you know there are a lot of workflows out there... and probably better than mine, but I just want to share with you the place where I find myself comfortable.
And yes... my git workflow is also powered by IPython (I am very repetitive when I love a project!). And it is a semi-automatic one, using the IPython notebooks (ipynbs) as a sort of templates, transforming them into a new conceptual entity: the ipytmpl (and yes, I love to invent names too!).
Read more… (10 min remaining to read)
Una de las tantas cosas que me gusta hacer como pasatiempo es cocinar, y hace mucho tiempo que tenia ganas de empezar a probar con los fiambres caseros.
Busque un poco en Internet, y encontré la bondiola, la cual parece ser uno de los embutidos más fáciles para hacer.
La hice, y salio muy bien, Así que ahora tengo ganas de hacer otros embutidos como Jamón Crudo y Quesos, y obviamente, otra bondiola, porque ya la comimos.
Así quedo la bondiolita casera.
Following the idea to release all the extensions I had working on in the last few weeks/months, today I will release an old but very useful IPython notebook extension for people blogging with Nikola: the nikola_deploy extension.
Read more… (2 min remaining to read)
OK, today I will release another IPython js extension: Spellchecker, which obviously do what you are thinking... spell check the content of your IPython notebook cells.
And why it is a poor man extension? Because it is a simple workaround to get the spell checker functionality and not a broad solution... but it works, and solve my spelling problems!
Read more… (4 min remaining to read)
>>> import pint
>>> ureg = pint.UnitRegistry()
>>> q = 500 * ureg.nm
Traceback (most recent call last):
pint.unit.DimensionalityError: Cannot convert
from 'nanometer' ([length]) to 'hertz' (1 / [time])
>>> q.to('Hz', 'spectroscopy')
>>> with ureg.context('spectroscopy'):
>>> q.to('Hz', 'sp')
>>> np.ones(3) * ureg.meter == np.ones(3) * ureg.meter
>>> np.ones(3) * ureg.meter == np.ones(3) * ureg.meter
array([ True, True, True], dtype=bool)
>>> np.all(np.ones(3) * ureg.meter == np.ones(3) * ureg.meter)