These two things above can be stored into config namespace not to leave it without namespace..

What do you want to use namespace for here?

Hm, actually the goal is just to use namespace. To have all the supporting stuff in one place and be sure you're referring to the them right

tend do agree, config::colors or config::keys would be easier to read when you see it in the code below

I think it's not really needed to store it in an anonymous namespace.
Maybe, to one of around - below or above?

Unfortunately, need.

So, at your discretion whether to move it into, for example, custom namespace below

Don't we have this feature already? I believe someone in the team has proposed that a while ago -- only passing .xml so that .bin is identified automatically

Why such #if needed in there, if it's handled inside giewrapper

It is for findDataFile(). For age gender we can find path for old IE. I don't know old path for semantic segmentation. And old IE isn't tested now, old path for network is deprecated.

old path - look at std::string SUBDIR *

Should I delete it?

Removed test.

Hm, actually the goal is just to use namespace. To have all the supporting stuff in one place and be sure you're referring to the them right

So, at your discretion whether to move it into, for example, custom namespace below

tend do agree, config::colors or config::keys would be easier to read when you see it in the code below

Don't we have this feature already? I believe someone in the team has proposed that a while ago -- only passing .xml so that .bin is identified automatically

I'd call it "colorize" or smt like this

I'd move it out of the kernel, if possible, and make it part of the graph.

Custom kernel could only produce a mask, and the rest done with our standard ops.

There are performance reasons to do that (e.g. involving a fluid backend for *, +, 1- and so on)

Again, it can be done after we merge this fix itself, so just take all sample-related comments as a to-do