Fault Files in this area for this model: Order from west to east 1 BX - Boxcar (barely touches west side of mesh) 2 BU - Buteo (full NS fault passing near U20) 3 SPMSZ - Southern Pahute Mesa Structural zone (EW cutting through SW corner) 4 WG - West Greeley (full NS, east of Buteo) 5 EG - East Greeley (full NS, east side of mesh) 6 ETCSZ - East Thirsty Canyon (EW dies out west of WG fault) These are nearby but do not intersect the mesh area: 7 RCSZ - Ribbon Cliff (dies out more than 100m west of domain) 8 SCSZW - Silent Canyon West (more than 500m north of domain) Interplated fault blocks for 50x50 grid resolution: 99 "below_WestBoxcar_S" FaultFile "fault/WB.2grd" 104 "below_WestBoxcar" FaultFile "fault/WB.2grd" 109 "above_Buteo_M" FaultFile "fault/BU.2grd" 110 "below_Buteo_M" FaultFile "fault/BU.2grd 111 "above_Buteo_S" FaultFile "fault/BU.2grd 112 "below_Buteo_S FaultFile "fault/BU.2grd" 116 "above_SCSZW_W" FaultFile "fault/SCSZW.2grd" 118 "above_SCSZW_MW" FaultFile "fault/SCSZW.2grd" 133 "above_EastGreeley_M" FaultFile "fault/EG.2grd" 134 "below_EastGreeley_M" FaultFile "fault/EG.2grd" See images in /images directory See names in fault_acronyms.xlsx Fault ETCSZ had problems with top and side truncation and took further work. First a different plan to triangulate was needed, it worked to connect and interpolate with y=0 instead of z=0 as this fault is very nearly vertical. The fault is truncated by WG and bottom of Calico Hills. Fault was refined along these sides to minimize the jagged effect of removing elements. A smooth edge version could be created with some work, but for these grids it is not needed. Tim Vogt sent surface files that represent the base of CH (a combination of the top of IA and the top of CFCU) /scratch/nts/ev_models/HFM_PM_20140305/fault -rw-r--r-- 1 tamiller sft 1089795 Apr 1 13:18 ../CFCU.surf.2grd -rw-r--r-- 1 tamiller sft 1089791 Apr 1 13:19 ../IA.surf.2grd Final fault surfaces are created and written in /scratch/nts/ev_models/HFM_PM_20140305/fault/tiploop_to_surf All fault related images are in /scratch/nts/ev_models/HFM_PM_20140305/fault/images -------------------------------------------------------------------------- 2012 fault surfaces: /scratch/nts/gable/grid_gen/ascem/pahute_mesa/data/ver01/CHZCM_Lavas4LANL 1 boxcar_wdcv2.dat / boxcar_wdcv2.tiploop.dat - Boxcar fault surface and tiploop polygon 2 eastgreeley_wdcv2.dat / eastgreeley_wdcv2.tiploop.dat - East Greeley fault surface and tiploop polygon 3 etcsz_wdc.dat / etcsz_wdc.tiploop.dat - East Thirsty Canyon Structural Zone fault surface and tiploop polygon 4 ribcliffwdfull.dat / ribcliffwdfull.tiploop.dat - Ribbon Cliff Structural Zone fault surface and tiploop polygon 5 westgreeley_wdc.dat / westgreeley_wdc.tiploop.dat - West Greeley fault surface and tiploop polygon Files created and exported by Kevin Day 6/19/2012 Kevin.Day@nv.doe.gov Files are exported from chzcm_lavas.100x100x4.z10.unsliced.faces, an Earthvision model representing conceptualized distribution of lava flow aquifers within the Calico Hills Hydrostratigraphic Unit of the Pahute Mesa Phase I Hydrostratigraphic Framework Model. This export was produced within a polygon centered on well U20_WW, constrained on the top and bottom by the Calico Hills HSU and by UTM Zone 11 NAD 27 coordinates: X Y Minimum 548500 4119800 Maximum 554000 4125500 Range 5500 5700 Dimensions 111 115 Grid spacing 50 50 -------------------------------------------------------------------------- Begin forwarded message: From: "Vogt, Tim (CONTR)" Date: April 1, 2014 10:47:39 AM MDT To: "Miller, Terry A" Subject: RE: ETCSZ fault with respect to geology Terry, Read the second thought first. First thought: There is a grid for each fault block. The fault is the seam where all of the fault blocks come together so there could be a step of some kind at the fault. The list below I believe is a list of the bordering fault blocks. (I might have an extra one because there is a different number north and south of the fault). In a perfect world one could go to the ‘horizon table’ information and find the polygons that are used for that grid for each fault block and thus blend all grids together. south of fault: above_EastGreeley_M_CH.2grd" above_ScrughamPeak_MN below_EastGreeley_M.2grd" below_RRSVM below_ScrughamPeak_MN below_ScrughamPeak_M north of fault: above_SCSZW_W above_SCSZW_MW above_ScrughamPeak_N below_ScrughamPeak_N above_Rickey Second thought: I’ve attached two files to this email that represent the top of the units needed. I wasn’t sure these files had been prepared until I just now looked. I think this may be easiest. In theory these two files are the output from the horizon table process. Try the second thought first. Tim Begin forwarded message: From: "Drellack, Sigmund" Date: April 1, 2014 8:04:08 AM MDT To: "Miller, Terry A" , "Vogt, Tim (CONTR)" Cc: "Coen, Kay L" , "Harp, Dylan R" , "Viswanathan, Hari S" , "Gable, Carl Walter" , "Kwicklis, Edward M" Subject: RE: ETCSZ fault with respect to geology Terry, Just to clarify: The top of the ETCSZ is the Base of the CHZCM. Smoothing makes sense. Sig Drellack National Security Technologies, LLC Contractor to the United States Department of Energy Mail Address Mail Stop NLV 082 P.O. Box 98521 Las Vegas, NV 89193-8521 Phone: 702-295-0170 FAX: 702-295-1313 E-mail: drellasl@nv.doe.gov From: Miller, Terry A [mailto:tamiller@lanl.gov] Sent: Tuesday, April 01, 2014 6:29 AM To: Vogt, Tim (CONTR); Drellack, Sigmund Cc: Coen, Kay L; Harp, Dylan R; Viswanathan, Hari S; Gable, Carl Walter; Kwicklis, Edward M Subject: Re: ETCSZ fault with respect to geology Thank you both. I will adjust the surface representing ETCSZ fault so that it has a smooth top set at a height equal to the CHZCM (Calico Hills) surface. I will send revised fault surface image when I am done. Terry On Mar 31, 2014, at 3:12 PM, Vogt, Tim (CONTR) wrote: Sig and Terry, Two informal images looking northish, along the entire length of the ETCSZ. The gray shows the ‘active fault’ area. The other is just so you can see the units more clearly. The top of the active fault does track the top of the CFCU (pink) reasonably closely. Sig – When queried the dip of the fault seems to be mostly between 88 and 89 degrees. if this does not fit your image of the way the top of the active area should be I’m sure it can be adjusted. Terry – if I can help you cut this along the top of the units or something let me know. Tim From: Drellack, Sigmund Sent: Monday, March 31, 2014 2:04 PM To: Miller, Terry A; Vogt, Tim (CONTR) Cc: Harp, Dylan R Subject: RE: ETCSZ fault with respect to geology Terry, The ETCSZ is one of several caldera structural margins to the Silent Canyon caldera complex (SCCC). The SCCC is comprised of an older Grouse Canyon caldera and the younger Area 20 caldera. The W-E ETCSZ is the southern boundary for the Grouse Canyon Inner Collapse (collapse down on the north side) and the northern boundary for the Area 20 outer Collapse (down on the south side). As such we conceptualized this structure as being vertical. But, the model does not allow truly vertical structures, so in the HFM it is not perfectly vertical. The top of the ETCSZ should be the top of the Inlet Aquifer (IA) HSU on the south, and the top of the Crater Flat confining unit (CFCU) on the north. The top of the ETCSZ can also be defined as the base of the Calico Hills HSU(s) which overlies the IA and the CFCU. I hope this helps. Let me know if you have more questions. Sig Drellack National Security Technologies, LLC Contractor to the United States Department of Energy Mail Address Mail Stop NLV 082 P.O. Box 98521 Las Vegas, NV 89193-8521 Phone: 702-295-0170 FAX: 702-295-1313 E-mail: drellasl@nv.doe.gov Begin forwarded message: From: "Vogt, Tim (CONTR)" Date: March 19, 2014 10:17:03 AM MDT To: "Miller, Terry A" Cc: "Kwicklis, Edward M" , "Birdsell, Kay H" , "Harp, Dylan R" Subject: RE: faults for U20 grids Terry, The small fault crossing Buteo within the box you defined earlier is SPMSZ. You are correct in that there are many additional faults throughout this Phase II model. You are correct in that the faces files are good tools for viewing – slicing etc. When assigning grid nodes to an irregular – nonorthogonal surface there is an “ev_dist2surf” routine that calculates the distance of points to that surface. That might help you get to where you want to be. Thanks for the additional background. Tim From: Miller, Terry A [mailto:tamiller@lanl.gov] Sent: Wednesday, March 19, 2014 6:42 AM To: Vogt, Tim (CONTR) Cc: Kwicklis, Edward M; Birdsell, Kay H; Harp, Dylan R Subject: Re: faults for U20 grids Thank you Tim, This helps very much. I will take a look at what you sent me via Kay when she has it. I am not very familiar with the .faces files, so be patient. They look handy for viewing. Looking at your images (below), I think I have ETCSZ clipped correctly. I think I have all the faults, except that small one crossing Buteo, can you tell me what that is? Is it RibCliff? It appears that faults in this area have changed quite a bit since our 2012 U20 models. Buteo did not exist in those and East Greeley was very short, stopping at ETCSZ. I am coloring uniform grids located around U-20WW. The colors represent HFM material zones and the intersection location of area faults. In these models, fault cells have properties different than HFM zone material cells. Ed Kwicklis and others were looking over my shoulder and are surprised at the added level of detail and changes in this area. I do not know what your time is like, but it would be nice to have a quick summary from your point of view of changes in this area. Here is the information I have from the 2012 model surfaces: --------------------------------- Files created and exported by Kevin Day 6/19/2012 Kevin.Day@nv.doe.gov Files are exported from chzcm_lavas.100x100x4.z10.unsliced.faces, an Earthvision model representing conceptualized distribution of lava flow aquifers within the Calico Hills Hydrostratigraphic Unit of the Pahute Mesa Phase I Hydrostratigraphic Framework Model. This export was produced within a polygon centered on well U20_WW, constrained on the top and bottom by the Calico Hills HSU and by UTM Zone 11 NAD 27 coordinates: X Y Minimum 548500 4119800 Maximum 554000 4125500 Range 5500 5700 Dimensions 111 115 Grid spacing 50 50 boxcar_wdcv2.dat / boxcar_wdcv2.tiploop.dat - Boxcar fault surface and tiploop polygon eastgreeley_wdcv2.dat / eastgreeley_wdcv2.tiploop.dat - East Greeley fault surface and tiploop polygon etcsz_wdc.dat / etcsz_wdc.tiploop.dat - East Thirsty Canyon Structural Zone fault surface and tiploop polygon ribcliffwdfull.dat / ribcliffwdfull.tiploop.dat- Ribbon Cliff Structural Zone fault surface and tiploop polygon westgreeley_wdc.dat / westgreeley_wdc.tiploop.dat - West Greeley fault surface and tiploop polygon --------------------------------- Terry On Mar 18, 2014, at 3:35 PM, Vogt, Tim (CONTR) wrote: Terry, The gold fault is Buteo. In a perfect geologic world it often makes sense that faults are truncated by other structures. In the modeling world these polygons are very important in defining the presentation of, and truncation of, and probably the calculation of offsets. I’ve enclosed an image that shows the details of this area. The grayish surface (mottled with purple) in the middle is the ‘active’ portion of the ETCSZ fault. Where that surface shows the colors of the fault blocks the fault is not ‘active’ or at least there is not offset across that surface. The image is created using the *.fb.unsliced.faces file. However the same effect can be created by using the regular faces file / coloring by fault block / and turning off some of the fault blocks. Hope this helps and don’t hesitate to ask if I can help. I’d prefer you were most efficient in getting what you need too. I know you are using tiploops etc . Are you creating a mesh and defining the regions affected by each fault and unit? Tim Begin forwarded message: From: "Vogt, Tim (CONTR)" Date: March 14, 2014 2:32:43 PM MDT To: "Miller, Terry A" Subject: RE: fault names Terry, Attached is a table with the correlations and acronyms. Let me know if you need more. Tim From: Vogt, Tim (CONTR) Sent: Friday, March 14, 2014 12:03 PM To: 'Miller, Terry A' Subject: RE: fault names Terry, I think the answer to your first question is included in the .seq file. See example below. For every FaultBlock section there is one Fault “xxx” and one FaultFile “yyy”. Is that the relationship you are looking for? FaultBlock "RMCSM" { Fault "RMCSM" FaultFile "fault/ATCSM_RMCSM_margin.2grd" BoundingPolygon "fault/RMCSM.ply" AboveBlock "M14" BelowBlock "BMCSM" The answer when you start with blocks may be achievable but not quite so straight forward. Try the seq file. There are still many acronyms included in the ‘real’ names. I’ll put together a list after sending this to you. Let me know if this does not answer your question. Tim TO TIM >>> This might be a better way to figure out which fault surfaces I need. I exported attributes on to my mesh, these are the blocks in this mesh. Can you give me a list of which faults are relevant given this list? 99 "below_WestBoxcar_S" 104 "below_WestBoxcar" 109 "above_Buteo_M" 110 "below_Buteo_M" 111 "above_Buteo_S" 112 "below_Buteo_S" 116 "above_SCSZW_W" 118 "above_SCSZW_MW" 133 "above_EastGreeley_M" 134 "below_EastGreeley_M" Terry On Mar 14, 2014, at 12:22 PM, wrote: Hi Tim, I hope this is a quick one for you. I need to know which faults are represented by which file names. I figured out West Greeley is WG.2grd These are names from 2012, what are their file names for EV? boxcar wdcv2 east greeley etcsz ribcliffwdfull Previous work in 2012 /scratch/nts/gable/grid_gen/ascem/pahute_mesa/data/ver01/CHZCM_Lavas4LANL/tiploop_to_surf