mxl-meep

스타10

포크5

업데이트2026년 2월 7일 01:19

This skill should be used when users need MaxwellLink + Meep FDTD workflows, including embedded vs socket coupling, MPI considerations, and recommended templates.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

TaoELi

TaoELi/MaxwellLink

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Meep FDTD workflows (MaxwellLink)

Confirm prerequisites

Ensure pymeep is installed and importable before generating Meep-based inputs.
Use mxl.MeepSimulation (not raw meep.Simulation) when using the unified mxl.Molecule API.

Build a Meep-coupled run

Set time_units_fs explicitly and keep it consistent across analysis.
Create molecules with either:
- Embedded driver: Molecule(driver=..., driver_kwargs=...)
- Socket driver: SocketHub(...) + Molecule(hub=hub, ...)
For "baseline" EM-only runs (no molecules), use raw mp.Simulation(...); switch to mxl.MeepSimulation(...) only when MaxwellLink molecules are present (common when generating reference spectra/fields first, then enabling coupling).
Use boundary_layers=[mp.PML(...)], set resolution, and keep Courant=0.5 (Meep default).

Prefer templates

Start from the copy-ready templates:
- skills/mxl-project-scaffold/assets/templates/meep-tls-embedded
- skills/mxl-project-scaffold/assets/templates/meep-tls-socket-unix
- skills/mxl-project-scaffold/assets/templates/slurm-meep-plasmon-rteh-tcp (3D plasmonic structure + RT-Ehrenfest molecular lattice)
Use SLURM/HPC patterns from skills/mxl-hpc-slurm/SKILL.md for multi-node socket runs.

References

Recipes: skills/mxl-meep/references/meep_run_recipes.md
Docs: docs/source/em_solvers/meep.rst

MPI/libfabric init tips (macOS/local single-rank)

Sandbox note: sandboxed runs often block the libfabric endpoint; if MPI_Init_thread fails with ep_enable/socket errors, rerun unsandboxed (sandbox_permissions=require_escalated).
When Matplotlib is imported, set MPLCONFIGDIR=/tmp/mplconfig to avoid cache permission errors.

Other common bugs

The dimensions=... input can only be assigned in mxl.Molecule() not mxl.MeepSimulation(). For example, assigning dimensions=1 in both mxl.Molecule() and mxl.MeepSimulation() will lead to runtime error: meep: cannot require a ez component in a 1D grid.
In 1D and 2D simulations, mxl.Molecule (or molecular drivers) should have a transition dipole moment along z-direction, because mxl.MeepSimulation() sets the mxl.Molecule to emit only along z-direction in 1D and 2D.

이 저장소의 다른 Skills

같은 저장소

mxl-multimode

TaoELi/MaxwellLink

This skill should be used when users need the MaxwellLink multimode Fabry-Pérot cavity solver to study a spatial grid of molecules coupled to many photonic modes (mesoscale VSC), in either socket or embedded mode.

2026-05-1110

mxl-core

TaoELi/MaxwellLink

This skill should be used when users need the canonical MaxwellLink workflow, including socket vs embedded coupling, units/time handling, and MPI/HPC invariants.

2026-05-0910

mxl-singlemode

TaoELi/MaxwellLink

This skill should be used when users need the MaxwellLink single-mode cavity solver for fast prototyping and regression, in either socket or embedded mode.

2026-05-0910

mxl-index

TaoELi/MaxwellLink

This skill should be used when users ask how to set up, choose, or run a MaxwellLink simulation and the correct solver/driver/HPC/post-processing workflow must be selected.

2026-05-0510

mxl-driver-dftbplus

TaoELi/MaxwellLink

This skill should be used when users want to couple MaxwellLink to the MaxwellLink-aware DFTB+ fork via the `MaxwellLinkSocket` block, including real-time Ehrenfest dynamics, VelocityVerlet Born-Oppenheimer MD, dipole-derivative choices, build/install, and TCP/UNIX socket connection patterns.

2026-04-2910

mxl-cli

TaoELi/MaxwellLink

This skill should be used when users need to initialize, clean, or configure MaxwellLink workspaces using the mxl command family.

2026-03-1910

Meep FDTD workflows (MaxwellLink)

Confirm prerequisites

Ensure pymeep is installed and importable before generating Meep-based inputs.

Use mxl.MeepSimulation (not raw meep.Simulation) when using the unified mxl.Molecule API.

Build a Meep-coupled run

Set time_units_fs explicitly and keep it consistent across analysis.

Create molecules with either:

Embedded driver: Molecule(driver=..., driver_kwargs=...)
Socket driver: SocketHub(...) + Molecule(hub=hub, ...)

For "baseline" EM-only runs (no molecules), use raw mp.Simulation(...); switch to mxl.MeepSimulation(...) only when MaxwellLink molecules are present (common when generating reference spectra/fields first, then enabling coupling).

Use boundary_layers=[mp.PML(...)], set resolution, and keep Courant=0.5 (Meep default).

Prefer templates

Start from the copy-ready templates:

skills/mxl-project-scaffold/assets/templates/meep-tls-embedded
skills/mxl-project-scaffold/assets/templates/meep-tls-socket-unix
skills/mxl-project-scaffold/assets/templates/slurm-meep-plasmon-rteh-tcp (3D plasmonic structure + RT-Ehrenfest molecular lattice)

Use SLURM/HPC patterns from skills/mxl-hpc-slurm/SKILL.md for multi-node socket runs.

References

Recipes: skills/mxl-meep/references/meep_run_recipes.md

Docs: docs/source/em_solvers/meep.rst

MPI/libfabric init tips (macOS/local single-rank)

Sandbox note: sandboxed runs often block the libfabric endpoint; if MPI_Init_thread fails with ep_enable/socket errors, rerun unsandboxed (sandbox_permissions=require_escalated).

When Matplotlib is imported, set MPLCONFIGDIR=/tmp/mplconfig to avoid cache permission errors.

Other common bugs

The dimensions=... input can only be assigned in mxl.Molecule() not mxl.MeepSimulation(). For example, assigning dimensions=1 in both mxl.Molecule() and mxl.MeepSimulation() will lead to runtime error: meep: cannot require a ez component in a 1D grid.

In 1D and 2D simulations, mxl.Molecule (or molecular drivers) should have a transition dipole moment along z-direction, because mxl.MeepSimulation() sets the mxl.Molecule to emit only along z-direction in 1D and 2D.

name	mxl-meep
description	This skill should be used when users need MaxwellLink + Meep FDTD workflows, including embedded vs socket coupling, MPI considerations, and recommended templates.