Currently the datasets are stored in a folder inside the current directory where the application has been started ("./datasets/").
This directory may or may not be accessible/writeable so we cannot rely on it. Also different projects are possibly using this library and all have their own datasets directory while they could all use the same files.
A way to specify the directory to be used should be implemented. I think the path to such a directory should be specified as a system property (System.setProperty(key, value)) and System.getProperty(key)). This way the dir can be set in code or even from the command line with java -DmyProperty="myValue" -jar myApplication.jar or different mechanisms.
A name (key) for the property will be needed, I'd suggest something like "dimred.datastes.directorypath".
When checking for this property, but it's not set (returns null), then we can fall back to "./datasets/" which we currently use.
Currently the datasets are stored in a folder inside the current directory where the application has been started (
"./datasets/"). This directory may or may not be accessible/writeable so we cannot rely on it. Also different projects are possibly using this library and all have their own datasets directory while they could all use the same files.A way to specify the directory to be used should be implemented. I think the path to such a directory should be specified as a system property (
System.setProperty(key, value))andSystem.getProperty(key)). This way the dir can be set in code or even from the command line withjava -DmyProperty="myValue" -jar myApplication.jaror different mechanisms. A name (key) for the property will be needed, I'd suggest something like"dimred.datastes.directorypath".When checking for this property, but it's not set (returns null), then we can fall back to
"./datasets/"which we currently use.