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

Introduce read only-path for tables? #391

Open
Jean1995 opened this issue Apr 26, 2024 · 1 comment
Open

Introduce read only-path for tables? #391

Jean1995 opened this issue Apr 26, 2024 · 1 comment
Labels

Comments

@Jean1995
Copy link
Member

At the moment, there is only one PROPOSAL::InterpolationSettings::TABLES_PATH. PROPOSAL will read interpolation tables from there, if required. But if they are not found, PROPOSAL will also write tables to there.

This might not be desired in some cases. I believe IceCube had a problem with this, and CORSIKA 8 containers might also have a problem with this.

In PROPOSAL 6 we had something like tables_read_only paths, where it was clear that PROPOSAL should only read tables from there, but never write to these paths. Maybe this would also be useful? Or we introduce something like a list of TABLE_PATHS, and every PATH has a setting whether it is read-only or not.

@MaxSac
Copy link
Contributor

MaxSac commented Jun 7, 2024

Why does the process have the right to write to the folder if it is not supposed to?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants