PFS-JIRA https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 [FIBERALLOC-13] Allow modification of the optimization problem after creation https://pfspipe.ipmu.jp/jira/browse/FIBERALLOC-13 Target to fiber allocation and configuration <p>Currently the ETS code builds an integer linear programming problem from the given inputs and determines an optimized solution. This solution can then be analyzed whether it produces fiber collisions during the movement stage. If such events are detected, it is desirable to be able to alter the problem configuration and re-run the optimization, hopefully without a complete restart.</p> <p>I'm preparing a change that exposes the LP variables and constraints in the problem to the user so that they may change their parameters even after optimization and then re-run the optimizer.</p> FIBERALLOC-13 Allow modification of the optimization problem after creation Task Normal Done Done Martin Reinecke Martin Reinecke Mon, 3 Jun 2019 07:56:24 +0000 Wed, 27 Nov 2019 23:58:21 +0000 Wed, 27 Nov 2019 23:58:21 +0000 0 2 <p>Implementation is taking place on the branch "tickets/<a href="https://pfspipe.ipmu.jp/jira/browse/FIBERALLOC-13" title="Allow modification of the optimization problem after creation" class="issue-link" data-issue-key="FIBERALLOC-13"><del>FIBERALLOC-13</del></a>" of <a href="https://github.com/Subaru-PFS/ets_fiber_assigner" class="external-link" rel="nofollow">https://github.com/Subaru-PFS/ets_fiber_assigner</a></p> <p>I have restructured the code so that an object describing the problem (instead of the full solution) is returned from the netflow module. This object supports writing to disk as MPS file (via`dump()`) and solution (via `solve()`).</p> <p>The problem's variables and constraints are accessible via their names and I plan to make them modifiable after the problem has been built. However I'd be happy about feedback on naming conventions. Please have a look at the code!</p> <p>Thank you for this update! The idea and naming convention are all fine to me.</p> <p>I have reflected the change to my survey simulator. I didn't check the output in very detail, but the new implementation also works.</p> <p>Merged to master.</p> Development Rank 0|zx00i8: