Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with defining different aperture values for deterministic and stochastic fractures #24

Open
nick-izu opened this issue Apr 25, 2022 · 1 comment

Comments

@nick-izu
Copy link

Hello Everyone,

I am working to generate deterministic fractures and stochastic fractures in the same domain. So the problem is that I can't seem to understand how to define the apertures for the deterministic fractures separately from that of stochastic fractures. Is there a way to assign specific transmissivities/apertures to deterministic fractures in the dfnWorks code?

Also, I understand that the gen_4_user_ellipses.dat file can be used to generate stochastic fractures and assign corresponding properties. So if I select an aperture option from the list below, will this option be used for both the deterministic fractures in the define_4_user_ellipses.dat and the stochastic fractures.

Aperture [m]
Mandatory parameter, and can be specified in several ways:

  • 1)meanAperture and stdAperture for using LogNormal distribution.
  • 2)apertureFromTransmissivity, first transmissivity is defined, and then,
    using a cubic law, the aperture is calculated;
  • 3)constantAperture, all fractures, regardless of their size, will have
    the same aperture value;
  • 4)lengthCorrelatedAperture, aperture is defined as a function of fracture size

Thanks!

@hymanjd
Copy link
Collaborator

hymanjd commented May 19, 2022

We are going to modify how apertures are defined in a future release. All fracture family properties will be done in python.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants