Closed j-harbin closed 2 years ago
My feeling is that the name is correct, although I would only say this at 0.7 on the usual -1 to +1 scale.
My reasons are:
Change is bad. We have users, and we have docs, and we even have a paper. So the name should not change, because it might confuse people. However, to be frank, I do not think these built-in datasets are much use, because they will go out of date as e.g. realtime items might change to delayed mode.
It sort of feels natural, by analogy to other things. A normal car is just called, maybe "Golf". The somewhat souped-up one is called "Golf-GTI" , and the really souped-up one is "Golf-R".
PS. I think they are no longer selling Golfs in the US, only GTI and R. I guess Americans hate hatchbacks, because they think trunks are better against thefts, or something.
I can agree with the points you presented above. I'll close this issue.
I don't think this issue is of high priority, but while getting ready for the workshop, one thought I had was that the
index
built in dataset should be namedindexCore
. My reasoning for this is that the other built-in datasets say what type of file their are (ie. bgc, deep, synthetic). Thoughts?