California… off a cliff June 22, 2009
Posted by gordonwatts in university.3 comments
Well… I used to think it Washington was the worst. It still is, but California is doing is best to take the crown. I’m talking about the budget of course.
Washington state legislature cut support for University of Washington 26%. That would have been the end of UW as I know it – and I guess the state legislature knew it too. To prevent that they allowed us to raise tuition on undergraduates by 30% over the course of two years (30%!!!). Which we will do. This is old news now – the reality came down at the end of April. Final budgets are being drawn up and they are every bit as bad as we were worried at the time. But the institution will survive.
Most states escaped such dramatic changes. I think only Nevada was going to be hurt as badly as we were. California was bad when I wrote that post – about 10%. What I didn’t realize was the 10% depended on a bunch of initiatives being passed that would raise various taxes. Apparently the complete political establishment (and a lot of people I know, including me) fooled themselves into thinking this was going to pass. Ops! I think the only budget related initiative that passed was one making sure the legislature didn’t give themselves a raise!
The upshot is going to be nasty. Berkeley’s chancellor just laid it on the line:
…the campus now facing a budget shortfall of around $145 million — "a shocking number," he said, more than twice the size of the deficit expected just six weeks ago…
…Birgeneau said all campus units will be asked to cut their budgets by an average of 20 percent over two years, instead of the 8 percent cuts expected as recently as mid-May. Staff who survive these contractions — and, the chancellor emphasized, "there will be eliminations of staff positions" — will see their paychecks shrink.
"We can all collectively expect wage reductions in the neighborhood of 8 percent," reported Birgeneau, adding that the formula could include some combination of furloughs and actual pay cuts.
Wow – 8% pay cut? That sucks. I’ve got a lot of friends in the Ca system. If only UW had some extra cash I’d say we should be off hunting there!! Too bad we will also have a multi-year hiring freeze.
To be fair, the Ca budget isn’t final yet. And it could be some of this is a warning shot at the legislature. But if it is anything like the Washington legislature, all the Ca university system will get back is a big ***ger.
Back To Marseille June 20, 2009
Posted by gordonwatts in Marseille, travel.1 comment so far
Term is done. It was done a week ago. Next week I move back to Marseille for three months. Those of you who have followed this blog for a while know that I spent 2007-2008 there. Well… I’m going back. Ironically, in 2007-2008 I was really hoping that I’d see first collision at CERN when I was there (it is less than 4 hours door-to-door from Marseille to CERN). This time there is no hope (there was a power outage there today – I wonder if that affected the LHC’s state? Nope, not really!). I was lucky enough that IN2P3 had some money available to help fund my three month trip (thanks IN2P3!).
To celebrate my return there I put together a synth of some 1000-odd pictures I took of the train station when I was there last time. There is lots of cool stuff up there (check out this one of the Hubble repair mission).
Synth’s are a very cool way to arrange a large collection of photo’s of a single subject. At any rate, enjoy it. I’m going a little crazy trying to get everything ready for the trip!
BTW – I wasn’t able to make this 1000 image synth until I got my new computer with huge amounts of memory – during the synth process it always ran out of memory! The irony here is that synth code is 32 bit. I guess Windows 64 bit gives just a bit more memory space to 32 bit programs than the 32 bit version of windows!
It’s about the work, dummy June 18, 2009
Posted by gordonwatts in university.12 comments
I read this in an article on ars technica. First the setting:
When San Jose State University student Kyle Brady published the source code of his completed homework assignments after finishing a computer science class, his professor vigorously objected. The professor insisted that publication of the source code constituted a violation of the school’s academic integrity policy because it would enable future students to cheat. Brady stood his ground as the confrontation escalated to the school’s judicial affairs office, which sided with the student and affirmed that professors at the university cannot prohibit students from posting source code.
And second, the thing that made me decide to write this post:
Cory Doctorow shared his thoughts about the issue on Thursday in a blog post on BoingBoing. Doctorow suggests that assignments are ultimately more valuable to the students when the work that they produce can have broader purpose than merely fulfilling academic requirements. He also rightly points out that peer review of source code and studying existing implementations are both common practices in the real world of professional software development.
These are both compelling points and they illustrate how traditional academic sensibilities can be detrimental to the intellectual development of students.
Give me a break. This has nothing to do with any high end ideals. It has to do with work. In lower division courses there are only so many types of homework problems you can write without making something really complex, and in upper division courses creating a good problem that is hard, solvable, and interesting takes an immense amount of time. The professor of the course just wants to be able to re-use the homework problems – and cut/pasting the answer from the web is something he/she wants to make as hard as possible.
I wrote a bunch of problems for my graduate course this last year – they took a lot of work – I spent hours on them. I’d very much like to be able to reuse them – or reuse the core of the problem. If the solutions were widely available then that means I have that much more work I need to do next year.
I think, on its own, the answer to the question about a student posting their source code is clear: they should be allowed to do it. But the issue isn’t black and white when you get right down to it – that solution is a product of both the students and the professor’s sweat. Finally, actually saying that you can’t post code is totally unenforceable in this day and age (e.g. RIAA). There is also the basic fact that a student that decides to cheat is only cheating themselves… boy, that sounds kind-a lame, doesn’t it?
I don’t have an opinion in this particular instance. But I think the overly simplistic view that is taken is a bit sensationalist. Cory Doctorow wrote a much more nuanced bit:
But the convenience of profs must be secondary to the pedagogical value of the university experience — especially now, with universities ratcheting up their tuition fees and trying to justify an education that can put students into debt for the majority of their working lives. Students work harder when the work is meaningful, when it has value other than as a yardstick for measuring their comprehension.
I disagree. It isn’t just about convenience of the profs – it is about having a good course for the next student. It is about the professor learning what worked to teach the students this time and refining it next time – these things have to be factored in. Both the students and the professors, it seems to me, have a shared responsibility here.
Though a bit later on he seems to go off the rails (no pun intended):
I’ve always thought it was miserable that we take the supposed best and brightest in society, charge them up to $60,000 a year in fees, then put them to work for four years on producing busywork that no one — not them, not their profs, not other scholars — actually wants to read.
Well, gee. When you start learning something you have to start with the basics. You can’t start with Quantum physics – you need to understand a bit about mechanics, E&M, and other things – after all, quantum had better devolve to those in the macroscopic world! You can start out students on cutting edge research – we all do it when we take on undergraduate researchers – but they have to learn the basics too. It is, sadly, a fact of life.
If you don’t know how to start a program, how can you learn how to write cool code!?!?
BTW, if you read down, you can find a response from the student involved in this case.
Fixing up those Emails June 5, 2009
Posted by gordonwatts in TextToHTML.8 comments
Emails which contain links to images have long bothered me. I get a lot of them in my day job. They usually contains some descriptive text, then a link to a jpeg or an eps file, and then more text, and then more links.
Often they contain text that says “compare x and y” or similar. This is actually pretty painful: I have to click on all the links. Each image opens up in a separate web browser tab.
To compare them I have to click on each tab, back and forth. Never can see the images at the same time.
On my last plane ride back from Chicago I wrote a tiny little utility, TextToHTML, to take care of this:
You simply paste in the text from the email, click Render, and it will pop open one web page with all the text and images interleaved:
It also knows how to deal with eps files (it will download them locally and render them).
This thing is dirt simple. It can’t do password protected files yet, for example. Suggestions here in the comments or on the project web site are welcome, of course. Feel free to download and play!
Making an Inch an Inch June 3, 2009
Posted by gordonwatts in computers.add a comment
In one of my last posts I wrote about Bill Hill and his efforts to improve onscreen reading. For me this has always been about high resolution displays. It would seem that Bill, who has thought about this a lot more, agrees. When I buy a portable there are two criteria. First, it has to be a convertible tablet. Second it has to be high resolution. The high resolution is for one reason only: gorgeous rendering of PDF documents. The more pixels per letter the better the letter looks. It definitely works!
Bill is constantly raving about his brand new Apple (he is running Windows on it):
But I have to say, their displays were not in the same class as this 133ppi display from Apple. It’s stunningly bright and crisp.
The key here is crisp. I have a large 1280×1024 monitor at home. It has one of those glass screens – the ones that reflect and are really really bright. I’ve never seen my photographs look so good as on that screen. But pop-up a PDF and compare it to my 1080p 24” screen? No comparison. Looks a lot better.
There is one problem. The OS and web pages. They all render things much smaller than they are designed to.
In Bill’s blog postings, however, I discovered there was a way to configure Windows to set the DPI correctly. Basically, if you asked your computer to draw a line an inch long on your screen, it would come out an inch only if your screen was built at 96 DPI. My X61T is 147 DPI! That makes the text too small. So my 9 pt text appears as something much smaller, which can be a problem:
It’s especially complicated because humans need (not want, need) to read type which is between 9 and 13 points high. This dimension is dictated by the size of the foveal area in the retina of the human eye, which is only 0.2mm in diameter, with about 1.5 degrees of visual arc.
Ok. So at least Windows has something in it that will allow it to set the Pixel DPI. I set it to 147. Boom. The inch was really an inch (I’d never seen that before). But it was also clear that not much else would work! Web pages were a disaster. Many programs I depend on acted very oddly (who would have thought RealVNC would have so much trouble with a setting like this!?). Such a pity, but MS Office, and the OS itself looked pretty good. So I had to set everything back (to about 120 DPI). My impression from reading around is because most programming is done in terms of pixels, not in terms of actual sizes or lengths. I’d never given this any real thought when writing my own code.
BTW, I have a Lenovo X61T for my portable. The high resolution screen is great (hey, better than the Apple), but it isn’t as bright or crisp as I’d like it. Apparently that is because it is a tablet, so the digitizer takes the edge off it a bit. So it is a compromise machine in that sense.
AF 447: All anyone is talking about June 2, 2009
Posted by gordonwatts in travel.11 comments
I’m spending a week at an ATLAS meeting here in Geneva. The day I flew was the day of the horrible Air France 447 crash. The plane just disappeared over the Atlantic on its way from Rio de Janeiro, Brazil, to Paris, France. Just disappeared. It flew through heavy turbulence and a thunder storm. And just disappeared.
As I’m sure you’ve read by now modern airplanes (which this A330 is most certainly one of) are built to deal with these sorts of conditions. Being struck by lighting, flying through strong and gusty winds, etc. So what happened?
Of course, none of us know. But many of the group of people over here at CERN that I hang out with are from the USA. Which means we take these long distance flights all the time. In the past month I’ve taken the equivalent of two of these flights. The uncertainty is really getting to us. Most of us will be on one of these long distance flights (and some on a A330) in less than a week. So you can imagine…
There is another plane crash I remember – Swiss Air 111. This flight was going from JFK to Geneva in 1998. It happened during the CHEP 1998 conference. There were a bunch of people on that flight from the CHEP conference.
I guess one comforting thing for those of us that have to fly is that this is the first A330 crash ever (besides one initial test flight). Still, it is the main topic of conversation over beer and lunch right now. Which is probably just making it worse.
Regardless, our hearts go out to the folks that survived the passengers of 447. We are all connected to the people on that flight one way or the other.
UPDATE: Now that they have found the wreckage they are sending a submersible down there to search for the black boxes. Apparently, the submersible they are using is the same one that is used to repair the Antares experiment (a neutrino experiment on the floor of the ocean).
UPDATE II: I went to dinner last night with someone that was actively trying to get on that Swiss Air 111 flight. It was sold out, fortunately. He knew some people from BNL that were on that flight, on their way to CERN.
The Art Of Noise June 1, 2009
Posted by gordonwatts in science.4 comments
We like to say that science is deterministic. You do x,y, and z, and then a will happen. I 100% agree with this. Except when it comes to noise.
What is noise? This is part of the problem – it comes in so many forms. Noise is like a weed. We call a plant a weed when it doesn’t belong. Got grass in your garden? It is a weed. Got grass in your lawn? Definitely now a weed. Is your cell phone making buzz-buzz-buzz sounds on your computer speakers? Noise! Are you using the cell phone signal to talk? Not noise!
But electronic noise is more insidious than the weed analogy implies. If you have an iPhone you can do the following experiment. Sit down at a computer that has separate speakers – the key is that an exposed wire connects the speakers to the computer. Place the iPhone near the speakers*. Wait for a few minutes. Now you’ll hear the buzz-buzz-buzz. So you know the source – you put the iPhone near the computer and it makes that buzzing sound. Lets say you didn’t know that. You had the iPhone in your pocket, and you walked up to your computer – it would start buzzing. You’d notice that every time you were near you’d get the buzzing. You might conclude you were the source of noise (talk about a loud heartbeat!!). You’d be both right and wrong.
The beauty of science is that if you do a, b, and c, then x will happen. Electronic noise is very much about science – if you do x, y, and z then you’ll get noise. The problem is it is very very difficult to determine what x, y, and z are. Above x might be “walk near your computer”, and y might be “have iPhone in your pocket”. You might get x right away, and then give up on fixing the speaker. A computer is no good if you can’t be near it! If you figured out y you might be able to do something different (like leaving your iPhone across the room, or better shield your speakers).
This is why finding and diagnosing electronic noise is an art.
I was on shift for two nights last week. On Friday night we saw a strange noise pattern in D0’s calorimeter. The pattern of noise is called high noon. And it was in four crates of electronics – typical high noon noise is never seen in more than one crate at a time. Experts were here until 2am trying to figure out what the source was. No clue. Eventually they went home – have to investigate the next morning when everyone was awake. Impact on data seemed to be minimal, and the automatic noise detection algorithms seemed perfectly capable of detecting this type of noise.
There were other problems with the detector that night too. A muon phototube kept looking synchronization with the readout. Each time this happens an automatic system would rap its knuckles and bring it back into line. Finally, after it had lost sync about 20 times, we decided to hit it with a hammer: reset it. And lo… the noise in the calorimeter, which had been mocking us for the last 6 hours disappeared.
Keep in mind – the muon system is meters away from the calorimeter system. They share no common electronics – not even racks of electronics are shared by the two. But the muon system was acting like the cell phone, transmitting electronic noise and the calorimeter was acting like an antenna – the speaker wire – and picking up the noise. D0 has been running since 2001. As far as I know, no one had seen this particular failure mode before.
If anyone tells you science isn’t an art – that there is no room for creativity – they are full of it. There are a lot of unknowns in unsolved problems – and it takes some creativity to guess what those unknowns are. And that is also the point behind reproducibility – to make sure you found x, y, and z that produce effect a.
Long live art!
* BTW, the iPhone isn’t the only one that will do this, it is just the worst offender of any of the smart phones I’ve seen. And easy way to fix it is place the iPhone on some tin foil. I’m not sure if that is because the tin foil becomes an antenna and so the iPhone needs less power to communicate with the tower or because it provides some shielding. But it works.
See? Art!