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

Passing in files and folders as command line arguments #220

Open
drbergman opened this issue Mar 8, 2024 · 0 comments
Open

Passing in files and folders as command line arguments #220

drbergman opened this issue Mar 8, 2024 · 0 comments

Comments

@drbergman
Copy link
Collaborator

drbergman commented Mar 8, 2024

Bottom line

Has anyone thought about passing in other files/folders at the command line rather than in the config file? I think it's going to be useful enough for me that I'll implement it in my own project, but just wondering if there's any advice out there to make it more readily merge-able into main.

Background

I'm finding it would be helpful to be able to pass in paths to folders/files as command line arguments into a PhysiCell executable, similar to what's already done with the configuration file. Basically, I want to avoid changing the configuration file just to change the files/folders it encodes (output folder, initial conditions, rules). I can get it to work with minor edits to main.cpp for the output folder and configuration files, but it's a much bigger lift for the others requiring either

  1. a rewrite of create_cell_types and setup_tissue which are essentially "core" code though live in custom_modules
  2. a rewrite of setup_cell_rules and load_cells_from_pugixml which are core and modules, respectively

Proposed solution

./project -c $(path_to_config) -o $(path_to_output) -i $(path_to_ic) -r $(path_to_rules)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant