Papers › Bloch points in nanostrips

Bloch points in nanostrips

25 Mar 2022arXiv:2203.13689links table onlyarchive 2025-07-28

Martin Lang, Marijan Beg, Ondrej Hovorka, Hans Fangohr

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Complex magnetic materials hosting topologically non-trivial particle-like objects such as skyrmions are under intensive research and could fundamentally change the way we store and process data. One important class of materials are helimagnetic materials with Dzyaloshinskii-Moriya interaction. Recently, it was demonstrated that nanodisks consisting of two layers with opposite chirality can host a single stable Bloch point of two different types at the interface between the layers. Using micromagnetic simulations we show that FeGe nanostrips consisting of two layers with opposite chirality can host multiple coexisting Bloch points in an arbitrary combination of the two different types. We show that the number of Bloch points that can simultaneously coexist depends on the strip geometry and the type of the individual Bloch points. Our simulation results allow us to predict strip geometries suitable for an arbitrary number of Bloch points. We show an example of an 80-Bloch-point configuration verifying the prediction.

PaperPDFCode

Code

lang-m/2022-paper-multiple-bloch-points officialmentioned on GitHub report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections