Skip to content

Remove refs to device.dat #4551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
timothy-nunn merged 1 commit into from
Aug 25, 2026
Merged

Remove refs to device.dat #4551

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/source/fusion-devices/inertial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

As well as magnetic confinement devices, `PROCESS` has the ability to model inertial fusion plants, in which a laser or ion beam is used to ignite a target pellet containing the fusion fuel.

To activate the inertial fusion energy (IFE) coding, it is necessary to create a file `device.dat`, containing the single character 3 in the first row, in the working directory. This has the effect of setting the internally-used switch `ife = 1`. If the file is absent, or its first character is set to something other than 3, the IFE model is not used, and `ife` is set to 0.
To activate the inertial fusion energy (IFE) coding, set switch `ife = 1`.

The IFE model[^1] is controlled using two additional switches.

Expand Down
4 changes: 2 additions & 2 deletions documentation/source/fusion-devices/stellarator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The model is largely based on W7-X and the HELIAS 5-B stellarator power plant de

*Figure 1: Fusion power core of the HELIAS 5-B conceptual power plant design*[^1]

To activate the stellarator coding, it is necessary to create a file `device.dat`, containing the single character 1 in the first row, in the working directory. This has the effect of setting the internally-used switch `istell = 1/StellaratorModel.HELIAS_5`. If the file is absent, or its first character is set to something other than 1, the stellarator model is not used, and `istell` is set to `0/StellaratorModel.DISABLED`.
To activate the stellarator coding, set switch `istell` to correspond to a particular stellarator model, which are detailed below.

## Stellarators in PROCESS

Expand All @@ -32,7 +32,7 @@ The user can switch between these models by using the switch variable `istell`:
- `istell=3`: Helias-3
- `istell=4`: W7-X
- `istell=5`: A W7-X variation with 30 coils
- `istell-6`: Use the `stella_conf.json` file.
- `istell=6`: Use the `stella_conf.json` file.

The stellarator version of PROCESS assumes the coil-set itself to be **fixed in shape** and can only scale the *overall* size of the machine in major radius `rmajor`. There is no capability in PROCESS to separately scale the minor coil radius -- in other words: the coil aspect ratio is fixed. Also the number of coils is considered fixed and is given by the configuration.

Expand Down
2 changes: 1 addition & 1 deletion process/data_structure/stellarator_variables.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ class StellaratorData:
"""Coil major radius (m)"""

istell: int = 0
"""Switch for stellarator option `StellaratorModel` (set via `device.dat`):
"""Switch for stellarator option `StellaratorModel`:
- `StellaratorModel.DISABLED` use tokamak model
- `StellaratorModel.HELIAS_5` use stellarator model: Helias5
- `StellaratorModel.HELIAS_4` use stellarator model: Helias4
Expand Down
Loading