2008/04/29
Čerenkov radiation (II)
Just a brief note about the Čerenkov radiation, that it was already mentioned here. I found photos of this blue water in a German neutron research facility.
2008/04/23
La suelta
This morning around 9 zulu in the morning (zulu means Coordinated Universal Time, locally was 11), I flew the instructors leader. I did it more or less like other days but a little bit nervous because this instructors was flew with me to evaluate if I am already able to fly alone.
After 4 touch and go, the tower calls as to say this will be last one because other traffics wait to do the same maneuver. This instructor ask the tower if can be possible to land brings himself down because the pilot student is able to practice one circuit alone. The tower was agree...
After land, back to Romeo 2, Carles (the instructor) says me 'bye, bye', then I say to the tower 'Echo Romeo Victor, listo para rodadura'. Tower: 'Roger, Echo Romeo Victor, ruede a punto de espera 13'.
Two other traffics was on the wait point, and when I was ready I said to the tower and wait for permision. When my torn arrives: 'Echo Romeo Victor, después del tráfico en salida entre y mantenga detras', then 'después del tráfico en salida, entrar y mantener detras, Echo Romeo Victor'. And just before stop in the line radio says 'Echo Romeo Victor, viento calma, con precedente que mantendrá en circuito, autorizado a despegar 13'; where is the moment 'con precedente a la vista, autorizado a despegar 13, Echo Romeo Victor': full engine and at 60kt rotation speed and go to the air flying alone...
First, cross wind then tail wind, apply the pre-landing procedure and notify the tower that I'm turning left to base 'con precedente a la vista'. 75kt watching the landing way on my left. Turn left to final approach, control the landing way and my air speed. A second flap point is required but the landing maneuver was fine. Free way to the tower and came back to Romeo 2. Carles was there waiting for me to ask my impresions: simply incredible! Really nice! He gives me the suelta!
After 4 touch and go, the tower calls as to say this will be last one because other traffics wait to do the same maneuver. This instructor ask the tower if can be possible to land brings himself down because the pilot student is able to practice one circuit alone. The tower was agree...
After land, back to Romeo 2, Carles (the instructor) says me 'bye, bye', then I say to the tower 'Echo Romeo Victor, listo para rodadura'. Tower: 'Roger, Echo Romeo Victor, ruede a punto de espera 13'.
Two other traffics was on the wait point, and when I was ready I said to the tower and wait for permision. When my torn arrives: 'Echo Romeo Victor, después del tráfico en salida entre y mantenga detras', then 'después del tráfico en salida, entrar y mantener detras, Echo Romeo Victor'. And just before stop in the line radio says 'Echo Romeo Victor, viento calma, con precedente que mantendrá en circuito, autorizado a despegar 13'; where is the moment 'con precedente a la vista, autorizado a despegar 13, Echo Romeo Victor': full engine and at 60kt rotation speed and go to the air flying alone...
First, cross wind then tail wind, apply the pre-landing procedure and notify the tower that I'm turning left to base 'con precedente a la vista'. 75kt watching the landing way on my left. Turn left to final approach, control the landing way and my air speed. A second flap point is required but the landing maneuver was fine. Free way to the tower and came back to Romeo 2. Carles was there waiting for me to ask my impresions: simply incredible! Really nice! He gives me the suelta!
2008/04/19
Higgs field
In this moment when I am compiling my compiler, I am reading something about the Higgs field in 'Investigación y Ciencia' (the two months delayed Spanish version of Scientific American). With the sentence "In quantum theory, quantities such as mass are not set once and for all but are modified by quantum effects.", from the article "The incoming revolutions in particle physics", an interesting point came back to my mind.
There are many places where you can read, for example this article, from where the mass can come or if the mass is from the particle itself or it is a result with the Higgs field. But what came back was the question why the values of the mass are this ones and not another ones. Are they arbitrary selected or it has a reason.
As far as I can understand from this article, the Higgs boson mass/energy has to have a big relation with this values. Correct me if I am wrong but this should be one of the reasons why we need to turn on the LHC. The point where I am becoming really disoriented is when they talk about the Technicolor, and how to understand the Higgs is not fundamental itself but is made by a conjunction of pieces that we, probably, already know.
Really huge phenomenons are waiting to be discovered when this machine starts to produce de amazing torrents of data. Believe that Grid will be able to chew this information.
There are many places where you can read, for example this article, from where the mass can come or if the mass is from the particle itself or it is a result with the Higgs field. But what came back was the question why the values of the mass are this ones and not another ones. Are they arbitrary selected or it has a reason.
As far as I can understand from this article, the Higgs boson mass/energy has to have a big relation with this values. Correct me if I am wrong but this should be one of the reasons why we need to turn on the LHC. The point where I am becoming really disoriented is when they talk about the Technicolor, and how to understand the Higgs is not fundamental itself but is made by a conjunction of pieces that we, probably, already know.
Really huge phenomenons are waiting to be discovered when this machine starts to produce de amazing torrents of data. Believe that Grid will be able to chew this information.
Present and past, simultaneous
Did you ever thought to see an evolution in time needs to wait this time? People from the university of Heidelberg (in Germany) saw a pulsar under five different time perspectives at the same time. How to understand this? The explanation is the gravitational lensing.
In 10th April 2008 Nature you can find a short article about this and also in the HubbleSite you can find a good images about this. The source article is from The Astrophysical Journal, but only the abstract is accessible.
As far as I understand, the point is the galaxy in the middle. It curves the light from the quasar that cannot come directly to as (because something is in the middle) an it came from five different paths. The light travels different distances to arrives here, and it means each ways has differences on time scale. They arrive here at the same time, but then they need to start the trip on different moments.
In 10th April 2008 Nature you can find a short article about this and also in the HubbleSite you can find a good images about this. The source article is from The Astrophysical Journal, but only the abstract is accessible.
As far as I understand, the point is the galaxy in the middle. It curves the light from the quasar that cannot come directly to as (because something is in the middle) an it came from five different paths. The light travels different distances to arrives here, and it means each ways has differences on time scale. They arrive here at the same time, but then they need to start the trip on different moments.
2008/04/16
PyQt Qimage problem...
But this image on the top left is not that easy. Some times it presents the good feel, but under unknown conditions (and it happens many times, more that acceptable) the image is shifted horizontally. This is like if the width of the image was not well measured. But from the same sources, and the same dimensions, why some times happen and some times the image is perfectly drawn?
As a sample, giving an image like the beam on the left, the same data draw using a Qimage, presents the view on the right.
Maybe with a bigger beam could be easy to realize how the image is shown and its trapezoidal view.Code: At this point I want to write where a little bit of the code written for this proposal and some logs from the execution.
Basically, when the image is received by an event:
def eventReceived(self, EventSource, EventType, EventValue):
self._imagedata=array.array('B',EventValue.value).tostring()
self._imagedim = [EventValue.dim_x, EventValue.dim_y]
self.ImageResize()
self.emit(Q
And this ImageResize() method do:
def ImageResize(self):
self._image = QtGui.QImage(self._imagedata,self._imagedim[0],self._imagedim[1],QtGui.QImage.Format_Indexed8)With or without the scaled method this trapezoid imaging happens...
width,height = [self.width(),self.height()]
self._image = self._image.scaled(width,height,Qt.Qt.IgnoreAspectRatio,Qt.Qt.FastTransformation)
Actualization: One clue or cheat in this question, the image published from the device is an unsigned short! And on this transformations I was assuming to convert it to unsigned char. Changing the array transformation from a 'B' to an 'H' is not enough because the 12bit format is not supported in Qt.
Solved! Finally, with Tiago's help the solution arrives:
QtGui.QImage(self._imagedata,self._imagedim[0],self._imagedim[1],self._imagedim[0],QtGui.QImage.Format_Indexed8)
Where the second time that 'self._imagedim[0]' is referenced means 'bytesPerLine'.
Actualization: Something solved.
2008/04/10
the Swiss Light Source
This week I was on the SLS to be impregnated with their knowledge. I will do a report for my Alba's comrade, and a seminar is possible. Preliminary, the SLS building is constructed with wood (not the tunnel that is made of concrete).
We saw four beamlines (PX I, Super XAS, cSXAS, and LUCIA). But it was a work trip and much of the photographs taken are about hutch lockers, motors, monochromators, Pilatus detectors,... All of this things has to be explained one by one.
On the left, there are the Pilatus detector protected by a metallic sheet. When the beam is on, the X-Ray comes from the right side and the sample place is in the centre of this image (sometimes cooled).
But when the beam is on, you cannot come in to change the sample and that why something like this robotic arm in need.
We saw four beamlines (PX I, Super XAS, cSXAS, and LUCIA). But it was a work trip and much of the photographs taken are about hutch lockers, motors, monochromators, Pilatus detectors,... All of this things has to be explained one by one.
On the left, there are the Pilatus detector protected by a metallic sheet. When the beam is on, the X-Ray comes from the right side and the sample place is in the centre of this image (sometimes cooled).
But when the beam is on, you cannot come in to change the sample and that why something like this robotic arm in need.
Cern LHC Open Seasson (II)
After a comment received on the last post about the Cern visit, I realize much more about how luck I was. I know it's not the same, but I like to put here some other photos from the visit.
This ones are from the atlas detector. First of all we access to the controls room (where I take freak photos about the GUIs and how the information is shown). After a nice presentation, where the slides was passing automatically probably to avoid delays, we move to the first flour to watch a 3D video.
But the important thing is in the underground. They only allows us to see the detector from this point. (only two groups at the same time in the cave).
On the CMS detector, was different. They likes more to shows us the machine. After a little video we was directed to an elevator. Bad name because this goes 100m underground.
They shows you the machine in a guided tour, where main groups of around 15 can be. This gives much more agility to the visit.
From the CMS building, a visit to the accelerator cave was possible. But for safety reasons only one group of 5 persons was allow to be under ground. And was impossible for us to be there.
I repeat that I am sorry for the people that, after horrible waits, was not able to visit the Cern's news detectors. We was so lucky visiting two of the four new LHC detectors. One open day is not enough...
This ones are from the atlas detector. First of all we access to the controls room (where I take freak photos about the GUIs and how the information is shown). After a nice presentation, where the slides was passing automatically probably to avoid delays, we move to the first flour to watch a 3D video.But the important thing is in the underground. They only allows us to see the detector from this point. (only two groups at the same time in the cave).
On the CMS detector, was different. They likes more to shows us the machine. After a little video we was directed to an elevator. Bad name because this goes 100m underground.They shows you the machine in a guided tour, where main groups of around 15 can be. This gives much more agility to the visit.
From the CMS building, a visit to the accelerator cave was possible. But for safety reasons only one group of 5 persons was allow to be under ground. And was impossible for us to be there.
I repeat that I am sorry for the people that, after horrible waits, was not able to visit the Cern's news detectors. We was so lucky visiting two of the four new LHC detectors. One open day is not enough...
2008/04/07
Cern LHC Open Seasson
In an hour I'll fly to visit the SLS in Zurich, but before I want to write something of this weekend visit to the Cern Open day. Mainly, if you think this machine is huge, probably you didn't have enough imagination to realize how huge it is. It is impressive, giant.
First of all, we visit the Atlas experiment. but the camera (worst mine, its all an poor) is not able to put everything in a picture. After lunch we went to the CMS, at the other side of the ring. Neither good photos but something to put here.
This detector is really compact and they already have it open, and is perfect for the visitors. You feels really small in front of this machine.
Waiting to collect more photos...
First of all, we visit the Atlas experiment. but the camera (worst mine, its all an poor) is not able to put everything in a picture. After lunch we went to the CMS, at the other side of the ring. Neither good photos but something to put here.
This detector is really compact and they already have it open, and is perfect for the visitors. You feels really small in front of this machine.Waiting to collect more photos...
2008/04/03
Our private tango guinness record
Wahoo! By now, and without a definitive confirmation we have a 'tango device server devices record'. I think this sentence is not much clear. Tango is a distributed systems who controls some synchrotrons, and like in unix (where everything is a file) in tango everything is a device. One device is one agent in this distributed systems, and this agents are running on a machine where the main process of this is the device server.
Normally, a tango developer has some devices controlled by a devices server, and our logics guides us to, when you have many devices split this between more instances of this device server. So, if you have ccd camera devices, like 50; and you likes to control them, normally you creates at least a device server for each sector, and this device server controls all the cameras in an specific sector. Easy (I think).
But what happens when you have a pool of devices to control a section of this machine (in this practical case the linac to booster transferline [LTB]) and you don't wanna a split this? Then we arrive to this situation where the pool device server has to manage 240 devices only in the first segment of the ltb.
I need to confirm if in the vacuum control system we don't have something in this level. Waiting for this confirmation, we are able to say (at low voice) that we have a record!
Actualization: This record has been overcome! We realize that the pool was consuming too much cpu when this large number of devices are not doing anything. Known this, a deadlock was solved and a stress test creates 1000 devices with non cpu consumption when they are free.
Normally, a tango developer has some devices controlled by a devices server, and our logics guides us to, when you have many devices split this between more instances of this device server. So, if you have ccd camera devices, like 50; and you likes to control them, normally you creates at least a device server for each sector, and this device server controls all the cameras in an specific sector. Easy (I think).
But what happens when you have a pool of devices to control a section of this machine (in this practical case the linac to booster transferline [LTB]) and you don't wanna a split this? Then we arrive to this situation where the pool device server has to manage 240 devices only in the first segment of the ltb.
I need to confirm if in the vacuum control system we don't have something in this level. Waiting for this confirmation, we are able to say (at low voice) that we have a record!
Actualization: This record has been overcome! We realize that the pool was consuming too much cpu when this large number of devices are not doing anything. Known this, a deadlock was solved and a stress test creates 1000 devices with non cpu consumption when they are free.
Subscribe to:
Posts (Atom)
