MCPcopy Index your code
hub / github.com/TeamAtomECS/AtomECS

github.com/TeamAtomECS/AtomECS @v0.7

Chat with this repo
repository ↗ · DeepWiki ↗ · release v0.7 ↗ · + Follow
413 symbols 676 edges 65 files 128 documented · 31%
What it actually does AI analysis from the code graph — generated when you open this
loading…
README

AtomECS

Simulate cold atoms with rust.

New: Paper out now on arxiv

crate_version crate_version build unit_tests

atomecs is a rust crate for simulating ultracold atom experiments. It supports numerous features: * Laser-cooling of atoms by optical scattering forces. * Doppler forces on atoms that scatter light, including the random fluctuations that give rise to the Doppler temperature limit. * Magnetic fields, implemented on a grid or through simple analytical models. * Hot atoms generated by an oven. * Hot atoms generated on the surface of a simulation volume (eg, to simulate thermal vapor in a chamber). * Cooling light beams, defined by their detuning and gaussian intensity profiles. * Volumes that define bounds for the simulation. * File output in binary or text format. * Thorough unit testing to ensure simulation results are correct. * Good parallel performance on modern multi-core CPUs. * Simulations can be wrapped using python/matlab, as shown in the source_optimisation_example or the matlab examples. * Optical dipole force traps. * Confinement of atoms by magnetic fields, e.g. quadrupole and TOP traps.

Getting Started

Instructions for installing rust can be found on the rust website, which includes the rust toolchain and cargo command line tool.

After cloning this repository using git, you can run examples using the cargo command line tool, e.g. cargo run --release --example 1d_mot. The matlab examples show how to load and plot simulation results.

You can build the program documentation using cargo doc.

Data-oriented design

atomecs follows the data-oriented Entity-Component-System (ECS) pattern, which is implemented using specs. ECS is well suited to high-performance simulations, and is sufficiently flexible to accomodate changing design goals.

If you are unfamiliar with data-oriented design - for instance, if you come from an object-oriented background - it is strongly recommended that you read up before diving into the code. Some useful ECS resources are: * Mike Acton's GDC talk, which discusses the advantages of ECS + DOD (in the context of the Unity game engine). * The specs book which describes the ECS used in atomecs. * Although written for Unity/C#, the concepts in the Unity Entities Package Documentation are very useful to understand.

Current Limitations

  • atom-atom interactions are not implemented. Most of our current work deals with atom sources, which have low steady-state number densities, so we haven't implemented this. Results for steady-state 3D MOTs should be interpreted carefully.

Getting Involved

Our goal is to make AtomECS user-friendly, with friendly developers! Please feel free to use the issue tracker to ask questions, or join the conversations happening within the issues.

If you would like to submit a contribution: * Take a look at the issues page to see if there is something suitable for a new user. * Freely develop and change your own fork. * When a feature is finished, raise a pull request to merge your changes back into the AtomECS repository. The team will openly review your code and suggest changes/improvements.

The Team

The current developers of atomecs are: * Dr. Elliot Bentine, Oxford * Dr. Tiffany Harte, Cambridge * Xuhui Chen, Oxford * Maurice Zeuner, Cambridge

The long term goal for atomecs is to have a complete simulation suite for cold atom experiments. If you'd like to get involved in development, please do!

Extension points exported contracts — how you extend this code

Plugin (Interface)
(no doc) [12 implementers]
src/simulation.rs
Format (Interface)
A trait implemented for each file output format. [4 implementers]
src/output/file.rs
Volume (Interface)
(no doc) [3 implementers]
src/shapes.rs
TransitionComponent (Interface)
A transition which can be used as a component. [1 implementers]
src/laser_cooling/transition.rs
MaxwellBoltzmannSource (Interface)
(no doc) [2 implementers]
src/atom_sources/precalc.rs
Lerp (Interface)
(no doc) [1 implementers]
src/ramp.rs
BinaryConversion (Interface)
(no doc) [2 implementers]
src/output/file.rs
Surface (Interface)
(no doc) [3 implementers]
src/shapes.rs

Core symbols most depended-on inside this repo

build
called by 64
src/simulation.rs
add_plugin
called by 42
src/simulation.rs
sample
called by 35
src/atom_sources/mod.rs
calculate_rayleigh_range
called by 17
src/laser/gaussian.rs
build
called by 15
src/laser_cooling/mod.rs
step
called by 12
src/simulation.rs
build
called by 12
src/magnetic/mod.rs
pos_to_id
called by 8
src/collisions.rs

Shape

Class 158
Method 142
Function 95
Interface 13
Enum 5

Languages

Rust100%

Modules by API surface

src/magnetic/mod.rs20 symbols
src/sim_region.rs18 symbols
src/collisions.rs18 symbols
src/atom.rs17 symbols
src/output/file.rs16 symbols
src/laser_cooling/photons_scattered.rs16 symbols
src/atom_sources/oven.rs16 symbols
src/laser_cooling/mod.rs14 symbols
src/integrator.rs13 symbols
src/dipole/mod.rs12 symbols
src/simulation.rs11 symbols
src/ramp.rs11 symbols

For agents

$ claude mcp add AtomECS \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact