In a surprise move Apple today announced
a new product closely related to the behyped
iPad. This move went completely
unexpected with technology analysts, who were expecting a new iPhone dubbed
"iPhone 4G" to be released next.The new product is called iPad mini, and features most of the iPad
functionality in a lot smaller form factor, with extended battery life and
without the overheating issues. It will focus on gamers, instead of the
deprecated community of newspaper readers. The smaller form factor allows
the users to bring the device along at any time.Get all the specifications of
the new iPad mini here [www.apple.com]. There is also a
special edition with voice-over-3G
functionality [www.apple.com].Yes, I'm referring to the iPod touch and the iPhone. Just goofing around.
The fact that it's only two weeks feels totally surreal. I think
it's the feeding approximately every 3 hours. That's approximately 100
interactions that we've had with her in only 2 weeks.
We had her two week weight check at the paediatrician's today. She's now
weighing 6 lbs 12 oz (3061 grams), so she's made back her birth weight and
then some.
We're still largely bottle feeding her with pumped breast milk. The
paediatrician said that once she's 7 pounds she should have enough strength
to breastfeed exclusively, so we'll get a lactation consultant involved if
that isn't the case in another week or so.
Other than that, everything's going swimmingly. She eats, sleeps and poops.
She sleeps amazingly well. I keep telling myself it won't last, but we're
making the most of not needing to tip-toe around the house. In the last
week, we had a new stove installed, which involved the contractor using a
hammer drill to install the anti-tip brackets. He also used a drop-saw to
modify one of the drawers. Didn't bother her. We had some shutters installed
in the kitchen, which involved a lot of cordless drilling. Also didn't
bother her. The gardeners for the complex were mowing the lawn and using a
leaf blower right outside her window. Not a peep.
Today, after the paediatrician's appointment, we dropped in to Palo Alto
Animal Services, the animal shelter where Sarah has volunteered for the
last 4.5 years, to show them Zoe. They threw a bit of a surprise baby
shower, and gave us a ton of baby clothes, which was very nice and totally
unexpected. Zoe slept in her car seat on the table in the lunch room while a
good dozen people or so made a lot of noise around her, and she was
oblivious to it all.
Sarah's Mum arrives on Wednesday. Tomorrow will be a busy day of final
cleaning up in preparation.
Some notes I think are worth sharing about the upgrade to KDE 4.4:
Romain and I are happy to
announce the release of
Rcpp version 0.8.0.
It has been uploaded to CRAN. A
Debian upload is delayed until the
now-required inline package is accepted into Debian. The source package is
also available from here.
This release brings a number of changes that are detailed below. Of
particular interest may be the much more robust treatment of exceptions, the
new classes for data frames and formulae, and the availability of the new
helper function cppfunction for use with inline. Also of note is the new
support for the 'LinkingTo' directive with which packages using Rcpp will get
automatic access to the header files.
An announcement email went to the r-packages list
(ETH Zuerich,
Gmane); Romain also
blogged about the release.
The full NEWS entry for this release follows below:
0.8.0 2010-05-17
o All Rcpp headers have been moved to the inst/include directory,
allowing use of 'LinkingTo: Rcpp'. But the Makevars and Makevars.win
are still needed to link against the user library.
o Automatic exception forwarding has been withdrawn because of
portability issues (as it did not work on the Windows platform).
Exception forwarding is still possible but is now based on explicit
code of the form:
try
// user code
catch( std::exception& __ex__)
forward_exception_to_r( __ex___ ) ;
Alternatively, the macro BEGIN_RCPP and END_RCPP can use used to enclose
code so that it captures exceptions and forward them to R.
BEGIN_RCPP
// user code
END_RCPP
o new __experimental__ macros
The macros RCPP_FUNCTION_0, ..., RCPP_FUNCTION_65 to help creating C++
functions hiding some code repetition:
RCPP_FUNCTION_2( int, foobar, int x, int y)
return x + y ;
The first argument is the output type, the second argument is the
name of the function, and the other arguments are arguments of the C++
function. Behind the scenes, the RCPP_FUNCTION_2 macro creates
an intermediate function compatible with the .Call interface and handles
exceptions
Similarly, the macros RCPP_FUNCTION_VOID_0, ..., RCPP_FUNCTION_VOID_65
can be used when the C++ function to create returns void. The generated
R function will return R_NilValue in this case.
RCPP_FUNCTION_VOID_2( foobar, std::string foo )
// do something with foo
The macro RCPP_XP_FIELD_GET generates a .Call compatible function that
can be used to access the value of a field of a class handled by an
external pointer. For example with a class like this:
class Foo
public:
int bar ;
RCPP_XP_FIELD_GET( Foo_bar_get, Foo, bar ) ;
RCPP_XP_FIELD_GET will generate the .Call compatible function called
Foo_bar_get that can be used to retrieved the value of bar.
The macro RCPP_FIELD_SET generates a .Call compatible function that
can be used to set the value of a field. For example:
RCPP_XP_FIELD_SET( Foo_bar_set, Foo, bar ) ;
generates the .Call compatible function called "Foo_bar_set" that
can be used to set the value of bar
The macro RCPP_XP_FIELD generates both getter and setter. For example
RCPP_XP_FIELD( Foo_bar, Foo, bar )
generates the .Call compatible Foo_bar_get and Foo_bar_set using the
macros RCPP_XP_FIELD_GET and RCPP_XP_FIELD_SET previously described
The macros RCPP_XP_METHOD_0, ..., RCPP_XP_METHOD_65 faciliate
calling a method of an object that is stored in an external pointer. For
example:
RCPP_XP_METHOD_0( foobar, std::vector<int> , size )
creates the .Call compatible function called foobar that calls the
size method of the std::vector<int> class. This uses the Rcpp::XPtr<
std::vector<int> > class.
The macros RCPP_XP_METHOD_CAST_0, ... is similar but the result of
the method called is first passed to another function before being
wrapped to a SEXP. For example, if one wanted the result as a double
RCPP_XP_METHOD_CAST_0( foobar, std::vector<int> , size, double )
The macros RCPP_XP_METHOD_VOID_0, ... are used when calling the
method is only used for its side effect.
RCPP_XP_METHOD_VOID_1( foobar, std::vector<int>, push_back )
Assuming xp is an external pointer to a std::vector<int>, this could
be called like this :
.Call( "foobar", xp, 2L )
o Rcpp now depends on inline (>= 0.3.4)
o A new R function "cppfunction" was added which invokes cfunction from
inline with focus on Rcpp usage (enforcing .Call, adding the Rcpp
namespace, set up exception forwarding). cppfunction uses BEGIN_RCPP
and END_RCPP macros to enclose the user code
o new class Rcpp::Formula to help building formulae in C++
o new class Rcpp::DataFrame to help building data frames in C++
o Rcpp.package.skeleton gains an argument "example_code" and can now be
used with an empty list, so that only the skeleton is generated. It
has also been reworked to show how to use LinkingTo: Rcpp
o wrap now supports containers of the following types: long, long double,
unsigned long, short and unsigned short which are silently converted
to the most acceptable R type.
o Revert to not double-quote protecting the path on Windows as this
breaks backticks expansion used n Makevars.win etc
o Exceptions classes have been moved out of Rcpp classes,
e.g. Rcpp::RObject::not_a_matrix is now Rcpp::not_a_matrix
As always, even fuller details are in
Rcpp Changelog page and the
Rcpp page which also
leads to the downloads, the
browseable
doxygen docs and zip files of doxygen output for the standard formats.
A local directory has
source and documentation too.
Questions, comments etc should go to the
rcpp-devel mailing list
off the R-Forge page
I find it surreal to have people guessing at my motivations when they could just ask me. On top of all that, I find it weird that people spend so much time with in-fighting. I just want my system not to suck.
Some time ago (during in the Ubuntu Karmic development cycle maybe in September 2009), I started having giant problems with my build system. All I/O would start to stall, wait times would surge, and usually my entire system would just go unresponsive with the disk light on solid. This scared the crap out of me, and it wasn t entirely obvious what was triggering it. No one else seemed to be seeing it. I managed to start tracking things using latencytop , and saw stuff like liferea going crazy. As I eliminated more and more things, I eventually settled on it being a problem with umount, and I reported an Ubuntu bug. It seemed to look like an upstream bug that no one else but the reporter could reproduce either.
Since no one else was seeing this issue, and it seemed related to LVM snapshots, I migrated off of snapshots, and started using aufs overlays for my builds. For a while, it seemed like things went away. It didn t, and I started hitting it again. I opened a new (now famous) bug in Ubuntu, since now snapshots weren t in the picture, and I didn t want to confuse the earlier history. I managed to find a relatively minimal test-case too. A few other people commenting on the bug were seeing the problem now too, but it was less pronounced for them.
As an aside, this wasn t a just wait a few seconds longer kind of issue on my system. A single umount would last 30-40 minutes. And when I m doing parallel builds of security updates, this would turn into my system being unavailable for hours at a stretch.
Since none of the kernel developers I was in contact with were able to track down the root cause, I asked Ted Ts o in email if he could just quickly peek in on this for me, since I figured he d be in a good position to confirm or deny it. I didn t want to start wasting upstream time with this if it wasn t reproducible (see earlier upstream kernel bug). To my great relief, Ted found a few minutes to check it, and was able to immediately confirm it and give me a viable work-around ( sync; umount ) for the time being. I confirmed the work-around, and went off to do other things.
A while later, Ted came back to deliver a bit of a rant, the purpose of which was not clear to me, but I ultimately ignored it I didn t seem directed at me. I just wanted my system operating normally, and he d done me a favor to check in on it and got me a work-around.
More time passes, and I eventually get caught in another I/O-wait melt-down. On investigation, it seemed that the in-kernel work-around in the Ubuntu kernel totally back-fired on me in some cases, rendering even the user-space work-around useless. After investigating the Ubuntu-specific work-around, I re-read Ted s rant in the course of researching what had happened during this bug s triage.
It seemed that Ted was basically saying:
In February 2009, my friend dim tried to force me using Emacs. I know a couple of people using it and Gnus for reading their mail, and it always made me curious. At that time, more than a year ago, Emacs 22 and Gnus did not seem usable from my point of view. But around mid February, with the help of dim, I tried again to start using Emacs. Actually, this was not something new for me. I (very basically) used Emacs between 2000 and 2006. In 2006, when I finished the university and started working at Easter-eggs, I met a couple of vim enthusiasts. They taught me how to use it in various ways, and I started to know more about vim than Emacs, so I switched. This time, I started by configuring it, but reading the manual and also learning a bit of Lisp. It took me several weeks, but step by step I learned many, many things. And I must admit, I liked it. I've configured and starting to use some very important mode, like Gnus, Muse, the famous Org mode or even ERC. I'll probably talk about various Emacs related things in the near future, since I already wrote more than a thousand lines of Lisp in the last 2 months. Anyhow, I'd just conclude by asserting that my new Emacs/Gnus/Org/ERC setup beats my old vim/mutt/nothing/irssi to the death with a baseball bat. :-)
I recently read an introductory article in an IT magazine on the increased usage of new currencies. It briefly mentioned the work of a researcher called Arthur Brock in using those currencies within open source communities. While I did not find more details on the research, it led me to think again about Debian s relation with money.
The reason why we have troubles using money to pay the time spent by our developers is that money is scarce and it s thus next to impossible to be fair in the way money is spent among us. So why not invent a new currency that is not scarce and that would encourage the kind of work that we really value? Apparently there is free software out there to build new currencies: see metacurrency.org or openmoney.org. Let s call the new currency swirly/swirlies for the sake of the examples below.
There are then multiple ways to create a small economy within the community and/or even create bridges with the national currencies:
I spent last week at the Ubuntu Developer Summit in Belgium, where we kicked off the 10.10 development cycle.
Due to our time-boxed release cycle, not everything discussed here will necessarily appear in Ubuntu 10.10, but this should provide a reasonable overview of the direction we re taking.
Presentations
While most of our time at UDS is spent in small group meetings to discuss specific topics, there are also a handful of presentations to convey key information and stimulate creative thinking.
A few of the more memorable ones for me were:
Conference Management systems are web applications designed to make the lives of conference organisers easier. They usually include features such as registration, payment, paper submission and review, scheduling and publishing of announcements.| Name | Used by | License | Programming Language |
|---|---|---|---|
| A Conference Toolkit | YAPC::Eu | Artistic License | Perl |
| ConMan | Utah Open Source Conference, Texax Linux Fest | GPL | Python (Django) |
| Open Conference Systems | various academic conferences | GPL | PHP |
| OpenConferenceWare | Open Source Bridge | MIT | Ruby on Rails |
| Pentabarf | DebConf, FOSDEM, CCC | GPL | Ruby on Rails |
| SCALEreg | SCALE | GPL | Python (Django) |
| Zookeepr | linux.conf.au | GPL | Python (Pylons) |
Some students of the Google Summer of Code are required to make a weekly report describing their activities. As far as I know, I m not, but I think it s a good idea in general, to comunicate to my mentor and other interested folks what I ve been doing. So I ll start to do them here.
My project is Implementing the Immix Garbage Collector Algorithm on GHC.
Last week I was most of the time involved in my school activities, so I didn t have much time to work on the project. I went to the bureaucratic services of my university to get a Proof of Enrollment in English, print/sign/scanned the Foreign Certification Form and sent them to Google on Friday afternoon. I asked them to confirm the receival, which they didn t. I m planning to ask again for a confirmal today in the afternoon, if I still get no reply.
I also tried to build the current version of GHC, from the darcs repository. I was getting an error with my old (and updated) repository, so I donwnloaded a new one and could build nicely. Then I noticed that with make distclean I could also build with my older one, so I just removed the new. I downloaded the nofib benchmark suite and made an initial benchmark.
While I was reading the documentation of the build process of GHC, I noticed a bug, and submitted a patch to the cvs-ghc mailing list. The patch was applied, with some changes.
This week I plan to focus more on the project, and spend the weekly 36 hours working on it. I m planning to start reading the Immix Technical Report to see if there s anything new there with regard to the article. After that I ll read the wiki documentation on the GHC current GC, together with the GHC source code. I ll also experiment with Criterion.
While I was writing this post I noticed that the GC benchmark in nofib is failing:
==nofib== fibheaps: time to run fibheaps follows... /usr/bin/time ../../runstdtest/runstdtest ./fibheaps -o1 fibheaps.stdout -o1 fibheaps.stdout -ghc-timing 300000; /usr/bin/time ../../runstdtest/runstdtest ./fibheaps -o1 fibheaps.stdout -o1 fibheaps.stdout -ghc-timing 300000; /usr/bin/time ../../runstdtest/runstdtest ./fibheaps -o1 fibheaps.stdout -o1 fibheaps.stdout -ghc-timing 300000; /usr/bin/time ../../runstdtest/runstdtest ./fibheaps -o1 fibheaps.stdout -o1 fibheaps.stdout -ghc-timing 300000; /usr/bin/time ../../runstdtest/runstdtest ./fibheaps -o1 fibheaps.stdout -o1 fibheaps.stdout -ghc-timing 300000; Command exited with non-zero status 2 0.72user 0.05system 0:00.77elapsed 99%CPU (0avgtext+0avgdata 277664maxresident)k 0inputs+32outputs (0major+17695minor)pagefaults 0swaps ././fibheaps 300000 < /dev/null **** expected exit status 0 not seen ; got 2 ././fibheaps 300000 < /dev/null expected stderr not matched by reality --- /tmp/no_stderr3559 2010-05-17 07:35:09.000000000 -0300 +++ /tmp/runtest3559.2 2010-05-17 07:35:10.000000000 -0300 @@ -0,0 +1,2 @@ +Stack space overflow: current size 8388608 bytes. +Use +RTS -Ksize -RTS' to increase it. Command exited with non-zero status 1 0.72user 0.06system 0:00.85elapsed 92%CPU (0avgtext+0avgdata 277664maxresident)k 368inputs+48outputs (1major+22085minor)pagefaults 0swaps Command exited with non-zero status 2 0.71user 0.04system 0:00.78elapsed 97%CPU (0avgtext+0avgdata 277664maxresident)k 0inputs+32outputs (0major+17694minor)pagefaults 0swaps ././fibheaps 300000 < /dev/null **** expected exit status 0 not seen ; got 2 ././fibheaps 300000 < /dev/null expected stderr not matched by reality --- /tmp/no_stderr3578 2010-05-17 07:35:10.000000000 -0300 +++ /tmp/runtest3578.2 2010-05-17 07:35:11.000000000 -0300 @@ -0,0 +1,2 @@ +Stack space overflow: current size 8388608 bytes. +Use +RTS -Ksize -RTS' to increase it. Command exited with non-zero status 1 0.72user 0.06system 0:00.80elapsed 98%CPU (0avgtext+0avgdata 277664maxresident)k 0inputs+48outputs (0major+22093minor)pagefaults 0swaps Command exited with non-zero status 2 0.72user 0.06system 0:00.80elapsed 98%CPU (0avgtext+0avgdata 277680maxresident)k 0inputs+32outputs (0major+17696minor)pagefaults 0swaps ././fibheaps 300000 < /dev/null **** expected exit status 0 not seen ; got 2 ././fibheaps 300000 < /dev/null expected stderr not matched by reality --- /tmp/no_stderr3597 2010-05-17 07:35:11.000000000 -0300 +++ /tmp/runtest3597.2 2010-05-17 07:35:12.000000000 -0300 @@ -0,0 +1,2 @@ +Stack space overflow: current size 8388608 bytes. +Use +RTS -Ksize -RTS' to increase it. Command exited with non-zero status 1 0.72user 0.07system 0:00.83elapsed 96%CPU (0avgtext+0avgdata 277680maxresident)k 0inputs+48outputs (0major+22095minor)pagefaults 0swaps Command exited with non-zero status 2 0.68user 0.08system 0:00.78elapsed 97%CPU (0avgtext+0avgdata 277680maxresident)k 0inputs+32outputs (0major+17695minor)pagefaults 0swaps ././fibheaps 300000 < /dev/null **** expected exit status 0 not seen ; got 2 ././fibheaps 300000 < /dev/null expected stderr not matched by reality --- /tmp/no_stderr3616 2010-05-17 07:35:12.000000000 -0300 +++ /tmp/runtest3616.2 2010-05-17 07:35:12.000000000 -0300 @@ -0,0 +1,2 @@ +Stack space overflow: current size 8388608 bytes. +Use +RTS -Ksize -RTS' to increase it. Command exited with non-zero status 1 0.70user 0.09system 0:00.80elapsed 98%CPU (0avgtext+0avgdata 277680maxresident)k 0inputs+48outputs (0major+22089minor)pagefaults 0swaps Command exited with non-zero status 2 0.71user 0.06system 0:00.93elapsed 82%CPU (0avgtext+0avgdata 277680maxresident)k 0inputs+32outputs (0major+17695minor)pagefaults 0swaps ././fibheaps 300000 < /dev/null **** expected exit status 0 not seen ; got 2 ././fibheaps 300000 < /dev/null expected stderr not matched by reality --- /tmp/no_stderr3635 2010-05-17 07:35:12.000000000 -0300 +++ /tmp/runtest3635.2 2010-05-17 07:35:13.000000000 -0300 @@ -0,0 +1,2 @@ +Stack space overflow: current size 8388608 bytes. +Use +RTS -Ksize -RTS' to increase it. Command exited with non-zero status 1 0.73user 0.06system 0:00.95elapsed 83%CPU (0avgtext+0avgdata 277680maxresident)k 0inputs+48outputs (0major+22089minor)pagefaults 0swaps make[1]: ** [runtests] Erro 1 Failed making all in fibheaps: 1 make: ** [all] Erro 1Erro is error in Portuguese. I ll investigate on that.
fuss-launcher:
* New upstream release
- Use newer apt-xapian-index: removed need of local index
- Dragging a file in the launcher shows the applications that can open it
- Remembers the applications launched more frequently
- Allow to set a list of favourite applications
To get it:
apt-get install fuss-launcher (after it passed NEW);git clone http://git.fuss.bz.it/git/launcher.git/
and apt-get install python-gtk2 python-xapian python-xdg apt-xapian-index app-install-dataapp-install-data: just run update-apt-xapian-index as root.fuss-launcher.
When you type some keywords, you get results as you type, and context-sensitive
completion:
When you drag a file on the launcher you only see the applications that can
open that file:
So for awhile, I've been questioning on why very few FOSS programs use newsgroups (or USENET on moderated groups) as their primary means of communication between developers. I personally find email to be a clunky way dealing with mass-mailings, and while switching to alpine and mutt have helped, I feel newsgroups would work better in place of mailing lists./etc/apt-xapian-index/aliases/
or /usr/share/apt-xapian-index/aliases/, and feeds them as
synonyms in the index.
apt-xapian-index ships an example alias file, to give people who know the wrong
software names a chance to find the right ones:
# Aliases expanding names of popular applications
excel XToffice::spreadsheet
powerpoint XToffice::presentation
photoshop XTworks-with::image:raster
coreldraw XTworks-with::image:vector
autocad XTworks-with::3dmodel
Notice how it is possible to use index terms that happen to be Debtags tags as
synonyms, which yields better results, language independence and extra
coolness.
Next.