Restore a script to the runtime environment
You can retrieve a script that was removed from the runtime environment but is still saved in
nonvolatile memory.
To restore a script from nonvolatile memory into the runtime environment, you can use
script.restore("scriptName"), where scriptName is the user-defined name of the script to
be restored.
For example, to restore a user script named "test9" from nonvolatile memory:
script.restore("test9")
Memory considerations for the runtime environment
The 2600B reserves 32 MB of memory for dynamic runtime use. Approximate allocation of this
memory is shown below:
Note that the runtime environment, user-created reading buffers, and active sweep configuration must
fit in the 24 MB of memory that is available. The amount of memory used by a reading buffer is
approximately 15 bytes for each entry requested.
Reading buffers also use a small amount of memory for reading buffer management, which is not
significant when making memory utilization calculations. For example, assume two reading buffers
were created. One of them was created to store up to 1,000 readings and the other to store up to
2,500 readings. The memory reserved for the reading buffers is calculated as follows:
(1000 * 15) + (2500 * 15) = 52,500 bytes or 52.5 kilobytes
Note that the dedicated reading buffers do not consume memory that is needed by the runtime
environment; do not include them in your memory consumption calculations. Also, reading buffers for
remote nodes consume memory on the remote node, not the local node. Make sure the total reading
buffer memory for any particular remote node does not exceed 24 MB, but do not include that amount
in your local memory consumption calculations.
The amount of memory used by a sweep configuration is based on the number of source points. The
actual memory consumption can vary greatly depending on the source-measure unit (SMU) settings,
but as a general rule, each source point can be expected to consume at least 24 bytes.
It is possible for the memory used for the runtime environment, sweep configuration and reading
buffers to exceed 24 MB. When this occurs, there is a risk that memory allocation errors will occur
and commands will not be executed as expected.