I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
In addition to what Wenje said: you don’t have to give a specific process to the mesh file. If non is given, every process will be calculated on the whole mesh. Then, you can also use the keyword $DEACTIVATED_SUBDOMAIN, if you don’t want every process to be calculated.
I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
On Thursday, December 11, 2014 1:17:48 AM UTC-5, Marc Walther wrote:
In addition to what Wenje said: you don’t have to give a specific process to the mesh file. If non is given, every process will be calculated on the whole mesh. Then, you can also use the keyword $DEACTIVATED_SUBDOMAIN, if you don’t want every process to be calculated.
I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
Thanks,
Xuan
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ogs-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
On Thursday, December 11, 2014 1:17:48 AM UTC-5, Marc Walther wrote:
In addition to what Wenje said: you don’t have to give a specific process to the mesh file. If non is given, every process will be calculated on the whole mesh. Then, you can also use the keyword $DEACTIVATED_SUBDOMAIN, if you don’t want every process to be calculated.
I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
Thanks,
Xuan
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ogs-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
Hi Marc,
I still could not go through the pcs file after the correction of typo. The ogs still paused at the same step.
Thanks,
Xuan #PROCESS
$PCS_TYPE
MASS_TRANSPORT
$NUM_TYPE
NEW
$PRIMARY_VARIABLE
CONCENTRATION1
#PROCESS
$PCS_TYPE
MASS_TRANSPORT
$DEACTIVATED_SUBDOMAIN
1 ;number of deactivated
2 ;material group index #STOP
···
On Thursday, December 11, 2014 10:46:09 AM UTC-5, Marc Walther wrote:
You have a typo in the mass transport pcs: it is CONCENTRATION1.
In addition to what Wenje said: you don’t have to give a specific process to the mesh file. If non is given, every process will be calculated on the whole mesh. Then, you can also use the keyword $DEACTIVATED_SUBDOMAIN, if you don’t want every process to be calculated.
I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
Thanks,
Xuan
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ogs-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
Hi Marc,
I still could not go through the pcs file after the correction of typo. The ogs still paused at the same step.
Thanks,
Xuan #PROCESS
$PCS_TYPE
MASS_TRANSPORT
$NUM_TYPE
NEW
$PRIMARY_VARIABLE
CONCENTRATION1
#PROCESS
$PCS_TYPE
MASS_TRANSPORT
$DEACTIVATED_SUBDOMAIN
1 ;number of deactivated
2 ;material group index #STOP
On Thursday, December 11, 2014 10:46:09 AM UTC-5, Marc Walther wrote:
You have a typo in the mass transport pcs: it is CONCENTRATION1.
On Thursday, December 11, 2014 1:17:48 AM UTC-5, Marc Walther wrote:
In addition to what Wenje said: you don’t have to give a specific process to the mesh file. If non is given, every process will be calculated on the whole mesh. Then, you can also use the keyword $DEACTIVATED_SUBDOMAIN, if you don’t want every process to be calculated.
I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
Thanks,
Xuan
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ogs-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
Hi Marc,
I still could not go through the pcs file after the correction of typo. The ogs still paused at the same step.
Thanks,
Xuan #PROCESS
$PCS_TYPE
MASS_TRANSPORT
$NUM_TYPE
NEW
$PRIMARY_VARIABLE
CONCENTRATION1
#PROCESS
$PCS_TYPE
MASS_TRANSPORT
$DEACTIVATED_SUBDOMAIN
1 ;number of deactivated
2 ;material group index #STOP
On Thursday, December 11, 2014 10:46:09 AM UTC-5, Marc Walther wrote:
You have a typo in the mass transport pcs: it is CONCENTRATION1.
In addition to what Wenje said: you don’t have to give a specific process to the mesh file. If non is given, every process will be calculated on the whole mesh. Then, you can also use the keyword $DEACTIVATED_SUBDOMAIN, if you don’t want every process to be calculated.
I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
Thanks,
Xuan
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ogs-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
Hi Marc,
I still could not go through the pcs file after the correction of typo. The ogs still paused at the same step.
Thanks,
Xuan #PROCESS
$PCS_TYPE
MASS_TRANSPORT
$NUM_TYPE
NEW
$PRIMARY_VARIABLE
CONCENTRATION1
#PROCESS
$PCS_TYPE
MASS_TRANSPORT
$DEACTIVATED_SUBDOMAIN
1 ;number of deactivated
2 ;material group index #STOP
On Thursday, December 11, 2014 10:46:09 AM UTC-5, Marc Walther wrote:
You have a typo in the mass transport pcs: it is CONCENTRATION1.
On Thursday, December 11, 2014 1:17:48 AM UTC-5, Marc Walther wrote:
In addition to what Wenje said: you don’t have to give a specific process to the mesh file. If non is given, every process will be calculated on the whole mesh. Then, you can also use the keyword $DEACTIVATED_SUBDOMAIN, if you don’t want every process to be calculated.
I have a question on variable density flow. So in the msh, we define the flow type at model domain: Richards_Flow, Groundwater_Flow. Where to define the MASS_TRANSPORT? Or is MASS_TRANSPORT will happen across the whole domain? Can we define a part of the domain has the MASS_TRANSPORT calculation?
Thanks,
Xuan
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ogs-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
Hello OGS community,
I model unsaturated RICHARDS_Flow within a 2D domain and OGS crashes when assembling the equation system (please see attached image for a screenshot of the executable). First I thought it would be a solver issue, but varying the solvers didn't make it.
I model unsaturated RICHARDS_Flow within a 2D domain and OGS crashes when assembling the equation system (please see attached image for a screenshot of the executable). First I thought it would be a solver issue, but varying the solvers didn’t make it.
Does anyone have experience with such a problem?
Cheers
Aaron
–
You received this message because you are subscribed to the Google Groups “ogs-users” group.
Check your mesh file. There are zero volume elements in the mesh.
···
On 12/16/2014 03:18 PM, Aaron Peche wrote:
Hello OGS community,
I model unsaturated RICHARDS_Flow within a 2D domain and OGS crashes when assembling the equation system (please see attached image for a screenshot of the executable). First I thought it would be a solver issue, but varying the solvers didn't make it.
Check your mesh file. There are zero volume elements in the mesh.
On 12/16/2014 03:18 PM, Aaron Peche wrote:
Hello OGS community,
I model unsaturated RICHARDS_Flow within a 2D domain and OGS crashes when assembling the equation system (please see attached image for a screenshot of the executable). First I thought it would be a solver issue, but varying the solvers didn't make it.
Does anyone have experience with such a problem?
Cheers
Aaron
--
Aaron Peche (M.Sc.)
PhD Student
Institute of Fluid Mechanics and Environmental Physics
Leibniz-Universität Hannover