Structure for NAS algorithms

[andreyvelich]

/kind feature

Since I am planning to support DARTS in Katib, I have few thoughts and questions about current NAS algorithms.

1. Do we want to name each NAS algorithm starting with nas. For example: nasdarts? Or we can name it with algorithm name, e.g darts.
2. Rename nasrl to enas. I think it will be more clear to user, since we are using ENAS implementation.
3. Do we want to create nas directory under suggestion folder. User can easily see what HP and NAS algorithms do we support.

What do you think @gaocegege @johnugeorge ?

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
question	0.83

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[gaocegege]

SGTM. I will add it into 2020 roadmap.

/priority p1

[andreyvelich]

/area nas

[andreyvelich]

What do you think about 1st and 3rd step? @gaocegege @johnugeorge
Should we name nas algorithms starting with nas or just like name of the algorithm?

[johnugeorge]

3 looks ok as it is just directory refactoring.

For 1, is it really required? If it needs to be added, I feel that we have to tag existing hp algorithms too.

[andreyvelich]

For 1, is it really required? If it needs to be added, I feel that we have to tag existing hp algorithms too.

No, it is not required. I am just worrying how users will distinguish HP and NAS algorithms.

[andreyvelich]

/assign @andreyvelich