View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003444 | OpenFOAM | Feature | public | 2020-02-07 06:34 | 2020-02-09 18:58 |
Reporter | tnnandi | Assigned To | henry | ||
Priority | none | Severity | feature | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | GNU/Linux | OS | Ubuntu | OS Version | 15.04 |
Summary | 0003444: Identification of the porous region in powerLawLopesdaCosta porosity model | ||||
Description | The standard porosity models implemented in OpenFOAM, e.g DarcyForchheimer and powerLaw, identify the regions in the computational domain where the body force term has to be added using the cellZone supplied by the user. This offers a very convenient way to prescribe the porous regions in the domain. But, in the newly added "powerLawLopesdaCosta porosity model", instead of utilizing user-prescribed cellZones, the model explicitly identifies the cells in the porous region using a convoluted process (using information from surface files representing the top and bottom regions of the porous region, and generating cellZone while running the model). I'm not sure why this length process has been pursued for the powerLawLopesdaCosta porosity model, but there should be an option to simply use cellZones to prescribe the porous regions. | ||||
Tags | No tags attached. | ||||
|
Maybe, there's an option to not create a new cellZone if there's already an existing one (created by the user manually, corresponding to the else branch of if (zoneId == -1), but it still requires surface files corresponding to the top and bottom of the porous regions to run the model. |
|
Is the lengthy process only to allow the porosity surface area per unit volume parameter (Sigma) to be a function of height? |
|
The handling of the porous region in the powerLawLopesdaCosta was specified in detail by the company funding the implementation. We could extend this model to handle alternative porosity specification if you would be interested in funding the work. |
|
Pending funding. |
Date Modified | Username | Field | Change |
---|---|---|---|
2020-02-07 06:34 | tnnandi | New Issue | |
2020-02-07 06:37 | tnnandi | Note Added: 0011140 | |
2020-02-07 06:42 | tnnandi | Note Added: 0011141 | |
2020-02-07 08:42 | henry | Note Added: 0011143 | |
2020-02-07 08:43 | henry | Priority | high => none |
2020-02-07 08:43 | henry | Severity | major => feature |
2020-02-09 18:58 | henry | Assigned To | => henry |
2020-02-09 18:58 | henry | Status | new => closed |
2020-02-09 18:58 | henry | Resolution | open => no change required |
2020-02-09 18:58 | henry | Note Added: 0011165 |