View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001890 | OpenFOAM | Bug | public | 2015-11-02 19:23 | 2016-02-02 18:26 |
| Reporter | GRAUPS | Assigned To | henry | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Intel64 | OS | RHEL | OS Version | 6.6 |
| Product Version | dev | ||||
| Summary | 0001890: timeActivatedFileUpdate function object inconsistent behavior | ||||
| Description | I've been trying to use the timeActivatedFileUpdate function object to update fvSchemes files to start simulations in first order and then switch to second order after a certain period. I've noticed that after the file update, OpenFOAM sometimes never re-reads the updated file (it follows a pattern though). Attached is a modified pitzDaily model. I've added fvSchemes_good and a fvSchemes_bad files. The fvSchemes_bad file has all divSchemes removed from it. I also added a time timeActivatedFileUpdate function object to the controlDict which at the beginning of the simulation (timestep -1) it updates fvSchemes to the fvSchemes_good file and at timestep 5 updates it to the fvSchemes_bad file (which should produce an error after it re-reads). | ||||
| Steps To Reproduce | 1.) Run allrun, the simulation will update the fvSchemes file to fvSchemes_good at the beginning of the simulation and to fvSchemes_bad at iteration 5 but will not re-read fvSchemes after iteration 5. The simulation will finish successfully because it's still using the old fvSchemes_good config. 2.) After the above simulation finishes, rm log files and run allrun again. The simulation will update the fvSchemes file to fvSchemes_good at the beginning of the simulation, however, it will not re-read it before starting the simulation and instead uses the fvSchemes as it was at the end of the last simulation (fvSchemes_bad). The simulation errors out. | ||||
| Additional Information | The above problem exists in both dev and 2.4.x. If you're able to fix this in both dev and 2.4.x, that would be best. | ||||
| Tags | functionObject, fvSchemes, pitzDaily, timeActivatedFileUpdate | ||||
|
|
|
|
|
small correction, in the report I said fvSchemes gets updated at iteration 5, but in the attached model it's configured to happen at iteration 10. FYI. |
|
|
What fileModificationChecking options have you tried: //- Modification checking: // - timeStamp : use modification time on file // - inotify : use inotify framework // - timeStampMaster : do time stamp (and file reading) only on master. // - inotifyMaster : do inotify (and file reading) only on master. fileModificationChecking timeStampMaster; and what fileModificationSkew are you using? |
|
|
Orphaned report. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-11-02 19:23 | GRAUPS | New Issue | |
| 2015-11-02 19:23 | GRAUPS | File Added: pitzDaily_file_update_bug.tar.gz | |
| 2015-11-02 19:52 | GRAUPS | Tag Attached: fvSchemes | |
| 2015-11-02 19:52 | GRAUPS | Tag Attached: pitzDaily | |
| 2015-11-02 19:52 | GRAUPS | Tag Attached: timeActivatedFileUpdate | |
| 2015-11-02 19:52 | GRAUPS | Tag Attached: functionObject | |
| 2015-11-02 19:54 | GRAUPS | Note Added: 0005543 | |
| 2016-01-17 12:16 | henry | Note Added: 0005839 | |
| 2016-02-02 18:26 | henry | Note Added: 0005875 | |
| 2016-02-02 18:26 | henry | Status | new => closed |
| 2016-02-02 18:26 | henry | Assigned To | => henry |
| 2016-02-02 18:26 | henry | Resolution | open => fixed |
