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

priority of --maxtime and --force-convergence #108

Open
QianXiaobo opened this issue Apr 24, 2024 · 1 comment
Open

priority of --maxtime and --force-convergence #108

QianXiaobo opened this issue Apr 24, 2024 · 1 comment

Comments

@QianXiaobo
Copy link

Hi developers,

I found that --maxtime can't make any limitation to --force-convergence. I think --maxtime should be priority to --force-convergence to kill the process when sometimes cannot achieve convergence very long time.

I don't know what I say is correct or not, you could think about it, or ignore it...

Best wishes,
Xiaobo

@tjstruck
Copy link
Collaborator

tjstruck commented Apr 24, 2024

Hi @QianXiaobo, you are correct.

--maxtime is a property of the optimization package dadi-cli uses. Each optimization dadi-cli starts gets the --maxtime assigned to it, so you are correct that --force-convergence would override it. If convergence isn't reached, --force-convergence would launch more optimizations with the --maxtime assigned to them.

It probably wouldn't be too hard to change --maxtime to be for the dadi-cli inference subcommands running, but I'll wait to hear what other devs think (whether --maxtime should stay the time limit of the individual optimization or change it to be the time limit for the subcommand).

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

2 participants