tum-ens
Move spurious input data to other branch/repo
Right now, the master branch includes data and run scripts for one specific research area. These files should be moved to their own branch, possibly their own repository. Only keep one exemplary, small-scale input dataset on branch master.
Hey, I have tried to reach out for you ojdo on the found @tum.de address, in which I have questions about the minimal input requirements of the rivus main component. I think that would be great if the simple example(s) (min, mnl ?) would consist of the bare minimum of feature attributes.
Throughout the examples data attributes like x, y, x0,... pop up, in haag15 maybe merged from the edge.xlsx but in mnl/Vertex I don't know why and from where they come from. They lookblike projected coordinates bit as far as I dived into rivus. create_model() such redundant information is not needed. Would you be so kind to clarify this?
