[PSyData] In kernel extraction don't write constants out
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing the PSyData extraction and driver paths, including dependency analysis and user-defined values. Then inspect the Fortran binary writer's expected variable order. Done means extraction and driver use the same ordered list, constants are excluded, and binary output remains aligned with driver input.
Written by the indexing model from the issue text.
Description
While #1990 ignores constant values in the driver, this solution only works with NetCDF (since NetCDF uses the name of the variables, and will therefore just skip unused values in the kernel data file). But the Fortran binary file writer relies on reading the variables in the right order, so writing constants to the file will not work since the driver will not skip these values. Additionally, there is no need to make the output files bigger by adding the constants in.
- Make sure the extraction and driver use the same list of variables names in the same order. ATM there is still code that might re-run the dependency analysis (or accept user-defined values), which could break things.
- Exclude all constants from the list of variables
- Verify this esp. with the binary Fortran writer (since it is sensitive to a mismatch in the extracted data and the read-in code in the driver).
- Dominant language
- Python
- Stars
- 137
- Forks
- 36
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 18
Contributor 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 stfc/PSyclone
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
frontend: add support for ALOG, ALOG10 and IDInt intrinsics. Specify FLOAT as available on GPU. Openenhancement PSyIR
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
NEMO
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100