Skip to content

Conversation

@chris-maes
Copy link
Contributor

These errors were caused by all LPs in the batch sharing the same concurrent halt variable. This meant that the first LP to solve, forced all other LPs to halt. So it was possible that both PDLP and Dual Simplex solves returned with a ConcurrentLimit termination status. This should never happen normally.

For now, we fix this by disabling the Concurrent method in batch mode. We set the method to PDLP, if Concurrent was chosen, and tell the user to choose PDLP or Dual Simplex to avoid this warning in the future.

These errors were caused by all LPs in the batch sharing the same
concurrent halt variable. This meant that the first LP to solve,
forced all other LPs to halt. So it was possible that both PDLP and
Dual Simplex solves returned with a ConcurrentLimit termination
status. This should never happen normally.

For now, we fix this by disabling the Concurrent method in batch
mode. We set the method to PDLP, if Concurrent was chosen, and tell
the user to choose PDLP or Dual Simplex to avoid this warning in the
future.
@chris-maes chris-maes requested a review from a team as a code owner May 19, 2025 17:12
@chris-maes chris-maes requested review from akifcorduk and rg20 May 19, 2025 17:12
@copy-pr-bot
Copy link

copy-pr-bot bot commented May 19, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@chris-maes chris-maes added bug Something isn't working non-breaking Introduces a non-breaking change labels May 19, 2025
@chris-maes
Copy link
Contributor Author

/ok to test b4eab6c

if (solver_settings->get_parameter<int>(CUOPT_METHOD) == CUOPT_METHOD_CONCURRENT) {
CUOPT_LOG_INFO("Concurrent mode not supported for batch solve. Using PDLP instead. ");
CUOPT_LOG_INFO(
"Set the CUOPT_METHOD parameter to CUOPT_METHOD_PDLP or CUOPT_METHOD_DUAL_SIMPLEX to avoid "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would be printed even if the user does not specify anything and leave it default right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. I think that is the correct behavior. IF the user leaves Concurrent as the default setting, we want to switch it and ask them to switch it themselves.

@chris-maes chris-maes added this to the 25.05 milestone May 19, 2025
@chris-maes
Copy link
Contributor Author

/merge

@rapids-bot rapids-bot bot merged commit f8d62ab into NVIDIA:branch-25.05 May 19, 2025
85 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working non-breaking Introduces a non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants