Re:Sniper – An efficient multi-scale object detection algorithm
by tabtab on Friday June 22, 2018 @06:57PM
(#17378217)
Re: "Let's be honest, the main use...going to be military."
While perhaps true, usually one finds a friendlier name regardless, in order to hide or reduce the perception of association with war. It's why we have a "Dept. of Defense" instead of a "Dept. of Offense" or "Dept. of War". I'm not necessarily condoning such a practice, merely making an observation of product and project naming practices.
Re:Sniper – An efficient multi-scale object detection algorithm
by _nothing on Friday June 22, 2018 @12:33PM
(#17375314)
Speaking of pontification and making mountains out of molehills, your response currently has more text than all the other replies combined.
No one here is "offended" by the name and you're the only one who seems "triggered", somehow connecting the reaction to liberal white men being offended by trivialities.
People are merely considering the implications of the name, which is a mature and reasonable thing to do. You're free to argue for its benignity and many of us would agree with you, but when you get up on a soapbox against "political correctness" (which has nothing to do with this), you're going to get a lot of eye rolls.
Re:Sniper – An efficient multi-scale object detection algorithm
by alexbeloi on Friday June 22, 2018 @04:02PM
(#17376906)
Competition is welcome, deep stack knowledge from driver to model building is hard to come by (it's more than just matrix multiplies).
To compete with CUDA you need high performance drivers and people that can write them, and also be able to anticipate and keep up with the future needs of ML as well as hardware development.
Re:Sniper – An efficient multi-scale object detection algorithm
by HanayamaTriplet on Friday June 22, 2018 @03:01PM
(#17376472)
The current title refers to the algorithm as "Sniper", but the name appears to actually be "SNIPER". According to the paper [1] linked in the repo, that stands for "Scale Normalization for Image Pyramids with Efficient Resampling."
Cars, household-robots, etc. all need to get around as well.
While perhaps true, usually one finds a friendlier name regardless, in order to hide or reduce the perception of association with war. It's why we have a "Dept. of Defense" instead of a "Dept. of Offense" or "Dept. of War". I'm not necessarily condoning such a practice, merely making an observation of product and project naming practices.
No one here is "offended" by the name and you're the only one who seems "triggered", somehow connecting the reaction to liberal white men being offended by trivialities.
People are merely considering the implications of the name, which is a mature and reasonable thing to do. You're free to argue for its benignity and many of us would agree with you, but when you get up on a soapbox against "political correctness" (which has nothing to do with this), you're going to get a lot of eye rolls.
To compete with CUDA you need high performance drivers and people that can write them, and also be able to anticipate and keep up with the future needs of ML as well as hardware development.
[1]: https://arxiv.org/abs/1805.09300