Fault program

We generally do not cite unpublished field mapping, field notes, and other gray-literature reports that are not generally available to the public. The data presented in the compilation are extensively referenced using the standard USGS reference style, with the exception of attaching a unique number to each cited reference for convenience. This numeric identifier allows us to clearly cite multiple-same year publications for authors. This table includes the definitions of classes used in the compilation of Quaternary faults, liquefaction features, and deformation Crone and Wheeler, Although seismicity maps and earthquake catalogs show the past to years of felt and instrumental earthquakes, many faults in the United States have return times of thousands to tens of thousands of years for surface faulting events.

Clearly the short seismic record will not image all the active faults that exist. Thus, this collection of data on faults and folds that record ancient earthquakes will help augment the rather short felt and instrumental seismic record that is typical of the United States and other recently developed countries. The database is primarily a text-based collection of descriptive data that will serve a wide and varied audience. The search capabilities described below will allow the user to sort the data on a variety of fields geographic, structural, time of movement, slip rate, etc.

The basic strategy in classifying the data has been to create a variety of bins categories to characterize these potential seismic sources in terms of their activity rates. You can sort the data by time of most recent movement 4 inclusive categories or slip rate 4 exclusive categories. The database has two search forms.

The Quick Search form is very simple with only four search options available. Two options permit searches on Name and Number of a particular fault or fold. The other two options permit geographic searches by State and County. The Advanced Search form can be used to further limit the search results. The Advanced Search form allows queries on the above four parameters and on geographic options, paleoseismic characteristics, and structural characteristics.

The additional geographic search options are AMS sheet and physiographic province. The searchable paleoseismic characteristics include time of most recent prehistoric deformation, year of historic deformation, and slip-rate category. Searchable structural characteristics include length of fault or fault section, average strike of fault or fault section, sense of movement , and dip direction of the fault. Complete as few or many of the fields as you wish.

The narrower the search; the quicker the results will be available. If you expect that your search will result in a large number of results more than 40 , you can reduce the amount of time to obtain those results by limiting the number of results on each page at the bottom of the search form. There are three basic types of search fields: those with 1 pull-down menus, 2 text, and 3 numeric. The fields having pull-down menus provide all available options. Text fields like Name, County, and AMS sheet are not case sensitive and will search on partial words.

The numeric fields such as Number, Year of historic deformation, Length, and Average strike should only contain numeric expressions.

The Number field will not find specific sections a, b, c, etc. The Year of historic deformation requires a four-digit year in each field; use values that would encompass the historical record such as and to search for all entries in this field.

The length and average-strike searches will yield all records with inclusive values and show all sections of a fault if one of those sections has the desired value. You should turn off this feature prior to conducting searches that require entering characters or digits. Science Explorer. Mission Areas. Unified Interior Regions. Science Centers. Frequently Asked Questions. Educational Resources. For example, you could use GNU's well-known debugger GDB to view the backtrace of a core file dumped by your program; whenever programs segfault, they usually dump the content of their section of the memory at the time of the crash into a core file.

Start your debugger with the command gdb core , and then use the backtrace command to see where the program was when it crashed. This simple trick will allow you to focus on that part of the code. If using backtrace on the core g file doesn't find the problem, you might have to run the program under debugger control, and then step through the code one function, or one source code line, at a time.

To do this, you will need to compile your code without optimization, and with the -g flag, so information about source code lines will be embedded in the executable file. This is document aqsj in the Knowledge Base. Last modified on Skip to: content search login. Knowledge Base Toggle local menu Menus About the team.

Knowledge Base Search. Log in. When troubleshooting segmentation errors, or testing programs to avoid these errors, there may be a need to intentionally cause a segmentation violation to investigate its impact. Most operating systems make it possible to handle SIGSEGV in such a way that they will allow the program to run even after the segmentation error occurs, to allow for investigation and logging.

It is fairly common for a container to fail due to a segmentation violation. The container then terminates, Kubernetes detects this, and may attempt to restart it depending on the pod configuration.

This can indicate:. The process above can help you resolve straightforward SIGSEGV errors, but in many cases troubleshooting can become very complex and require non-linear investigation involving multiple components.

As a Kubernetes administrator or user, pods or containers terminating unexpectedly can be a pain, and can result in severe production issues. Container termination can be a result of multiple issues in different components and can be difficult to diagnose. The troubleshooting process in Kubernetes is complex and, without the right tools, can be stressful, ineffective and time-consuming.

This is the reason why we created Komodor, a tool that helps dev and ops teams stop wasting their precious time looking for needles in hay stacks every time things go wrong. If you are interested in checking out Komodor, use this link to sign up for a Free Trial.

Best practices for migrating to Kubernetes, from personal experience of working with it daily for the last four years This post will outline the 5 quick wins you should make a point of implementing to make your Kubernetes system easier to troubleshoot Just six months after emerging from stealth Komodor has just been recognized as a Cool Vendor by Gartner!

This website uses cookies. By continuing to browse, you agree to our Privacy Policy. In addition, the following may take place: A core file is typically generated to enable debugging SIGSEGV signals may logged in more detail for troubleshooting and security purposes The operating system may perform platform-specific operations The operating system may allow the process itself to handle the segmentation violation SIGSEGV is a common cause for container termination in Kubernetes.

Simplify k8s troubleshooting Get the context you need to troubleshoot efficiently and independently. Try Komodor for Free.