ARINAM(3NCARG)

✨ ARINAM ✨ β€” it's giving "area map origin story" πŸ’–

okay bestie, so this is ARINAM, a lil routine from the NCAR GRAPHICS library (you'll find it filed under section 3NCARG, iykyk). Its whole job? Initializes an area map. That's it, that's the vibe. πŸŽ€


🌸 SYNOPSIS 🌸

CALL ARINAM (MAP,LMAP)

like. that's the whole summoning ritual. ✨


πŸ’œ C-BINDING SYNOPSIS πŸ’œ

for my C girlies 🫢

#include <ncarg/ncargC.h>

void c_arinam (int *map, int lmap)

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's what those two lil arguments actually do, no gatekeeping:

  • MAP β€” (output array, of type INTEGER, dimensioned at least LMAP) β€” this is the integer array where your area map gets built, bestie. it's the canvas, it's the main character. ✨ and here's the tea: every single vertex for an edge segment in your area map eats up ten words in the array MAP. ten. words. per. vertex. and no, you cannot forget the extras β€” the total vertex count includes the ones added at each intersection of edges, plus the ones added when long edge segments get broken into shorter edge segments. so budget accordingly, okay? don't come crying to me when your array is too smol 😭
  • LMAP β€” (an input expression of type INTEGER) β€” this is just the length of the MAP array. boring, right? WRONG. because as part of the initialization process, the value of LMAP gets stored in MAP(1) πŸ‘‘ which means you never have to pass it as an argument again in calls to the other routines that use the area map. it remembers for you. it's giving thoughtful. πŸ’…

🧚 C-BINDING DESCRIPTION 🧚

the C-binding argument descriptions are literally the same as the FORTRAN argument descriptions. same facts, different accent. no notes. πŸ’–


⭐ EXAMPLES ⭐

want to see this thing in action? use the ncargex command to check out these relevant examples β€” and yes, I'm listing every single one, because we don't skip:

cardb1, cardb2, carfill, carline, carmap, ccpcldm, ccpfil, ccplbam, ccpllb, ccpllc, ccplll, ccpllo, ccpllp, ccpllt, ccpllw, ccppc, ccppc1, ccppc2, ccppc3, ccppc4, ccprc, ccpscam, ccpvs, colcon, cmpfil, cmpgrp, cmpita, cpmitm, cmplab, cmpmsk, cmptit, cpex01, cpex02, cpex03, cpex04, cpex05, cpex06, cpex07, cpex08, eezmpa, arex01, cbex01, vvex01, tareas, tconpa, tezmpa, fcover, ffex00, ffex03, ffex05, fcirc, fsfsgfa, fsppoint.

that's a whole buffet, go feast. πŸ“


πŸ”₯ ACCESS πŸ”₯

to use ARINAM or c_arinam, you gotta load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c β€” and preferably in that order. order matters, bestie, don't freestyle it. ✨


🌈 SEE ALSO 🌈

Online: areas, areas_params, ardbpa, ardrln, aredam, argeti, argetr, argtai, armvam, arpram, arscam, arseti, arsetr, ncarg_cbind

Hardcopy: NCAR Graphics Contouring and Mapping Tutorial

go read, I'll wait. πŸ“š


Copyright (C) 1987-2009 University Corporation for Atmospheric Research The use of this Software is governed by a License Agreement.

yes, that's the real legal text, keep it, respect it, don't touch it. πŸ’…

okay and finally, the lil sign-off: this page lives in the NCAR GRAPHICS manual, it's from March 1993 (aged like fine wine fr fr 🍷), and it was formatted for UNIX. mwah. bye bestie, go init some area maps πŸ’–βœ¨πŸŽ€