Operation Manual

Chapter 18: Memory and Variable Management 329
Archiving and unarchiving can be done in two ways:
• Use the
5:Archive or 6:UnArchive commands from the MEMORY menu or CATALOG.
• Use a Memory Management editor screen.
Before archiving or unarchiving variables, particularly those with a large byte size (such as large
programs) use the MEMORY menu to:
• Find the size of the variable.
• See if there is enough free space.
Note: If there is not enough space, unarchive or delete variables as necessary. Be aware that when you
unarchive a variable, not all the memory associated with that variable in user data archive will be
released since the system keeps track of where the variable has been and where it is now in RAM.
Even if there appears to be enough free space, you may see a Garbage Collection message when you
attempt to archive a variable. Depending on the usability of empty blocks in the user data archive, you
may need to unarchive existing variables to create more free space.
Polar functions
r1, r2, r3, r4, r5, r6 no not
applicable
Sequence
functions
u, v, w no not
applicable
Stat plots
Plot1, Plot2, Plot3
no not
applicable
Graph
databases
GDB1, GDB2,...
yes yes
Pictures (Pic
Vars)
Pic1, Pic2, ... , Pic9,
Pic0
yes no
Background
Images (Image
Vars)
Image1, Image2, ... ,
Image9, Image0
yes no
Strings
Str1, Str2, . . . Str9,
Str0
yes yes
Tables
TblStart, @Tbl,
TblInput
no not
applicable
Apps Applications see Note
above
no
AppVars Application variables yes yes
Groups see Note
above
no
Variables with
reserved names
minX, maxX, RegEQ,
and others
no not
applicable
System variables
Xmin, Xmax, and
others
no not
applicable
For: Sizes must be such that:
Archive Archive free size > variable size
UnArchive RAM free size > variable size
Variable Type Names
Archive?
(yes/no)
UnArchive?
(yes/no)