You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a user needs to create many files (sometimes more than 10) to implement a single example using Dolphin. Although #7 solves this partially, #7 will not be resolved for a while. It'd be better if we can reduce the number of new files a user needs to code without the help of a DSL.
The text was updated successfully, but these errors were encountered:
Too many files also have bothered me. I think we can reduce the numbers by using inner classes.
For example, it seems that ClusteringPreCommGroup and KMeansMainCommGroup do not need to be a separate file.
Hi, I guess we could pack the classes together to reduce the number of files, but I'm not sure about using only a single file. We would have to pack CtrlTask, CompTask, StageInfo, the Launcher class (e.g. PageRankREEF), and the parameter classes together in one file, and that would be pretty ugly. I think we should consider abstracting the interfaces a bit more, than trying to implement an example that uses only one file.
Currently, a user needs to create many files (sometimes more than 10) to implement a single example using Dolphin. Although #7 solves this partially, #7 will not be resolved for a while. It'd be better if we can reduce the number of new files a user needs to code without the help of a DSL.
The text was updated successfully, but these errors were encountered: