From baeuchle@th.physik.uni-frankfurt.de Wed Feb 8 20:52:39 2012 From: baeuchle@th.physik.uni-frankfurt.de (=?UTF-8?B?QmrDuHJuIELDpHVjaGxl?=) Date: Wed, 08 Feb 2012 20:52:39 +0100 Subject: [user@urqmd] New patch regarding isospin asymmetry Message-ID: <4F32D287.2030706@th.physik.uni-frankfurt.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear UrQMD-users, we have published a patch to resolve issues with isospin asymmetry: This is a bug-fix regarding isospin symmetry between meson-baryon and meson-antibaryon scattering as well as a false scaling factor for meson-antibaryon scattering: 1) previously, reactions like antiproton pi_minus would be calculated using the neutron pi_minus cross section instead of the (proper) proton pi_plus cross section. I.e. only the negative sign of the baryon ityp was stripped, but not the iso_3 components flipped, as is necessary for the full isospin symmetry. 2) all resonant antibaryon meson scattering cross sections were falsely reduced by a combinatorical factor of two which is needed for the scattering of strange mesons with strange antimesons of different type, e.g. kaon with anti-k*. This has been fixed as well. The largest impact of this patch will be on anti-baryon spectra at the LHC. Please find the patch attached to this mail and at . To apply the patch, please use the utility patch: $ patch -p0 < baryons.patch inside the directory where your copy of UrQMD is and recompile the code. You may need to delete the file tables.dat. If there are any further questions, do not hesitate to post questions to this list. Regards, Bj?rn B?uchle -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPMtKGAAoJEP3PGkynoDrpbQAP/3mktIxyKJ3XJIfG/xjYD90M X8EKUUfHSkVJpkIQ9iKxd6BPnmM58hHYlVTh9F9Hn8cMVCH3p5iNZzi1k3iHx9uA aSPROXzojsWm90oEj/WhItirW4R5jAdnAU3ApAUQxwJLtWIkNAU0m1bFJZ8hcTIG VAqqfgxyyCBl6WMeoMlM08nSJba99WtK1ZgSjXETfc4CLYNYaUWK/8PRDFWCTDlB hgNztwUiXbznnwQtpnDQIM89C4CLaxMt7lxrG28lKQwpYQxW00LRqnnz3MFQ51cM Qr5l5LhsTS0n8Lp86kppwaKIf/0bX7Vj6CghmIG90zuMZAx+AFFcj54dg/FCn217 0mCueLAD9iiMv4XEliVjoIllkSgFNu7gRxVLRLuz0WVFE5hRmWd0qQM60eEKu9hG zeWskQp8TIDa7fHCRGpB6op1+H3NlN3/Z4V/Y/5ZvrG3Hpl3Wo+wVzaNdSa9vdlL A7rK1MRhBqZdbzGDaxvHeq90dBsT/nAU3411e3FBP/5XSwTrGXHyQqrk0UjaN4bq BiIfqtAK6Pc8OfDjEJFGOmj8E/D/J7KCIuI44a5xFa4bb2poGMsPvlzFqmj99Q+0 bcAAsf9RN883xC/8m7dkMga5u4hGyVfhlYydBZgMFPSOXHoDi17g4Z37nKo+i9G9 NiY6sx0j2mYxDQ+sCtEo =w7vW -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: baryons.patch Type: text/x-patch Size: 3251 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: baeuchle.vcf Type: text/x-vcard Size: 491 bytes Desc: not available URL: From skvitek@gmail.com Fri Feb 17 18:07:34 2012 From: skvitek@gmail.com (=?KOI8-R?B?98nL1M/SIOvJ0sXF1w==?=) Date: Fri, 17 Feb 2012 19:07:34 +0200 Subject: [user@urqmd] Parsing of collision history file Message-ID: Dear UrQMD, Please, explain me the decay entry (" 1 2 20 ...") of the collision history file (ftn15). Where are the uin and id of in- and outgoing particles? In the next 3 lines of entry I can find them, but I cant't determine which of them is ingoing and which is outgoing. And the second question: how can I add information on leptons to the collision file? Is it necessary to use rQMD? With best regards, Victor P.S.: Sorry for my bad english. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baeuchle@th.physik.uni-frankfurt.de Sat Feb 18 08:47:25 2012 From: baeuchle@th.physik.uni-frankfurt.de (=?UTF-8?B?QmrDtnJuIELDpHVjaGxl?=) Date: Sat, 18 Feb 2012 08:47:25 +0100 Subject: [user@urqmd] Parsing of collision history file In-Reply-To: References: Message-ID: <4F3F578D.2040901@th.physik.uni-frankfurt.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear ??????, I am unsure what you mean with "uin". You can find the number of in- and outgoing particles as the first and second fields of the collision header, see page 22 of the User Guide [1]. In the example you give, this should be one ingoing and two outgoing particles (the twenty in your examples actually marks this as a decay, see page 26 of the User Guide). Concerning leptons: there is currently no lepton physics included in UrQMD. To my knowledge, the same is true for rQMD, but I'm not sure there. Hope this helps Bj?rn [1] http://urqmd.org/documentation/urqmd-3.3p1.pdf Am 17.02.2012 18:07, schrieb ?????? ??????: > Dear UrQMD, > > Please, explain me the decay entry (" 1 2 20 ...") of the collision history file (ftn15). > Where are the uin and id of in- and outgoing particles? > In the next 3 lines of entry I can find them, but I cant't determine which of them is ingoing and which is outgoing. > > > And the second question: how can I add information on leptons to the collision file? Is it necessary to use rQMD? > > With best regards, > Victor > > P.S.: Sorry for my bad english. > > > > _______________________________________________ > user@urqmd.org mailing list > https://th.physik.uni-frankfurt.de/mailman/listinfo/urqmd-user - -- - ------------------------------------------------------------ Bj?rn B?uchle Programm Coordinator Helmholtz International Center for FAIR HIC for FAIR Frankfurt Institute for Advanced Studies Raum 02|300 Ruth-Moufang-Stra?e 1 D-60438 Frankfurt am Main http://www.hicforfair.de/ ++49 (69) 798 47 532 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPP1eMAAoJEP3PGkynoDrpCrAQAKp6ZkcvPLaFijWD9Sbb5tFX AFFSnh6xJF2lrV6Mf7Bd1Q6/88MhrTRVwlFer2IMtUZHigf0uT9HM9gHV1vzfZit yTjoF/hPiHAYlGVPghDXsizIkj1Z/BJGQdbNgBCmTe+jZJEr1etNhee+U/X/PB7x phaan2tlX1wh61ery3Dda9Rgbv9eYgKCihziH4gt/EA4Mgg6Lo/qNMxwZdU2W77K v5LG4ki/a1fHUlk7O4XmA+LiPuB77PmTNeioREW7gmWGl2cQC3fJu5uucb/XYlmA GG077puBIKHbEJd53hzQZuVridOu7Y6CVU9rEcFm0FldZo2TsYWNV/1w0Af8xTXd Gj1wtl31ip3rI5iE1DvdslOnSgmkxoPy8WixcfzlSy1HfcT4XJ7OPYVWRaHDPhxY /a7//jWtQz/fO3xW0iu3S3Mt6UmWxTgVzDBGqJZI+e8z4qUJU7VxG7S7aNqetu67 3GRTn0ZkSGXnNB9u3Ym3zveFket2mlP+Sn4mw3ZEe9UxyohdQMXnIEdHnHdBXErA L1dTr0FWb7xEwB4L47io30/JSzbAyoDqEEvNyTkPmd8JBuSHXI5gq6abe5Q0XRpF gVkzdwpcp2lTBCbutOyCjyiJRZ+Ma9PU6rpoaeDR5nQ7o7rvhdZA3Zglq6Xcav7h YVYTkHnf/29J+/C4SsIB =IXbQ -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: baeuchle.vcf Type: text/x-vcard Size: 509 bytes Desc: not available URL: From skvitek@gmail.com Tue Feb 21 09:37:31 2012 From: skvitek@gmail.com (=?KOI8-R?B?98nL1M/SIOvJ0sXF1w==?=) Date: Tue, 21 Feb 2012 10:37:31 +0200 Subject: [user@urqmd] Parsing of collision history file Message-ID: Hello! "uin" - is an index of particle (col 1 in collision history file). So, if I have a decay "1 2 20 ...", the first line after header is ingoing and the second and third is lines of outgoing particles? But in this case in my collision file I get two and more particles with same index(not particle-ID) which are outgoing particles in different decays, with different parent process and collision partner(col 17 and 14). It worries me. Should it be like this? With best regards, Victor I am unsure what you mean with "uin". You can find the number of in- and > outgoing particles as the first and second fields of the collision > header, see page 22 of the User Guide [1]. In the example you give, this > should be one ingoing and two outgoing particles (the twenty in your > examples actually marks this as a decay, see page 26 of the User Guide). > > Concerning leptons: there is currently no lepton physics included in > UrQMD. To my knowledge, the same is true for rQMD, but I'm not sure there. > > Hope this helps > Bj?rn > -------------- next part -------------- An HTML attachment was scrubbed... URL: From graef@th.physik.uni-frankfurt.de Thu Feb 23 11:13:51 2012 From: graef@th.physik.uni-frankfurt.de (Gunnar Graef) Date: Thu, 23 Feb 2012 11:13:51 +0100 Subject: [user@urqmd] Parsing of collision history file In-Reply-To: References: Message-ID: <4F46115F.9030702@th.physik.uni-frankfurt.de> Dear Victor, yes, the first lines after the collision header always contain the ingoing particles and the next lines the outgoing particles. I am also not sure what you mean with "uin" hoewever, if you refer to column 1 in the collision entries (not the header) it is denoted as index in the user manual. It has no physical meaning whatsoever and is just for internal bookkeeping and usefull for code debugging. The index of an particle does not stay the same during a collision, so it's not possible to keep track of a single particle using this number. I hope this answers you questions. All the best, Gunnar Gr?f On 21/02/12 09:37, ?????? ?????? wrote: > Hello! > > "uin" - is an index of particle (col 1 in collision history file). So, > if I have a decay "1 2 20 ...", the first line after header is ingoing > and the second and third is lines of outgoing particles? But in this > case in my collision file I get two and more particles with same > index(not particle-ID) which are outgoing particles in different decays, > with different parent process and collision partner(col 17 and 14). > It worries me. Should it be like this? > > With best regards, > Victor > > > I am unsure what you mean with "uin". You can find the number of in- and > outgoing particles as the first and second fields of the collision > header, see page 22 of the User Guide [1]. In the example you give, this > should be one ingoing and two outgoing particles (the twenty in your > examples actually marks this as a decay, see page 26 of the User Guide). > > Concerning leptons: there is currently no lepton physics included in > UrQMD. To my knowledge, the same is true for rQMD, but I'm not sure > there. > > Hope this helps > Bj?rn > > > > > _______________________________________________ > user@urqmd.org mailing list > https://th.physik.uni-frankfurt.de/mailman/listinfo/urqmd-user From koreshev@mail.ihep.ru Wed Feb 29 11:36:14 2012 From: koreshev@mail.ihep.ru (koreshev) Date: Wed, 29 Feb 2012 14:36:14 +0400 Subject: [user@urqmd] Bug Message-ID: <4F4DFF9E.7000306@mail.ihep.ru> Dear Colleages! Even after applying the last patch to UrQMD 3.3p1 I still have, after about 1000000 events the message ***(E) wrong collision update (col) *** 213 125 2.58866460265146 9.69228624652365 anndex(dec): no final state found for: 0 0.00000000000000 0 please check minimal masses: m1,m1min,m2min and iso3 of decaying particle 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 0.00000000000000 Before I had its after about 10000 events, so it looks for me that "the problem with isospin" is not solved completely. Best Regards, Victor