Dynamic Charge Workflow
CLI workflow for per-atom dynamic charge changes and summaries.
Command: get_dynamic_charge_changes
Compare each atom's dynamic charge with its charge at frame zero.
Writes per-atom and per-frame summaries; per-atom detail is opt-in. --gen-plots writes one charge and one delta-charge trace per atom.
Examples
reaxkit get_dynamic_charge_changes --fort7 fort.7 --xmolout xmolout --gen-plots --x-axis time
Arguments
Scientific choices
| Flag |
Required |
Default |
Help |
Choices |
--atom-numbers, --atom-ids |
No |
|
|
|
--frames |
No |
|
Frames, e.g. 0:101:10. |
|
--every |
No |
1 |
Keep every Nth selected frame. |
|
| Flag |
Required |
Default |
Help |
Choices |
--engine |
No |
|
|
reaxff, ams, lammps |
--input |
No |
. |
Input path used for engine detection. |
|
--run-dir |
No |
. |
Fallback simulation directory. |
|
--fort7 |
No |
fort.7 |
Dynamic charge input for ReaxFF. |
|
--xmolout |
No |
xmolout |
Optional atom identity/time source. |
|
--summary |
No |
|
Optional summary.txt metadata source. |
|
--control |
No |
control |
Control file used to derive time. |
|
Outputs and plots
| Flag |
Required |
Default |
Help |
Choices |
--write-detailed-charges |
No |
False |
Stream per-atom details (Parquet by default). |
|
--gen-plots |
No |
False |
Generate per-atom PNG plots. |
|
--global-y-axis |
No |
False |
Use one shared charge y-axis across atoms and one shared delta-charge y-axis across atoms. |
|
--skip-detailed-csv |
No |
False |
Do not create the potentially very large charges.csv file. |
|
--x-axis, --xaxis |
No |
frame |
Horizontal axis for generated plots. |
frame, time, iter |
--dpi |
No |
180 |
Plot resolution in dots per inch. |
|
--output-dir |
No |
|
Optional output root for charges.csv, the three summary CSVs, and plots/. |
|
--export |
No |
|
Optional CSV destination; all enabled CSV outputs are written beside it. |
|
--detail-format |
No |
|
Optional detail format (default: Parquet; legacy: CSV). |
parquet, csv |
Execution
| Flag |
Required |
Default |
Help |
Choices |
--execution |
No |
auto |
Execution backend; unsupported backends fall back to serial with a logged reason. |
auto, serial, threads, processes |
--workers |
No |
0 |
Frame workers: auto or N (default: auto). |
|
--chunk-size |
No |
0 |
Maximum in-flight frames: auto or N. |
|
Storage and cache
| Flag |
Required |
Default |
Help |
Choices |
--run-id |
No |
|
Run identifier for run-scoped layout. Example: --run-id run_91ac0e, which reuses that run identifier. |
|
--project-root |
No |
reaxkit_workspace |
Project root that contains inputs/, data/, analysis/, etc. Example: --project-root ./workspace, which stores run artifacts there. |
|
--analysis-id |
No |
|
Optional analysis artifact id; defaults to run id. Example: --analysis-id comparison-a, which names the analysis artifact explicitly. |
|
--input-cache, --no-input-cache |
No |
True |
Reuse parsed input frames across commands (default: enabled; use --no-input-cache to force source reads for reproducibility checks or benchmarks). Example: --no-input-cache, which reloads frames from their source files. |
|
--frame-cache-max-gb |
No |
10.0 |
Maximum workspace frame-cache size in GiB (default: 10; use 0 for unlimited). Example: --frame-cache-max-gb 20, which caps cached frames at 20 GiB. |
|
--output-profile |
No |
standard |
Select the shared artifact policy. Standard writes declared default outputs; minimal keeps core tables; full and legacy include optional details. Default: standard. Example: --output-profile full, which includes declared optional detail tables. |
minimal, standard, full, legacy |
Diagnostics and compatibility
| Flag |
Required |
Default |
Help |
Choices |
-h, --help |
No |
|
show this help message and exit |
|
--help-all, --all-flags |
No |
|
Show every option, grouped by purpose. |
|
--log |
No |
quiet |
|
verbose, quiet |
Common Runtime and Presentation Arguments
These are shared workflow-level CLI flags added before command-specific options, covering runtime context (engine/input/storage) and output presentation/export behavior.
Each command table above includes its shared and inherited options.