memory limitations to markstat
Adrian, many thanks. A 'marktable' function, as you describe it, would do what I have been doing with the combination of markstat and table--but presumably on much larger sets of points. Sounds like a useful addition! Cheers, Ian Robertson
adrian at maths.uwa.edu.au wrote:
If I understand correctly, you want to generate a large table in which the columns represent the points in the data pattern, the rows represent the possible mark values, and the entries are frequencies. Thus a column with entries 0, 2, 1, 0 means that there were 2 points with mark = 2 and 1 point with mark=3 in the r-neighbourhood of the point in question. The nearest existing equivalent in spatstat is Kcross (at least this is the function that has to compute how many points of type j there are within an r-neighbourhood of each point). I will implement a function `marktable' that does what you want, and add it to the next version of spatstat (1.12-6) that should be released this weekend. regards Adrian Baddeley