View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004184 | OpenFOAM | Contribution | public | 2024-11-25 07:45 | 2024-11-26 12:01 |
Reporter | nguyenhung97 | Assigned To | will | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | GNU/Linux | OS | Other | OS Version | (please specify) |
Product Version | 12 | ||||
Summary | 0004184: Particle got stuck warning cause too much space for log | ||||
Description | We injected about 1 million particles and the particle got stuck warning cause too much space for log (~ 500Gb). According to my previous issue #0004183, this is because the log is written at every time step which could be hundreds of thousands and combined with about 1 million particles injected many warnings were created. An option of writing this log or not should be added for log-friendly feature but since particle.C does not read data from dictionary so I don't know how to modify it yet. Maybe we can put it in an if (debug) as follows: if (debug) { // Warn if stuck, and incorrectly advance the step fraction to completion WarningInFunction << "Particle #" << origId_ << " got stuck at " << position(mesh) << endl; } | ||||
Tags | No tags attached. | ||||
|
I think if that many parcels are getting stuck then you have larger issues. Regardless, as with the previous report, if you want the logging customised for the convenience of your workflow then you will need to pay for that work. Closed pending funding. |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-11-25 07:45 | nguyenhung97 | New Issue | |
2024-11-26 12:01 | will | Assigned To | => will |
2024-11-26 12:01 | will | Status | new => closed |
2024-11-26 12:01 | will | Resolution | open => no change required |
2024-11-26 12:01 | will | Note Added: 0013478 | |
2024-11-26 12:01 | will | Note Edited: 0013478 |