This repository contains the OCD service of WebOCD. In the repository, java based codes of overlapping community detection algorithms (OCDA) can be found.
Currently the ocd service itself is only really able to log wrong requests. It would be highly beneficial to relay more information regarding which algorithm is executed and with what parameters, adding to that if it fails and why it fails.
For algorithm classes we can for example currently not use the one of the service classes because using this logger outside the class does not produce any output. Using an own logger here would however produce an own file.
General ideas on how to circumvent this would be to either have one central object/class with a logger that gets information from other objects, or to use an other logging library than las2peers built in one
Currently the ocd service itself is only really able to log wrong requests. It would be highly beneficial to relay more information regarding which algorithm is executed and with what parameters, adding to that if it fails and why it fails. For algorithm classes we can for example currently not use the one of the service classes because using this logger outside the class does not produce any output. Using an own logger here would however produce an own file. General ideas on how to circumvent this would be to either have one central object/class with a logger that gets information from other objects, or to use an other logging library than las2peers built in one