In order to publish your scientific work through conference proceedings, it is mandatory you present your work to an audience of peers at the conference. To some, presenting comes more natural than to others. There are many howtos and excellent books out there how to prepare and execute your presentation, but here I’ll list a few ways how NOT to present.
The purpose of this article is two-fold: make sure you give better presentations, and protect your audience against poor presentations.
As a frequent user of the IEEEXplore database to search for literature concerning wireless networking, I often export a citation to BibTeX for use in my papers.
One of the things which has puzzled me for a long time, is why the BibTeX exporter adds a trailing comma after the last field.
You may be using the PRISM Model Checker for your research. You may also want to put some code in your text, for instance in your PhD thesis. Using and the Listings environment is probably your best bet. Read the rest of this entry »
For years I have been running Linux servers. Some time ago I built a NAS box running Ubuntu Server. I’ve done quite some tweaks to reduce power consumption. But there must be more. Or less, so to speak.
Read the rest of this entry »
Anyone who has ever done anything even remotely related to science is probably aware of Google Scholar. There’s this feature where you can keep track of your citations (e.g. how many and which papers by which authors cite your publications). A very nifty feature and quite easy to set up. Your data will only show up after your email address has been verified. And that’s where stuff borked.
The verification link did not work, giving a 404 Not Found error. After inspecting the url I noticed that the dots in my email address had been removed. I figure they probably have some scripts there like php’s
htmlspecialchars() and addslashes() to prevent such things as SQL injection, but apparently this also removes dots from the email address being verified, and then obviously the url does not coincide with what I entered, yielding 404.
Solution: simply add the dots in the url and it works.