Changes between Version 1 and Version 2 of Notes/MiriadScalingLimitations

Timestamp:

06/07/07 17:42:53 (17 years ago)

Author:

mci156

Comment:

--

Notes/MiriadScalingLimitations

@@ -9 +9 @@
 There is also a {{{MAXBUF}}} parameter for the C parts of MIRIAD, defined in {{{inc/maxdimc.h}}}, but used only by tasks that use routines from {{{xyzio.c}}}.
 
-The maximum image size that can be handled is to some extent defined by the {{{MAXDIM}}} parameter in {{{inc/maxdim.h}}}, whcih 
-However the actual maximum may vary from that suggested by MAXDIM, depending on how big MAXBUF is, whether the task processes the entire image or in a raster fashion, and whether any subregions have been allocated out of the space defined by MAXBUF. This last item adds some unpredictability to the whole issue.
+The maximum image size that can be handled is to some extent defined by the {{{MAXDIM}}} parameter in {{{inc/maxdim.h}}}, which is often used to indicate the maximum size of maps (the longest side will be less than {{{MAXDIM}}}).
+However the actual maximum may vary from that suggested by MAXDIM, depending on how big {{{MAXBUF}}} is, whether the task processes the entire image or in a raster fashion, and whether any subregions have been allocated out of the space defined by {{{MAXBUF}}}. This last item adds some unpredictability to the whole issue; different ordering of clean windows may change the efficiency of allocation of chunks of {{{MAXBUF}}}.
 
 There are (now) comments in the include files explaining the upper limits in some detail.