XSection allows the user to display any variable present in cross section. Perform fault, stratigraphic, and structural analysis in large and complex datasets.Graphically edit/ fine tune the formations and fault picks from the point clouds in cross sections.Extract and visualize subsurface orientations directly from the cross sections, core images and log files.Data AnalysisĪ comprehensive set of visualization and analysis tool for any kind of oriented data. References ManagementĬreate effective correspondences between all the references of your well, such as Measured Depth (MD), True Vertical Depth (TVD) for a better understanding of the deviation survey data. In addition you can print the cross section directly from XSection or by exporting as a metafile for display on a montage in GeoAtlas. XSection can integrate many types of data including log data, point data, seismic and image files, and supports common formats such as LAS/LBS. Pictures to add core photographs, index title blocks, spreadsheets, etc.Arrows to point to features within the wellbore.Rectangle and Polygons to display intra-formational lithology, oil legs, etc.Identify, annotate and/or explain features on the cross section to enhance the understanding of the overall picture. Index map layers showing the location of the cross section in GeoAtlas.Customizable lithology area fills and patterns.DST and Core data from the WellBase data files.Variety of data in well headers/footers.A "type" vector or raster log curve and use it to graphically correlate formation tops in other wells. Deviated wells and logs with measured depth (MD) or true vertical depth (TVD).Faults and IsoMap layers on the section.Logs with vector log data and raster images on the same cross section.XSection has a robust displaying capacity that allows the user to display: Graphically edit formation and fault picks that are saved as data, which can be used to define consistent inter-well structural and stratigraphic interpretation for the project. # draw MMIs and interconnects and automatically get NoFill layers:Ī less surgical alternative is to use the cell’s bounding box and fill it with the NoFill layer (not shown in the example above).Integration with LMKR GeoGraphix applicationsĮffectively define and analyze the cross sections in a smooth and steady environment using data from WellBase, GVERSE Petrophysics, ZoneManager, IsoMap and GVERSE Geophysics. ow(layer='NoFill', grow=grow).put(0) # add NoFill layer based on original Polygon. Poly = nd.Polygon(points=bb_body, layer='layer1') # create a building block (cell) from Polygon points and add the NoFill layer Ic = nd.interconnects.Interconnect(xs="myXS", width=2.0, radius=10.0) # create interconnect Nd.add_layer2xsection(xsection='myXS', layer='NoFill', growx=grow) # add a NoFill layer Nd.add_layer2xsection(xsection='myXS', layer='layer1') Nd.add_layer(name='NoFill', layer=2, accuracy=0.1) # NoFill can be course, here 0.1 um resolution The above solutions look like this when applied to the MMI polygon tutorial: import nazca as nd In another case, when working directly with Polygon objects, you can grow the Polygon (with pyclipper installed) and redirect the result to the NoFill layer. Whenever you use that interconnect your get the NoFill layer. You can add that to your xsection definition and use interconnects. Is there any way to define “xsections” for the instance of the custom building blocks? Or, is there a way I can make a cell instead of the custom building block that would act in the same way as Nazca-design built-in cells?Ī “NoFill” layer to protect from tiling is a specific layer. However, when working with many built-in cells and custom building blocks to build the cell this would be very impractical. This can be done manually by working with polygons and layers. Here, I want to have these “xsections” around both straight section “strt” and the AWG building block. The simple device consists of a straight section “strt” and the AWG building block. The foundry adds filling patterns to achieve the desired density of the deposited material, and I don’t want to have filling patterns too close to my waveguides.Īn example of a custom building block is an apodized waveguide grating (AWG) with a complicated free-form shape. Regarding “xsections” I use them to define the distance (guide) around my device where the foundry will not add filling patterns. In my design, I use together Nazca-design built-in cells (strt, bend, taper) and custom building blocks.
0 Comments
Leave a Reply. |