Rivus class

[lnksz]

I would like to start a discussion about status que vs. a Rivus class.

Has anybody already thought about OOP-ing the module?
I was creating the rivus.graph submodule and thought something like this would be pretty intuitive instead of what we are doing now:

import rivus as rv
prob = rv.Rivus(edge, vertex, sheet_data, ...)  # constructor (maybe even from paths instead of objects?
prob.solve('gurobi', threads=6, MIPGap=.001, ...)
prob.report('./result/abc')
prob.to_igraph('./result/graph/')
prob.plot()
....

What are your thoughts about it?
Does somebody have experience regarding the performance difference between the two paradigms?

#discussion #enhancement