From: Andras V. <and...@ui...> - 2014-03-15 12:22:39
|
Hi Raimar, The reason is historical: the ParticleCavity bundle was designed to cover the 4 usecases appearing in 1particle1mode.cc, which all fulfill this requirement for physical reasons, so it seemed a good idea to introduce this check against erroneous parameter-passing to this script. That is, it was not designed as a really generic element. (The same applies to some other interaction elements.) Please feel free to extend the element (constructor overloads, etc.) at your leisure, I also do not find it a good idea to write a specialized custom interaction for this case, especially because we claim that the supported interaction elements are of "general purpose". Best regards, András On Fri, Mar 14, 2014 at 3:54 PM, Raimar Sandner <rai...@ui...>wrote: > Hi András, > > I am trying to simulate particles moving along a cavity, pumped > transversally. > > Could you explain to me the reason for UnotEtaeffSignDiscrepancy? Why is it > not allowed to have Unot<0 (cooling regime for DeltaC<0) but still > VClass>0? > > Also, to compare my simulation to Wolfgang's result, I would need to set > Unot=0 and still have eta>0 in the Hamiltonian eta(a^dagger m(x) + h.h.). > The > constructor of ParticleAlongCavity does not allow to set the parameters > independently in such a way. Du you think such a generic constructor would > be > of general interest to have it in the framework? I would like to avoid > maintaining my own specialized interaction for this purpose. > > Very best regards > Raimar > |