issues
search
wouterbles
/
pyaugmecon
An AUGMECON based multi-objective optimization solver for Pyomo.
Other
24
stars
8
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
fixed bug within options.py
#25
kschulze26
opened
3 months ago
0
Enhanchement branch
#24
npaterakis
closed
7 months ago
0
Check if user-provided model component names conflict with pyaugmecon-added component names
#23
npaterakis
opened
7 months ago
1
Automate objective deactivation
#22
npaterakis
opened
7 months ago
0
Update deps
#21
wouterbles
closed
8 months ago
0
Any plan to add other solver like CBC?
#20
shuaiwang88
opened
9 months ago
7
Wait for processes to exit instead of STOP result
#19
yvanoers
closed
1 year ago
3
Correctly enqueue items such that work can be taken by other processes
#18
wouterbles
closed
1 year ago
0
Improve how solutions are stored
#17
wouterbles
opened
1 year ago
0
Improve GitHub actions testing
#16
wouterbles
opened
1 year ago
0
Publish to PyPI on release
#15
wouterbles
opened
1 year ago
0
Job queue issues
#14
wouterbles
opened
1 year ago
5
Release 1.0.2
#13
wouterbles
closed
1 year ago
0
Update deps
#12
wouterbles
closed
1 year ago
0
Enqueue work items instead of a list of them
#11
yvanoers
closed
1 year ago
1
PyAugmecon opens multiple environments simultaneously
#10
AndresFCortes
closed
1 year ago
2
Update and use Pyomo 6.6.1 syntax
#9
torressa
closed
1 year ago
2
Update to Pyomo 6.6.1 to allow solver disposal
#8
torressa
closed
1 year ago
0
Allow disabling print()s
#7
yvanoers
opened
1 year ago
1
Allow injecting a logger
#6
yvanoers
opened
1 year ago
1
Make QueueHandler work on MacOS
#5
yvanoers
closed
1 year ago
4
Refactor, add comments, and new solution retrieval methods
#4
wouterbles
closed
1 year ago
0
Add support for storing decision variables result
#3
wouterbles
closed
1 year ago
0
ZeroDivisionError when optimizing
#2
senniraf
closed
1 year ago
2
KeyError: "Index '0' is not valid for indexed component 'e'"
#1
senniraf
closed
1 year ago
2