-
Notifications
You must be signed in to change notification settings - Fork 1
Bake PHOLD into the Docker image #149
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
base: main
Are you sure you want to change the base?
Changes from all commits
018214d
e4e77fa
7b86831
9c47997
d30c730
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,14 +10,11 @@ DJANGO_MINIO_STORAGE_MEDIA_URL=http://localhost:9000/django-storage | |
| # access from non-internal addresses. | ||
| DJANGO_INTERNAL_IPS=0.0.0.0/0 | ||
|
|
||
| # Path to ROSS simulation framework directory | ||
| # ROSS_PATH=../ross | ||
|
|
||
| # PHOLD simulation configuration | ||
| # DJANGO_PHOLD_BINARY_PATH=/home/vscode/ross/build/models/phold/phold | ||
| DJANGO_PHOLD_BINARY_PATH=/opt/ross/phold | ||
|
|
||
| # Directory for PHOLD output files | ||
| # DJANGO_PHOLD_OUTPUT_DIR=/tmp/phold_output | ||
| DJANGO_PHOLD_OUTPUT_DIR=/tmp/phold_output | ||
|
|
||
| # Number of MPI processes for PHOLD simulations (set to 1 for no MPI) | ||
| # DJANGO_PHOLD_MPI_PROCESSES=4 | ||
| DJANGO_PHOLD_MPI_PROCESSES=4 | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why set this at the Django settings level (rather than let it be part of the run configuration)?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Great question. Do we want to expose this to users? Initially this was the easiest way to get things up and running, and I didn't really consider exposing it because I wasn't sure if we wanted users to have to think about this. Maybe if we don't expose it we do something a little smarter to detect available resources and set a reasonable value, or we just skip that and expose it to users as a part of the run configuration. What do you think?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this needs to be a user-settable value, and per run. We can disallow outlandish values through form validation or something, and it's a bigger question how we decide on reasonable limits for this type of thing in a real deployment. For now, I would just file an issue saying to expose this through the run configuration. |
||
Uh oh!
There was an error while loading. Please reload this page.