Further Integrate PleiadesConfig workflow into InpManager INP generation path
@along4 is already working on this.
Since Feb 18, 2026.
Assessment
This issue has not been assessed yet.
Description
InpManager now supports a typed FitConfig + InpDatasetMetadata interface, but the higher-level PleiadesConfig orchestration is still disconnected.
Current docs and call patterns show direct FitConfig construction, while production workflow is expected to start from PleiadesConfig (workspace, datasets, fit_routines, global nuclear isotope config).
I would like to add first-class integration so INP generation can be driven directly from information in PleiadesConfig, including consistent mapping of PleiadesConfig metadata (min/max energy, element/mass hints, density/thickness/atomic mass, temperature), routine fit_config overrides, and isotope population from global nuclear config (populate_fit_config_isotopes).
Proposed scope: add an adapter/constructor path in InpManager (or a nearby orchestration utility) that takes PleiadesConfig + routine_id and produces INP deterministically, update docs to include this end-to-end flow, and add unit/integration tests validating round-trip behavior for routine selection, metadata precedence rules, and missing/invalid config handling.
- Dominant language
- Python
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lanl/PLEIADES
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
-
Add validation constraints to FitConfig Card 2 integer fieldsMay be free again @along4 claimed this 247 days ago, and no pull request is open. Open
-
Clarify precedence of nuclear data cache dir across config layersMay be free again @along4 claimed this 247 days ago, and no pull request is open. Open
Similar issues
-
Project submission:Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
slavakurilyak/awesome-ai-agents#845 ·
Maintainers usually reply within 1 day
-
tests: pin that the atomic writers in utils/paths.py stage the temporary file in the target's directoryPossibly taken A pull request linked to this issue is open or already merged. Opendifficulty:2 enhancement good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
MakazhanAlpamys/Soup#2178 ·
Maintainers usually reply within 1 day
-
[BUG] dcg.waggr permutation p-values are folded twice, so near-zero scores get the smallest p-valuesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
scverse/rapids-singlecell#854 ·
Maintainers usually reply within 1 day
-
Slang input: int8_t4_packed and uint8_t4_packed are copied into CrossGLPossibly taken @ninglinLiu claimed this today. Openarea:frontend backend:slang bug direction:input
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
random_elements(unique=True) on an OrderedDict: ZeroDivisionError once only zero weights remain, AssertionError with use_weighting=FalsePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 13 days