GSI Forum: Tracking » Different x-y resolutions

Home » PANDA » PandaRoot » Tracking » Different x-y resolutions

Show: Today's Messages :: Polls :: Message Navigator

Different x-y resolutions [message #12295]

Tue, 19 July 2011 13:16

Simone Bianco
Messages: 29
Registered: January 2009

continuous participant

From: *cb.uni-bonn.de

Dear Tracking experts,

I am simulating simple events with 4 pions (2pi+ and 2 pi-) with a momentum of 1GeV/c, which are propagated from (0,0,0). I am generating these particles with an homogeneus distribution in phi and in theta (where theta is restricted to the range [20,140]°).
The simulations are performed with all the detectors in, but I set as active only the MVD, the Stt, the GEMs and the forward tracer.
I perform my reconstruction using:
PndMvdRiemannTrackFinderTask,PndSttTrackFinderReal,PndSttMvdTracking,Pnd RecoKalmanTask,PndMCTrackAssociator,PndPidCorrelator (with pion hypothesis),PndPidIdealAssociatorTask.
At the end of this chain I am running some analysis using the PndVtxPoca vertex finder.
I fill histograms with the three components of the reconstructed vertices. As you can see in the attached figures I get a significantly different sigmas for x and y.
index.php?t=getfile&id=6523&private=0

X always looks worse (even with different momenta and theta ranges).
I have already tried with different topologies like using two particles instead of four, or using pions of the same charge, but I always get worse results for X.
I tried with different vertexing tools (POCA, Ralf's fast fitter, another implementation of the POCA) and I always noticed this behaviour. It really seems to come from previous steps since if I try to rotate of 90° the tracks just before running the POCA vertex finder I obtain symmetrical results (worse Y than X, see the second figure attached).
index.php?t=getfile&id=6524&private=0

Does any of you have an idea about possible reasons of this effect?

Thanks in advance.

Cheers,

Simone

Attachment: Vtx-0-0-0-1GeV-4Pions.png
(Size: 32.38KB, Downloaded 515 times)
Attachment: Rotation-Vtx-0-0-0-1GeV-4Pions.png
(Size: 32.28KB, Downloaded 459 times)

Report message to a moderator

Re: Different x-y resolutions [message #12298 is a reply to message #12295]

Tue, 19 July 2011 13:25

StefanoSpataro
Messages: 2736
Registered: June 2005
Location: Torino

first-grade participant

From: *to.infn.it

Have you tried the PndKinVtxFitter? There I do not see strong differencies.

Report message to a moderator

Re: Different x-y resolutions [message #12300 is a reply to message #12298]

Tue, 19 July 2011 18:10

Simone Bianco
Messages: 29
Registered: January 2009

continuous participant

From: *cb.uni-bonn.de

I have not done it yet. I will try this now and report about the results I obtain. Thanks for your hint

Report message to a moderator

Re: Different x-y resolutions [message #12302 is a reply to message #12298]

Tue, 19 July 2011 21:52

Simone Bianco
Messages: 29
Registered: January 2009

continuous participant

From: *dip0.t-ipconnect.de

Hi again, this is what I get using the PndKinVtxFitter:
index.php?t=getfile&id=6525&private=0

X is still significantly worse than Y

Attachment: PndKinVtx.png
(Size: 49.16KB, Downloaded 356 times)

Report message to a moderator

Re: Different x-y resolutions [message #12303 is a reply to message #12295]

Wed, 20 July 2011 08:40

Jens Sören Lange
Messages: 193
Registered: June 2005

first-grade participant

From: *physik.uni-giessen.de

Hi Simone,
one idea: which field are you using?
PndMultifield("FULL") or PndMultifield("SOLENOID") only?
(i.e. can you maybe try to switch off the dipole field?)
best regards, Soeren

Report message to a moderator

Re: Different x-y resolutions [message #12304 is a reply to message #12303]

Wed, 20 July 2011 11:13

Simone Bianco
Messages: 29
Registered: January 2009

continuous participant

From: *cb.uni-bonn.de

Hi Soeren,

I have never tried this before, so I am now sorprized to see that setting in the simulation macro:

PndMultiField *fField= new PndMultiField("SOLENOID");
fRun->SetField(fField);

I get really bad results: I nearly never get all the four pions reconstructed and anyway their momentum is not the one set in the particle generator. This sounds really strange to me since I am shooting the pions in the theta range [20,140], so I would expect the dipole not to play any role in their reconstruction.
What am I doing wrong?

Attachment: runSimPGun.C
(Size: 4.70KB, Downloaded 207 times)

Report message to a moderator

Re: Different x-y resolutions [message #12306 is a reply to message #12304]

Wed, 20 July 2011 16:22

Jens Sören Lange
Messages: 193
Registered: June 2005

first-grade participant

From: *physik.uni-giessen.de

Hi Simone,

1.) my idea, that it could have something to do with the B field, came from the X and Y differences which were observed for luminosity monitor (which was to my knowledge the only time, that any azimuthal asymmetry was reported). Now I re-checked, and I found that I was wrong: it was not the dipole field generating the effect, but the aperture. See

http://forum.gsi.de/index.php?t=tree&goto=9206&rid=0&S=77db7 7666b257eeb980ffbd17eec1d35&srch=Jost#msg_9206

However, same as the dipole field, the effect should be forward peaked.

2.) HOWEVER, your result shows, that there is an effect even in your polar angle range.

After all, there might be an effect which was probably never seen before because you are looking at very small track DCA resolutions (50-60 um), but the B field grid is (if I remember correctly) in the central region 4 cm point-to-point distance (with linear interpolation between the points).

I checked field/PndMultiField.cxx

        

if (Map=="FULL") {

            PndTransMap *map_t= new PndTransMap("TransMap", "R");
                PndDipoleMap *map_d1= new PndDipoleMap("DipoleMap1", "R");
                PndDipoleMap *map_d2= new PndDipoleMap("DipoleMap2", "R");
                PndSolenoidMap *map_s1= new PndSolenoidMap("SolenoidMap1", "R");
                PndSolenoidMap *map_s2= new PndSolenoidMap("SolenoidMap2", "R");
                PndSolenoidMap *map_s3= new PndSolenoidMap("SolenoidMap3", "R");
                PndSolenoidMap *map_s4= new PndSolenoidMap("SolenoidMap4", "R");

                AddField(map_t);
                AddField(map_d1);
                AddField(map_d2);
                AddField(map_s1);
                AddField(map_s2);
                AddField(map_s3);
                AddField(map_s4);

        }else if (Map="DIPOLE") {
                PndDipoleMap *map_d1= new PndDipoleMap("DipoleMap1", "R");
                PndDipoleMap *map_d2= new PndDipoleMap("DipoleMap2", "R");

                AddField(map_d1);
                AddField(map_d2);

        }else if (Map=="SOLENOID") {

                PndSolenoidMap *map_s1= new PndSolenoidMap("SolenoidMap1", "R");
                PndSolenoidMap *map_s2= new PndSolenoidMap("SolenoidMap2", "R");
                PndSolenoidMap *map_s3= new PndSolenoidMap("SolenoidMap3", "R");
                PndSolenoidMap *map_s4= new PndSolenoidMap("SolenoidMap4", "R");

                AddField(map_s1);
                AddField(map_s2);
                AddField(map_s3);
                AddField(map_s4);
        }

so when you change from "FULL" to "SOLENOID", it means:
it is the SAME solenoid maps, but only the dipole map and the trans map IN ADDTION (!).

In the moment, I don't understand why you see such a strong effect for the dipole field. The best would be to switch off the B field completely, but then of course the track fitter does not work for straight tracks. I have the feeling that the track fitter also uses the field map, and then fails if B field in Geant and fitter are different. But I don't know where to set the field map for the fitter. I hope that someone else has a clever idea.

Soeren

Report message to a moderator

Re: Different x-y resolutions [message #12307 is a reply to message #12302]

Wed, 20 July 2011 17:12

Elisa Fioravanti
Messages: 84
Registered: January 2008

continuous participant

From: *47-79-r.retail.telecomitalia.it

Hello Simone,

I'm studing the pi+pi-pi+pi- analysis with the dataset available on GRID (pandaroot version july11).
I would like to show you the resolution that I have with the PndKinVtxFitter, in the STT case.
As you can see, in my case the X and Y resolution are almost the same.

best
Elisa

Attachment: vertex.png
(Size: 60.40KB, Downloaded 199 times)

Report message to a moderator

Re: Different x-y resolutions [message #12308 is a reply to message #12307]

Wed, 20 July 2011 17:17

Simone Bianco
Messages: 29
Registered: January 2009

continuous participant

From: *cb.uni-bonn.de

Hi Elisa,

I suppose there you have a forward boost for the system, which theta range do your pions span? Are these tracks measured with the mvd/stt/gems only or you use the forward tracker as well?

Cheers,

Simone

Report message to a moderator

Re: Different x-y resolutions [message #12309 is a reply to message #12308]

Wed, 20 July 2011 17:41

Elisa Fioravanti
Messages: 84
Registered: January 2008

continuous participant

From: *47-79-r.retail.telecomitalia.it

Hello Simone,

I used EvtGen and the four pions are simulated with phase space distribution.
And the tracks are measured with stt/mvd/gem only

Elisa

[Updated on: Wed, 20 July 2011 17:42]

Report message to a moderator

Re: Different x-y resolutions [message #12310 is a reply to message #12306]

Wed, 20 July 2011 18:34

Simone Bianco
Messages: 29
Registered: January 2009

continuous participant

From: *cb.uni-bonn.de

Dear Soeren,

I performed one test: I ran the simulation with the full field, but setting the fBeamMom to a small value, so that the map chosen for the dipole field is the least intense. With this setup I see no differences with the case in which fBeamMom was bigger (leading to a different dipole map). I would expect this change to show some effects if the x-y difference is in some way due to the dipole, but this doesn't seem to be the case. I will keep on investigating, thanks for your help!

Best regards,

Simone

Report message to a moderator

Re: Different x-y resolutions [message #12311 is a reply to message #12310]

Thu, 21 July 2011 09:25

Tobias Stockmanns
Messages: 489
Registered: May 2007

first-grade participant

From: *ikp.kfa-juelich.de

Hi Simone,

it is possible to set the magnetic field to a constant value without using the field maps. This is done in PndConstField.

Maybe you can try this method to exclude any effects of an asymmetric magnetic field.

Cheers,

Tobias

Report message to a moderator

Re: Different x-y resolutions [message #12322 is a reply to message #12311]

Thu, 21 July 2011 17:54

Simone Bianco
Messages: 29
Registered: January 2009

continuous participant

From: *cb.uni-bonn.de

Thanks Tobias, the constant field worked fine. Using the same parameters as before I got really similar results:
index.php?t=getfile&id=6546&private=0

So, this should exclude effects of asymmetries in the magnetic field.

I tried to select smaller theta ranges and what I notice is that in the "forward" part everything works fine. For example here you see what I obtained (always with four pions of 1GeV/c) limiting the theta range to teh range [30,40]°:
index.php?t=getfile&id=6547&private=0

Increasing theta the situation gets worse. This is what I obtained in the range [60,70]:
index.php?t=getfile&id=6548&private=0

Cheers,

Simone

PS: all these plots were obtained using the POCA vertex finder

Attachment: ConstField_20_140deg.png
(Size: 30.50KB, Downloaded 335 times)
Attachment: ConstField_30_40deg.png
(Size: 33.07KB, Downloaded 396 times)
Attachment: ConstField_60_70deg.png
(Size: 33.21KB, Downloaded 391 times)

Report message to a moderator

Previous Topic:	TPC signal data available on GRID
Next Topic:	PndSttMvdGemTracking with MC pdg.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Apr 28 03:55:30 CEST 2024

Total time taken to generate the page: 0.00928 seconds