Closed buutrg closed 2 years ago
Hi thanhbuu04, the SAIGE getting killed - this may be due to the fact that SAIGE's memory requirement exceeds the machine's capacity. To test this hypothesis, you'll have to start SAIGE while monitoring SAIGE's resources using "top" on a UNIX computer, or the "system monitor" on a Windows station. If SAIGE uses more than 80-90% of the computer's memory then it might be killed by the operating system. Please let us know!
Hi @thanhbuu04, the memory usage can be estimated as #markers * #samples/4 bytes, so you job should only need < 1 Gb . As @unepanthere suggested, can you try use "top" to monitor?
Thanks, Wei
We have just released a new version 1.0.0. It has substantial computational efficiency improvements for both Step 1 and Step 2 for single-variant and set-based tests and clearer log output. We have created a new program github page https://github.com/saigegit/SAIGE with the documentation provided https://saigegit.github.io/SAIGE-doc/ The program will be maintained by multiple SAIGE developers there. The docker image has been updated. Please feel free to try the version 1.0.0 and report issues if any.
Thanks! Wei
Dear Authors, I am using SAIGE for binary trait association analysis but it is said that the program is killed after a few iterations? May I ask how to solve this problem? Your help is really appreciated!