Skip to content
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.

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

Config file vs cli for parameters #53

Open
pkMyt1 opened this issue Dec 20, 2017 · 1 comment
Open

Config file vs cli for parameters #53

pkMyt1 opened this issue Dec 20, 2017 · 1 comment
Milestone

Comments

@pkMyt1
Copy link

pkMyt1 commented Dec 20, 2017

I like what you have done with this. I am also willing to help in anyway to keep this project moving forward. A suggestion I have is to use a tab delimited config file for inputting parameters something along the lines of the one I pasted below. The file can then be simply parsed into a named tuple and passed around easily. Even though the code is likely to break I would like some sort of API to allow simpler integration into my pipelines. I have started to play around with that but I am still very early into it. Again, let me know if there is something I might be able to help you with.

run_Mimir.txt

@jdidion
Copy link
Owner

jdidion commented Dec 20, 2017

Thanks! Atropos actually does take a config file right now, it's just not documented yet. The format is pretty simple right now - just put one argument per line. The config file is loaded before parsing any command line arguments, so anything you specify on the command line overrides anything in the config file.

I like the idea of using a more structured config file. I might look at TOML or the tab-delimited format you suggest in a future release.

@jdidion jdidion added this to the 1.3 milestone Dec 28, 2017
@jdidion jdidion modified the milestones: 1.3, 2.1 Dec 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants