Displaying 1 result from an estimated 1 matches for "ennorm".
Did you mean:
nnnorm
2005 Nov 15
1
cannot.allocate.memory.again and 32bit<--->64bit
...3.4 150315042 1146.9 150060261 1144.9
> object.size(my.matrix)/1024^2 #calculate object.size directly
[1] 381.4698
so, the matrix actually - according to the used.Mb - needs the same Mb
as the vector.
but, the trigger.Mb - and i still have problems with understanding of
this - grows ennormously.
and i can sure, i had received the "cannot allocate the vector of
xxxKb"-error last time, trying the same experiment.
if we know, that the matrix (or array generally) is acctually alloccated
as a vector (with removed dimensions), why do we need so much trigger.Mb
for it?
is...