ctools

ctobssim can take a large amount of memory if multiple runs are simulated at once. This is related to the fact that first all events are simulated and only after all simulations are done the results are saved. One can circumvent this by adding a save step directly after the simulation step in case that the @execute()@ method is called. The only problem is then that ctobssim may process the runs in parallel (due to the OpenMP) support, leading still to important memory requirements. But this could be controlled by setting the
<pre>
export OMP_NUM_THREADS=2 OMP_NUM_THREAD=2
</pre>
environment variable to limit for example the maximum number of threads to 2.