-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sleipner CO2 .data won't run #4836
Comments
Hi, Thanks for reaching out. As seen in the console output ("Processing grid, Total number of active cells:"), the Sleipner data set has on the order of 1.98 million active cells, and typically requires at least 10-12 GB of RAM to run comfortably. Usually more if you're running the case in parallel. Although it doesn't say in your output, the "Killed" message may be generated by the operating system because you're running out of memory. Flow fundamentally expects that the host system has "enough" memory available and is not set up to deal with low-memory situations. For what it's worth, Flow does not generate the "Killed" message itself. |
Thanks Bård,
That makes perfect sense. I have a memory upgrade planned for the machine in question but right now it’s just 8Gb.
I’ll give it another go once I’ve installed the memory and see if it’ll run.
Thanks for the very rapid response.
Best regards
Rhod
Rhod Phillips
Principal Reservoir Engineer
ERCE
The expertise tomorrow needs
Office +44 (0) 20 8256 1150<tel:+442082561150>
Direct +44 (0) 20 8256 1168
Mobile +44 (0) 7962 676 303
***@***.******@***.***>
ERCE, Stephenson House
2 Cherry Orchard Road
Croydon, CR0 6BA, UK
On 5 Sep 2023, at 16:04, Bård Skaflestad ***@***.***> wrote:
Hi, I've just started investigating Flow and was interested in running the Sleipner CO2 flood dataset. I'm running Flow 2023.4 on an Ubuntu set of on a PC (v22.04.3).
Hi,
Thanks for reaching out. As seen in the console output ("Processing grid, Total number of active cells:"), the Sleipner<https://github.com/OPM/opm-data/tree/eaa2261683a97027e057c2bc49612ad1c86390b3/sleipner> data set has on the order of 1.98 million active cells, and typically requires at least 10-12 GB of RAM to run comfortably. Usually more if you're running the case in parallel. Although it doesn't say in your output, the "Killed" message may be generated by the operating system because you're running out of memory. Flow fundamentally expects that the host system has "enough" memory available and is not set up to deal with low-memory situations. For what it's worth, Flow does not generate the "Killed" message itself.
—
Reply to this email directly, view it on GitHub<#4836 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCLXQOTUYFSWMSU6PXQRA63XY45RNANCNFSM6AAAAAA4L5JZ5U>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
…________________________________
A Carbon Neutral Company
ERC Equipoise Limited is a limited company registered in England and Wales with number 03587074. Our registered office is Eastbourne House, 2 Saxbys Lane, Lingfield, Surrey RH7 6DN, UK. ERC Equipoise Pte Ltd is a private company limited by shares registered in Singapore with number 201535355Z. Our registered office is 48B Tras Street, #3-01, Singapore 078987.
The contents of this e-mail and any attachments are confidential to the intended recipient, and no third party is entitled to rely on them. If you are not the intended recipient please do not use or publish its contents,. Please contact us immediately, then delete. Emails are not secure and may contain viruses. We accept no liability for viruses or interception. Any email or communication which does not relate to the official business of ERC Equipoise Ltd or ERC Equipoise Pte Ltd, as applicable (“ERCE”) is neither given nor endorsed by it.
ERCE has made every effort to ensure that the interpretations, conclusions and recommendations set out in this email and its attachments are accurate and reliable in accordance with good industry practice. ERCE does not, however, guarantee the correctness of any such interpretations and shall not be liable or responsible for any loss, costs, damages or expenses incurred or sustained by anyone resulting from any interpretation or recommendation made by any of its officers, agents or employees. ERCE does not sanction the publication of any part of this email.
|
I am happy to help, because we're very much dependent on our users to grow the community. Do please get in touch if you run into other issues. |
Hi, I've just started investigating Flow and was interested in running the Sleipner CO2 flood dataset. I'm running Flow 2023.4 on an Ubuntu set of on a PC (v22.04.3). The file seemingly gets read OK but then dies at the first timestep with the work "Killed" as the only console output (console image attached). There is no user input at that stage. The PRT file doesn't see that but does write as far as saying it 's on time step zero. Is this an issue that anyone has come across before. The manual is pretty silent on cases killing themselves.
The text was updated successfully, but these errors were encountered: