Improve functionality to write new in.dat from an mfile
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start at the command-line argument handling for writing a new IN.DAT from an MFILE.DAT. Verify that -f and -o work without -i, that the default new_IN.DAT is created beside the specified MFILE.DAT, and that an explicitly different output directory is honored.
Written by the indexing model from the issue text.
Description
This functionality currently requires 3 arguments:
[-f path/to/MFILE.DAT] [-i path/to/IN.DAT] [-o path/to/new_IN.DAT]
This needs changing to be shorter and easier to use:
-f path/to/MFILE.DAT -o new_IN.DAT
The new IN.DAT would by default be created in the same directory as the specified MFILE, but the user could specify a different directory if they wished.
- Dominant language
- Python
- Stars
- 71
- Forks
- 27
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 33
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 ukaea/PROCESS
-
papercut
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Command Line Interface
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
papercut
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Dependencies Physics Refactor
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100