Open nategarver-daniels opened 8 years ago
Try using the 'scrunch' functionality. Right now it is up-sampling the frequency axis to 524288 channels to get to the maximum DM. With scrunching it will instead down sample the time axis for the higher DMs (where time is smeared anyhow).
Let me know if this works for you. To close this issue, I suppose I should put a note about memory requirements, and how to get around them, in the README. Your thoughts?
Kiyo,
I think you can close the issue. Makeing a note about the memory requirements would be good though. I tried the --scrunch option but ended up with a different error (but one possibly related to compiling the package). I also tried limiting the DM range to just a few DM but was still getting memory errors. Trying to sort out if it's a system issue or if I really need to be using a lot of nodes over MPI to spread things out (and reduce the memory pressure on each individual node)
-Nate
On 07/14/2016 12:31 PM, Kiyoshi Masui wrote:
Let me know if this works for you. To close this issue, I suppose I should put a note about memory requirements, and how to get around them, in the README. Your thoughts?
You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/kiyo-masui/burst_search/issues/37#issuecomment-232718732
I'm probably doing something wrong, but I've been trying to run burst_guppi on some 820MHz GUPPI search data that I have. The file size is ~11G and I inevitably get a MemoryError after the code runs for 20 minutes or so. Program output is:
I suspect that there is probably something simple that I'm not doing.