KUMY(3NCARG)

πŸ“¦ version 6.6.2, in epel 9, fedora 43, fedora 44

πŸ’– KUMY β€” the 3NCARG glow-up πŸ’–

okay bestie, so this is the KUMY page from the NCAR Graphics manual (3NCARG, the whole family reunion of converter functions) and honestly? it's giving ✨coordinate transformation✨ and we're gonna get through it together.

🌸 NAME 🌸

KUMY β€” literally just converts from user coordinates to metacode coordinates. that's the whole job. no cap.


πŸ¦‹ NAME (the sequel, aka spps_converters) πŸ¦‹

spps_converters is a whole squad of functions, and each one transforms a coordinate from one NCAR Graphics coordinate system to another. the full roster, alphabetically, no one left out:

CFUX, CFUY, CMFX, CMFY, CMUX, CMUY, CPFX, CPFY, CPUX, CPUY, CUFX, CUFY, KFMX, KFMY, KFPX, KFPY, KMPX, KMPY, KPMX, KPMY, KUMX, KUMY, KUPX, KUPY.

twenty-four icons. that's it, that's the list. πŸ‘‘


⚠️ STATUS ⚠️

okay so listen. Plotter Address Units (PAUs) and Metacode Units (MUs) are no longer used in NCAR Graphics. so every single function with either an M or a P as the second or third letter of the name? obsolete, bestie. retired. living in the past. πŸ™ˆ

The coordinate systems we actually recognize these days are:

  • GKS world coordinates
  • GKS normalized device coordinates
  • NCAR Graphics fractional coordinates
  • NCAR Graphics user coordinates

if you want the full lore on those, go read the NCAR Graphics document "NCAR Graphics Fundamentals, UNIX Version". it's the source material, iykyk. πŸ“–

now, for the purpose of interpreting and converting codes that still use PAUs or MUs, here are the definitions, preserved for the archives:

The plotter coordinates of a point are integers IPX and IPY, where IPX is between 1 and 2**MX and IPY is between 1 and 2**MY. MX and MY are internal parameters of SPPS; each has a default value of 10. Values of MX and MY can be set by calling the routines SETI or SETUSV and retrieved by calling the routines GETSI or GETUSV. 🫢

The metacode coordinates of a point are integers IMX and IMY between 0 and 32767 inclusive. The area addressed is a square in a "metacode space" that is usually mapped into a square subset of the addressable area of the plotting device. Metacode coordinates were used in calls to the routine PLOTIT and are returned in calls to FL2INT. πŸ’…


✨ SYNOPSIS ✨

Current:

X = CFUX (RX),  Y = CFUY(RY)
X = CUFX (RX),  Y = CUFY(RY)

Obsolete:

X = CMUX (IX),  Y = CMUY(IY)
X = CPUX (IX),  Y = CPUY(IY)
X = CMFX (IX),  Y = CMFY(IY)
X = CPFX (IX),  Y = CPFY(IY)
I = KFMX (RX),  J = KFMY(RY)
I = KUMX (RX),  J = KUMY(RY)
I = KFPX (RX),  J = KFPY(RY)
I = KUPX (RX),  J = KUPY(RY)
I = KPMX (IX),  J = KPMY(IY)
I = KMPX (IX),  J = KMPY(IY)

πŸŽ€ C-BINDING SYNOPSIS πŸŽ€

#include <ncarg/ncargC.h>

float c_cfux (float rx)

float c_cfuy (float ry)

float c_cufx (float rx)

float c_cufy (float ry)

🌈 DESCRIPTION 🌈

  • RX β€” an input expression of type REAL, and it's an X coordinate in whatever coordinate system the second letter of the function name says. so in a reference to CFUX, RX is a fractional X coordinate; in a reference to CUFX, RX is a user X coordinate. same letter, different vibe. πŸ’«
  • RY β€” an input expression of type REAL, a Y coordinate in the coordinate system specified by the second letter of the function name. in a reference to CFUY, RY is a fractional Y coordinate; in a reference to CUFY, RY is a user Y coordinate.
  • IX and IY β€” these only show up as arguments in references to some of the obsolete functions. they're input expressions of type INTEGER, specifying the X and Y coordinates of a point in either PAUs or MUs (which one depends on the second letter of the function name).

now the naming scheme, because bestie this is genuinely elegant and i'm obsessed:

  • The first letter of the function name is a C if the result is of type REAL and a K if the result is of type INTEGER (and that only happens for some of the obsolete ones). this conforms to the usual FORTRAN convention for implicit typing. slay, honestly.
  • The second letter of the function name specifies the coordinate system of the argument.
  • The third letter of the function name specifies the coordinate system of the functional result. in references to CFUX and CFUY, the result is in the user system; in references to CUFX and CUFY, the result is in the fractional system. (yes the letters swap, yes that's the point πŸ’…)
  • The fourth letter of the function name is an X or a Y, depending on whether an X or a Y coordinate is being converted.

πŸ’œ C-BINDING DESCRIPTION πŸ’œ

The C-binding argument description is the same as the FORTRAN argument description. copy-paste energy, but make it official.


πŸ“ EXAMPLES πŸ“

Use the ncargex command to see the following relevant examples which use coordinate converters: mpex10, cbex10, sfex02, epltch.

The command "ncargex -n mpex10" will load the driver mpex10.f into your current working directory where you can examine the file using a local editor, or the UNIX more command. go peek at it, it's cute. πŸ‘€


πŸ”₯ ACCESS πŸ”₯

There were 24 conversion functions in the original set. These functions (12 for the X coordinate of a point, and 12 for the Y coordinate) allowed one to convert between any combination of PAUs, MUs, fractional coordinates, and user coordinates. absolute versatility era.

But PAUs and MUs are now obsolete, so only four of the conversion functions are still pertinent: CFUX and CFUY allow one to convert the X and Y coordinates of a point from the fractional system to the user system, while CUFX and CUFY do the opposite. four survivors. main character energy, honestly. ⭐

To use any of the conversion routines, load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c, preferably in that order. order matters, bestie, don't fight it. 🧚

🌟 SEE ALSO 🌟

Online: cfux, cfuy, cmfx, cmfy, cmux, cmuy, cpfx, cpfy, cpux, cpuy, cufx, cufy, kfmx, kfmy, kfpx, kfpy, kmpx, kmpy, kpmx, kpmy, kumx, kumy, kupx, kupy, spps, ncarg_cbind

Hardcopy: NCAR Graphics Fundamentals, UNIX Version; User's Guide for NCAR GKS-0A Graphics


Copyright (C) 1987-2009 University Corporation for Atmospheric Research

The use of this Software is governed by a License Agreement.


and that's the whole page, bestie πŸ’– this came from the UNIX release, dated March 1993, under the SPPS_converters(3NCARG) banner β€” and yes, KUMY(3NCARG) is the title up top, NCAR GRAPHICS is the family it runs with. take care of your coordinates and they'll take care of you πŸ¦‹βœ¨

πŸ“¦ where this page comes from