aidanstansberry

It appears that when assigning the hydraulic properties we incorrectly assume that there is only one fracture defined in the file. This will only be a problem when using add_user_fract_from_file()....

There is a straightforward workaround on your end while we work on a fix on our end. If the user fracture is rejected during network generation, we have already stored...

It looks like the same issue occurs when we remove isolated fractures from the domain. If you just want to visualize the DFN add these flags to the script DFN.params['keepIsolatedFractures']['value']...