[FIBERALLOC-8] Control some Gurobi parameters in the netflow fiber assigner Created: 18/Sep/18  Updated: 20/Jan/20  Resolved: 20/Jan/20

Status: Done
Project: Target to fiber allocation and configuration
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Kiyoto Yabe Assignee: Kiyoto Yabe
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

During studies of the netflow fiber assigner, I realized that it is useful to able to change some parameters of Gurobi optimizer in the netflow code. The current parameters I expect are:

  • the number of CPU threads during the optimization
  • the threshold of GAP to terminate the optimization
  • the timeout to terminate the optimization

 



 Comments   
Comment by Martin Reinecke [ 02/Jun/19 ]

Dear Kiyoto,

could you please have a look at the branch "tickets/FIBERALLOC-8_mr" I just pushed to the repository?

This is based on your branch but contains a few changes which make integration with other developments easier for me:

  • I reverted some of the white space changes (PEP-8 does not require white spaces around the operators +, -, *, /, although many code reformatting tools unfortunately get this wrong).
  • The Gurobi-specific options are now passed as a dictionary; this makes it easier to add new parameters in the future, since it doesn't require additional code changes.
  • It is now possible to specify the name of the MPS file. If this is None, no file is written.

Please let me know if these changes are OK with you. If so, I propose to merge this branch onto "tickets/FIBERALLOC-8".

Best regards,

  Martin

Comment by Kiyoto Yabe [ 10/Jun/19 ]

Thank you, Martin. I'll take a look at your change.

Comment by Martin Reinecke [ 17/Jan/20 ]

I don't recall how this happened, but the changes on this branch already made it into the master branch. So unless there are objections, I suggest to close this.

Generated at Sat Feb 10 16:52:48 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.