Gautam,
Where is the linkage that assigns temperature on a cell by cell basis from a dataset? I see time series being supported in PatchUpdateCouplerAuxVars(), but not datasets.
Glenn
No, I am not concerned with the time varying component. I just wanted to ensure that the approach is sufficiently general for TH, and it is.
Romain,
Reading large datasets from ASCII files does not scale well with large parallel jobs. It is better to train/force everyone to use more scalable approaches such as HDF5.
Glenn
Romain,
Gautam and I have discussed this. You have uncovered an issue in our implementation. For the time being, please create a new HDF5 file where you have two datasets at the top of the file (i.e. no group). One named ‘Cell Ids’ with a list of all the cell ids in the domain (1-N) and another named ‘Temperature’ with the value of temperature at each grid cell. Then, try running it again. Send the new dataset file to pflotr...@googlegroups.com if that does not work.
I have created a new issue on the issue tracker where we can hopefully refactor the datasets to avoid this confusion in the future. We need something that forces the users to declare what type of dataset they are using, but we need to define the approach.
Glenn
Glenn,
For the time being, please create a new HDF5 file where you have two datasets at the top of the file (i.e. no group). One named ‘Cell Ids’ with a list of all the cell ids in the domain (1-N) and another named ‘Temperature’ with the value of temperature at each grid cell. Then, try running it again. Send the new dataset file to pflotr...@googlegroups.com if that does not work.
Thanks. I will take this further when I have a bit more time and iterate with you directly on it. Having users send test cases that run fast (i.e. <= 6 seconds) greatly improves our regression suite.
Glenn
From: pflotra...@googlegroups.com [mailto:pflotra...@googlegroups.com] On Behalf Of Romain P.
Sent: Wednesday, October 30, 2013 7:58 AM
To: pflotra...@googlegroups.com
Romain,
We discontinued the legacy support for the GRID,BOUNDS card. The BOUNDS card now is formatted like the COORDINATES card in a REGION:
BOUNDS
xmin ymin zmin
xmax ymax zmax
/
Easy fix. Change
GRID
TYPE structured
ORIGIN 0.d0 0.d0 0.d0
NXYZ 1 1 100
BOUNDS
0.d0 1.d0
0.d0 1.d0
0.d0 100.d0
/
END
To
GRID
TYPE structured
ORIGIN 0.d0 0.d0 0.d0
NXYZ 1 1 100
BOUNDS
0.d0 0.d0 0.d0
1.d0 1.d0 100.d0
/
END
Let us know if that solves the problem.
Glenn
From: pflotra...@googlegroups.com [mailto:pflotra...@googlegroups.com] On Behalf Of Romain P.
Sent: Wednesday, January 08, 2014 7:46 AM
To: pflotra...@googlegroups.com
No worries Romain.
Glenn
From: pflotra...@googlegroups.com [mailto:pflotra...@googlegroups.com] On Behalf Of Romain P.
Sent: Wednesday, January 08, 2014 10:23 AM
To: pflotra...@googlegroups.com
Romain,
According to the code in patch.F90:PatchUpdateCouplerAuxVarsTH, you should be able to assign the following
CONDITION
TYPE
PRESSURE hydrostatic
TEMPERATURE heterogeneous_dirichlet
/
…
/
and it should work. However, I believe that I see a bug under the pressure conditional where the temperature dataset is being assigned to the PRESSURE_DOF:
case(HET_DIRICHLET)
call PatchUpdateHetroCouplerAuxVars(patch,coupler, &
flow_condition%temperature%dataset, &
num_connections,TH_PRESSURE_DOF,option)
Shouldn’t it be flow_condition%pressure%dataset, not %temperature% that is applied? I believe that this has nothing to do with your question/statement, but Gautam should verify.
Glenn
From: pflotra...@googlegroups.com [mailto:pflotra...@googlegroups.com] On Behalf Of Romain P.
Sent: Thursday, January 09, 2014 4:55 AM
To: pflotra...@googlegroups.com