|
Yesterday I returned from Montana, USA. The conference (International Conference on Magnetic Resonance Microscopy) was awesome, traveling was good and the Americans are weird; in particular their food and cars In a few hours, I am leaving to visit the ICMRM, a conference about physics (magnetic resonance and stuff like this) in Montana. It will be my first time in America, but a very short time: just a week. Hello you out there! I just started running the first serious test of the system I’ve developed during this year’s Google Summer of Code. If I wanted to put it in sensational words, the test could be called “Distribution of Particle Physics High Performance Computing Jobs among Multiple Computing Clouds”; just to get some readers How tides, lakes and trains influenced measured particle masses in the Large Electron-Positron Collider at CERN, is described in a very impressive and colorful way in a citation in this wikipedia article: During development, a system running ATLAS Software has to be tested and validated. There are some standard tests that almost don’t need any input data, stress the system and — if they run properly — are a (very) good indicator that everything is set up correctly. I talk about the so-called JobTransforms. By combining these JobTransforms, the so-called Full Chain can be run — a convenient test. In this blog post I summarize what’s behind the Full Chain and provide a shell script to easily run it. |
|
|
Copyright © 2010 Jan-Philip Gehrcke 34 queries. 0.286 seconds. |
|
.