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

The parameter --amp_cutoff isn't working #445

Closed
amizeranschi opened this issue Jan 28, 2025 · 2 comments
Closed

The parameter --amp_cutoff isn't working #445

amizeranschi opened this issue Jan 28, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@amizeranschi
Copy link

The problem appears with the latest dev version. Running the pipeline with --amp_cutoff 0.4 results in the following warning message:

WARN: The following invalid input values have been detected:

* --amp_cutoff: 0.4

For more info and a command which reproduces the error, see: #444

@amizeranschi amizeranschi added bug Something isn't working and removed bug Something isn't working labels Jan 28, 2025
@Darcy220606
Copy link
Contributor

Darcy220606 commented Feb 2, 2025

Hi @amizeranschi i checked your command again in #444 . You are passing the wrong parameter to change the amp cutoff, we have changed it in the new dev version to --amp_ampcombi_parsetables_cutoff 0.6. If you change it to the updated flag that should fix the issue 😃

@amizeranschi
Copy link
Author

Alright, thank you for pointing that out. I hadn't noticed the change in the parameter name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants