AREDAM(3NCARG)
β¨ AREDAM β bestie, we're adding edge segments to an area map π
okay so real quick, this is a page from the NCAR GRAPHICS manual, and it lives in section 3NCARG. It's giving "niche but iconic," and honestly? We love her for it. π
πΈ NAME πΈ
AREDAM β she adds edge segments to an area map. That's it. That's the whole job. Slay. π
π¦ SYNOPSIS π¦
CALL AREDAM (MAP,XCA,YCA,LCA,IGI,IDL,IDR)
β¨ C-BINDING SYNOPSIS β¨
#include <ncarg/ncargC.h>
void c_aredam (int *map, float *xca, float *yca, int lca, int igi, int
idl, int idr)
π DESCRIPTION π
okay so here's the lineup, bestie, every single one of them, no skips:
MAPβ an input/output array of type INTEGER, aka an array holding an area map that has already been initialized by a call toARINAM.
note bestie: whenARINAMinitialized the area map, it stored the dimension ofMAPinsideMAP(1). so the dimension does NOT have to be passed as an argument when you callAREDAM. she already knows her own size. main character energy. π
XCAβ an input array, dimensionedLCA, of type REAL. These are the X coordinates (in the user coordinate system) of the points that define an edge. πYCAβ an input array, dimensionedLCA, of type REAL. The Y coordinates (in the user coordinate system) of those same points defining an edge. πLCAβ an input expression of type INTEGER. It's the number of coordinates sitting inXCAandYCA. count 'em. π’IGIβ an input expression of type INTEGER. The identifier of the group that the edge belongs to. π·οΈIDLβ an input expression of type INTEGER. The identifier of the area lying to the left of the edge. β¬ οΈIDRβ an input expression of type INTEGER. The identifier of the area lying to the right of the edge. β‘οΈ
π C-BINDING DESCRIPTION π
the C-binding argument descriptions are literally the same as the FORTRAN argument descriptions. same energy, different font. π«Ά
π₯ USAGE π₯
The area-map array MAP must have been initialized by a call to ARINAM β no skipping that step, bestie, she needs her setup. π
After that, every subsequent call to AREDAM adds the LCA-1 edge segments to the area map. Those segments are defined by the points whose user coordinates live in the arrays XCA and YCA. and here's how the pairing goes, it's lowkey simple:
- points 1 and 2 define the first edge segment
- points 2 and 3 define the next edge segment
- points 3 and 4 define the one after that
- and so on, forever, iconic behavior
β EXAMPLES β
use the ncargex command to see the following relevant examples, bestie, go look, they ate:
cardb1, cardb2, carfill, carline, carmap, arex01, cbex01, tareas, fsppoint
π ACCESS π
to use AREDAM or c_aredam, load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c β preferably in that exact order, no cap. π
π MESSAGES π
see the areas man page for a description of all Areas error messages and/or informational messages. she's got receipts. π§Ύ
πΈ SEE ALSO πΈ
Online: areas, areas_params, ardbpa, ardrln, argeti, argetr, argtai, arinam, armvam, arpram, arscam, arseti, arsetr, ncarg_cbind
Hardcopy: NCAR Graphics Contouring and Mapping Tutorial
π COPYRIGHT π
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, we did it π this lil gem came to you courtesy of the UNIX manual, dated March 1993, filed under AREDAM(3NCARG) β fr fr, iconic since '93. bye bestie, go plot something gorgeous π¦β¨
π¦ where this page comes from
- epel 9: ncl-devel 6.6.2-59.el9 Β· LicenseRef-Callaway-BSD
- fedora 43: ncl-devel 6.6.2-58.fc43 Β· LicenseRef-Callaway-BSD
- fedora 44: ncl-devel 6.6.2-62.fc44 Β· LicenseRef-Callaway-BSD
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms