Embodiments of the present invention generally relate to designing electromagnetic coils.
Electromagnetic coils are used to create a magneto-optical trap (MOT) which is an apparatus that uses a combination of laser cooling and magnetic fields to produce cold, trapped, neutral atoms. These cold atoms can then be used for various applications such as quantum computers and quantum sensors (e.g., high precision clocks).
However, the traditional structure of a MOT is cumbersome. Conventional MOT geometry uses laser beams (e.g., six) that lie along at least two perpendicular planes. Also, the laser beams have to be arranged so they are not occluded by the coils in the MOT. These requirements result in bulky MOTs that are not suitable for many compact applications.
Miniaturizing the MOT design often requires unorthodox approaches to generating the magnetic field for a MOT, such as simply “guessing-and-checking” or intuition-guided design of the coils to result in more compact MOT design. More robust and time efficient solutions for designing electromagnetic coils are needed.
One embodiment herein is a method that includes providing a constraint for designing a magnetic coil and generating a shape of the magnetic coil that satisfies the constraint by iteratively: calculating a magnetic field generated by the shape, determining, using an objective function, a closeness between the magnetic field generated by the shape and a desired magnetic field, and adjusting the shape based on the closeness and to satisfy the constraint.
Another embodiment herein is a method that includes providing a constraint for designing a magnetic coil for a MOT and generating a shape of the magnetic coil that satisfies the constraint by comparing a magnetic field generated by the shape to a desired magnetic field for the MOT.
Another embodiment herein is a magnetic coil that includes a current carrying component configured to generate a magnetic field for trapping atoms in a MOT, where the current carrying component is non-planar.
Another embodiment herein is a MOT that includes a first magnetic coil comprising a first current carrying component configured to generate a magnetic field for trapping atoms in the MOT where the first current carrying component is non-planar and a second magnetic coil comprising a second current carrying component configured to generate a magnetic field for trapping atoms in the MOT where the second current carrying component is non-planar.
So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the disclosure, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only exemplary embodiments and are therefore not to be considered limiting of its scope, may admit to other equally effective embodiments.
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements and features of one embodiment may be beneficially incorporated in other embodiments without further recitation.
Embodiments herein describe techniques for designing an electromagnetic coil. The coil can include a coil mount where current-carrying wires are wrapped around the mount, or a current-carrying bar where the electric current flows through the part itself. In one embodiment, the electromagnetic coil can be used for a MOT, but the techniques herein can be used to design coils for other applications such as an electrical transformer, electrical generator, electrical motor, and the like.
In one embodiment, the coils are designed for an application that is constrained geometrically, spatially, by power requirements, a required field strength, field geometry, alignment with laser beams, and the like. These constraints can limit the shape of the electrical coil. An engineer could design a coil to meet a constraint (e.g., a coil that fits inside a particular space) but then a simulation should be run to verify its performance. However, simulations for some applications can be compute intensive and can take a substantial amount of time. Instead, the embodiments herein determine a shape (or shapes) of electrical coils that satisfy the constraints before executing a costly simulation. This can be done using an objective function that indicates how close a magnetic field generated by a current design is to a desired (or ideal) magnetic field. For example, for a MOT, the desired or ideal magnetic field is known. The objective function can then indicate how close the magnetic field for a current coil design is to the desired magnetic field. A metaheuristic algorithm or a machine learning (ML) algorithm can then adjust the shape (e.g., deform the current coil shape or try a different coil shape) using the output of the objective function. The process can repeat until the objective function reaches a threshold—e.g., identifies an optimal coil design.
Once an optimal coil shape (or multiple optimal coil shapes) is identified, then a simulation can be performed to ensure the coil shape performs as desired. For example, the coil shape can be used in a full, Monte Carlo MOT simulation to determine how well it traps and cools atoms. Advantageously, the simulation only has to run once to verify an optimal coil shape, unlike other solutions where a full simulation is run each time a new coil shape is tested. These techniques can also be applied to other applications were a desired magnetic field is known. That is, using an objective function, a magnetic field for a current coil shape can be compared to a desired magnetic field. The output of the objective function can then be used to iteratively adjust the coil shape until identifying an optimal shape. Thus, only the magnetic field of the current coil shape is determined during each iteration. Once the optimal coil shape is identified, then a full simulation of the application (e.g., a MOT, transformer, generator, motor, etc.) can be run using the optimal coil shape to verify its performance, thereby reducing the amount of time and compute resources needed to identify an optimal coil design.
The memory 115 stores a magnetic field calculator 120, a coil deformer 130, an objective function 135, and a MOT simulator 140. The magnetic field calculator 120 (e.g., a software application) determines (or calculates) a shape of a magnetic field generated by a magnetic coil that is currently being tested. Further, the shape of the coil being tested can be limited by one or more constraints 125, such as a geometric constraint, a spatial constraint, a power constraint (or requirement), a field strength constraint (or requirement), a field geometry constraint (or requirement), alignment constraint, and the like.
The coil deformer 130 (e.g., a software application) can iteratively adjust the shape of the coil (e.g., by deforming a current shape or testing a new shape) based on an output of the objective function 135. In one embodiment, the objective function 135 indicates how closely the magnetic field for the current magnetic coil being tested is to an ideal or desired magnetic field. Using a MOT as an example, the vector-valued functional form of the desired magnetic field used in a MOT is known. The objective function 135 compares this known magnetic field to the magnetic field generated by the coil being tested. For example, a higher score (or value) can indicate the magnetic fields are close, while a lower score indicates the magnetic fields are different. In one embodiment, the coil deformer 130 can then adjust the coil based on the score or value generated by the objective function 135. For example, if the score is high, the coil deformer 130 may make a small adjustment to the current coil shape and determine whether the resulting magnetic field is even closer to the desired magnetic field by calculating a new score using the updated magnetic field and the objective function 135. If the score is low, the coil deformer 130 may try a completely new shape for the coil, or make more dramatic changes to the current shape of the coil.
The MOT simulator 140 (e.g., a software application) can simulate the performance of a particular coil. For example, after the coil deformer 130 identifies an optimal coil shape after iterating through the process described above, the MOT simulator 140 can test that coil shape to determine whether it traps atoms. Advantageously, the MOT simulator 140 does not have to be run each time a new coil is being tested. Instead, the magnetic field calculator 120, the coil deformer 130 and the objective function 135 can execute to identify an optimal coil (or a family of optimal coils) which is then tested using a MOT simulator 140. Executing the magnetic field calculator 120, the coil deformer 130 and the objective function 135 may use much fewer compute resources than the MOT simulator 140, thereby reducing the compute power and time required to identify a magnetic coil for a MOT that satisfies the constraints 125. Various techniques for determining a constrained coil are described in more detail in
The spacing 165 between the laser optics 155 in the MOT 150A is larger than the spacing 180 between the laser optics 155 in the MOT 150B. Put differently, the MOT 150B is more constrained than the MOT 150A. This may be for any variety of reasons, such as achieving more compact packaging, better performance, lowering power consumption, and the like.
The MOT 150A illustrates the optimal coils 160 determined by the coil deformer 130 using the techniques discussed above (and in more detail in
While the shape of the coils 160 and 170 are different, the magnetic fields generated by these coils 160 and 170 are the same or very similar within a region of interest. That is, as discussed above, the coil deformer 130 can use the objective function 135 to determine coil shapes that generate a magnetic field that matches, or is very close, to the ideal or desired magnetic field given the particular constraints. As such, the magnetic fields for the coils 160 and 170 may be the same or very close to each other's magnetic field, as well as the ideal or desired magnetic field. However, the coils 170 can fit within the smaller spacing 180 while the coils 160 cannot.
The method 200 can use a single constraint (e.g., a spacing constraint between the laser optics 155 in
In typical MOTs, the magnetic coils are disposed outside of the vacuum chamber 305. However, it may be advantageous to put the coils within the vacuum chamber 305. For example, the power required to generate a sufficiently strong magnetic field for trapping the atoms falls as the coils are moved closer to the atoms, and so often can be reduced significantly if the coils are within the vacuum chamber 305. However, the space in the vacuum chamber 305 is limited, thereby enforcing a spacing constraint on the coils. Thus,
Returning to the method 200, at block 210, the coil deformer generates coil shapes using an objective function (e.g., the objective function 135 in
In one embodiment, the coil deformer performs an iterative process at block 210. Using an initial coil shape, a magnetic field calculator (e.g., the magnetic field calculator 120 in
In this example, the objective function 135 determines the dot product of the magnetic fields (B) for the ideal field (AH) and the coil shape currently being tested (Trial) at a set of points (P). P samples the region where the atoms are being trapped by the MOT. The individual dot products are then squared and summed, and the resulting summation is then multiplied with the inverse of the winding length of the coil. When the winding length is lower, then the coils are more power efficient.
The output FObj (or score) of the objective function 135 reflects both the closeness between the field generated by the current coil shape 405 being tested and the ideal or desired field for the MOT, and the power efficiency of the current coil shape 405. In this example, the higher the output FObj, the better the fields match and/or the lower the power required to generate the field.
The objective function 135 in
The embodiments herein are not limited to a particular type of metaheuristic algorithm or ML algorithm for deforming the coil shape 405 at block 410. In one embodiment, a simulated annealing algorithm is used to deform the coil shape 405 each time the workflow 400 repeats. However, other suitable metaheuristic algorithms could include a scatter search, particle swarm optimization, evolution strategy, an iterated/stochastic/guide local search, and the like. If a ML algorithm is used, the ML algorithm could use reinforcement learning (RL) or another deep learning method.
Returning to the method 200, at block 215, the MOT simulator (e.g., the simulator 140 in
Returning to
At block 225, the coil shape is fabricated to form a physical magnetic coil. In one embodiment, the coil shape can be for coil mounts where current-carrying wires are wrapped around the mounts or for current-carrying bars where the electric current flows through the part itself. If the coil shape is for coil mounts, in a subsequent step, current carrying wire can be wound around the mounts.
In one embodiment, the magnetic coil is formed using a mold or cast. For example, as shown in
In another embodiment, the magnetic coil is formed using additive manufacturing to deposit material in a layer-by-layer manner. Each new layer can bond to the preceding layer to generate a 3D object (e.g., a magnetic coil or coil mount).
As discussed in
Further, the method 600 is generally applicable to any application where coils are used to generate magnetic fields such as transformers, electrical motors, generators, MOTs, etc.
At block 610, the coil deformer generates a shape of a coil that satisfies the constraint provided at block 605. Further, block 610 includes several sub-blocks 615-625 that can be used to generate the shape of the coil. In one embodiment, the method 600 iterates through the sub-blocks 615-625 until identifying an optimal coil shape.
At block 615, the magnetic field calculator calculates a magnetic field generated by the shape.
At block 620, the coil deformer determines a closeness between the magnetic field calculated at block 615 and a desired magnetic field for the particular application—e.g., a desired magnetic field for a transformer, electrical motor, generator, MOT, etc. The objective function can include any of the examples discussed above.
At block 625, the coil deformer adjusts the shape of the coil. The manner in which the coil deformer adjusts the shape can vary according to the type of metaheuristic algorithm or ML model used. For example, a simulated annealing algorithm may perform random changes in the shape using the output of the objective function as guidance. Some metaheuristic algorithms may result in a family of coil shapes when the sub-blocks 615-625 are performed iteratively, while other algorithms may deform a single shape until reaching a maximum value of the objective function.
Although not shown in the method 600, once block 610 is complete, the shape of the coil may be used in a full-simulator of the particular application—e.g., a transformer simulator, motor simulator, MOT simulator, etc. Advantageously, rather than running a full simulation during each iteration, the method 600 can perform the blocks 610-625 to identify one or more candidate coil shapes before executing the simulator. However, in other embodiments, it may be advantageous to execute the simulator each time the blocks 610-625 iterate. Put differently, a simulation block could also be performed during each iteration of the blocks 610-625 to fully test each coil shape.
However, in other embodiments, rather than designing coil mounts, the techniques above can be used to directly fabricate coil bars. In that example the coil mounts 705 could be coil bars (i.e., current carrying components), which means the grooves 710A and 710B can be omitted since the additional step of winding the wire is not needed. In this example, the coils would be a solid, conductive material rather than wound wires. The solid, conductive material could be formed using a mold or additive manufacturing as discussed above.
As shown, the coil mounts 705 are twisted, which means when wires are disposed in the mounts 705, they form a coil with a twisted shape. Stated differently, each of the coil mounts 705 is non-planar, unlike traditional magnetic coils for MOTs that are planar.
In addition,
While in other implementations the coil mounts 705 may have different shapes, in
The preceding description is provided to enable any person skilled in the art to practice the various embodiments described herein. The examples discussed herein are not limiting of the scope, applicability, or embodiments set forth in the claims. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.
As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).
As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
The methods disclosed herein comprise one or more steps or actions for achieving the methods. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components with similar numbering.
As will be appreciated by one skilled in the art, the embodiments disclosed herein may be embodied as a system, method, or computer program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments presented in this disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block(s) of the flowchart illustrations and/or block diagrams.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other device to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the block(s) of the flowchart illustrations and/or block diagrams.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer, other programmable data processing apparatus, or other device provide processes for implementing the functions/acts specified in the block(s) of the flowchart illustrations and/or block diagrams.
The flowchart illustrations and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments. In this regard, each block in the flowchart illustrations or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The following claims are not intended to be limited to the embodiments shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. § 112 (f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.
This invention was made with government support under Subcontract 1560823 awarded by the DARPA. The government has certain rights in the invention.