-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evaporation #81
Comments
Hey there, The collision module is still being developed by @DavidGarrick so I'll tag him and see what he has to say. Are you certain your parameters for atom number and temperature will lead to runaway evaporative cooling? If number is too low then the evaporation can fail and the density starts decreasing instead of increasing over time |
Thanks for the quick reply! I tried putting 1,000,000 atoms at the beginning (which I guess is enough?) with cloud radius of about 12 μm and T about 50 μK. The density was increasing for about 1 s while the increasing rate getting lower, then start from 1 s, where I still had ~ 600 ,000 atom left, the density started decreasing. |
What species are you stimulating and what is the s-wave scattering length you are using? Also, what does the phase space density look like during evap? |
The PSD does go up in whole process, I was simulating Rb, the sigma I used was 3.5e-16, same as in the "top_trap_with_collisions" example. |
Hi, As Elliot says this sounds like you aren't getting runaway evap. This could be that the initial density is too low (though 1e6 atoms sounds reasonable), or it could also be that you are evapping too quickly and the cloud doesn't have time to thermalise as atoms are removed. I am still in the process of improving the collisions system, which includes automatically rescaling the spatial partitioning system to account for significant changes in the cloud size or density. You could try pulling the collisions_upgrades branch and using that. This code runs and produces sensible looking results, but I haven't yet compared to experimental data as a final test. If you don't use that, make sure your spatial partition cell size is a good size - containing on average ~30 particles, but also not more than around 5-10% of the cloud size. This can be hard to achieve when the cloud density changes a lot. I think the 3.5e-16 value for the Rb cross section is a factor of 2 too small, since I missed the bosonic enhancement factor when I first estimated it. Again, I haven't compared to experiment. I'd suggest correcting the cross section and slowing the evap process a little. Also calculate your collision rate throughout the process and check that it is neither very low nor too high. If it is very high you need to ensure that the simulation timestep is smaller than the mean free time for a particle, and you also could be in a hydrodynamically limited regime. |
Cross reference #14 |
@d-garrick Hi, Thanks a lot for the advice. I'll go through it and see if I get any better results. |
@d-garrick Hi, Should I expect the number of box to be the cube of an integer? as the number of boxes is set same for each dimension, or am I missing something? I was trying to dig into the collision data from the tracker but found the total number of boxes for each step (I was using the dynamic cell partition branch) doesn't have an integer cubic root. |
Hi, The number of total cells is the cube of the number along each direction, but the system will only consider boxes that actually contain any atoms. This goes for both the collisions loop and the tracker. Presumably if you check how many atoms are in each box that the tracker outputs, you will find they all contain at least one atom. |
Hi, Guys I started the simulation with 1e5 particles, the positions and velocities are drawn from normal distributions, the std for the position and velocity distribution is 1.2e-5 (12 μm) and 0.03 m/s, respectively. I have two gaussian beams crossing each other with a 60 degree angle between them. Each beam has wavelength of 1064e-9 and e_radius of the power of each beam decreases from 5w to 0.023w in the time range of 5.7 s, after I hold the beam power at 5w for 0.1s. So The total simulation time is 5.8s, where I "load" the odt for 0.1s then do the evap cooling for another 5.7s. The collision parameters are as below: The partition parameters (I am using @d-garrick 's branch that repartition the box in each step): I am not using the losses options in this case. The capture region is a sphere of r = 5e-4. Another thing I think might worth noting is that I define the radius of the cloud as following, The radius of the cloud is then defined as Then I can calculate volume and density based on this radius. I'm not sure if I'm missing something substantial, so --Yang |
Hey Elliot @ElliotB256
I'm trying to simulate a cross beam evaporative cooling in ODT, I have two cross gaussian beam setup, the power of each beam decreases from 5 W to 0.02 W (wavelength: 1064 nm and spot size: about 35 μm) in a time range of around 6 s. Atoms are initiated at around ~ 50 μK.
My question is, is the density of the atom cloud supposed to be increasing in this whole process? In my simulation, the density increased a little at the beginning then started to decrease until the end. If it really should be increasing then should I consider tunning the collision parameters? or is there anything else you think could contribute to this issue?
The text was updated successfully, but these errors were encountered: