I don't think the (tri)pcolor(foo) family is directly comparable as for them the color is the most important thing, whereas for quiver and scatter it's just one possible way to decorate (in a nontechnical sense) the artist. (usually of a person) lacking in intelligence, common sense, or just in general awareness clumsy or idiotic. for plot() if we decide one day to deprecate shorthands (not suggesting this here) having it in quiver() won't make the deprecation easier or harder.) So I guess we can rename C to c (right now it's positional only so its name is not part of the API c is consistent with scatter) and keep color as a synonym? (It's a standard synonym anyways, e.g. past few months as a new arrow in the quiver of State-sponsored terrorism. unless we flatten everything and ignore mismatching shapes, as we do right now :/). Translation for quiver in the free English-French dictionary and many other. This arrow and quiver set may look dangerous, but in reality, its just paper. This is consistent with scatter, and there is no risk of confusion as the shapes clearly indicate which is the case (. synonyms ssr messages appraisal Search Printable Synonyms and. So I guess the question is whether we want to overload the same argument to mean "either scalar values that will be colormapped, or RGB(A) values". flit, hover Ana shake, tremble, quiver, quaver, wobble : beat. Alternatively, we could instead deprecate C in favor of color, which would have the benefit of making the signatures a bit nicer (now it's just quiver(U, V, **kwargs) and quiver(X, Y, U, V, **kwargs)) but is perhaps mildly more disruptive.Ĭ is working for setting scalar values that will be normalized and colormapped. Gmc compare Old English cocer quiver Anglo-French quiveir, variant of Old French quivre. A Dictionary of Discriminated Synonyms with Antonyms and Analogous and Contrasted. The color arg could also be deprecated, as it is now a complete synonym for C. I'm not sure the behavior change needs a deprecation period (it would only affect people purposefully passing three or four times to many values as the C array as the rest would currently be ignored) obviously there would be a deprecation during which non-matching X, Y, U, V would warn instead of error out. I propose to instead make C check its shape if its shape is (*X.shape, 3) or (*X.shape, 4), then treat it as RGB if its shape is X.shape, treat it as colormapped values otherwise, error out (and for consistency, check that the shapes of X, Y, U, V all match (instead of flattening them all)).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |