:bug: `--mfile` arg does not work as expected
Open
Beginner friendly
Nobody has claimed this yet.
Command Line Interface
- Dominant language
- Python
- Stars
- 71
- Forks
- 27
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 33
Description
Describe the bug
The --mfile argument when running PROCESS is not working as expected
Steps to reproduce
process -i path/to/IN.DAT --mfile TEST_MFILE.DAT
Expected behaviour
Running PROCESS as above should write the MFILE to your current working directory with the specified name (TEST_MFILE.DAT in this case), but it doesn't do this
Evidence
Environment
- OS:
- Version:
Additional context
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.
Research direction
Start with the PROCESS command-line entry point and trace how the --mfile argument is handled for process -i path/to/IN.DAT --mfile TEST_MFILE.DAT. Reproduce the issue, then verify that the run writes an MFILE named TEST_MFILE.DAT in the current working directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100