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

--psd-file vs --asd-file is a dangerous trap #5029

Open
titodalcanton opened this issue Jan 31, 2025 · 0 comments
Open

--psd-file vs --asd-file is a dangerous trap #5029

titodalcanton opened this issue Jan 31, 2025 · 0 comments

Comments

@titodalcanton
Copy link
Contributor

I have heard multiple reports of people confusing --psd-file and --asd-file and producing incorrect results as a consequence. Are there ideas on how to avoid this? The first thing I can think of is a check for the values in the file, which should be fairly robust for realistic detectors. But I am not sure what should happen then, should the code just print a warning? Or fail and require a --i-am-sure-just-do-what-i-said option?

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