From 41b604adfff2d0a77044581813a8b15e6b94f04b Mon Sep 17 00:00:00 2001 From: Nicola Baldo Date: Tue, 6 Nov 2012 11:45:12 +0100 Subject: [PATCH] minor update to lte-user docs --- src/lte/doc/source/lte-user.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/src/lte/doc/source/lte-user.rst b/src/lte/doc/source/lte-user.rst index ac4dc28ea..a648ad0fd 100644 --- a/src/lte/doc/source/lte-user.rst +++ b/src/lte/doc/source/lte-user.rst @@ -547,9 +547,12 @@ create one separate instance for each REM. Note that the REM generation is very demanding, in particular: * the run-time memory consumption is approximately 5KB per pixel. For example, - a REM with a resolution of 500x500 needs about 1.25 GB of memory, and - a resolution of 1000x1000 needs about 5 GB (too much for a - regular PC at the time of this writing). + a REM with a resolution of 500x500 would need about 1.25 GB of memory, and + a resolution of 1000x1000 would need needs about 5 GB (too much for a + regular PC at the time of this writing). To overcome this issue, + the REM is generated at successive steps, with each step evaluating + at most a number of pixels determined by the value of the + the attribute ``RadioEnvironmentMapHelper::MaxPointsPerIteration``. * if you generate a REM at the beginning of a simulation, it will slow down the execution of the rest of the simulation. If you want to generate a REM for a program and also use the same program to