View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004019 | OpenFOAM | Bug | public | 2023-10-03 12:47 | 2023-10-03 20:19 |
| Reporter | joegi | Assigned To | henry | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 11 | ||||
| Summary | 0004019: deactivate fvConstraints using Function1 | ||||
| Description | I don't know if this is a proper bug (small in any case) or if I misunderstood how Function1 works. I have a fvConstraint in my domain (fixed temperature), and I want it active only for 1 second. So, I am using a time-varying temperature as follows, mode uniform; temperature table ( (0 1000) (1 1000) ); So my logic dictates that this constraint will deactivate after 1 second, but it remains always active. Let me know if my logic is correct or flawed. | ||||
| Steps To Reproduce | Just add a time-varying uniform temperature constraint to any case (with temperature), and you will be able to reproduce this issue | ||||
| Tags | No tags attached. | ||||
|
|
https://cpp.openfoam.org/v11/classFoam_1_1Function1s_1_1Table.html#details |
|
|
To give you more context, you can try the tutorial multicomponentFluid/simplifiedSiwek, it does pretty much what I am trying to do. In the fvConstraints file, the keywords timeStart and duration are used, but I think they are deprecated. The way to do it now is by using Function1, if I am not mistaken, but it does not work, the constraint is always on. mode uniform; temperature table ( (0.1 2000) (0.5 2000) ); |
|
|
In the link I provided, there is documentation on how to use the Table Function1... there it mentions the option for "outOfBounds" and the "clamp" option... Although from the comments here: https://github.com/OpenFOAM/OpenFOAM-11/blob/master/src/OpenFOAM/primitives/functions/Function1/Table/tableBase.H#L59 - it does seem that the default should both warn and clamp... But I see what you mean. I was expecting that one of the "outOfBounds" modes would help solve the issue. And indeed, the "timeStart" and "duration" keywords don't seem to be used, at least with a quick overview through the CPP guide. So what is missing is either: 1. To be able to turn off the constraint, based on the "outOfBounds" mode of Function1. 2. Or have the "timeStart" and "duration" keywords (or similar) operational once again. |
|
|
//- Fraction of the constraint to apply. Facilitates ramping, or // pulsing, or deactivation after a time. Should take a value between // 0 and 1. Defaults to 1 (i.e., apply all of the constraint). autoPtr<Function1<scalar>> fraction_; |
|
|
User support request |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-10-03 12:47 | joegi | New Issue | |
| 2023-10-03 15:52 | wyldckat | Note Added: 0013126 | |
| 2023-10-03 16:16 | joegi | Note Added: 0013127 | |
| 2023-10-03 16:45 | wyldckat | Note Added: 0013128 | |
| 2023-10-03 20:03 | henry | Assigned To | => henry |
| 2023-10-03 20:03 | henry | Status | new => closed |
| 2023-10-03 20:03 | henry | Resolution | open => suspended |
| 2023-10-03 20:18 | henry | Note Added: 0013131 | |
| 2023-10-03 20:19 | henry | Resolution | suspended => no change required |
| 2023-10-03 20:19 | henry | Note Added: 0013132 |
