View Issue Details

IDProjectCategoryView StatusLast Update
0001776OpenFOAMBugpublic2015-09-12 13:32
Reporteruser758Assigned Towyldckat  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionunable to reproduce 
PlatformGNU/LinuxOSOpenSuSEOS Version13.2
Summary0001776: clock time per iteration increases during sub iterations within time step
DescriptionIf sub-iterations are used within a time step the clock time per individual iteration decreases with increasing sub-iteration steps.

In essence the solver steps are slowing down as a function of how many sub-iterations are required within a model. When the time step is advanced the speed per iteration resets and then slowly increases again as the sub-iteration process proceeds.
Steps To ReproduceThis behaviour is not present in version 1.6. Steps to reproduce involve adding a manual sub-iteration loop within the pitzDaily and outputing time per sub-iteration. The time used per sub-iteration steadily increases as more iterations are taken.

A modified pitzDaily is available to demonstrate the issue.
Additional InformationThis issue is not present in version 1.6 and is present in 2.3.x and 2.4.x. This issue will affect any model that uses sub-iterations for calculations within a time step such as multiRegion cases, if the sub-iterations are significant.
TagsNo tags attached.

Activities

wyldckat

2015-07-18 21:37

updater   ~0005098

@davhar: Sorry, but I'm having trouble understanding your description. Can you please provide the test case (or test cases) and the output you get for 1.6 and 2.3.x/2.4.x, so that we can see what you're seeing?

Because from your description, I've got the feeling that what you're seeing is actually a bug that was in version 1.6.

wyldckat

2015-08-13 19:26

updater   ~0005238

@davhar: You mentioned that "A modified pitzDaily is available to demonstrate the issue". Please provide that test case you indicated you had, otherwise this issue will be closed in a few days as "unable to reproduce".

wyldckat

2015-09-12 13:32

updater   ~0005354

Closing as "unable to reproduce".

@davhar: If and when you can provide more details and a test case, please re-open this report!

Issue History

Date Modified Username Field Change
2015-07-07 15:53 user758 New Issue
2015-07-18 21:37 wyldckat Note Added: 0005098
2015-07-28 21:55 wyldckat Priority urgent => normal
2015-08-13 19:26 wyldckat Note Added: 0005238
2015-09-12 13:32 wyldckat Note Added: 0005354
2015-09-12 13:32 wyldckat Status new => closed
2015-09-12 13:32 wyldckat Assigned To => wyldckat
2015-09-12 13:32 wyldckat Resolution open => unable to reproduce